NIST SP 800-30, "Guide for Conducting Risk Assessments" — currently Revision 1 (September 2012) — structures a federal risk assessment around four activities: prepare, conduct, communicate, and maintain. Its own abstract states its purpose is to provide "guidance for conducting risk assessments of federal information systems and organizations, amplifying the guidance in Special Publication 800-39." Revision 1 superseded the original July 2002 edition and has not been updated since. Although written for US federal agencies, the risk model and four-activity process it defines are widely used outside government as a vendor-neutral way to structure a security risk assessment.
Key takeaways
- NIST SP 800-30, "Guide for Conducting Risk Assessments" — currently Revision 1 (September 2012) — structures a federal risk assessment around four activities: prepare, conduct, communicate, and maintain.
- SP 800-30 does not stand alone.
- NIST's own glossary, sourced to SP 800-30 Rev.
- Section 2.3 of the publication separates two choices that are often blurred.
What does "amplifying SP 800-39" mean?
SP 800-30 does not stand alone. NIST's companion publication, SP 800-39, "Managing Information Security Risk: Organization, Mission, and Information System View," sets out the broader program: an "integrated, organization-wide program for managing information security risk" built on "a structured, yet flexible approach," explicitly positioned as something that "can be used as part of a more comprehensive Enterprise Risk Management (ERM) program." SP 800-39 defines risk management as happening across three tiers — the organization, the mission/business process, and the information system — and names risk assessment as one of four components of that program, alongside framing, responding to, and monitoring risk. SP 800-30 is the detailed how-to guide for that one component: it tells you how to actually conduct a risk assessment, not how to run the rest of the program around it. See NIST SP 800-39 for the program layer.
The risk model: what feeds a risk level?
SP 800-30 builds a risk assessment from a defined set of inputs rather than a single subjective judgment call:
| Input | What it captures |
|---|---|
| Threat sources | The origin of a potential adverse event — adversarial, accidental, structural or environmental |
| Threat events | The specific event a threat source could cause |
| Vulnerabilities and predisposing conditions | Weaknesses that could be exploited, and conditions that make exploitation more or less likely |
| Likelihood | The probability a threat event occurs and results in an adverse impact |
| Impact | The magnitude of harm if the threat event succeeds |
NIST's own glossary, sourced to SP 800-30 Rev. 1 and reused verbatim across SP 800-37 Rev. 2, SP 800-39 and SP 800-171 Rev. 3, defines risk assessment as "the process of identifying risks to organizational operations (including mission, functions, image, reputation), organizational assets, individuals, other organizations, and the Nation, resulting from the operation of an information system," adding that it is synonymous with "risk analysis" and is "part of risk management" that "incorporates threat and vulnerability analyses, and considers mitigations provided by security controls" that are scheduled or already in place. That last clause matters in practice: a risk assessment under SP 800-30 is never purely theoretical likelihood-times-impact math — it has to account for the controls, such as those catalogued in NIST SP 800-53, that are already scheduled or in place.
The full text also asks assessors to state uncertainty openly. It lists four causes: limits on how far the future will resemble the past, incomplete knowledge of the threat, "undiscovered vulnerabilities in technologies or products," and unrecognised dependencies that lead to unforeseen impacts.
Which assessment and analysis approaches can you choose?
Section 2.3 of the publication separates two choices that are often blurred. The assessment approach is how values are expressed; the analysis approach is where the analysis starts.
| Choice | Options in SP 800-30 | What the text says about it |
|---|---|---|
| Assessment approach | Quantitative | Uses numbers whose meaning holds outside the assessment; best for cost-benefit analysis, but rigor drops when subjective judgments are buried in the numbers |
| Qualitative | Uses categories such as very low to very high; good for communicating with decision makers, but a small value range makes ranking hard | |
| Semi-quantitative | Uses bins or scales (for example 0–100) that map to qualitative terms; supports relative ranking within and across bins | |
| Analysis approach | Threat-oriented | Starts from threat sources and events and builds threat scenarios |
| Asset/impact-oriented | Starts from critical assets and the impacts of concern | |
| Vulnerability-oriented | Starts from predisposing conditions or exploitable weaknesses |
The publication warns that the starting point "can potentially bias the results," and recommends identifying risks "from a second orientation" to improve rigor. For a product team, a practical pairing is vulnerability-oriented (start from the SBOM and CVE matches) checked against asset/impact-oriented (start from what the device controls or protects).
What does the process look like: prepare, conduct, communicate, maintain?
SP 800-30's Chapter Three, "The Process," structures a risk assessment around four activities. It is worth being precise here, because NIST's own published abstract for the document describes this slightly differently — stating the guidance covers "each of the three steps in the risk assessment process (i.e., prepare for the assessment, conduct the assessment, and maintain the assessment)," treating communication as something that happens throughout rather than as its own numbered step. The document's chapter structure, by contrast, is commonly summarized as four distinct activities. Either framing describes the same underlying process:
| Step | What it involves |
|---|---|
| Prepare for the assessment | Identify the assessment's purpose, scope, assumptions and constraints, the information sources to use, and the risk model to apply |
| Conduct the assessment | Identify threat sources and events, vulnerabilities and predisposing conditions, likelihood of occurrence, and the resulting impact and risk |
| Communicate the results | Share the assessment's findings and supporting risk-related information with decision-makers who need it |
| Maintain the assessment | Monitor the risk factors identified in the assessment on an ongoing basis, and update the analysis as conditions change |
Assessments are not meant to be run once at a single scope. SP 800-39's three-tier model (organization, mission/business process, information system) means the same four-step process can run at each tier, with results from a system-level assessment rolling up to inform mission- and organization-level risk decisions, and organization-level risk tolerance decisions flowing back down to shape how lower-tier assessments are scoped.
Which tasks sit inside each step?
Chapter Three breaks the steps into 15 numbered tasks. The names below are condensed from the Rev. 1 text:
| Task | What you produce |
|---|---|
| 1-1 | The purpose: what information the assessment must produce and which decisions it supports |
| 1-2 | The scope: organisational applicability, time frame, architecture and technology |
| 1-3 | Assumptions and constraints |
| 1-4 | Sources of descriptive, threat, vulnerability and impact information |
| 1-5 | The risk model and analytic approach |
| 2-1 | Threat sources, with capability, intent and targeting for adversaries |
| 2-2 | Threat events, their relevance, and which sources could start them |
| 2-3 | Vulnerabilities and predisposing conditions |
| 2-4 | Likelihood that threat events result in adverse impacts |
| 2-5 | Adverse impacts |
| 2-6 | Risk, as a combination of impact and likelihood |
| 3-1 | Results communicated to decision makers |
| 3-2 | Risk-related information shared with the people who need it |
| 4-1 | Ongoing monitoring of risk factors |
| 4-2 | Updates to the assessment from that monitoring |
Appendices D to I give input tables, example taxonomies and assessment scales for tasks 2-1 to 2-6, Appendix K describes the report, and Appendix L summarises all tasks.
How do the scales and the risk matrix work?
Every exemplary scale in Appendices D to I uses the same five levels, each with a semi-quantitative range and a single score:
| Qualitative value | Semi-quantitative range | Score |
|---|---|---|
| Very High | 96–100 | 10 |
| High | 80–95 | 8 |
| Moderate | 21–79 | 5 |
| Low | 5–20 | 2 |
| Very Low | 0–4 | 0 |
Likelihood is built in two parts: the likelihood a threat event is initiated or occurs (Tables G-2 and G-3), and the likelihood it then causes an adverse impact (Table G-4). Table G-5 combines them into overall likelihood. Table I-2 then combines overall likelihood with impact (Table H-3) into the level of risk:
| Likelihood ↓ / Impact → | Very Low | Low | Moderate | High | Very High |
|---|---|---|---|---|---|
| Very High | Very Low | Low | Moderate | High | Very High |
| High | Very Low | Low | Moderate | High | Very High |
| Moderate | Very Low | Low | Moderate | Moderate | High |
| Low | Very Low | Low | Low | Low | Moderate |
| Very Low | Very Low | Very Low | Very Low | Low | Low |
The matrix is weighted towards impact: a very-high-likelihood event with low impact stays Low. NIST presents these tables as starting points to be tailored, not as fixed values.
Where does this sit next to the RMF and SP 800-53?
Risk assessment is not a one-off report; it is one recurring activity inside NIST's broader Risk Management Framework (RMF), described in SP 800-37. The RMF's steps include categorizing a system, selecting applicable controls from the SP 800-53 control catalogue, implementing and assessing those controls, authorizing the system to operate, and monitoring it continuously — and risk assessment, in the SP 800-30 sense, is the activity that informs several of those steps, not a separate process run in isolation. SP 800-37 Rev. 2 names this the RMF's "Assess" step, which evaluates whether the SP 800-53 controls selected for the system are implemented correctly and operating as intended. See NIST SP 800-37.
How can a device maker use SP 800-30 for the CRA risk assessment?
The EU Cyber Resilience Act requires manufacturers to "undertake an assessment of the cybersecurity risks associated with a product with digital elements" (Article 13(2)). Article 13(3) says it must be documented, updated "as appropriate during a support period," and must analyse risks "based on the intended purpose and reasonably foreseeable use, as well as the conditions of use." Article 13(4) puts it in the technical documentation. SP 800-30 does not give presumption of conformity with the CRA, but its tasks map cleanly onto those clauses:
| CRA wording | SP 800-30 task that produces it |
|---|---|
| Intended purpose, foreseeable use, conditions of use (Art. 13(3)) | 1-2 scope and 1-3 assumptions, written per product |
| Operational environment and assets to be protected (Art. 13(3)) | 2-1 threat sources and 2-5 impacts |
| Whether each Annex I Part I point (2) requirement applies, and how | 2-3 vulnerabilities and predisposing conditions, plus the controls considered in 2-4 |
| Placed on the market "without known exploitable vulnerabilities" (Annex I Part I (2)(a)) | 2-3 fed by SBOM matches against KEV and EPSS |
| Updated during the support period (Art. 13(3)) | 4-1 monitoring and 4-2 updates |
For industrial products, IEC 62443-3-2 and ISO/IEC 27005 cover the same ground; see CRA Annex I explained for the requirement list itself.
Worked example: what does one product-level risk entry look like?
Synthetic example. The product and ratings are invented to show how Tables G-5 and I-2 combine; they are not NIST values for any real device.
A Tier 3 assessment of a hypothetical Wi-Fi security camera, vulnerability-oriented, using the qualitative scales:
| Threat event | Initiation (G-2) | Adverse impact given initiation (G-4) | Overall likelihood (G-5) | Impact (H-3) | Risk (I-2) |
|---|---|---|---|---|---|
| Remote exploitation of a KEV-listed flaw in the embedded web server, reachable on the default configuration | High | High | High | High | High |
| Root shell through an unlocked debug UART on an installed unit | Low | Very High | Moderate | High | Moderate |
| Exploitation of a Bluetooth stack CVE on a variant with no radio fitted | Moderate | Very Low | Low | Moderate | Low |
The first row is the one to act on before release. The third row is still recorded: the assessment explains why the matched CVE does not lead to harm on this hardware, which is the evidence an auditor or a customer will ask for.
What should the report contain?
Appendix K suggests three parts, and stresses that its list is "informative and exemplary only":
- Executive summary: date, purpose, scope, whether this is an initial or follow-up assessment (with a reference to the previous report), the overall level of risk, and the number of risks at each level.
- Body: purpose and questions answered, assumptions and constraints, risk tolerance inputs, the risk model with its value scales and the rule for combining values, the rationale for risk-related decisions, the uncertainties and how they affect decisions, a description of the systems in scope, a summary of results, the time frame for which the assessment is valid, and the lists of adversarial and non-adversarial risks.
- Appendices: references and information sources, the team that ran the assessment, and the supporting tables needed to reuse the results in later assessments.
What are the common pitfalls?
- Working from the old edition. The July 2002 edition treated risk assessment as the first step of a risk management methodology; Rev. 1 replaced it in September 2012 with the task structure above. Check which edition a template or checklist follows.
- Undefined scale values. The text warns that unless each value is clearly defined, "different experts relying on their individual experiences could produce significantly different assessment results."
- One orientation only. Starting only from the CVE list misses design-level risks such as debug ports; starting only from assets misses third-party code.
- Skipping uncertainty. A rating with no stated confidence looks more certain than it is.
- No trigger for updates. Task 4-2 needs a rule for when the assessment is redone, such as a new KEV listing for a shipped component or a new hardware variant.
What is a workable starting point?
Separate "assessment" from "management."If your organization only has a risk register and no documented process for how entries get there, you have skipped the SP 800-30 layer SP 800-39 assumes exists underneath it. Name your tier before you startAn assessment scoped at the information-system level (a single product, a single firmware image) asks different questions than one scoped at the organization level — decide which one you are running before picking threat sources and impact criteria. Treat "maintain" as a standing commitment, not a wrap-up taskA risk assessment that is never revisited after the initial report stops reflecting reality the moment a new vulnerability, threat actor technique, or compensating control appears. Feed existing control evidence in, don't assess from zeroIf controls from SP 800-53 or an equivalent catalogue are already documented, use that evidence directly in the "mitigations provided by security controls" step rather than re-deriving it.
SoftWSP builds risk assessments on real firmware SBOM, CVE and fleet-exposure evidence rather than a generic questionnaire, so the "conduct the assessment" step starts from actual data instead of assumptions: see device firmware security. The platform extracts a CycloneDX 1.6 SBOM from firmware and matches it against NVD, the CISA KEV catalog, FIRST EPSS and CISA's CSAF ICS advisories, which supplies the inputs to tasks 2-3 and 2-4; the likelihood and impact ratings are set and reviewed by engineers.
This guide summarises a public NIST publication; it does not constitute legal or compliance advice.
Put this guide to work
Frequently asked questions
What is NIST SP 800-30?
Special Publication 800-30, "Guide for Conducting Risk Assessments," is a US National Institute of Standards and Technology (NIST) publication that, per its own abstract, provides "guidance for conducting risk assessments of federal information systems and organizations, amplifying the guidance in Special Publication 800-39." The current version is Revision 1, published in September 2012, which superseded the original July 2002 edition; it has not been revised since. Its listed author is Ron Ross of NIST.
What is the risk assessment process it defines?
The document's Chapter Three, "The Process," organizes risk assessment around four activities: preparing for the assessment (establishing purpose, scope, assumptions, constraints and the risk model to be used), conducting the assessment (identifying threat sources and events, vulnerabilities and predisposing conditions, likelihood and impact, and deriving the resulting risk), communicating the results to decision-makers, and maintaining the assessment over time by monitoring risk factors as conditions change. Note that SP 800-30's own published abstract describes this more narrowly as three steps — prepare, conduct, and maintain — treating communication as woven through the other steps rather than named as a fourth; both framings describe the same document, and a reader should expect secondary sources to count the steps either way.
How does SP 800-30 define risk, threat and vulnerability?
NIST's own glossary, sourced from SP 800-30 Rev. 1 and echoed in SP 800-37 Rev. 2, SP 800-39 and SP 800-171 Rev. 3, defines risk assessment as "the process of identifying risks to organizational operations (including mission, functions, image, reputation), organizational assets, individuals, other organizations, and the Nation, resulting from the operation of an information system," noting it is synonymous with risk analysis and "part of risk management" that "incorporates threat and vulnerability analyses, and considers mitigations provided by security controls" in place or intended for the system. SP 800-30's risk model builds that analysis from threat sources and threat events, vulnerabilities and predisposing conditions, likelihood of occurrence, and impact — combined to produce a level of risk.
How does SP 800-30 relate to SP 800-39 and the Risk Management Framework (SP 800-37)?
SP 800-30's own abstract states it amplifies SP 800-39, "Managing Information Security Risk: Organization, Mission, and Information System View," which sets out the broader, organization-wide risk management program; SP 800-30 is the detailed how-to for one part of that program, the risk assessment activity itself, performed at the organization, mission/business-process and information-system tiers SP 800-39 defines. Risk assessment is also one of the steps in the Risk Management Framework described in SP 800-37 Rev. 2 — the "Assess" step, which evaluates the security controls selected under SP 800-53 for the system.
Sources
- NIST: NIST Special Publication 800-30 Rev. 1, Guide for Conducting Risk Assessments — publication page
- NIST CSRC: SP 800-30 Rev. 1 — final publication page
- NIST CSRC Glossary: Risk Assessment (sourced to SP 800-30 Rev. 1)
- NIST CSRC: SP 800-39, Managing Information Security Risk — final publication page
- NIST: NIST.SP.800-30r1 — full text PDF
- NIST CSRC: SP 800-30 (July 2002, superseded) — publication page
- EUR-Lex: Regulation (EU) 2024/2847 (Cyber Resilience Act), Article 13 and Annex I
About this guide
SoftWSP Firmware Security Desk
Covers the Firmware vulnerabilities & fixes cluster: 127 guides.

In this cluster
Questions about this page?
