Air command and control is one of those domains where the security design has to be right before anything is built, because nobody gets to take the system offline for a rethink. This role sits at that point: shaping policy-compliant architectures for air C2 and its mission-support systems, then staying close enough to the engineering to make sure the design survives contact with reality.

It is a genuinely mixed post. Some weeks are architecture — specifications, interfaces, design decisions written down properly so the next person can follow them. Other weeks are hands-on: configuring and troubleshooting security products, or working out how to give a local site an equivalent service when it cannot reach the central infrastructure.

What you would be doing

• Contribute to security architectures for air command and control and related mission-support areas, and document the decisions that matter.
• Produce specifications for cloud and on-premises components, tiers and interfaces, ready for detailed design.
• Support projects and change initiatives with technical plans that apply the agreed design principles.
• Configure, test and troubleshoot security products and services across the supported estate.
• Integrate local security services with the central security infrastructure — and engineer an equivalent where integration is not possible.
• Apply and maintain the security controls that policy and local risk assessment require.
• Communicate risk to the people who have to decide, and propose countermeasures rather than only naming problems.

What you would bring

• Real security architecture experience in a large, governed environment.
• Hands-on security engineering — products, integration, troubleshooting.
• Comfort across cloud and on-premises design.
• The habit of writing decisions down in a form other engineers can act on.
• Clear communication with non-technical stakeholders about risk.

The work is full time on site in The Hague.