CA.L2-3.12.3 Continuous monitoring
What the standard requires
Monitor security controls on an ongoing basis to ensure the continued effectiveness of the controls.
Quoted verbatim from NIST SP 800-171 Rev 2 (NIST CPRT), which is in the public domain.
Maps to 1 control in 1 other framework
| Framework | Control |
|---|---|
| NIST Cybersecurity Framework (1.1, legacy) | DE.DP-5 Detection processes continuously improved |
Mappings are CMDash’s own, seeded with the product and shown on both frameworks they connect. In the product they mean evidence you attach here also counts against the controls listed above.
Integrations that carry evidence for this family
These connectors produce data relevant to CMMC Level 2’s Security Assessment family, which is the granularity CMDash publishes — there is no pre-built per-control mapping, and claiming one would be inventing it. You decide which evidence answers which control.
In CMDash this control is a row with an owner, a status, uploaded evidence kept with its full history, and an export an assessor can read.