Tony

> Security. Systems. Software.

01 / about

Hello.

Offensive security and security engineering. I work across penetration testing, adversary simulation, cloud infrastructure and autonomous AI systems.

Most of my time sits on the boundary between offensive operations and engineering: testing systems, and building the infrastructure, tooling and telemetry that the testing depends on. Increasingly that means the security of AI agents themselves: what they are allowed to do, and how you stop them doing the rest.

role
senior consultant, offensive security
based
Brisbane, AU
focus
adversary simulation, cloud, AI agents
stack
Python, Go, C, AWS, Azure, Linux
lab
private GitLab + AWS
status
not open to work

02 / scope

Security. Systems. Software.

  1. 01

    Offensive Security

    Penetration testing and adversary simulation across networks, Active Directory, cloud and APIs.

  2. 02

    Security Engineering

    The infrastructure behind the testing: C2, telemetry pipelines, GitOps, tooling and platforms.

  3. 03

    AI Systems

    Securing autonomous agents, and building constrained agent systems in a private lab.

03 / writing

Recent writing

  1. Why more agent autonomy creates a security architecture problem

    Draft: work in progress

    Authority, delegation, trust boundaries and least privilege, once the thing acting on your behalf makes its own decisions.

  2. Why agent memory is not just a vector database

    Draft: work in progress

    Task state, provenance, authority and time all matter. Similarity search alone captures none of them.

  3. Agents need a control plane, not just a system prompt

    Draft: work in progress

    A system prompt is a request, not a boundary. Tool-using agents need enforcement that sits outside the model.

ls writing/ --all

04 / index

Find your way around

tony@site:~/