mcpField
S
security-bluebook-builder

security-bluebook-builder

github.com/shadowpr0Security845 installsUpdated 5d ago
Repository

About security-bluebook-builder

Security Bluebook Builder helps teams define a concise, enforceable security policy for sensitive applications. It gathers system context and produces a single Blue Book with assumptions, controls, and release gates.

Key features

  1. 01Context gathering with up to six questions
  2. 02Blue Book drafted from a template
  3. 03Explicit assumptions and TODOs
  4. 04Threat model and data-handling rules
  5. 05Auth, tokens, logging, and retention policies
  6. 06Incident response and release checklist

Use cases

  1. 01Drafting a security policy for a sensitive app
  2. 02Recording unknowns as explicit assumptions
  3. 03Defining controls for data and trust boundaries
  4. 04Reviewing security readiness before release

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/shadowpr0/security-bluebook-builder --skill security-bluebook-builder

After installing, type/security-bluebook-builderin Claude Code to confirm it loaded.

Bundled filesreferences/bluebook_template.md

Details

From the project README

Security Bluebook Builder

Overview

Build a minimal but real security policy for sensitive apps. The output is a single, coherent Blue Book document using MUST/SHOULD/CAN language, with explicit assumptions, scope, and security gates.

Workflow

1) Gather inputs (ask only if missing)

Collect just enough context to fill the template. If the user has not provided details, ask up to 6 short questions:

  • What data classes are handled (PII, PHI, financial, tokens, content)?
  • What are the trust boundaries (client/server/third parties)?
  • How do users authenticate (OAuth, email/password, SSO, device sessions)?
  • What storage is used (DB, object storage, logs, analytics)?
  • What connectors or third parties are used?
  • Retention and deletion expectations (default + user-initiated)?

If the user cannot answer, proceed with safe defaults and mark TODOs.

2) Draft the Blue Book

Load references/bluebook_template.md and fill it with the provided details. Keep it concise, deterministic, and enforceable.

3) Enforce guardrails
  • Do not include secrets, tokens, or internal credentials.
  • If something is unknown, write "TODO" plus a clear assumption.
  • Fail closed: if a capability is required but unavailable, call it out explicitly.
  • Keep scope minimal; do not add features or tools beyond what the user asked for.
4) Quality checks

Confirm the Blue Book includes:

  • Threat model (assumptions + out-of-scope)
  • Data classification + handling rules
  • Trust boundaries + controls
  • Auth/session policy
  • Token handling policy
  • Logging/audit policy
  • Retention/deletion
  • Incident response mini-runbook
  • Security gates + go/no-go checklist

Resources

  • references/bluebook_template.md

Comments

Markdown supported