Security engineering for federal assessments

We build the parts of your environment that a federal assessment tests: identity, networks, encryption keys, cloud accounts and your Microsoft 365 or Google Workspace tenant. Our engineers make the changes themselves.

Example: What you keepHandover
  • program-handover/
  • terraform/cloud accounts, network and guardrails
  • m365-config/exported tenant configuration
  • control-map.csveach setting and the requirement it meets
  • runbook.mdhow to check each control, and what to do when it drifts
What we build is handed over as files your team can change and apply again.

Engineering services

Multi-cloud architecture

Identity, networking, guardrails and logging set up the same way in AWS, Azure and Google Cloud, including each provider’s government offering.

Security architecture

Access and encryption changes that apply to all the clouds and systems you run.

Workplace

Email, files and sign-in for your staff.

AI systems

AI applications built in a federal cloud, on a model service that reaches the level your data needs.

  • AI engineeringAzure OpenAI, Amazon Bedrock and Google’s Gemini models

What you keep

Configuration as code

Terraform for cloud accounts, and exported configuration for Microsoft 365 and Google Workspace where the product supports it. Your team can change it and apply it again.

Control map

Each setting next to the SP 800-53 or SP 800-171 requirement it meets, in wording you can use in the SSP.

Runbook

How to check each control, where its alerts go, and what to do when it drifts.