Ctrl+Alt+Trace · Search · Explore · Compare · Build
Control Atlas is a public research tool for federal cybersecurity requirements, controls, techniques, and guidance.
Uses public NIST, DISA, FedRAMP, MITRE, and CISA data only. No login. No evidence upload. No organizational data stored.
Use Control Atlas for research, not compliance or authorization decisions.
Future work must preserve this order:
- Exact publication identity and official source text
- Publisher-declared hierarchy
- Labeled, source-traceable relationships
- Concrete retrieval, comparison, navigation, or document action
- Product-authored notes and limitations
- Raw technical detail on demand
- Finds published records by identifier or topic
- Shows exact publisher, publication, official text, and declared structure
- Traces published and candidate relationships with their provenance
- Compares records through explicitly selected published mapping sources
- Generates blank starter documents from explicitly selected inputs
- Lists external tools, templates, data, training, and communities with owner and provenance
- Ingest evidence or process authorization packages
- Store user, organization, or system data
- Connect to eMASS, STIG Manager, or any operational system
- Determine applicability, baselines, compliance, inheritance, authorization, or ATO outcomes
- Replace a practitioner, assessor, ISSO, responsible authority, or AO
Mappings and starter documents are based on public sources, with their owners and limitations attached.
This application has no backend.
Live site target: https://rambulls.github.io/control-atlas/
Built by RAM.BULLS. If Control Atlas saves you time, you can support the work.
- Static GitHub Pages deployment with a React + Vite translation-first shell
- Build-time public-data importers, normalizers, and validators under
scripts/ - Stable public runtime bundles:
sources,nodes,edges,evidence, andgraph-health - Browser-only search, browse, comparison, source inspection, and CSV export behavior
- Current D3-based relationship visualization foundation for the Epic 0 provenance filter surface and later roadmap work
- Contract, browser, runtime, and data tests enforcing the public-data-only boundary
Start with docs/README.md, which points to the canonical product, page, architecture, data, operations, and backlog contracts.
npm run build:data
npm run audit:deps
npm run sbom:generate
npm test
npm run test:browser
npm run audit:coverage
npm run verify:public
npm run precommit