FedRAMP Moderate
SA - System and Services Acquisition

FedRAMP Moderate SA-22: Unsupported System Components. a. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or b. Provide the following options for alternative sources for continued support

Unsupported System Components. a. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer; or b. Provide the following options for alternative sources for continued support

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

What else in your programme already covers this

This control maps to 36 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 · 4 controls

  • CIS-12.1 Ensure Network Infrastructure is Up-to-Date
  • CIS-16.5 Use Up-to-Date and Trusted Third-Party Software Components
  • CIS-2.2 Ensure Authorized Software is Currently Supported
  • CIS-9.1 Ensure Use of Only Fully Supported Browsers and Email Clients

ISO 27001:2022 · 4 controls

  • 5.22 Monitoring, review and change management of supplier services
  • 8.32 Change management
  • 8.8 Management of technical vulnerabilities
  • 8.9 Configuration management

NIST SP 800-53 Rev 5 · 4 controls

  • NIST800-CM-8 System component inventory
  • NIST800-MA-6 Timely Maintenance. Obtain maintenance support and/or spare parts for [organization-defined] within [organization-defined] of failure
  • NIST800-SA-10 Developer configuration management
  • NIST800-SI-2 Flaw remediation

PCI DSS 4.0 · 4 controls

  • 12.3.4 Hardware and software technologies reviewed annually
  • 5.2.1 An anti-malware solution(s) is deployed on all system components, except for those system components identified in periodic evaluations per Requirement 5.2.3 that concludes the system components are not at risk from malware
  • 6.3.1 Security vulnerabilities are identified and managed as follows: • New security vulnerabilities are identified using industry-recognized sources for security vulnerability information, including alerts from international and national computer emergency response teams (CERTs). • Vulnerabilities
  • 6.3.3 All system components are protected from known vulnerabilities by installing applicable security patches/updates as follows: • Patches/updates for critical vulnerabilities (identified according to the risk ranking process at Requirement 6.3.1) are installed within one

ACSC Essential Eight · 3 controls

NIST Cybersecurity Framework 2.0 · 3 controls

  • 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

Cloud Security Alliance Cloud Controls Matrix (CCM) v4.0.1 · 2 controls

UK Cyber Essentials · 2 controls

  • CE-SU.1 Software Licensed and Supported
  • CE-SU.4 Remove Out-of-Support Software

ANSSI Guide d'hygiene informatique (42 mesures, v2.0) · 1 control

  • ANSSI-HYG-35 Anticipate the End of Maintenance of Software and Systems

APRA CPS 230 Operational Risk Management · 1 control

  • CPS230-P25 Information and Technology Capability and Asset Health

AWS Well-Architected Security Pillar · 1 control

Azure Security Benchmark · 1 control

  • ASBv3-PV-6 Rapidly and automatically remediate vulnerabilities

DORA · 1 control

ISO 27002:2022 · 1 control

  • 8.8 Management of technical vulnerabilities

NIST SP 800-161 Rev 1 · 1 control

NIST SP 800-171 Rev 3 · 1 control

NIST SP 800-218 · 1 control

SOC 2 · 1 control

  • SOC2-CC8.1 Change management processes are in place

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 SA - System and Services Acquisition

You are reading one control. How much of FedRAMP Moderate have you already done?

FedRAMP Moderate SA-22 is one control. If you already hold one of the frameworks below, a reviewed crosswalk already says how much of FedRAMP Moderate your existing evidence covers. Hold ISO 27002:2022 and 182 of 323 FedRAMP Moderate controls already carry evidence.

If you hold ISO 27002:202256.3% covered · 141 gapsIf you hold PCI DSS 4.051.1% covered · 158 gapsIf you hold ISO 27001:202249.8% covered · 162 gapsIf you hold NIST SP 800-171 Rev 345.5% covered · 176 gapsIf you hold C5 (Germany)37.2% covered · 203 gapsIf you hold CMMC 2.035% covered · 210 gaps

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. 348 were rejected on the ISO 27002:2022 pair alone.

See the released pairs, $299 eachBrowse the graph free

Query this from an agent

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

MCP endpointAll FedRAMP Moderate controls