Security Workflow Control Contract

Overview

If your AI can find a vulnerability, draft a patch, and open a PR, your biggest risk is no longer detection quality.

Your biggest risk is workflow ownership:

This episode translates four current signals into one operational playbook for next week.

• who can analyze,
• who can approve,
• who can merge,
• who can pause,
• and who can attest the execution chain under pressure.

What changed this week

1. OpenAI launched Codex Security in research preview (2026-03-06).
2. Anthropic + Mozilla published concrete AI-assisted vulnerability workflow details (2026-03-06), including CVD and exploit-analysis references.
3. NIST published AI 800-4 on monitoring deployed AI systems (2026-03-06).
4. OpenAI launched GPT-5.4 and ChatGPT for Excel beta (2026-03-05), expanding business-user AI execution surfaces.

Operator translation

• Treat AI security pipelines as action-controlled workflows, not assistant features.
• Separate discovery throughput from remediation readiness.
• Move monitoring from dashboarding to a named ownership control.
• Add spreadsheet-AI usage controls where sensitive decisions or data handling occur.

Monday block (45 minutes, one owner)

• Minute 0-10: action matrix lock (Analyze, Draft fix, Open PR, Merge, Deploy) with allowed/checkpointed/restricted levels.
• Minute 10-20: credential and identity check (remove over-scoped inherited credentials).
• Minute 20-30: evidence contract (logs, retention, export path, access controls).
• Minute 30-40: disclosure + rollback ownership (name owners, define stop authority).
• Minute 40-45: operator memo (what changed, what is approved, what is restricted, who approves exceptions, next review date).