ra-2-1-impact-level-prioritization

name	RA-2(1)_impact-level-prioritization
description	Conduct an impact-level prioritization of organizational systems to obtain additional granularity on system impact levels.
category	information-gathering
version	5.2.0
author	cyberstrike-official
tags	["nist","sp800-53","rev5","ra-2-1","ra","enhancement"]
tech_stack	["any"]
cwe_ids	[]
chains_with	[]
prerequisites	["RA-2"]
severity_boost	{}

RA-2(1) Impact-level Prioritization

Enhancement of: RA-2

High-Level Description

Family: Risk Assessment (RA) Framework: NIST SP 800-53 Rev 5

Organizations apply the "high-water mark" concept to each system categorized in accordance with FIPS 199 , 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 for security objective-related categorization.

What to Check

• Verify RA-2(1) Impact-level Prioritization is documented in SSP
• Confirm control is operating effectively
• Review evidence of continuous monitoring for RA-2(1)
• Verify enhancement builds upon base control RA-2

How to Test

Step 1: Review Documentation

Examine the System Security Plan (SSP) and related artifacts for RA-2(1) implementation details. Verify the organization has documented how this control is satisfied.

Step 2: Validate Implementation

# For cloud environments, use cloud-audit-mcp tools
# For on-premises, review system configurations directly

# Example: Check if account management policies exist
grep -r "account.management\|access.control" /etc/security/ 2>/dev/null

Step 3: Test Operating Effectiveness