nist-cps
NIST Framework for Cyber-Physical Systems (SP 1500-201/202/203)
Source: NIST (US Government work, public domain) | Chapters: 8
When to use
Use this skill to conceptualize, realize, and assure a cyber-physical system or IoT system in a disciplined way: structuring the analysis on the CPS Framework's grid, managing the interacting trustworthiness properties as one cross-property risk problem rather than five silos, making data exchange actually interpretable across domains, treating timing as a first-class architectural and security concern, and deriving requirements from use cases. It is the CPS/IoT counterpart to the broader SE canon (sebok, nasa-npr-7123, dau-se-guidebook) and the security-engineering packs (nist-sse).
Prerequisites: none — plain Markdown; no MCP server, API key, or licence tier needed at runtime.
How to Use This Skill
- Without arguments — load the core frameworks below: the aspect × facet grid, cross-property trustworthiness, data interoperability, the timing aspect, and secure/resilient time.
- With a topic — ask about an aspect or facet, a trustworthiness property (e.g. "resilience vs. reliability"), data interoperability (e.g. "canonical model", "identifiers"), a timing-interval class, or secure time (e.g. "GNSS spoofing", "PTP attacks", "holdover").
- With a chapter —
ch02(the Framework grid),ch04(cross-property risk),ch05(data interoperability),ch06(timing),ch08(managing and securing time).
Supporting files: glossary.md, patterns.md, cheatsheet.md.
Three volumes, one Framework. Vol 1 (SP 1500-201) defines the CPS Framework (chapters 1–3 here). Vol 2 (SP 1500-202) is the working-group reports — cybersecurity/privacy, data interoperability, timing, and use cases (chapters 4–7). Vol 3 (SP 1500-203) is the Timing Annex (chapter 8). This is a 2017 v1.0 living document, explicitly draft in places.