Skip to content
Category

Security

Identity, credentials, guardrails and the boundaries that hold when something goes wrong.

Posts in Security

Zero trust access for engineers

How people should reach production: federated sessions instead of users, no long-lived keys anywhere, and access that ends the day someone leaves.

Nine security services, one account

What GuardDuty, Security Hub, Config, CloudTrail and their siblings each actually catch, what they cost, and the order to switch them on.

Permission sets that survive an audit

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.

Service control policies that hold

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.

Find out what production would take.

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.

The invite goes to this address. Prefer to write? Send a message.