Chapters0/43 ▾
0 of 43 lessons finished
- 1.Security Principles & Control Types0/5
- 2.Risk, Policy Hierarchy & Ethics0/4
- 3.Governance, Risk & Compliance0/4
- 4.Continuity, Disaster Recovery & Awareness0/4
- 5.Identity Lifecycle Management0/4
- 6.Logical Access Controls & Models0/4
- 7.Network Security Concepts0/5
- 8.Network Architecture & Cloud Security0/4
- 9.Data Security & Security Operations0/5
- 10.Incident Response, Assets & Testing0/4
Chapter 10 · Lesson 3 of 4
Asset lifecycle, configuration and change management
1 min read
Asset protection starts with knowing what you have. If nobody can list the company's servers, laptops and cloud subscriptions, building a complete inventory comes before anything else, because scanning, patching and access reviews only cover assets already on the list.
The lifecycle also has an end. When end-of-life laptops are disposed of, sanitizing the drives is not the last step: the inventory entry is retired with a dated disposal record, and the licenses, certificates and machine accounts tied to the devices are revoked.
End of support is a growing risk even when software still works: newly found flaws will never be patched, so exposure rises until the system is replaced or fenced off with compensating controls such as segmentation and restricted access.
Configuration management is about state. A baseline is the approved secure configuration for a type of system, often based on a hardening benchmark; new systems are built to it and later audited against it to spot drift. Change management is about process: a change is requested, assessed for risk, approved, tested, scheduled and recorded before the state may change.
Example: a technician opens a remote desktop port on a shop's point-of-sale server to help a vendor and never logs it. That unrecorded change is an unauthorized deviation from the baseline and counts as a security incident even before anyone exploits it. Emergency changes can be fast-tracked, but they are still documented and reviewed afterward.
Check yourself
1. An auditor asks a team to distinguish configuration management from change management. Which statement is correct?
2. A new security manager finds that nobody can say how many servers, laptops and cloud subscriptions the company has. Vulnerability scanning, patching and access reviews are all running. Which action should be taken FIRST, and why?
Facts checked 2026-11-15 · Sources: ISC2 CC Certification Exam Outline, NIST SP 800-61 Rev. 3, Incident Response Recommendations and Considerations for Cybersecurity Risk Management
ISC2 Certified in Cybersecurity (CC) cheat sheet: every key fact on one page →