Study guide

Asset Lifecycle and End-of-Life Management

ISC2 Certified in Cybersecurity CC

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

Official 2026 CC Exam Facts and Timeline CAT Format and Beginner Security Judgment Domain Map and Time Allocation 30, 60, and 90 Day Study Plan with Readiness Thresholds

2 Domain 1: Security Principles (24%)

CIA Triad as a Practical Decision Tool Authentication, Authorization, Accounting, and Non-Repudiation Privacy in the CC Outline Beginner Security Decision Scenarios AI Security in Security Principles

3 Domain 1: Risk Management and Security Controls

Risk Identification in Business Context Risk Management Processes Risk Treatment Decisions Security Controls: Technical, Administrative, and Physical

4 Domain 1: Governance, Ethics, Policy, and Privacy

Governance and the ISC2 Code of Ethics Policies, Procedures, Standards, Laws, and Regulations Privacy and AI Governance Due Care, Due Diligence, and Governance Decisions

5 Domain 1: Physical Security Controls

Physical Controls and Their Monitoring Tailgating and Physical Penetration Testing

6 Domain 2: Security Governance - Business Continuity

Business Continuity (BC)

7 Domain 2: Security Governance - Disaster Recovery

Disaster Recovery (DR) Redundancy in Business Continuity and Disaster Recovery

8 Domain 2: GRC Planning

GRC Planning: Purpose, Importance, and Tools

9 Domain 2: Measuring Cybersecurity Effectiveness

Security Metrics, KRIs, and Dashboards AI Security in Governance, Awareness, and Continuity

10 Domain 2 and Domain 5: Security Awareness and Triage

Security Awareness and Organizational Culture Phishing and Password Protection Security Event Triage and Human Review

11 Domain 3: Identity Lifecycle Management

Identification, Authentication, Authorization, and Accountability Multi-Factor Authentication and Password Protection Provisioning, Deprovisioning, and Access Reviews Service Accounts and AI Bots in Identity Management AI Bots and Service Accounts in Identity Management

12 Domain 3: Logical Access Controls

Least Privilege and Separation of Duties DAC, MAC, RBAC, and ABAC

13 Domain 4: Networking Fundamentals

Network Models and IP Addressing Firewalls: Ports and Applications Virtual Private Networks (VPN) Wireless Networks and Embedded Systems

14 Domain 4: Network Security Architecture and Cloud Security

Network Segmentation Defense in Depth and Zero Trust Cloud Characteristics and Shared Security Model Cloud Service Models, Deployment Models, and Shared Security AI in Network Security and Cloud Hosting

15 Domain 5: Incident Response

Incident Response (IR) and the Incident Response Plan Preparing the Incident Response Plan Incident Response Exercises and Tabletops AI in Security Operations and Incident Response

16 Domain 5: Security Monitoring

Logging and Monitoring Security Events

17 Domain 5: Threat Actors and Threat Intelligence

Threat Actors, Threat Intelligence, and Frameworks

18 Domain 5: Data Security

Encryption and Hashing for Data Security Data Handling: Classification, Labeling, Masking, and Sanitization Security of the AI Workspace

19 Domain 5: Asset Protection

Configuration and Change Management Change Management and Asset Protection Asset Lifecycle and End-of-Life Management

20 Domain 5: Data Handling Policy

Data Handling Policy and Classification

21 Domain 5: Security Testing

Security Readiness, Application, and Physical Testing

22 Integrated CC Scenario Labs

Risk and Control Selection Drill Continuity, Recovery, and Response Drill Access Control Design Drill Segmentation and Triage Drill

23 Final 14-Day Review and Exam Readiness

CAT Pacing and 100-125 Item Strategy Missed-Question Notebook and Domain Repair Exam Day Logistics and Rescheduling After Passing: AMF and CPE

Asset Lifecycle and End-of-Life Management

Key Takeaways Explain This Topic AI

Subdomain 5.4 names asset lifecycle management and configuration and change management under asset protection.

End-of-life (EOL) software and devices are the outline's named example of lifecycle risk.

Retiring or replacing an asset is a change, so it needs authorization, documentation, and a way to reverse it.

Sanitizing storage before disposal links asset lifecycle to data handling (subdomain 5.1).

Source: ISC2 CC Exam Outline v01/2026, subdomain 5.4, checked 2026-10-22.

Last updated: October 2026

Asset Lifecycle Management in the 2026 Outline

Subdomain 5.4, Understand asset protection , names two topics: asset lifecycle management , with the outline's example of end-of-life (EOL) software and devices , and configuration and change management . Asset protection means knowing which assets exist, keeping them supported, and changing them in a controlled way.

Source: ISC2 Certified in Cybersecurity Exam Outline, effective September 1, 2026 (v01/2026), subdomain 5.4, checked 2026-10-22.

Tracking an Asset Through Its Life

An asset is protected only while someone knows it exists and whether it is still supported. Lifecycle management follows each asset from inventory through service to retirement. The outline's example, end-of-life software and devices, is the key risk point: once a vendor stops providing updates, known weaknesses are no longer fixed by that vendor.

Lifecycle stage Security question Example

Inventory Do we know the asset exists and who owns it? A router appears in the asset register with a named owner

  • In service Is it configured, patched, and monitored? Updates are installed under change control
  • End of life Is vendor support still available? An operating system reaches end of support
  • Retirement Is data removed and the asset disposed of safely? Storage is sanitized before disposal

Connecting Lifecycle to Change Management

Retiring or replacing an asset is a change. Good change management usually means the change is authorized, tested, documented, and reversible. Sanitizing storage media before disposal is a data-handling topic under subdomain 5.1, so one retirement can touch more than one outline subtopic.

Scenario: The Forgotten Server

A legacy server stays in a closet after its application moves to the cloud. It is missing from the asset register, its operating system is out of support, and it still answers on the network. The fix is to add it to inventory, decide whether to support or retire it, and remove it under change control with its storage sanitized.