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.
What production-ready actually means, and what it takes to get there. Specific, technical, and honest about the trade-offs — including the ones that make our own work harder.
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.
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.
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.
These are the subject areas we write about most.
Controls, evidence and audits, treated as an output of infrastructure rather than a project.
8 posts
Account boundaries, networks and topology: the decisions that are expensive to change later.
7 posts
Identity, credentials, guardrails and the boundaries that hold when something goes wrong.
6 posts
What production engineering costs, what skipping it costs, and how to argue either case.
1 post
Pipelines, review gates and promotion: how a change reaches production without a hero.
1 post
Day 2: running a system, handing it over, and being woken by it without dreading the call.
1 post
Infrastructure as code, drift, state and the repositories an engineering team actually lives in.
1 post
Failure you planned for, recovery you have rehearsed, and the difference between the two.
1 post
BuiltForProd builds production-grade cloud foundations and the reference architectures that run on them. This blog is where the thinking behind that work is published: the account boundaries, the credential model, the restore drill, the review gate, the evidence an auditor asks for. Every post is written so an engineer can act on it without buying anything.
Where a post uses concrete numbers, they describe a real system — usually the AWS Enterprise Baseline — and they are labeled as such. Where something is a judgment call, it says so. Where we would tell a customer not to do the work yet, we say that too.
When a post describes a gap you recognize, the BuiltForProd Assessment is the paid, evidence-based version of the same question: findings, priorities, a future-state architecture and a migration plan, in about two weeks, with up to 50% of the fee credited toward a Baseline.
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.