NIST SP 800-171 Rev 3
03.16 SA (System and Services Acquisition)

NIST SP 800-171 Rev 3 03.16.02: Unsupported System Components

Replace system components when support for the components is no longer available; provide justification and approval for continued use of unsupported components.

Maintained by Gerard BlokdykVerified against the published standard Control text last updated

What else in your programme already covers this

This control maps to 27 controls across 18 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.

CIS Controls v8 · 3 controls

  • CIS-12.1 Ensure Network Infrastructure is Up-to-Date
  • CIS-2.2 Ensure Authorized Software is Currently Supported
  • CIS-9.1 Ensure Use of Only Fully Supported Browsers and Email Clients
  • NIST-CSF-ID.AM-08 Systems, hardware, software, services, and data are managed throughout their life cycles
  • NIST-CSF-PR.PS-02 Software is maintained, replaced, and removed commensurate with risk
  • NIST-CSF-PR.PS-03 Hardware is maintained, replaced, and removed commensurate with risk

ACSC Essential Eight · 2 controls

  • E8-PATCHAPP-ML1 Patch Applications (ML1)
  • E8-PATCHOS-ML1 Patch Operating Systems (ML1)
  • AM-3 Ensure security of asset lifecycle management
  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities

UK Cyber Essentials · 2 controls

  • CE-SU.1 Software Licensed and Supported
  • CE-SU.4 Remove Out-of-Support Software
  • ANSSI-HYG-35 Anticipate the End of Maintenance of Software and Systems
  • CPS230-P25 Information and Technology Capability and Asset Health

C5 (Germany) · 1 control

  • C5-OPS-18 Managing Vulnerabilities, Malfunctions and Errors - Concept

FedRAMP High · 1 control

  • SA-22 Unsupported System Components (SA-22)

FedRAMP Moderate · 1 control

  • SA-22 Unsupported System Components (SA-22)

ISO 27001:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

NIS2 Directive · 1 control

  • Art.21.2.e Security in acquisition, development and maintenance, including vulnerability handling and disclosure

NIST SP 800-218 · 1 control

PCI DSS 4.0 · 1 control

  • 12.3.4 12.3.4 Annual review of hardware and software technologies

Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.

Other controls in 03.16 SA (System and Services Acquisition)

You are reading one control. How much of NIST SP 800-171 Rev 3 have you already done?

NIST SP 800-171 Rev 3 03.16.02 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of NIST SP 800-171 Rev 3 your existing evidence covers. Hold PCI DSS 4.0 and 69 of 97 NIST SP 800-171 Rev 3 controls already carry evidence.

Each report names every control your existing framework evidences, every one it does not, the reasoning behind each claim, and the claims that were argued against and rejected. 0 were rejected on the PCI DSS 4.0 pair alone.

Query this from an agent

The graph holds this control, the 27 it maps to, and the evidence behind each claim, over MCP and REST.