For agencies, contractors, and public institutions at every level

Security leadership for government and the organisations that serve it

Government security work has its own shape. The adversaries are different, the accountability is public, the frameworks aren't optional, procurement moves at its own pace, and the mission usually can't stop while you fix things. I've served as the subject-matter expert for US and allied governments from the municipal level to the national, and for the contractors and institutions that work alongside them. I know the difference between a control that satisfies an assessor and one that would stop an intrusion, and I know you often need both.

What I bring to a public-sector role

Operational depth: about twenty years hands-on in incident response and security operations, which matters in environments where the incident is a national-security or public-safety event rather than a business interruption. Framework fluency: NIST's families of guidance as working tools rather than compliance paperwork, and an understanding of how authorisation, continuous monitoring, and incident reporting actually get done inside an agency or a contractor. The academic grounding, through a PhD centred on cybersecurity, AI, and the criminal use of technology, and a law school education that helps when the question is what the rules actually require. And the patience public-sector delivery takes.

The kinds of role

Agency or departmental security leadership. Security leadership inside a contractor or systems integrator serving government. Programme leadership for an authorisation, a modernisation, or an incident-driven rebuild. Advisory roles for public institutions, utilities, and critical infrastructure operators with government oversight. And the allied and international variants of each, where I've worked as well.

What I don't claim here

Specific agencies, programmes, and engagements stay under NDA, and I don't publish clearance or employment detail. If a role requires particular eligibility, we'll establish that privately and early.

The honest fit

This works where leadership wants someone who can run the operation and speak the framework language, and where the role has the authority to act between oversight cycles. It doesn't work where the security role exists to produce documentation and nothing else.

What I've written on this.

Read these before we talk, if you like. They're the long version of the argument.

Related work.

Other ways I'm engaged on the same problems.

Discuss an executive role.

Tell me about the role, the organisation, and what the first year has to deliver. I'll say quickly whether it's a fit.

Much of what I've done can't be described in public, and I've had an intimate relationship with NDAs most of my adult life. What I can say here, I do; the rest we talk about in confidence.

  • Agencies and public institutions at federal, state, and local level hiring senior security leadership.
  • Contractors and integrators serving government who need a security leader who's worked both sides.
  • Allied governments and international organisations with comparable requirements.

Everything I do, in twelve places.