Security executive reviewing an assessment in his office

FIPS 199Security categorization

NIST 800-53 baselines and FIPS 199, explained

Your impact level decides your baseline, and your baseline decides how many controls you must meet. Here is how it works.

25+ yearsIT and cybersecurity leadership
CISO, CISSPC|CISO certified assessor
Southern CaliforniaOn-site from Irvine
NationwideRemote assessments
Engineers checking controls on laptops in a data center
287controls and enhancements in the Moderate baseline

The short version

Categorize the system, then pick the baseline

NIST SP 800-53 is a catalog, not a list of everything you must do. The work starts with security categorization under FIPS 199: you rate the potential impact on your organization and the people you serve if the system’s confidentiality, integrity or availability were lost. Each of the three is rated Low, Moderate or High.

The highest of the three ratings becomes the system’s overall impact level, a rule often called the high-water mark. That level selects one of the three control baselines published in NIST SP 800-53B. A Moderate system starts from the Moderate baseline, then tailors it to its own technology, mission and risk.

Getting this right decides the size of everything that follows. Our NIST 800-53 assessment confirms your categorization and tests the controls in the baseline you select.

FIPS 199 impact levels

What Low, Moderate and High mean

FIPS 199 defines each level by the potential adverse effect of a loss of confidentiality, integrity or availability.

Impact levelPotential adverse effectExample of what that looks like
LowLimited adverse effect on operations, assets or individualsA short outage of an internal tool with minor inconvenience and no sensitive data
ModerateSerious adverse effectExposure of personal information, significant financial loss or a major disruption to a service customers depend on
HighSevere or catastrophic adverse effectLoss of life, major financial ruin or failure of a critical mission

The overall impact level is the highest rating across confidentiality, integrity and availability. Examples are illustrative; your own categorization depends on your information types and mission.

SP 800-53B baselines

How many controls each baseline selects

BaselineControls and enhancementsWhat changes as you move up
Low149Core controls in every family: basic access control, logging, backup, incident response and policies
Moderate287Adds most control enhancements: MFA for more access, stronger logging and monitoring, configuration baselines, alternate processing and supply chain controls
High370Adds the strongest enhancements: more automation, tighter monitoring, faster response and stronger physical and continuity protection
Privacy96A separate baseline applied when the system processes personally identifiable information

Source: NIST SP 800-53B. The baselines are cumulative: Moderate includes Low, and High includes Moderate. SP 800-53 Release 5.2.0 (August 27, 2025) made no changes to the baselines.

Tailoring

From baseline to the controls you actually assess

01

Identify common controls

Mark controls inherited from your cloud provider or provided centrally by the organization.

02

Scope

Remove or adjust controls that truly do not apply to your technology, with a written reason.

03

Set parameters

Fill in the organization-defined values, such as how often access is reviewed.

04

Compensate

Where a control cannot be met as written, document an equivalent control.

05

Supplement

Add controls or overlays when your risk or customer requires more than the baseline.

Every tailoring decision belongs in the system security plan. Without a record, an assessor will treat a removed control as a gap.

Common mistakes

Where baseline decisions go wrong

Three patterns we see before assessments start.

Choosing Low to save effort

A system that stores personal information, payment data or anything a customer depends on is rarely Low. Under-categorizing does not reduce risk; it only hides it until a customer or incident exposes it.

Treating the baseline as the whole job

The baseline is a minimum. Organization-defined parameters left blank, inherited controls never confirmed and missing enhancements are all findings in a real assessment.

Forgetting what changed

A system categorized years ago may now hold more sensitive data or support more customers. Revisit the categorization after every major change, and update the plan with it.

How the sample handled it

The fictional organization in our sample report runs a case-management platform at FIPS 199 Moderate. Its focused assessment covered 35 Moderate-baseline controls in nine families, with the remaining families recommended for a second phase.

Ali Hassani, CISO and CISSP, founder of OC Security Audit

Who leads the assessment

Led by Ali Hassani, CISO

Certified CISO (C|CISO) and CISSP with 25+ years in IT, cybersecurity, compliance and infrastructure, and dozens of Microsoft and Cisco certifications, including MCSE, MCITP, MCSA Security, CCNP and CCNA.

Ali reviews your categorization with you before a single control is tested, so the assessment measures the right baseline and the result holds up when a customer asks why.

FAQ

Questions about this page

What is FIPS 199?

FIPS 199 is the federal standard for security categorization. It rates the potential impact of losing confidentiality, integrity or availability as Low, Moderate or High, and the highest of the three sets the system's overall impact level.

How many controls are in the Moderate baseline?

The SP 800-53B Moderate baseline selects 287 controls and control enhancements. Low selects 149 and High selects 370.

Which baseline do most businesses use?

Moderate is the most common, because most business systems hold data whose loss would have a serious adverse effect. Low is for systems with only limited potential harm.

Can we remove controls from the baseline?

Yes, through tailoring, when a control truly does not apply. Each decision must be justified and recorded in the system security plan, or an assessor will treat it as a gap.

Did the 2025 release change the baselines?

No. NIST SP 800-53 Release 5.2.0, issued August 27, 2025, added new controls and enhancements to the catalog but made no changes to the SP 800-53B baselines.

ocsa pa2 h three pros tablet racks

Confirm your baseline before you invest in controls

We will review your categorization and assess the controls your baseline selects, then rank every gap by risk.

Or call 949-777-5567