NIST Special Publication 800-137 defines Information Security Continuous Monitoring (ISCM) as "maintaining ongoing awareness of information security, vulnerabilities, and threats to support organizational risk management decisions." Published in September 2011 and still listed as "Final" with no superseding revision, it is NIST's guide to building an organization-wide monitoring strategy and program — not a single tool, scan or dashboard, but the strategy, roles and process that decide what gets monitored, how often, and what happens when the data shows a problem.
Key takeaways
- Because a point-in-time authorization goes stale as systems, threats and environments change, and ISCM is the mechanism that keeps the picture current.
- The document frames this as recursive rather than linear: situational awareness from monitoring improves control of the processes being monitored, which in turn improves situational awareness.
- Policy flows down and status flows up.
- By risk, control by control, not on one calendar.
Why is ISCM a strategy, not a scan?
Because a point-in-time authorization goes stale as systems, threats and environments change, and ISCM is the mechanism that keeps the picture current. SP 800-137 is explicit that organization-wide monitoring "cannot be efficiently achieved through manual processes alone or through automated processes alone." Automated tools (vulnerability scanners, network scanning devices, SIEM feeds) make monitoring more cost-effective and consistent, but interpreting findings and running the response still require people.
What are the six steps of the ISCM process?
Chapter 3 of SP 800-137 lays out the process for developing an ISCM strategy and implementing an ISCM program as six steps:
| Step | What it involves |
|---|---|
| 1. Define an ISCM strategy | Grounded in organizational risk tolerance; covers asset visibility, vulnerability awareness, up-to-date threat information and mission/business impact |
| 2. Establish an ISCM program | Determine metrics, status-monitoring frequencies, control-assessment frequencies and the ISCM technical architecture |
| 3. Implement the ISCM program | Collect the security-related information required for metrics, assessments and reporting; automate collection, analysis and reporting where possible |
| 4. Analyze data and Report findings | Analyze collected data, determine the appropriate response, and collect additional information if needed to clarify or supplement it |
| 5. Respond to findings | Technical, management and operational mitigating activities, or a decision to accept, transfer/share, or avoid/reject the risk |
| 6. Review and Update the monitoring program and strategy | Adjust the ISCM strategy and mature measurement capabilities to increase visibility and awareness over time |
The document frames this as recursive rather than linear: situational awareness from monitoring improves control of the processes being monitored, which in turn improves situational awareness.
How do the three tiers and the ISCM roles fit together?
Policy flows down and status flows up. SP 800-137 mirrors the tiered view from NIST SP 800-39 and SP 800-37: Tier 1 (Organization) sets risk tolerance, governance and organization-wide metrics; Tier 2 (Mission/Business Processes) translates that into monitoring requirements for specific missions and program-management controls; Tier 3 (Information Systems) runs the system-level assessments and status reporting that feed both higher tiers and the system's ongoing-authorization decisions.
Roles follow the tiers, and organizations may rename or combine them. The Risk Executive (Function) oversees the strategy and reviews status against risk tolerance; the Chief Information Officer (CIO) leads the program and secures resources; the Senior Information Security Officer (SISO) runs it day to day; the Authorizing Official (AO) decides whether a system's risk remains acceptable; and Information System Owners, Common Control Providers, Information System Security Officers and Security Control Assessors carry out system- and control-level monitoring. For a device maker, the closest equivalents are the head of product security (SISO), the product owner (system owner) and the PSIRT lead.
How does SP 800-137 decide how often to monitor?
By risk, control by control, not on one calendar. Section 3.2.2 lists the criteria an organization weighs when setting monitoring and assessment frequencies:
| Criterion | What SP 800-137 says | Device-maker reading |
|---|---|---|
| Security control volatility | Volatile controls are assessed more often; CM-6 and CM-8 are examples, PS-2 and PS-3 are not volatile | Component inventories change every release; re-check them per build |
| System categorization / impact level | High-impact systems are monitored more often than moderate, moderate more than low | Safety-relevant or medical products first |
| Controls providing critical functions | Log servers and firewalls are candidates for more frequent monitoring | Secure boot, update signing, remote-access services |
| Controls with identified weaknesses | Items in the SAR or POA&M are monitored more often until fixed | Open findings from the last pentest |
| Organizational risk tolerance | Low-tolerance organizations monitor more often | Set by management, written down |
| Threat information | A new attack against an implemented technology may justify a temporary increase | A new exploit for your RTOS's TCP stack |
| Vulnerability information | A vendor's monthly patch cycle suggests scanning at least that often; the text points to nvd.nist.gov | NVD and supplier advisories for each shipped component |
| Risk assessment results | Risk scores can justify more or less frequent monitoring | The product threat model |
| Output of monitoring strategy reviews | Covered in Section 3.6 | The last strategy review |
| Reporting requirements | They "do not drive the ISCM strategy but may play a role in the frequency of monitoring" | Customer and regulator reporting deadlines |
The document's AC-2 example shows the granularity: identifying account types (AC-2a) rarely changes, so it is assessed infrequently, while automatic disabling of inactive accounts (AC-2(3)) is automated and volatile, so it is monitored often. Event-driven assessments sit on top of the schedule: incidents, new threat information, significant changes and security impact analyses can trigger an unplanned assessment. Frequencies also move over time. In the Section 3.6 example, six months of stable weekly inventory checks justify moving to biweekly or monthly, and rising anomalies in biweekly audit reviews justify moving to weekly.
Which automation domains and metrics does SP 800-137 list?
Appendix D names eleven security automation domains that support continuous monitoring:
- Vulnerability Management and Patch Management
- Event Management and Incident Management
- Malware Detection
- Asset Management, Configuration Management and Network Management
- License Management and Information Management
- Software Assurance
For metrics, the text gives examples such as "the number and severity of vulnerabilities revealed and remediated," unauthorized access attempts, configuration baseline information, contingency plan test results, training currency and system risk scores. Metrics may combine data collected at different frequencies, so each one needs a stated refresh rate.
SP 800-137 favours tools that pull from many sources, use open specifications such as the Security Content Automation Protocol (SCAP), and interoperate with help desk, inventory, configuration-management and incident-response systems. It also sets realistic expectations: "it is not possible to fully automate all of an organization's information security program functions." Sampling, assessing a representative subset rather than every asset, is an accepted way to keep monitoring practical, provided the sample covers enough object types and enough objects per type.
Where does ISCM sit in the RMF, SP 800-53 and CSF 2.0 today?
At RMF Step 6 Monitor, in control CA-7, and in the CSF 2.0 Detect function. SP 800-137 calls ISCM "a critical step in an organization's Risk Management Framework (RMF)," and its Figure 2-2 places it at Step 6, Monitor. That figure shows the six-step RMF of 2011; today's RMF, per our SP 800-37 guide, adds a seventh step, Prepare, from Revision 2 in 2018. The relationship is unchanged, but the step numbering in SP 800-137's diagrams is not the current count.
The 2011 text cites SP 800-53 controls of its time. In the current SP 800-53 Rev. 5 catalog, the ISCM ideas live in these places:
| Reference | What it requires |
|---|---|
| SP 800-53 CA-7 Continuous Monitoring | A system-level strategy with metrics, monitoring and assessment frequencies, ongoing assessments, correlation and analysis, response actions and status reporting |
| CA-7(3) Trend Analyses | Use empirical data to decide whether monitoring frequency and activities need to change |
| CA-7(4) Risk Monitoring | Effectiveness, compliance and change monitoring as part of the strategy |
| PM-31 Continuous Monitoring Strategy | The organization-wide strategy, the Tier 1 counterpart of CA-7 |
| RA-5 Vulnerability Monitoring and Scanning | Scan on a schedule "and when new vulnerabilities potentially affecting the system are identified and reported" |
| CSF 2.0 DE.CM Continuous Monitoring | DE.CM-01 networks, 02 physical environment, 03 personnel activity and technology usage, 06 external service providers, 09 hardware, software, runtime environments and their data |
CA-7's seven elements track the six-step process closely, which is why SP 800-137 remains the explanatory text behind it. CSF 2.0 (26 February 2024) states outcomes rather than frequencies; see our CSF 2.0 guide. ISCM also feeds the SP 800-53 catalog, KEV and EPSS prioritization and enterprise patch management. None of those signals help if an organization cannot say what it has deployed. For OT environments, see our SP 800-82 guide.
How does SP 800-137A assess an ISCM program?
With a catalog of assessment elements and a simple judgment scale. SP 800-137A, published May 2020, asks how effective an existing program is, not what it should look like. Its companion catalog holds 128 assessment elements, each with an assessment procedure; 89 of them (70 %) derive from SP 800-137 and 39 from other sources. The default judgment for each determination statement is two-valued, "Satisfied" or "Other than Satisfied," aligned with SP 800-53A, with annotations explaining any shortfall. Organizations may use a finer scale, such as "Somewhat True" or "Mostly False," to rank what to fix first. It is the document to pick up once a program from SP 800-137 is running.
Worked example: what does ISCM look like for a device maker's shipped firmware?
Synthetic example, not a real product. An industrial gateway maker has about 40,000 units in the field across six firmware versions. SP 800-137 is written for an organization's own systems, but its six steps fit the product fleet as well:
DefineManagement sets a tolerance: a component on the CISA KEV list in any supported version gets a fix or mitigation plan within 14 days. EstablishThree metrics: share of supported versions with a current SBOM; KEV-listed components per version; median days from advisory to fixed release. The SBOM inventory is volatile, so it is re-matched daily; the PSIRT procedure is reviewed yearly. ImplementEvery release build produces an SBOM, which is matched against NVD, KEV and supplier advisories. AnalyzeA new KEV entry for the TLS library triggers an event-driven assessment: four of six versions ship it, and two expose the affected function. RespondA fix for the two exposed versions; a VEX statement for the other two; customers informed. ReviewAfter six months the advisory-to-fix median has fallen, and the team adds the bootloader to the inventory it had missed.
How should a team start, and what are the pitfalls?
Write the strategy before buying toolsThe process starts with Define, not Implement. Pick metrics that trigger a decision, not metrics that are merely easy to collect. Set a frequency per control, using the Section 3.2.2 criteria, and write down why. Use sampling deliberately where full coverage isn't practical, documenting object types and sample sizes. Review the strategy on a schedule, not just after an incidentReview and Update is a standing step.
Common pitfalls:
- One frequency for everything. Volatile controls get under-checked and static ones over-checked.
- No event-driven trigger. A new KEV entry should start an assessment, not wait for the next cycle.
- Monitoring the network but not the products you ship. For a manufacturer, the fleet is the largest asset.
- Reading the 2011 control numbers as current. Map them to Rev. 5 first.
SoftWSP supplies one input to that kind of program: the component inventory and vulnerability matches for each firmware release. It extracts a CycloneDX 1.6 SBOM from the image, matches the components against NVD, CISA KEV, FIRST EPSS and CISA CSAF ICS advisories, and drafts a cited report that an engineer reviews; watchlist alerts on a CVE ID, vendor or product flag new advisories between scans. It does not set your risk tolerance, metrics or frequencies, and it does not monitor customer networks. See device & firmware security services and the firmware SBOM guide.
This guide summarises public NIST publications (SP 800-137, SP 800-137A, SP 800-53 Rev. 5 and CSF 2.0); it does not constitute legal or compliance advice. SP 800-137 is written for US federal information systems under FISMA but states it may be used voluntarily by other organizations.
Put this guide to work
Frequently asked questions
What is NIST SP 800-137?
NIST Special Publication 800-137, "Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations," published September 2011 by Kelley Dempsey, Nirali Shah Chawla, Arnold Johnson, Ronald Johnston, Alicia Clay Jones, Angela Orebaugh, Matthew Scholl and Kevin Stine. NIST's own CSRC publication page lists its status as "Final" with no superseding revision, so as checked for this guide it remains the current version. It was developed under NIST's FISMA statutory responsibilities for federal information systems, though NIST's text states it "may be used by nongovernmental organizations on a voluntary basis."
What is Information Security Continuous Monitoring (ISCM)?
The document defines it directly: "Information security continuous monitoring (ISCM) is defined as maintaining ongoing awareness of information security, vulnerabilities, and threats to support organizational risk management decisions." It is not a single tool or scan — SP 800-137 is explicit that "organization-wide monitoring cannot be efficiently achieved through manual processes alone or through automated processes alone," and that ISCM is most effective when automation is used where possible while recognizing many aspects cannot be easily automated.
What are the six steps of the ISCM process?
Per SP 800-137 Chapter 3: Define an ISCM strategy (based on risk tolerance, covering assets, vulnerabilities, threats and mission impact); Establish an ISCM program (metrics, monitoring and assessment frequencies, technical architecture); Implement the ISCM program (collect the security-related information needed for metrics and reporting, automating where possible); Analyze data and Report findings (determine the appropriate response, collecting more data if needed); Respond to findings (technical, management or operational mitigation, or acceptance/transference/avoidance of the risk); and Review and Update the monitoring program and strategy (adjusting metrics and maturing measurement capabilities over time).
How does ISCM fit into NIST's Risk Management Framework (RMF)?
SP 800-137 calls ISCM "a critical step in an organization's Risk Management Framework (RMF)," and its own Figure 2-2 maps ISCM onto RMF Step 6, Monitor. That figure shows a six-step RMF (Categorize, Select, Implement, Assess, Authorize, Monitor) because the document predates the 2018 Revision 2 of SP 800-37, which added a seventh step, Prepare (see our [NIST SP 800-37 RMF guide](/guides/nist-sp-800-37-risk-management-framework/)) — the step numbering in SP 800-137's own figures should be read as describing the pre-2018 RMF, not today's 7-step version, even though the ISCM-to-Monitor relationship itself is unchanged.
What is SP 800-137A, and is it different from SP 800-137?
SP 800-137A, "Assessing Information Security Continuous Monitoring (ISCM) Programs: Developing an ISCM Program Assessment," published May 2020, is a separate, complementary document. Where SP 800-137 defines the ISCM strategy and six-step process, SP 800-137A provides a methodology for assessing whether an organization's actual ISCM program is effective and complete — reviewing its strategies, policies, procedures, operations and the continuous monitoring data it produces. NIST's CSRC page lists it under "Related NIST Publications" for SP 800-137 rather than as a revision of it.
Sources
- NIST CSRC: SP 800-137, Information Security Continuous Monitoring (ISCM) — final publication page
- NIST: SP 800-137, Information Security Continuous Monitoring (ISCM) for Federal Information Systems and Organizations (full text, September 2011)
- NIST CSRC: SP 800-137A, Assessing Information Security Continuous Monitoring (ISCM) Programs — final publication page
- NIST: SP 800-137A, Assessing Information Security Continuous Monitoring (ISCM) Programs (full text, May 2020)
About this guide
SoftWSP Firmware Security Desk
Covers the Firmware vulnerabilities & fixes cluster: 131 guides.

In this cluster
Questions about this page?
