NIST 800-53 REV 5 • RISK ASSESSMENT

RA-2(1)Impact-level Prioritization

Conduct an impact-level prioritization of organizational systems to obtain additional granularity on system impact levels.

CMMC Practice Mapping

No direct CMMC mapping

NIST 800-171 Mapping

No direct NIST 800-171 mapping

Related Controls

No related controls listed

Supplemental Guidance

Organizations apply the "high-water mark" concept to each system categorized in accordance with [FIPS 199](#628d22a1-6a11-4784-bc59-5cd9497b5445) , resulting in systems designated as low impact, moderate impact, or high impact. Organizations that desire additional granularity in the system impact designations for risk-based decision-making, can further partition the systems into sub-categories of the initial system categorization. For example, an impact-level prioritization on a moderate-impact system can produce three new sub-categories: low-moderate systems, moderate-moderate systems, and high-moderate systems. Impact-level prioritization and the resulting sub-categories of the system give organizations an opportunity to focus their investments related to security control selection and the tailoring of control baselines in responding to identified risks. Impact-level prioritization can also be used to determine those systems that may be of heightened interest or value to adversaries or represent a critical loss to the federal enterprise, sometimes described as high value assets. For such high value assets, organizations may be more focused on complexity, aggregation, and information exchanges. Systems with high value assets can be prioritized by partitioning high-impact systems into low-high systems, moderate-high systems, and high-high systems. Alternatively, organizations can apply the guidance in [CNSSI 1253](#4e4fbc93-333d-45e6-a875-de36b878b6b9) for security objective-related categorization.

Practitioner Notes

Impact-level prioritization means that during contingency situations or when resources are limited, you focus recovery and protection efforts on the highest-impact systems first.

Example 1: Create a prioritized system recovery list ranked by security categorization and mission criticality. During an incident, your team knows to restore the 'High' impact systems before the 'Moderate' systems. Document this priority order in your contingency plan and incident response procedures.

Example 2: In your patch management process, use impact level to prioritize which systems get patched first. Critical vulnerabilities on high-impact systems are patched within 24-48 hours; the same vulnerability on a low-impact system might have a 7-day window. Document these timelines in your vulnerability management procedure.