Answering a 300-question security questionnaire
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.
12 posts on this subject.
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.
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.
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.
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.
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 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.