Writing on security, AI systems, and technology leadership.
Specific pieces on security frameworks and metrics, AI systems that run in production, and the decisions a CTO makes when everything looks urgent. Written from inside the work, with sources.
AI governance framework: what belongs in it and how to build one in ninety days
Decisions, owners and evidence: the six artifacts a small company needs, a framework map, a ninety-day plan and a ten-question sprint checklist.
· 8 min read
MTTD vs MTTR: what each measures and how to calculate them
MTTD tells you how good your visibility is. MTTR tells you how good your response is. How to calculate both, which of the four meanings of MTTR to use, and what the trend is for.
· 6 min read
CIS Controls v8 Implementation Groups explained: IG1 vs IG2 vs IG3
IG1 is 56 safeguards of essential cyber hygiene. IG2 adds 74. IG3 adds the last 23. How to decide which group fits, with an example that falls between IG1 and IG2.
· 7 min read
What a fractional CTO is, and when you need one
The role in plain terms, what the person does week to week, a comparison with the other people you might hire, and three questions that show whether you have a leadership gap.
· 6 min read
Fractional CTO cost: what drives the price
No price list, because scope sets the number. The drivers, the pricing models and their trade-offs, and why a full-time salary understates the cost of a hire.
· 6 min read
NIST SSDF vs Microsoft SDL vs BSIMM: choosing a secure development framework
SSDF tells you what good looks like, SDL tells you how one large vendor does it, and BSIMM tells you where you are. How to choose, with two worked examples.
· 7 min read
How to scope a PCI DSS cardholder data environment, and which SAQ applies
Scope the cardholder data environment, determine your merchant level, then rule out each SAQ with a reason. Includes a worked example of a retailer storing card data on AWS.
· 7 min read
How to reconstruct an attack chain for a security gap analysis
Write the incident as numbered steps, name the failure at each one, map it to a control and its safeguards, scope to the Implementation Group, then sort into prevent, detect, respond.
· 6 min read
How to write a cybersecurity incident report (the sections that matter)
Header, factual summary, incident description, plain-language technical detail, impact by category, data sensitivity, explicit unknowns, and a remediation plan sequenced by speed of risk reduction.
· 6 min read
Maturity score vs remediation priority: why the lowest score is not always first
Score every domain, write what each gap exposes, weigh it against the business, add urgency, check for dependencies. Incident Response first, Awareness Training last, same score.
· 6 min read
Where threat modeling fits in the SDLC
The four questions, STRIDE, the triggers across the life cycle, system-level versus software-level modeling, and how a threat model should drive design, policy, and maturity.
· 6 min read
HIPAA Security Rule vs NIST SP 800-53: legal requirement or benchmark?
Required versus addressable, the technology-neutral design of the Rule, how SP 800-66 bridges to SP 800-53, and the one sentence that keeps a healthcare assessment honest.
· 6 min read
Security coverage metrics: finding the blind spots in logging, inventory and allowlisting
Coverage is the denominator that makes speed metrics honest. Three formulas, where the denominators come from, and what to report.
· 6 min read
How these articles are written
Each article answers one question a business owner or IT lead actually asks, and gives the answer in the first paragraph. Framework facts come from the publisher: NIST, the Center for Internet Security, the PCI Security Standards Council and HHS, listed under Sources at the end of every piece.
Where a method has been used in real work, the article links to the case study that shows it, so you can see the framework applied rather than only described.
The cybersecurity pieces cover CIS Controls implementation groups, incident reports, MTTD and MTTR, PCI DSS scoping, the HIPAA Security Rule against NIST SP 800-53, secure development frameworks and threat modeling. The fractional CTO pieces cover what the role owns and what drives its price. Pieces on AI readiness and AI agent security are being added.
When guidance changes or a piece is improved, it is revised in place rather than replaced by a new post, so links to it keep working.
Where to go next
- Need someone to own security? vCISO and cybersecurity consulting.
- Need senior technology decisions without a full-time hire? Fractional CTO services.
- Deciding where AI would pay off? Fractional CAIO and AI consulting.
- Want a written read on your own company? Free cybersecurity assessment for small business.
- Thinking about automating work with AI? Free AI readiness assessment.