Active

End-of-Life Identification

The organization shall identify technology assets that have reached or are approaching end-of-life, including operating systems, applications, and hardware. Identification shall include monitoring of vendor end-of-life announcements, assessment of asset lifecycle status, and documentation of end-of-life dates.

Requirement ID
OPS-006-R003
Parent Control
Domain Code

Requirement Details & Guidance

OPS-006-R003 · OPS-006
Why This Requirement Exists

This requirement exists to identify technology approaching or reaching end of life using vendor and lifecycle information and to ensure operational services are managed consistently, reliably, and with appropriate control.

Implementation Guidance

Define and document the process for identify technology approaching or reaching end of life using vendor and lifecycle information. Establish accountable owners, inputs and outputs, approval or validation points, operating criteria, schedules or thresholds where applicable, exception handling, monitoring, reporting, review, and evidence requirements. Integrate the process with change, incident, risk, asset, security, and service-management processes where relevant.

Practical Application & Audit Readiness

OPS-006-R003 · Field Guidance

Business Examples

    Common Audit Findings

      Common Mistakes

        Best Practices & Ownership

        OPS-006 · Recommended Approach

        Recommended Practices

          Typical Owner

          Cross-Mapped Regulatory Frameworks

          Harmonized Control Mappings
          FRAMEWORK CODE FRAMEWORK NAME & DETAILS FAMILY / CATEGORY VERSION ACTION
          IRDAI IRDAI Information & Cyber Security Guidelines IRDAI information and cyber-security requirements... Clause: §2.2-3.2.2 – Asset Tracking; §1.8-III – Technology Risk Assessment Process
          India
          Guideline
          vLatest View →
          RBI-CSF RBI Cyber Security Framework / Master Directions RBI cyber-security requirements and directions set... Clause: 6) Application Security Life Cycle (ASLC) – 6.9 Security evaluation and maturity assessment before adopting new technologies for critical systems; 5) Secure Configuration – 5.1 Baseline security requirements/configurations across device categories and lifecycle, with periodic review
          India
          Regulation
          vLatest View →
          SEBI-CSCRF SEBI Cyber Security & Cyber Resilience Framework SEBI’s Cybersecurity and Cyber Resilience Framewor... Clause: 4.1 DE.CM: Security Continuous Monitoring
          India
          Regulation
          vLatest View →
          DORA Digital Operational Resilience Act The EU Digital Operational Resilience Act establis... Clause: Article 9(4)(f) – Documented policies for patches and updates Article 7 – ICT systems, protocols and tools
          EU
          Regulation
          vCurrent View →
          ISO27002 ISO/IEC 27002 ISO/IEC 27002 is a guidance standard containing a... Clause: 8.16 – Monitoring activities
          ISO
          Standard
          v2022 View →
          NIS2 NIS2 Directive The NIS2 Directive establishes EU-wide cybersecuri... Clause: Article 21(2)(e) – Security in network and information systems acquisition, development and maintenance, including vulnerability handling and disclosure
          EU
          Directive
          vCurrent View →
          COBIT2019 COBIT COBIT is an enterprise governance and management f... Clause: 4.3 – Build, Acquire and Implement (BAI) > BAI06 – Managed IT Changes > BAI06.01 – Evaluate, prioritize and authorize change requests.
          COBIT
          Governance Framework
          v2019 View →
          NIST-CSF NIST Cybersecurity Framework (CSF) The NIST Cybersecurity Framework provides high-lev... Clause: PR.PS – Platform Security | PR.PS-01 – Configuration management practices are established and applied DE.CM – Continuous Monitoring | DE.CM-09 – Computing hardware and software, runtime environments, and their data are monitored to find potentially adverse events ID.RA – Risk Assessment | ID.RA-07 – Changes and exceptions are managed, assessed for risk impact, recorded, and tracked
          NIST
          Framework
          v2 View →
          NIST80053 NIST SP 800-53 NIST SP 800-53 Rev. 5 presents control families, i... Clause: 3.17 – SYSTEM AND SERVICES ACQUISITION, 3.13 – PROGRAM MANAGEMENT; SA-22 – UNSUPPORTED SYSTEM COMPONENTS, PM-5 – SYSTEM INVENTORY
          NIST
          Control Catalog
          vRev. 5 View →
          SOC2 SOC 2 Trust Services Criteria SOC 2 is an independent examination and reporting... Clause: CC3.4 – Risk Assessment – COSO Principle 9: The entity identifies and assesses changes that could significantly impact the system of internal control. CC8.1 – Change Management – The entity authorizes, designs, develops or acquires, configures, documents, tests, approves, and implements changes to infrastructure, data, software, and procedures to meet its objectives.
          AICPA
          Audit Framework
          vLatest View →

          Parent Domain Context

          Governance Domain Baseline
          Domain Name:
          IT Operations & Service Management (OPS)
          Purpose:
          To ensure the availability, performance, and resilience of IT services.
          Scope:
          Enterprise

          Parent Control Context

          Control Baseline
          Control Name:
          End-of-Life & Technology Lifecycle Management (OPS-006)
          Summary:
          Establishes end-of-life management including inventory review, EOL identification, risk assessment, replacement planning, compensating controls, monitoring, reporting, and continuous improvement.
          Business Description:
          Establish and maintain processes to identify, assess, monitor, replace, retire, or apply compensating controls for obsolete, unsupported, and end-of-life technology assets.