NIST SP 800-137, "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations," is NIST guidance on how to run ongoing monitoring of security controls, vulnerabilities and threats. It is not a law and has no certification attached, so "compliance" with it really means building a monitoring program that meets the expectations of the regimes that rely on it. This article explains what the publication asks for and how to put it into practice.
What it is
SP 800-137 was published by the National Institute of Standards and Technology (NIST) in September 2011. It is a Special Publication, which is guidance rather than a statute or regulation. It supports the Risk Management Framework (RMF) and the broader federal information security program under FISMA.
NIST defines information security continuous monitoring as maintaining ongoing awareness of information security, vulnerabilities and threats so that risk management decisions can be made. The word "continuous" does not mean every control is checked in real time. It means monitoring happens at a frequency matched to risk, and that the results feed decisions.
A companion document, SP 800-137A (2020), covers how to assess an ISCM program. The base publication dates from 2011, so read it alongside newer NIST material, in particular SP 800-37 Rev. 2 (the RMF, 2018) and SP 800-53 Rev. 5 (controls, 2020). Check NIST's publication page for any later revision or draft update.
Who it applies to
- Federal agencies. Agencies operating federal information systems are the primary audience. FISMA and OMB policy require agencies to have a continuous monitoring capability, and NIST guidance is how agencies generally meet it.
- Contractors and cloud providers. Organizations operating systems on behalf of agencies usually meet the guidance indirectly, through contract terms, agency authorization requirements, or programs such as FedRAMP, which has its own continuous monitoring expectations.
- Everyone else. Nothing legally compels private organizations outside these relationships to follow it. Many use it voluntarily as a model for a monitoring program.
If you are told you "must comply with 800-137," ask which requirement sits behind it: a contract clause, an authorization to operate (ATO) condition, or a control such as CA-7.
Key requirements and control areas
The six-step ISCM process
- Define an ISCM strategy based on risk tolerance.
- Establish an ISCM program, including metrics, monitoring and assessment frequencies, and the technical architecture.
- Implement the program and collect the data, automating where possible.
- Analyze and report findings in terms of risk.
- Respond to findings with mitigation, acceptance, transfer or avoidance, as the risk decision dictates.
- Review and update the strategy and program as threats, technology and mission change.
Three-tier view
The guidance builds on the multitiered model from SP 800-39. Tier 1 (organization) sets the strategy and risk tolerance. Tier 2 (mission/business process) covers the processes and shared controls. Tier 3 (information system) covers the technical monitoring of individual systems. A common failure is to do only Tier 3 and leave leadership without risk-level reporting.
Metrics and frequency
Organizations must decide what to measure and how often, and justify the choices. Frequencies should reflect control volatility, the system's impact level, threat information and the cost of monitoring. Not every control needs the same cadence. Metrics should be tied to controls and to risk decisions, not collected for their own sake.
Automation
The publication encourages automated collection across areas such as asset management, configuration and vulnerability management, patch management, event and incident management, and malware detection. Where automation is not possible, manual assessment still counts, but it must be scheduled and recorded.
Ongoing authorization
ISCM data supports ongoing authorization. Rather than relying only on a point-in-time assessment every few years, authorizing officials can use current monitoring results to keep or revisit their risk decisions.
Assessment, audit and enforcement
There is no SP 800-137 certification and no accreditation body. How it gets checked depends on the context:
- Agency systems: assessed through the RMF, with oversight from authorizing officials, agency security teams, inspectors general and the FISMA reporting process. CA-7 (Continuous Monitoring) in SP 800-53 is the control where expectations are written down and tested.
- Cloud service providers: FedRAMP-authorized services submit ongoing monitoring deliverables to their authorizing agency or program office. Specific deliverables and cadences change, so check current FedRAMP requirements.
- Program assessment: SP 800-137A describes how to evaluate whether an ISCM program is well formed and effective.
Consequences are mainly operational and contractual: findings in audits or assessments, adverse authorization decisions, or contract issues. They do not come from a fine schedule tied to this document.
A practical path to meeting it
- Confirm the driver. Identify whether the requirement comes from FISMA, an ATO, FedRAMP, a contract or internal policy.
- Inventory systems and controls. Know your authorization boundaries, impact levels and which controls are system-specific, inherited or shared.
- Write the ISCM strategy. Document risk tolerance, roles, tiers and how results reach decision makers.
- Select metrics and frequencies. For each control, choose a measure, a data source, a cadence and a rationale. Prioritize high-impact and volatile controls.
- Automate collection. Connect cloud platforms, identity systems, code repositories, vulnerability scanners and ticketing. Schedule manual checks for what cannot be automated.
- Define thresholds and response. Decide what counts as drift, who is alerted and how findings enter the plan of action and milestones (POA&M).
- Report at each tier. Give system owners technical detail, and give leadership risk-based summaries.
- Review annually or on major change. Update the strategy, metrics and tooling, and test the program using SP 800-137A.
How it maps to other frameworks
These are overlaps, not equivalences.
- NIST SP 800-53: CA-7 is the direct link, and related controls in the CA, RA, SI and CM families depend on monitoring data.
- NIST RMF (SP 800-37): the Monitor step reflects ISCM and ongoing authorization.
- FedRAMP: builds on 800-53 baselines and sets its own continuous monitoring deliverables.
- NIST CSF: detection and continuous-monitoring outcomes overlap, though the CSF is outcome-based and not a monitoring methodology.
- ISO/IEC 27001: monitoring, measurement, internal audit and management review (clauses 9.1 to 9.3) share the same intent but are less prescriptive about technical data collection.
- SOC 2: the monitoring criteria overlap, and a Type 2 report depends on evidence over a period, which monitoring data can supply.
FAQs
Is NIST SP 800-137 mandatory?
The publication itself is guidance. The obligations come from FISMA, OMB policy, agency requirements, contracts and FedRAMP, which expect a continuous monitoring capability that NIST guidance describes.
Can I get certified against it?
No. There is no certification. You can show conformance through RMF authorization artifacts, FedRAMP authorization, or an assessment based on SP 800-137A.
Does continuous mean real-time?
No. Frequencies are set by risk and may range from near-real-time to annual depending on the control and the system.
How does it relate to CA-7?
CA-7 is the control that requires a continuous monitoring program. SP 800-137 is the guidance on how to design and operate that program.
Does it replace periodic assessments?
No. It complements them. Monitoring supplies ongoing data between assessments and supports ongoing authorization decisions.
How Aristiun helps
Aristiun is the AI-powered compliance automation and threat modeling platform, powered by Ayurak AI. The effort in an ISCM program is collecting evidence, tracking control health and showing results by framework, and those are the problems the platform addresses. See the compliance frameworks it covers.
- Automated evidence collection: evidence is gathered from connected systems such as AWS, Azure, GCP and GitHub, without manual screenshots or spreadsheets.
- Real-time control monitoring: alerts show when controls drift out of compliance, so you can remediate before auditors find issues.
- Cross-framework mapping: each piece of evidence maps to the relevant controls across all applicable frameworks, so one evidence base can serve several requirements.
- Gap analysis and audit-ready reports: AI-powered validation identifies gaps early, and reports are organized by framework requirement.