Myles Agnew

Cyber Security Specialist

Securing the
digital frontier
one layer at a time.

Practical cloud and web security perspectives for people building resilient systems — from architecture patterns and web hardening to incident response readiness and secure infrastructure automation.

myles@agnew ~ $ whoami
cat profile.json
"name": "Myles Agnew"
"role": "Cyber Security Specialist"
"focus": ["Cloud","Data","Security"]
"location": "Australia 🇦🇺"
"coffee": "always"

status --live
✔ Open to coffee chats

18+
Years in Tech
3
Cloud Platforms
22
Open Source Repos
Coffees Consumed

Security through
experience

I'm Myles — a cyber security practitioner who's spent years on a journey down the rabbit hole of practical, real-world security. I believe in reducing fear and complexity for teams, builders, and stakeholders, not adding to it.

My approach is grounded in the realities of modern infrastructure: cloud-first environments, dynamic data pipelines, and the ever-expanding attack surface that comes with them. I've spoken at WordCamp Brisbane, built open-source tooling, and been in the trenches with AWS, Azure, GCP, Cloudflare, and everything in between.

When I'm not hardening infrastructure, you'll find me surfing, snowboarding, mountain biking, running, or on the back of a motorbike. Dad. Tech geek. Coffee addict. In that order.

Surfing Snowboarding Mountain Biking Running Motorcycling Podcasting WordPress Coffee Arduino Raspberry Pi
Cloud Platforms
AWS Azure Google Cloud DigitalOcean Cloudflare Linode
Security Tooling
Splunk Pi-hole Bitwarden Velociraptor Cisco Ubiquiti
Infrastructure & DevOps
Docker Kubernetes Terraform Ansible Nginx Apache
Observability
Grafana Prometheus Elasticsearch Redis
Languages & Scripting
PowerShell Python Bash HTML5
Data
MySQL MariaDB DynamoDB Confluence

Cyber security focus areas

🛡️

Security Architecture

Threat modelling, secure architecture patterns, and hardening frameworks for modern stacks. Practical thinking that balances risk, usability, and business context.

☁️

Cloud Security

Securing workloads across AWS, Azure, and GCP. IAM policies, network security groups, encryption strategies, and compliance posture.

🔍

Incident Response & SIEM

Splunk-driven detection, Velociraptor endpoint forensics, and building playbooks that cut response time when it matters most.

⚙️

Infrastructure as Code

Terraform, Ansible, Docker, and Kubernetes — building reproducible, auditable infrastructure with security baked in from day one.

🌐

WordPress & Web Security

Hardening WordPress deployments, WAF configuration via Cloudflare, and reducing attack surface for web-facing applications.

📡

Network & DNS

Pi-hole DNS filtering, Ubiquiti network segmentation, VLAN design, and zero-trust principles for home lab and enterprise environments.

Choose a practical security starting point

If you want to compare notes, these are useful places to start a conversation. Each topic is grounded in practical risk reduction, realistic fixes, and implementation paths teams can actually follow.

Cloud security foundations

Practical discussion around AWS, Azure, or Google Cloud foundations: IAM, network exposure, encryption, logging, backups, and configuration drift.

Book a Coffee Chat →

Web & WordPress security

Conversation around public-facing sites, WordPress deployments, DNS, Cloudflare controls, WAF posture, backups, and practical hardening steps.

Book a Coffee Chat →

Incident Response Readiness

Ideas for playbooks, logging, SIEM/detection coverage, endpoint visibility, and response workflows before a real incident forces the issue.

Book a Coffee Chat →

Not sure where to start? Book a Coffee Chat →

Projects on GitHub

Let's talk security

Want to compare notes on cloud, website, or infrastructure security? Book a coffee chat and bring the system, risk, or idea you want to talk through.

Book a Coffee Chat →

Please do not include passwords, secrets, or sensitive credentials when booking. Share only enough context to start a safe security conversation.

What happens next

  • You pick a time for a coffee chat.
  • Bring a short summary of the system, risk, or project on your mind.
  • We talk through context, trade-offs, and useful next questions.