Study guide
2.3 System Categorization Process & Impact Analysis (FIPS 199 / SP 800-60)
ISC2 Certified in Governance, Risk and Compliance CGRC
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
0.1 ISC2 CGRC Exam Structure, Logistics & Passing Strategy 0.2 NIST RMF 7-Step Lifecycle & GRC Architecture
2 Chapter 1: Security and Privacy Governance, Risk Management, and Compliance Program
1.1 Enterprise Governance & GRC Frameworks 1.2 Security and Privacy Objectives: CIA, Non-Repudiation and Privacy Concepts 1.3 Multi-Tier Risk Management & Assessment Methodologies 1.4 System Development Life Cycle and Information Life Cycle Management 1.5 Establishing and Operating the Compliance Program 1.6 Legal, Regulatory & Federal Compliance Drivers 1.7 Privacy Governance, Organizational Roles & ISC2 Code of Ethics
3 Chapter 2: Scope of the System
2.1 System Boundary Definition, Architectural Context & Types 2.2 Identifying Information Types with NIST SP 800-60 2.3 System Categorization Process & Impact Analysis (FIPS 199 / SP 800-60) 2.4 Impact and Risk Determination Under Non-Federal Frameworks 2.5 System Registration, Environment & Interconnection Agreements
4 Chapter 3: Selection and Approval of Framework, Security, and Privacy Controls
3.1 Control Catalogs & NIST SP 800-53 Rev. 5 Structure 3.2 Control Allocation & Inheritance Models 3.3 Control Tailoring, Scoping & Overlay Guidance 3.4 Data Handling and Marking Requirements 3.5 Documenting Control Selection and Securing Stakeholder Agreement 3.6 Continuous Monitoring Strategy & Control Selection Approval
5 Chapter 4: Implementation of Security and Privacy Controls
4.1 Developing the Implementation Strategy: Resourcing, Funding and Timeline 4.2 Identifying Control Types: Management, Operational, Technical and Functional Classes 4.3 System Security and Privacy Plan (SSP/SSPP) Development 4.4 Security Engineering Principles & Technical Control Implementation 4.5 Secure Baseline Configuration & System Hardening 4.6 Implementing Compensating and Alternate Controls 4.7 DevSecOps, SDLC Integration & Supply Chain Risk Management 4.8 Documenting Control Implementation: Policies, Procedures, Plans and Risk Registers
6 Chapter 5: Assessment/Audit of Security and Privacy Controls
5.1 Security Assessment Plan (SAP) & Assessor Independence 5.2 Assessment Methods, Objects & Depth/Coverage 5.3 Assessment Execution, Vulnerability Scanning & Testing 5.4 Preparing the Initial Assessment/Audit Report 5.5 Selecting Risk Responses: Avoid, Accept, Share, Mitigate, Transfer 5.6 Stakeholder Collaboration, Corrective Action and Reassessment 5.7 Security Assessment Report (SAR) & Risk Findings Analysis 5.8 Developing the Risk Response Plan: Prioritization and Resources
7 Chapter 6: System Compliance and Authorization
6.1 The Core Authorization Package & Supporting Artifacts 6.2 Plan of Action and Milestones (POA&M) Architecture & Management 6.3 System Risk Acceptance Criteria and Stakeholder Concurrence 6.4 Authorization Decision Process & Decision Types 6.5 Residual Risk Acceptance, Terms of Authorization & Continuous ATO 6.6 Documenting and Communicating the Compliance Decision
8 Chapter 7: Compliance Maintenance and Continuous Monitoring
7.1 Continuous Monitoring Strategy & Operations (NIST SP 800-137) 7.2 Configuration Management & Security Impact Analysis (NIST SP 800-128) 7.3 Incident Response and Contingency Activities in Sustained Compliance 7.4 Awareness, Training, Evidence Collection and Monitoring-Strategy Revision 7.5 Ongoing Remediation, POA&M Sustainment & Annual Reviews 7.6 Event-Driven Reauthorization & System Decommissioning
2.3 System Categorization Process & Impact Analysis (FIPS 199 / SP 800-60)
Key Takeaways Explain This Topic AI
FIPS 199 establishes mandatory federal standards for categorizing information and information systems across three security objectives: Confidentiality, Integrity, and Availability.
Potential impact levels under FIPS 199 are strictly defined as Low (limited adverse effect), Moderate (serious adverse effect), and High (severe or catastrophic adverse effect).
NIST SP 800-60 Rev. 1 provides a systematic two-volume process to map specific government information types to provisional security categories and tailor them based on operational context.
The overall System Security Category is determined using the High-Water Mark (HWM) rule, where the system category equals the highest rating assigned across the three security objectives for all hosted information types.
Special data classifications, such as PII, Controlled Unclassified Information (CUI per NIST SP 800-171), and National Security Systems (CNSSI 1253), introduce specialized categorization baselines and non-watermark overlays.
Last updated: August 2026
System Categorization Process & Impact Analysis (FIPS 199 / SP 800-60)
Core Blueprint Focus: System categorization is the initial operational step (Step 1) of the NIST RMF. It dictates the entire baseline security and privacy control allocation (NIST SP 800-53 Rev. 5). Categorizing too low creates severe organizational vulnerability and non-compliance; categorizing too high wastes millions of dollars implementing unnecessary controls.
Categorization is governed primarily by two mandatory federal publications:
FIPS Publication 199 ( Standards for Security Categorization of Federal Information and Information Systems ): Establishes the definitions of security objectives and potential impact levels.
NIST SP 800-60 Rev. 1 ( Guide for Mapping Types of Information and Information Systems to Security Categories , Volumes I & II): Provides the execution methodology and catalog of information types aligned with the Federal Enterprise Architecture (FEA).
The FIPS 199 Triad: Objectives & Impact Levels
FIPS 199 evaluates risk across the three fundamental pillars of information security, assigning an impact rating to each objective:
Confidentiality: Preserving authorized restrictions on information access and disclosure, including means for protecting personal privacy and proprietary information. A loss of confidentiality is the unauthorized disclosure of information.
Integrity: Guarding against improper information modification or destruction, including ensuring information non-repudiation and authenticity. A loss of integrity is the unauthorized modification or destruction of information.
Availability: Ensuring timely and reliable access to and use of information. A loss of availability is the disruption of access to or use of information or an information system.
FIPS 199 Potential Impact Levels
FIPS 199 defines three precise, standardized levels of potential impact on organizational operations (mission, functions, image, or reputation), organizational assets, or individuals:
Impact Level Statutory Definition (FIPS 199) Operational & Real-World Consequences
LOW The loss of confidentiality, integrity, or availability could be expected to have a limited adverse effect on organizational operations, organizational assets, or individuals. • Causes a minor degradation in mission capability to the point where the organization can perform primary functions, but effectiveness is noticeably reduced.; • Results in minor damage to organizational assets.; • Incurs minor financial loss.; • Results in minor harm to individuals (e.g., minor inconvenience, no financial distress, no physical injury).
MODERATE The loss of confidentiality, integrity, or availability could be expected to have a serious adverse effect on organizational operations, organizational assets, or individuals. • Causes a significant degradation in mission capability to the point where the organization can perform primary functions, but effectiveness is significantly reduced.; • Results in significant damage to organizational assets.; • Incurs significant financial loss.; • Results in significant harm to individuals that does not involve loss of life or serious life-threatening injuries (e.g., substantial financial loss, significant identity theft, severe privacy violation).
HIGH The loss of confidentiality, integrity, or availability could be expected to have a severe or catastrophic adverse effect on organizational operations, organizational assets, or individuals. • Causes a severe degradation in or total loss of mission capability to the point where the organization cannot perform one or more primary functions.; • Results in major damage to organizational assets.; • Incurs catastrophic financial loss.; • Results in severe harm to individuals involving loss of life or serious, life-threatening injuries , or complete destruction of personal livelihood.
NIST SP 800-60 Rev. 1 Categorization Methodology
NIST SP 800-60 Rev. 1 bridges abstract impact definitions and concrete operational data types through a four-step execution process: +-----------------------------------------------------------------------------------+
- | NIST SP 800-60 CATEGORIZATION METHODOLOGY |
- | |
- | [ Step 1: Identify Info Types ] |
- | • Inventory all data processed, stored, transmitted (FEA Business Ref Model) |
- | | |
- | v |
- | [ Step 2: Select Provisional Impact Levels ] |
- | • Consult SP 800-60 Vol. II for baseline C-I-A values per info type |
- | | |
- | v |
- | [ Step 3: Review & Adjust Provisional Levels ] |
- | • Assess contextual factors: aggregation risk, mission criticality, public data |
- | | |
- | v |
- | [ Step 4: Determine Overall System High-Water Mark ] |
- | • SC system = {(C, max), (I, max), (A, max)} => System Baseline Determination |
- +-----------------------------------------------------------------------------------+
- Step 1: Identify Information Types
The system owner and security team inventory all distinct types of information input, stored, processed, or output by the system. NIST SP 800-60 Volume II maps these to standard government mission lines (e.g., C.2.4 Financial Management , C.3.5 Health Care Records , D.1.1 Human Resource Management , D.16.1 Information Security ).
Step 2: Select Provisional Impact Levels
For each identified information type, the team looks up the baseline recommended provisional impact ratings in NIST SP 800-60 Vol. II. For example, Public Relations data may be provisionally rated as {(Confidentiality, Low), (Integrity, Moderate), (Availability, Low)} , whereas Payroll Information may be provisionally rated as {(Confidentiality, Moderate), (Integrity, Moderate), (Availability, Moderate)} .
Step 3: Review and Adjust Provisional Impact Levels
Provisional ratings are not final. The organization must adjust levels based on specific contextual and environmental realities:
Aggregation Risk: Large aggregations of otherwise low-impact data records (e.g., millions of public employee directory records or non-sensitive log entries) can represent a high-value target when correlated, justifying an upward adjustment for Confidentiality.
Criticality to Mission Function: If a specific system's downtime will immediately ground national airspace or halt emergency first responder dispatch, the Availability rating must be adjusted upward to High.
Public Information Exception: For data intentionally published for public consumption (e.g., weather reports, public press releases), Confidentiality is explicitly designated as Not Applicable (NA) or Low, while Integrity often remains Moderate or High to prevent unauthorized defacement or disinformation.
Step 4: Determine the Overall System Security Category (High-Water Mark)
The security category of an information system is expressed as an ordered set containing the maximum impact rating for each security objective across all contained information types: SC system = { ( Confidentiality , max ( C i ) ) , ( Integrity , max ( I i ) ) , ( Availability , max ( A i ) ) } \text{SC}_{\text{system}} = \{ (\text{Confidentiality}, \max(C_i)), (\text{Integrity}, \max(I_i)), (\text{Availability}, \max(A_i)) \} SC system = {( Confidentiality , max ( C i )) , ( Integrity , max ( I i )) , ( Availability , max ( A i ))}
High-Water Mark Calculation Example
Consider an enterprise human resources and operational logistics system hosting three distinct information types:
- Information Type Confidentiality Impact Integrity Impact Availability Impact
- 1. Public Job Postings Low (Publicly available) Moderate (Prevent tampering) Low (Short outage tolerable)
2. Employee PII & Payroll Moderate (Privacy Act data) Moderate (Accurate disbursement) Moderate (Payroll deadlines)
3. Emergency Disaster Dispatch Low (Unclassified operations) Moderate (Data accuracy) High (Life safety communication)
System High-Water Mark MODERATE MODERATE HIGH
In this scenario, the resulting system category is: SC HR-Logistics = { ( Confidentiality , MODERATE ) , ( Integrity , MODERATE ) , ( Availability , HIGH ) } \text{SC}_{\text{HR-Logistics}} = \{ (\text{Confidentiality}, \text{MODERATE}), (\text{Integrity}, \text{MODERATE}), (\text{Availability}, \text{HIGH}) \} SC HR-Logistics = {( Confidentiality , MODERATE ) , ( Integrity , MODERATE ) , ( Availability , HIGH )}
Because the highest individual water mark across the entire triad is HIGH (driven by Availability), the system is classified as an overall FIPS 199 HIGH-impact system . Under NIST SP 800-53 Rev. 5, the initial baseline control selection will default to the High baseline, which can subsequently be tailored during RMF Step 2 (Select).
Special Data Classifications & Regulatory Overlays
When performing categorization, GRC practitioners must account for specific legal regimes and data classifications:
Personally Identifiable Information (PII) & Privacy
Under the Privacy Act of 1974 and OMB Circular A-130 , systems maintaining PII must undergo a Privacy Threshold Analysis (PTA) and, if PII is confirmed, a full Privacy Impact Assessment (PIA) . The potential harm to individuals from identity theft, financial ruin, or harassment must directly influence the FIPS 199 Confidentiality impact level.
Controlled Unclassified Information (CUI)
Governed by Executive Order 13556 and 32 CFR Part 2002 , CUI is sensitive federal information requiring safeguarding and dissemination controls. Systems processing CUI (e.g., defense contractors subject to NIST SP 800-171 or CMMC) typically mandate a minimum baseline of FIPS 199 Moderate across Confidentiality and Integrity.
National Security Systems (NSS) & CNSSI 1253
Systems processing classified or national security information are governed by CNSSI 1253 ( Security Categorization and Control Selection for National Security Systems ). Unlike civilian NIST RMF systems, CNSSI 1253 does NOT use a single global high-water mark to select all controls. Instead, it selects controls independently for each objective (Confidentiality, Integrity, Availability), allowing precise control baseline mapping.
Categorization Traps & Critical Governance Rules
Important
Categorization Represents Inherent Risk, NOT Residual Risk: A common mistake is attempting to downgrade a system's FIPS 199 categorization because the system has implemented strong firewalls, multifactor authentication, or encryption. Categorization reflects the inherent potential harm if the information or system were compromised, completely independent of whatever security controls are currently deployed.
Warning
Over-Categorization Pitfall: Unjustifiably assigning a "High" categorization to a system whose true impact is Moderate inflates control implementation and assessment costs by 300% to 500%, requiring continuous monitoring tools, multi-site hardware failovers, and invasive physical controls that may be entirely disproportionate to actual mission risk.