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.
Security engineering and modernization
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.
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.
- Amazon Web ServicesAWS GovCloud (US)
- Microsoft AzureAzure Government
- Google CloudAssured Workloads
Security architecture
Access and encryption changes that apply to all the clouds and systems you run.
- Zero TrustNIST SP 800-207 and the CISA maturity model
- Post-quantum cryptographyFIPS 203, 204 and 205
Workplace
Email, files and sign-in for your staff.
- Microsoft 365Commercial, GCC and GCC High, and the move between them
- Google WorkspaceAssured Controls Plus and client-side encryption
What you keep
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.