Evidence automation beats screenshot season
Audit evidence has a shelf life, and most findings services keep only 90 days. Here is how to make infrastructure produce evidence that survives the period.
22 posts on this subject.
Audit evidence has a shelf life, and most findings services keep only 90 days. Here is how to make infrastructure produce evidence that survives the period.
Investors, acquirers and enterprise procurement inspect the same six things. Here is what each finding signals, and a self-audit to run before they arrive.
A security questionnaire is a revenue blocker answered by your most expensive engineers. Here is how to answer with evidence and never write the answer twice.
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.
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.
Least privilege fails when people cannot do their jobs. Here is an identity model with read-only production and an access review that produces evidence.
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.
Infrastructure drift is not a sign of a broken team. It is information about what your environment needs. Detect it, triage it, and never auto-revert it.
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.
Production-ready is not a feeling. It is eight properties, each with a question you can answer about your own estate this week, with evidence.
A cloud foundation built in-house costs far more than the estimate says. Here is the work nobody scopes, and when building it yourself is still right.
An audit is an evidence problem. Here are the evidence sources cloud infrastructure should generate on its own, and why readiness is not certification.
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 backup nobody has restored is a hypothesis, not a control. Here is how to run a restore drill and set an RTO and an RPO you can defend.
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.