Gap
data/frameworks/nist-800-53-r5.json declares only scoring.profiles (Low / Moderate / High baselines). The 20 control families that every 800-53 controlId starts with (AC-1, AU-2, IA-5, …) are not declared in CheckID. Downstream consumers (M365-Assess #843) regex the family code out of controlId strings via the family-letter-prefix strategy.
Families to declare
The NIST 800-53 r5 control catalog defines 20 families:
| Code |
Name |
| AC |
Access Control |
| AT |
Awareness and Training |
| AU |
Audit and Accountability |
| CA |
Assessment, Authorization, and Monitoring |
| CM |
Configuration Management |
| CP |
Contingency Planning |
| IA |
Identification and Authentication |
| IR |
Incident Response |
| MA |
Maintenance |
| MP |
Media Protection |
| PE |
Physical and Environmental Protection |
| PL |
Planning |
| PM |
Program Management |
| PS |
Personnel Security |
| PT |
Personally Identifiable Information Processing and Transparency |
| RA |
Risk Assessment |
| SA |
System and Services Acquisition |
| SC |
System and Communications Protection |
| SI |
System and Information Integrity |
| SR |
Supply Chain Risk Management |
Extraction
Every 800-53 controlId starts with the 2-letter family code followed by - (e.g. AC-1, IA-5(7)). Strategy: letter-prefix-before-dash.
Acceptance criteria
Blocked by
Spike #317.
Related
The FedRAMP r5 family axis (filed as a sibling issue) uses the same 20 families and could share the values map.
Gap
data/frameworks/nist-800-53-r5.jsondeclares onlyscoring.profiles(Low / Moderate / High baselines). The 20 control families that every 800-53 controlId starts with (AC-1,AU-2,IA-5, …) are not declared in CheckID. Downstream consumers (M365-Assess #843) regex the family code out ofcontrolIdstrings via thefamily-letter-prefixstrategy.Families to declare
The NIST 800-53 r5 control catalog defines 20 families:
Extraction
Every 800-53 controlId starts with the 2-letter family code followed by
-(e.g.AC-1,IA-5(7)). Strategy:letter-prefix-before-dash.Acceptance criteria
data/frameworks/nist-800-53-r5.jsondeclares the family axis per agreed shapedata/registry.jsonresolves to a declared familyscoring.profiles(Low/Mod/High) coexists with the new family axis (or is migrated to abaselineaxis — TBD by spike)Blocked by
Spike #317.
Related
The FedRAMP r5 family axis (filed as a sibling issue) uses the same 20 families and could share the values map.