[Industries]

Who we work with.

Our work started in aerospace and defense. The same engineering serves manufacturers, growing businesses and any organization with data to protect.

Aerospace & Defense

Suppliers whose contracts require proof that sensitive data is protected.

CMMC Level 2, in GCC High where the contract requires it
An environment built in your own tenant and at your site
A scope small enough to afford
A boundary drawn around how sensitive data moves
Records kept current
Kept patched, logged, reviewed and documented
CloudsMicrosoft 365 and AzureCommercial and US government.Our role

We build and support the environment. We do not certify it; an independent assessor does.

Manufacturing

Shops with machines that cannot move to the cloud.

Machines that must stay on site
Cloud and site designed as one environment
Customer and insurer security questionnaires
Logs and documentation you can point to
Kept apart
  • Office
  • Shop floor
  • Guests
Managed firewall and VPN
FIG. 01 Shop-floor control systems stay with the people who run them, with the boundary written down.

Small & Medium Businesses

Businesses where one person ended up responsible for IT.

Someone to call when something breaks
Day-to-day IT: accounts, devices, Microsoft 365, network, backups
Security without an enterprise budget
A written business technology assessment, then a security baseline
Stays in your name
  • Accounts
  • Licenses
  • Equipment
Scope

Agreed in writing before you sign.

Regulated Organizations

Organizations that answer to a contract, a framework or an auditor.

What data is in scope and where it lives
The data mapped, and the boundary drawn around it
A record an auditor can follow
Built from code in infrastructure you own, with changes recorded
  1. Requirement
  2. Control
  3. Evidence
FIG. 02 Controls mapped to your framework.
[Next step]

Not on this list? Ask anyway.

If you have an environment to secure and someone to prove it to, the work is the same.

Not ready to talk? See how an engagement starts