CMMC 2.0 for defense suppliers
CMMC Level 1 and Level 2 decide whether a supplier can hold the contract. Here is what infrastructure covers, what it cannot, and where it gets hard.
14 posts on this subject.
CMMC Level 1 and Level 2 decide whether a supplier can hold the contract. Here is what infrastructure covers, what it cannot, and where it gets hard.
Account isolation is the cheapest PCI scope reduction available, and the most over-claimed. Here is what it removes, what stays in scope, and what proves it.
The HIPAA Security Rule splits across your policies, your cloud provider and your infrastructure. Here is the part infrastructure owns, and how it is proven.
How people should reach production: federated sessions instead of users, no long-lived keys anywhere, and access that ends the day someone leaves.
Encrypted secrets in Git, one key per stage, and a sync to parameter storage: why repository write access still does not let anyone read production.
A separate account, an organization-wide trail with file validation, and a policy that forbids stopping it — plus what tamper-resistant does not mean.
What GuardDuty, Security Hub, Config, CloudTrail and their siblings each actually catch, what they cost, and the order to switch them on.
Overlapping CIDRs are the cheapest mistake to make and one of the most expensive to fix. Here is how to plan an address space once and enforce it in CI.
Spoke VPCs with no NAT, one centralized egress path, and blackhole routes between production and non-production: what a hub and spoke topology buys.
A guardrail works only if engineers cannot route around it. Here is how to design, exempt and test a service control policy before it blocks production.
AWS Control Tower gives you the account and guardrail layer at no license fee. Here is where a code-owned foundation wins, and where it honestly does not.
The account boundary is the first security control you get. Here is how to decide what deserves its own account, and how the structure survives growth.
Static cloud keys in CI are a liability you chose to keep. OIDC federation replaces them with short-lived tokens your pipeline requests per job.
Account boundaries are the first security control you get and the hardest to add later. Here is what each account in a landing zone is for, and why.
A 30 minutes call with an engineer who scopes engagements, not a salesperson. Tell us what you run and what is coming: a funding round, an audit, a first enterprise customer, a migration. You leave with a next step, a fixed fee, or an honest no.