Resources and automation for conducting security architecture reviews of System Design Documents (SDDs). Helps engineering teams think like "Security Steve" — considering security implications during design and development.
Type
Purpose
Flexibility
References
Concepts, analogies, and mental models to understand security
Use as learning material — adapt to your context
Specifications
Step-by-step checklists and required validations
Follow exactly — these are security requirements
Rule of thumb: If it asks questions, it's a reference. If it has checkboxes, it's a specification.
I want to...
Use this
Self-review before requesting Security's help
Quick Security Review
Use Claude to help document my architecture
Quick Review Prompt
Prepare for a walkthrough with Security
Self-Service Checklist
Get automated security questions for my SDD
SDD Review Action
Get a security review of a pull request diff
PR Review Action
Run SDD review interactively in Claude Code
/sdd-review skill in Claude Code
Run PR review interactively in Claude Code
/pr-review skill in Claude Code
Triage any security question with AI
/security-steve skill in Claude Code
Record decisions on a completed review
/decision <slug> skill in Claude Code
See all resources and workflows
Security Review Guide
See an example of a completed review
Example Review
What is "Security Steve"?
Security Steve is a persona that helps engineers think about security concerns during development. When reviewing your feature, ask yourself:
"What would Security Steve notice? What questions would they ask?"
Key Security Steve questions:
What could go wrong if a malicious user got access?
What data could be exposed, and to whom?
How would we know if something bad happened?
A GitHub Action that reads your SDD from Notion, pulls in source code and context, and generates a security review including:
Security Team Involvement Recommendation — Required / Recommended / Not Required, with NIST 800-30 risk score
1–10 Security Questions — specific to your design, prioritized by impact
Data Classification Table — Critical/High/Medium/Low
Compliance Considerations — scope changes, data residency, audit logging
Incident Response Scenarios — what breaks, how to detect, blast radius
Architecture Diagrams — draw.io (interactive) and ASCII (inline)
See the full setup instructions and documentation .
Files to copy into your repo
your-repo/
.github/
workflows/
sdd-review.yml # from .github/workflows/sdd-review.yml
scripts/
sdd_reviewer.py # from .github/scripts/sdd_reviewer.py
Secret
Description
ANTHROPIC_API_KEY
From console.anthropic.com
NOTION_TOKEN
Notion integration secret (see setup guide )
SOURCE_REPO_TOKEN
Optional: GitHub PAT for accessing source code in other repos, and for reading a private risk register repo
SDD_SLACK_WEBHOOK_URL
Optional: Incoming webhook URL for Slack notifications on Required/Recommended reviews
LINEAR_API_KEY
Optional: Linear API key for auto-creating triage tickets on Required reviews
LINEAR_TEAM_ID
Optional: Linear team UUID to create tickets in; required if using Linear integration
LINEAR_TRIAGE_STATUS_ID
Optional: Linear status UUID for the triage state; required if using Linear integration
/guides/ — How-to Documentation
/reviews/ — Review Records
/_static/ — Reference Data
/.claude/commands/ — Claude Code Skills
File
Purpose
sdd-review.md
Interactive Claude Code skill for the SDD review workflow; includes built-in decision capture
pr-review.md
Interactive Claude Code skill for the PR security review workflow; includes built-in decision capture
security-steve.md
Security Concierge triage and dispatch skill — routes any security question to the right workflow
decision.md
Record or update per-question decisions on a completed review (/decision <slug>)
For Engineers (Self-Service)
Quick Review — Answer the 10 essential questions
Use Claude — Paste the Quick Review Prompt to get AI assistance
Automated SDD Review — Use the SDD Review Action to get security questions from your SDD
Check the Checklist — Validate against the Self-Service Checklist
Request Review — If needed, engage your security team
Prepare — Review the Architecture Walkthrough Questions
Conduct Review — Use the Security Architecture Review Template
Document — Save the review under reviews/<feature-name>/review.md
Track — Add a row to reviews/TRACKING.md
Record Decisions — Disposition each follow-up question using /decision <slug> in Claude Code
When adding new guides or templates:
Follow the "Security Steve" mindset — focus on practical security thinking
Prefer "how" questions over yes/no questions
Keep guides actionable and concise
Add an entry to reviews/TRACKING.md for each completed review