Free compliance framework explorer — browse controls, evidence, and implementation guidance.Subscribe for updates →
SOC 247
ITSP.10.17198
ISO 42001soon
ISO 27001soon

Browse

98 controls

03.16.02Unsupported system componentsITSP.10.171System and services acquisition

Official Requirement

A. Replace system components when support for the components is no longer available from the developer, vendor, or manufacturer. B. Provide options for risk mitigation or alternative sources for continued support for unsupported components if components cannot be replaced.

Source: Canadian Centre for Cyber Security ITSP.10.171 (2025), adapted from NIST SP 800-171 Rev. 3

In Plain English

When software, hardware, or firmware reaches end-of-life and the vendor no longer provides security updates, you must replace those components. If immediate replacement is not feasible, you must implement risk mitigation measures or find alternative support sources to address the security gap.

Help us build what matters.

Vote for the next framework, subscribe for updates, and let us know if you'd contribute.

The Trust Services Criteria referenced in this tool are published by the American Institute of Certified Public Accountants (AICPA) and incorporate principles from the Committee of Sponsoring Organizations of the Treadway Commission (COSO). Criteria descriptions are reproduced for reference purposes. All implementation guidance, evidence recommendations, and control language are original work by Truvo Cyber. ISO 27001 and ISO 42001 are standards published by the International Organization for Standardization (ISO). Framework and standard names are the property of their respective owners. This tool is not affiliated with, endorsed by, or certified by AICPA, COSO, or ISO.

© 2026 Truvo Cyber. All rights reserved.

On-premises implementation and evidence

End-of-life component management

Implementation steps

  1. Inventory all hardware, software, and firmware with vendor support status and end-of-life dates
  2. Track vendor end-of-support announcements and plan component replacements in advance of end-of-life dates
  3. Execute replacement projects for end-of-life components before support expires
  4. For components that must remain temporarily after end-of-life, implement compensating controls (isolation, enhanced monitoring) and document risk acceptance

Tools / systems

Evidence artifacts

Evidence frequency: Quarterly inventory review; per-event migration planning; annual lifecycle assessment