OneClickComply
    NIST SP 800-171 Rev. 3Supported in OneClickComply

    Get ready for NIST 800-171 Rev. 3 before your contracts require it

    NIST SP 800-171 Rev. 3 is the May 2024 revision of NIST's security requirements for protecting Controlled Unclassified Information (CUI) in non-federal systems and organisations. It replaces Rev.

    See the NIST 800-171 Rev. 3 requirements
    NIST 800-171 Rev. 3 mapped
    Automated evidence
    Continuous monitoring
    Who needs NIST 800-171 Rev. 3

    Is NIST 800-171 Rev. 3 right for your organisation?

    2's 110 requirements with 97 requirements in 17 families, aligned with NIST SP 800-53 Rev. 5. It also introduces organisation-defined parameters (ODPs), which let the contracting agency set values such as time periods and frequencies.

    Rev. 3 applies to non-federal organisations, such as defence contractors, research universities and service providers, when a federal agency contract or agreement requires CUI to be protected to this revision. US Department of Defense contracts currently still require Rev. 2 under a 2024 class deviation to DFARS 252.204-7012, so most defence suppliers use Rev. 3 to plan their transition rather than as their contractual baseline today.

    It is usually required by customers, partners or schemes rather than by law.

    How we help

    How OneClickComply helps with NIST 800-171 Rev. 3

    NIST SP 800-171 Rev. 3 is supported in OneClickComply today, so you can work towards it on the same controls you use for Rev. 2, ISO 27001 or SOC 2. Automated evidence collection, continuous monitoring and AutoComplete policy generation help you build the system security plan and evidence an assessor expects, with our in-house audit team on hand to interpret requirements and ODPs.

    Requirements covered

    97 security requirements across 17 families (03.01 Access Control to 03.17 Supply Chain Risk Management), with gaps in the numbering where Rev. 2 requirements were withdrawn or merged.

    Why automate

    Manual NIST 800-171 Rev. 3 compliance vs OneClickComply

    Doing it manually

    • Re-mapping 110 Rev. 2 requirements to 97 Rev. 3 requirements by hand in spreadsheets
    • Tracking organisation-defined parameters and proving each one is actually enforced
    • Writing new policies for supply chain risk, acquisition and rules of behaviour from scratch
    • Screenshotting settings across every tool to evidence the system security plan
    • Running Rev. 2 and Rev. 3 programmes side by side with duplicated effort

    With OneClickComply

    • Rev. 3 requirements supported today and mapped to your existing controls
    • Controls tied to defined parameters and monitored continuously so drift is flagged
    • Audit-ready policies generated from your real environment, including the new families
    • Evidence collected automatically from connected tools and logged with timestamps
    • One control set, so evidence collected once counts towards Rev. 2, Rev. 3 and other frameworks
    Capabilities

    Everything you need for NIST 800-171 Rev. 3

    • Rev. 3 requirements mapped to a single control set shared with Rev. 2, ISO 27001 and SOC 2

    • Automated evidence collection from cloud, identity and device tools for access, logging and configuration requirements

    • AutoComplete policies covering the new Planning, acquisition and supply chain families

    • Continuous monitoring with alerts when CUI system controls drift

    • Vendor risk management to support supply chain risk management requirements 03.17.01 to 03.17.03

    • Ask an Auditor guidance on organisation-defined parameters and Rev. 2 to Rev. 3 gaps

    How it works

    Three steps to NIST 800-171 Rev. 3 compliance

    1. Connect and scan

      Connect your cloud, identity and SaaS tools. OneClickComply checks them against NIST 800-171 Rev. 3 and shows which controls pass and which fail.

    2. Fix and generate

      OneClickFix fixes supported misconfigurations automatically, and AutoComplete drafts NIST 800-171 Rev. 3 policies from your real environment.

    3. Monitor and evidence

      Continuous monitoring flags drift as it happens, and our in-house audit team is on hand when you need expert guidance.

    See how far your current setup is from NIST 800-171 Rev. 3.

    Requirements

    NIST SP 800-171 Rev. 3 requirements

    All 97 active NIST SP 800-171 Rev. 3 security requirements across 17 families; withdrawn requirement numbers are omitted.

    ReferenceRequirement
    03.01.01Account Management
    03.01.02Access Enforcement
    03.01.03Information Flow Enforcement
    03.01.04Separation of Duties
    03.01.05Least Privilege
    03.01.06Least Privilege: Privileged Accounts
    03.01.07Least Privilege: Privileged Functions
    03.01.08Unsuccessful Logon Attempts
    03.01.09System Use Notification
    03.01.10Device Lock
    03.01.11Session Termination
    03.01.12Remote Access
    03.01.16Wireless Access
    03.01.18Access Control for Mobile Devices
    03.01.20Use of External Systems
    03.01.22Publicly Accessible Content
    03.02.01Literacy Training and Awareness
    03.02.02Role-Based Training
    03.03.01Event Logging
    03.03.02Audit Record Content

    Always check the official text of NIST 800-171 Rev. 3 for the exact wording.

    FAQs

    NIST 800-171 Rev. 3 questions, answered

    Can't find what you need? Our in-house auditors can talk you through NIST 800-171 Rev. 3 on a 30-minute call.

    What is NIST SP 800-171 Rev. 3?

    NIST SP 800-171 Rev. 3 is the third revision of NIST's security requirements for protecting Controlled Unclassified Information in non-federal systems and organisations, published in May 2024. It contains 97 requirements in 17 families, aligned with NIST SP 800-53 Rev. 5 and its moderate baseline. It is intended for federal agencies to apply through contracts and agreements with the organisations that handle their CUI.

    What changed between NIST 800-171 Rev. 2 and Rev. 3?

    Rev. 3 cuts the requirement count from 110 to 97 by withdrawing, merging and rewriting requirements, and renumbers them in a 03.xx.xx format. It adds three families: Planning, System and Services Acquisition, and Supply Chain Risk Management. It also introduces organisation-defined parameters, removes the separate basic and derived requirement split, and makes requirements more specific so they are easier to assess consistently.

    Do DoD contractors have to comply with Rev. 3 now?

    Not yet for most DoD contracts. In May 2024 the Department of Defense issued class deviation 2024-O0013, which keeps DFARS 252.204-7012 tied to NIST SP 800-171 Rev. 2, and CMMC Level 2 assessments are also based on Rev. 2. DoD has published Rev. 3 organisation-defined parameter values to support a future transition, so contractors should check each contract and plan ahead.

    What are organisation-defined parameters in Rev. 3?

    Organisation-defined parameters (ODPs) are placeholders within Rev. 3 requirements, such as time periods, frequencies or event types, whose values are set by the organisation or specified by the federal agency in the contract. For example, a requirement may call for a review at an organisation-defined frequency. Agencies can fix ODP values so all contractors meet the same standard, which DoD did with guidance released in April 2025.

    How do you comply with NIST SP 800-171 Rev. 3?

    Compliance starts by scoping the systems that process, store or transmit CUI, then assessing each of the 97 requirements and recording the results in a system security plan. Gaps go into a plan of action and milestones. Organisations then implement controls, set organisation-defined parameter values, collect evidence and use the NIST SP 800-171A Rev. 3 assessment procedures to test that each requirement is met.

    How does NIST 800-171 Rev. 3 relate to ISO 27001 and SOC 2?

    There is significant overlap but no equivalence. ISO 27001 and SOC 2 cover many of the same areas, such as access control, logging, incident response and supplier management, so existing evidence can often be reused. However, Rev. 3 has CUI-specific requirements, such as CUI media marking, CUI-focused scoping and agency-defined parameter values, so an ISO 27001 certificate or SOC 2 report does not demonstrate Rev. 3 compliance by itself.

    How long does it take to implement NIST 800-171 Rev. 3?

    It depends on the size of your CUI environment and how mature your controls already are. Organisations already compliant with Rev. 2 mainly need a gap analysis against the rewritten and new requirements, especially supply chain risk management and planning, plus ODP values. Organisations starting from scratch face a larger programme covering all 17 families, so timelines vary considerably.

    Does OneClickComply support NIST SP 800-171 Rev. 3?

    Yes. NIST SP 800-171 Rev. 3 is supported in OneClickComply today. Because controls are shared across frameworks, evidence you collect for Rev. 2, ISO 27001 or SOC 2 can count towards Rev. 3, with continuous monitoring and policy generation built in. OneClickComply helps you prepare and evidence your controls but does not certify compliance or replace a formal assessment.

    Start working towards NIST 800-171 Rev. 3

    Automate controls, gather evidence continuously and stay audit-ready, all on one platform.