Notes from the field.
Written from engagement work. Each note cites the guidance behind it and ends with something you can check in your own environment.
Draw the CMMC boundary before you write the SSP
Most of the cost of CMMC Level 2 is decided by scope. Here's how I map where CUI actually goes before any control work starts.
What a retest proves that a report cannot
A penetration test report describes a moment. The retest is the only part of the engagement that shows the fix actually holds.
Your forked merge requests are running with your secrets
One pipeline decision controls whether a stranger's merge request can read your deploy keys. Here's how to check it in five minutes.
Stop collecting SBOMs. Start diffing them.
An SBOM nobody reads is just a compliance artifact. The diff between two releases is where the signal is.
One stolen token: tracing blast radius in a GovCloud account
Zero trust starts with a simple exercise. Pick one credential, assume it leaked, and follow everywhere it can reach.
Sign everything, and plan for the day the key leaks
Commit, artifact and image signing is easy to switch on. Key custody and rotation are where teams get burned.
No notes under this topic yet.
Every note, by date.
- 006 Nov 17, 2026 Draw the CMMC boundary before you write the SSP cmmc · nist-800-171 · compliance 6 min →
- 005 Nov 6, 2026 What a retest proves that a report cannot offensive · pentest 3 min →
- 004 Nov 4, 2026 Your forked merge requests are running with your secrets ci-cd · gitlab · secrets 3 min →
- 003 Oct 21, 2026 Stop collecting SBOMs. Start diffing them. supply-chain · sbom 2 min →
- 002 Oct 20, 2026 One stolen token: tracing blast radius in a GovCloud account cloud · zero-trust 3 min →
- 001 Oct 2, 2026 Sign everything, and plan for the day the key leaks signing · supply-chain 3 min →
New notes land in the feed first. No mailing list, no tracking.