Framework · Security and privacy controls · US federal

NIST SP 800-53 Rev. 5: control families, baselines and assessment

NIST Special Publication 800-53 is the US catalogue of security and privacy controls for information systems. Revision 5 organises more than 1,000 controls and enhancements into 20 families. Federal agencies and FedRAMP use it with SP 800-53B baselines (low, moderate, high) and the Risk Management Framework to authorise systems.

Key takeaways

What you need to know about NIST 800-53

Control catalogue800-53 lists controls; you select a baseline and tailor it.
BaselinesSP 800-53B sets low, moderate and high baselines by system impact.
Security and privacyRev. 5 combines both and adds supply chain risk management.
FedRAMPCloud services selling to US agencies use 800-53 via FedRAMP.
AuthorizationThe outcome is an authorization to operate, not a certificate.

Who uses NIST 800-53?

It is mandatory for some and voluntary for many.

US federal agenciesRequired for federal information systems under FISMA.
Cloud providers selling to governmentFedRAMP baselines are built on 800-53.
Government contractorsContracts often flow 800-53 controls down.
Large enterprisesA detailed control catalogue for mature programmes.
State and local governmentMany states base their policies on it.

QULDEX helps here first: the readiness check shows where you stand before you commit budget.

20 control families

What does NIST 800-53 require?

NIST 800-53 requires you to select, tailor, implement and assess controls from its catalogue, based on the system's impact level. The Risk Management Framework (SP 800-37) sets the process from categorisation to continuous monitoring.

Prepare RMF 1

Prepare

Set roles, risk strategy and common controls.

In QULDEX: Programme setup recorded once
Categorize RMF 2

Categorize

Rate the system low, moderate or high (FIPS 199).

In QULDEX: Impact level per system
Select RMF 3

Select

Pick and tailor the baseline from SP 800-53B.

In QULDEX: Baseline loaded with tailoring notes
Implement RMF 4

Implement

Put controls in place and document them in the SSP.

In QULDEX: Controls with owners and evidence
Assess RMF 5

Assess

Test controls with SP 800-53A procedures.

In QULDEX: Assessment procedures per control
Authorize RMF 6

Authorize

An official accepts risk and grants an ATO.

In QULDEX: Authorization package assembled
Monitor RMF 7

Monitor

Track controls and changes continuously.

In QULDEX: POA&M items tracked in CAPA
20 control families

What are the NIST 800-53 control families?

Rev. 5 groups its controls into 20 families, each with a two-letter ID. Select any family to see what it covers, typical evidence and the matching ISO 27001 and NIST CSF controls.

20control families
1,000+controls and enhancements
3baselines plus privacy
2new families in Rev. 5

Showing up to 6 per group. Search, filter, or open a group to see all 20.

Access and people 4

  1. ACAccess control

    Limit system access to authorised users, processes and devices, including least privilege and remote access.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Access policies, reviews
    Maps to
    NIST CSF PR.AAISO 27001 A.5.15

  2. IAIdentification and authentication

    Identify and authenticate users, devices and services, including MFA.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    IdP and MFA settings
    Maps to
    NIST CSF PR.AAISO 27001 A.8.5

  3. PEPhysical and environmental protection

    Protect facilities, equipment and supporting infrastructure.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Facility access logs
    Maps to
    ISO 27001 A.7

  4. PSPersonnel security

    Screen people, manage terminations and transfers, and sign access agreements.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Screening and termination records
    Maps to
    ISO 27001 A.6.1A.6.5

System protection 4

  1. AUAudit and accountability

    Generate, protect and review audit records so actions can be traced.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Log configuration, reviews
    Maps to
    NIST CSF PR.PS-04ISO 27001 A.8.15

  2. CMConfiguration management

    Set baselines, control changes and keep an inventory of system components.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Baselines, change records
    Maps to
    NIST CSF PR.PSISO 27001 A.8.9

  3. SISystem and information integrity

    Find and fix flaws, protect against malicious code and monitor systems.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Patch and monitoring records
    Maps to
    NIST CSF DE.CMISO 27001 A.8.7A.8.8

  4. SCSystem and communications protection

    Protect communications and system boundaries, including encryption.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Boundary and encryption settings
    Maps to
    NIST CSF PR.DSPR.IRISO 27001 A.8.20–A.8.24

Risk and governance 4

  1. RARisk assessment

    Categorise systems, assess risk and scan for vulnerabilities.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Risk assessments, scans
    Maps to
    NIST CSF ID.RAISO 27001 6.1.2

  2. CAAssessment, authorization and monitoring

    Assess controls, authorise systems to operate and monitor continuously.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Assessment reports, ATO, POA&M
    Maps to
    NIST CSF ID.IM

  3. PLPlanning

    Write system security and privacy plans and rules of behaviour.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    System security plans
    Maps to
    ISO 27001 6.1

  4. PMProgram management

    Run the organisation-wide security and privacy programme.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Programme plans, risk strategy
    Maps to
    NIST CSF GV

Response and resilience 4

  1. IRIncident response

    Prepare for, detect, respond to and report incidents.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    IR plan, tests
    Maps to
    NIST CSF RS.MAISO 27001 A.5.24

  2. CPContingency planning

    Plan, back up and test recovery of systems.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Contingency plans, test results
    Maps to
    NIST CSF RC.RPISO 27001 A.5.29A.8.13

  3. MAMaintenance

    Control maintenance of systems, tools and personnel.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Maintenance records
    Maps to
    ISO 27001 A.7.13

  4. MPMedia protection

    Protect, sanitise and control access to media.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Sanitisation records
    Maps to
    ISO 27001 A.7.10A.7.14

Training, acquisition and privacy 4

  1. ATAwareness and training

    Train users and roles in security and privacy.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Training records
    Maps to
    NIST CSF PR.ATISO 27001 A.6.3

  2. SASystem and services acquisition

    Build security into acquisition and the development life cycle.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    SDLC and acquisition records
    Maps to
    ISO 27001 A.8.25–A.8.30

  3. SRSupply chain risk managementNew in Rev. 5

    Manage risks from suppliers, products and services across the supply chain.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Supplier risk assessments
    Maps to
    NIST CSF GV.SCISO 27001 A.5.19–A.5.21

  4. PTPII processing and transparencyNew in Rev. 5

    Process personally identifiable information with authority, purpose and transparency.

    In QULDEXQULDEX holds this family's controls with baseline tags, owners and assessment procedures, mapped to NIST CSF and ISO 27001.

    Typical evidence
    Privacy notices, PII inventories
    Maps to
    ISO 27701GDPR Art. 5

Family IDs and names follow NIST SP 800-53 Rev. 5. Groupings and summaries are QULDEX's; the NIST text is the authority.

Risk Management Framework

How do you implement NIST 800-53 and get an ATO?

Follow the Risk Management Framework: categorise the system, select and tailor a baseline, implement and assess controls, then an authorising official grants an authorization to operate. A first ATO commonly takes 6 to 18 months.

  1. Prepare and categorise the system

    Set roles and risk strategy, then rate the system's impact using FIPS 199.

  2. Select and tailor the baseline

    Start from the SP 800-53B baseline and tailor controls with documented rationale.

  3. Implement controls and write the SSP

    Put controls in place and describe each one in the system security plan.

  4. Assess controls

    An assessor tests controls with SP 800-53A procedures and writes the security assessment report.

  5. Authorize

    The authorising official reviews the package and the POA&M, then grants an ATO.

  6. Monitor continuously

    MonthlyPOA&M updates, scans
    YearlyAssess a subset of controls
    On changeSecurity impact analysis

Durations are typical planning ranges. FedRAMP adds its own process and assessors (3PAOs).

Authorization package

What documents does an 800-53 authorization need?

Authorising officials decide based on the authorization package. These are its core parts.

DocumentSourceWhere it lives in QULDEX
System security and privacy plan (SSP)SP 800-18, PL familyEvidence vault
Security categorisationFIPS 199Program setup
Security assessment plan and reportSP 800-53A, CA familyAudit workspace
Plan of action and milestones (POA&M)CA-5CAPA automation
Contingency plan and test resultsCP familyEvidence vault
Incident response planIR familyEvidence vault
Configuration management planCM familyEvidence vault
Supply chain risk management planSR familyVendor register
Authorization decision (ATO letter)RMF Authorize stepSecure report sharing

FedRAMP packages use FedRAMP templates built on the same structure.

Time and cost

How long does NIST 800-53 take and what drives the effort?

A first authorization commonly takes 6 to 18 months. The impact level drives effort most: a high baseline has far more controls than a low one.

Where the time goes

Prepare and categorise2–6 wk
Select and tailor2–4 wk
Implement and SSP3–9 mo
Assess1–3 mo
Authorize2–6 wk

Bars show the upper end of each range on one scale (9 months = full width).

What changes the effort

  • Impact level: moving from low to moderate to high adds many controls
  • System boundary: more components and interconnections mean more evidence
  • Inherited controls: cloud providers' FedRAMP controls can be inherited
  • Existing ISO 27001: reused controls cut implementation effort
  • Privacy baseline: PII processing adds PT family controls
Readiness check · 2 minutes

How ready are you for an 800-53 assessment?

Assessors check these eight things first. Nothing you enter leaves this page.

RA-2Have you categorised the system as low, moderate or high?
PL-2Is the system security plan complete and current?
CM-8Is the system component inventory current?
AC-2Are accounts managed and reviewed?
IA-2Is MFA enforced for privileged and network access?
AU-6Are audit records reviewed regularly?
CP-4Has the contingency plan been tested this year?
CA-5Is the POA&M current with owners and dates?
Crosswalk

How NIST 800-53 maps to NIST CSF 2.0 and ISO 27001

NIST publishes mappings from 800-53 to the Cybersecurity Framework and to ISO 27001. One implemented control can provide evidence for all three.

NIST 800-53 vs NIST CSF 2.0

NIST SP 800-53NIST CSF 2.0
TypeDetailed control catalogueHigh-level outcome framework
Size1,000+ controls and enhancements106 subcategories
SelectionBaselines by impact levelProfiles by priority
Typical usersFederal systems, FedRAMP, contractorsAny organisation
OutcomeAuthorization to operateCurrent and target profiles
In QULDEXQULDEX maps 800-53 controls to CSF subcategories so one evidence set supports both.

Family crosswalk

NIST 800-53NIST CSF 2.0ISO 27001:2022SOC 2Shared evidence
AC Access controlPR.AAA.5.15 · A.8.3CC6.1–CC6.3Access reviews
AU AuditPR.PS-04 · DE.CMA.8.15CC7.2Log reviews
CM ConfigurationPR.PSA.8.9 · A.8.32CC8.1Baselines, changes
CP ContingencyRC.RPA.5.29 · A.8.13A1.2–A1.3Recovery tests
IA AuthenticationPR.AAA.8.5CC6.1MFA settings
IR IncidentsRS.MAA.5.24–A.5.26CC7.3–CC7.5IR records
RA Risk assessmentID.RA6.1.2 · A.8.8CC3.2Risk assessments
SR Supply chainGV.SCA.5.19–A.5.21CC9.2Supplier assessments
AT TrainingPR.ATA.6.3CC1.4Training records

Indicative mapping. NIST publishes official 800-53 to CSF and ISO 27001 mappings; the full crosswalk is in the QULDEX control library.

Where QULDEX fits

How QULDEX runs NIST 800-53 from baseline to ATO

QULDEX is NIST 800-53 compliance and audit management software built from EGV Group's audit delivery, used by system owners and the assessors who test them. Pick your role to see who does what.

For agencies, contractors and cloud providers.

  1. CategorizeRate the systemImpact level recorded per system
  2. SelectTailor the baselineBaseline with tailoring rationale
  3. ImplementDocument controlsSSP sections linked to evidence
  4. AssessSupport the assessorControlled, logged evidence sharing
  5. AuthorizeAssemble the packagePackage built from live records
  6. MonitorKeep the ATOPOA&M tracked in CAPA
Without one systemWith QULDEX
SSP in a Word document nobody can updateSSP sections linked to live evidence
POA&M in a spreadsheetPOA&M items tracked with owners and dates
Separate work for 800-53, CSF and ISO 27001One control set mapped to all three
Evidence emailed to assessorsControlled, logged sharing
10+years of audit delivery500+audits deliveredBoth sidesof the audit on one platformRBACand a full audit trail on every action
FAQ

NIST 800-53 questions people ask

What is NIST SP 800-53?

A catalogue of security and privacy controls for information systems, published by NIST. Federal agencies must use it, and many others adopt it voluntarily.

How many control families are in NIST 800-53 Rev. 5?

20, from Access Control (AC) to Supply Chain Risk Management (SR). Rev. 5 added PII Processing and Transparency (PT) and Supply Chain Risk Management (SR).

What are the NIST 800-53 baselines?

SP 800-53B defines low, moderate and high security baselines by system impact, plus a privacy baseline. You tailor the baseline to your system.

What is the difference between NIST 800-53 and NIST CSF?

800-53 is a detailed control catalogue; CSF is a high-level outcome framework. NIST maps one to the other.

Can you be NIST 800-53 certified?

No. Systems receive an authorization to operate (ATO) from an authorising official after assessment. FedRAMP authorizes cloud services on 800-53 baselines.

What is the Risk Management Framework?

The seven-step process in SP 800-37: prepare, categorise, select, implement, assess, authorise and monitor.

Can QULDEX run NIST 800-53 alongside ISO 27001?

Yes. Controls are mapped once to ISO 27001, NIST CSF and SOC 2, so one evidence set supports each.

Sources

References

  1. NIST SP 800-53 Rev. 5, Security and Privacy Controls for Information Systems and Organizations. nist.gov
  2. NIST SP 800-53B, Control Baselines. nist.gov
  3. NIST SP 800-53A Rev. 5, Assessing Security and Privacy Controls. nist.gov
  4. NIST SP 800-37 Rev. 2, Risk Management Framework. nist.gov
  5. FIPS 199, Standards for Security Categorization. nist.gov

Reviewed by

Abhishek Yadav

Lead Auditor · QULDEX

Reviewed this page against NIST SP 800-53 Rev. 5, 800-53B and 800-37: families, baselines, RMF path and crosswalk.

Page history
  • : Rebuilt with the 20 families, RMF path, authorization package, crosswalk and readiness check
  • : Page first published

Find your NIST 800-53 gaps in 15 minutes

Answer a short readiness check and get a gap summary by family. No sales call needed to see the result.

Schedule
Book a Demo