Study guide
4.7 Information System Lifecycle Engineering and Retirement
CISSP Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CISSP Orientation, CAT, and Official Source Control
1.1 Credential Scope, CISSP Mindset, and Search Language 1.2 Exam Outline Effective Date and Eight-Domain Map 1.3 CAT Format, 100-150 Items, and Forward-Only Rules 1.4 Passing Grade, Results, Feedback, and Retake Policy 1.5 Experience, Endorsement, and Associate of ISC2 Path 1.6 Pricing, AMF, CPE, and Maintenance Overview
2 Chapter 2: Security and Risk Management
2.1 Professional Ethics, CIA, and Security Governance 2.2 Policies, Standards, Procedures, Guidelines, and Control Ownership 2.3 Legal, Regulatory, Privacy, and Investigation Context 2.4 Risk Identification, Analysis, Treatment, and Reporting 2.5 Business Continuity, BIA, and Recovery Prioritization 2.6 Personnel Security, Training, Awareness, and Culture 2.7 Threat Modeling, Supply Chain Risk, and Third-Party Governance 2.8 Security and Risk Management Case Lab
3 Chapter 3: Asset Security and Data Lifecycle
3.1 Asset and Data Classification, Ownership, and Roles 3.2 Handling Requirements, Labeling, Privacy, and Cross-Border Data 3.3 Data States and Protection Methods: DLP, DRM, and CASB 3.4 Data Lifecycle, Retention, Remanence, and Destruction 3.5 Secure Provisioning, Inventory, and Asset Management 3.6 Asset Security Case Lab
4 Chapter 4: Security Architecture, Engineering, and Cryptography
4.1 Secure Design Principles and Security Models 4.2 Control Selection, System Security, and Architecture Risk 4.3 Cryptography Foundations: Symmetric, Asymmetric, Hashing, and PKI 4.4 Cryptographic Lifecycle, Key Management, and Attack Patterns 4.5 Cloud, Container, IoT, Edge, and Shared Responsibility Architecture 4.6 Physical Site, Facility, and Environmental Security 4.7 Information System Lifecycle Engineering and Retirement 4.8 Architecture and Engineering Case Lab
5 Chapter 5: Communication, Network Security, and Zero Trust
5.1 Network Architecture, OSI/TCP/IP, and Secure Design 5.2 Secure Protocols, Encryption in Transit, and Channel Protection 5.3 Segmentation, Microsegmentation, SDN, VPC, and Zero Trust 5.4 Wireless, Cellular, Remote Access, and Third-Party Connectivity 5.5 Network Components: NAC, IDS/IPS, Firewalls, and Endpoints 5.6 Monitoring, Observability, Capacity, and Resilient Communications 5.7 Communication and Network Security Case Lab
6 Chapter 6: Identity and Access Management
6.1 Identity Proofing, Authentication, Authorization, and Accountability 6.2 Access Control Models: RBAC, MAC, DAC, ABAC, and Risk-Based Access 6.3 Federation, SSO, MFA, Passwordless, and Session Management 6.4 Provisioning, Deprovisioning, JML, and Access Reviews 6.5 Service Accounts, Non-Human Identities, and Privilege Management 6.6 Physical, Logical, Cloud, and Hybrid Access Boundaries 6.7 IAM Case Lab
7 Chapter 7: Security Assessment, Testing, and Audit Strategy
7.1 Assessment, Test, and Audit Strategy Selection 7.2 Control Testing, Vulnerability Assessment, and Penetration Testing 7.3 Log Review, Code Review, Misuse Cases, and Compliance Checks 7.4 Security Process Data, KPIs, KRIs, and Reporting 7.5 Remediation, Exceptions, Risk Acceptance, and Evidence Quality 7.6 Security Assessment and Testing Case Lab
8 Chapter 8: Security Operations, Incident Response, and Resilience
8.1 Investigations, Evidence, Forensics, and Legal Readiness 8.2 Logging, Monitoring, SOC, and Alert Triage 8.3 Configuration, Change, Patch, and Vulnerability Operations 8.4 Incident Management, Containment, Eradication, and Recovery 8.5 Disaster Recovery, Backup, Availability, and Resilience 8.6 Physical Security Operations and Safety 8.7 Security Operations Case Lab
9 Chapter 9: Software Development Security and DevSecOps
9.1 Secure SDLC Governance and Requirements 9.2 Architecture, Threat Modeling, and Design Review 9.3 Secure Coding, Code Review, and Application Testing 9.4 CI/CD, Source Control, and Environment Separation 9.5 Software Supply Chain, Third-Party Components, and Deployment 9.6 DevSecOps Vulnerability Management and Release Risk 9.7 Software Development Security Case Lab
10 Chapter 10: Integrated CISSP Governance Scenario Labs
10.1 Enterprise Risk Committee Decision Lab 10.2 Cloud Migration Security Architecture Lab 10.3 Ransomware Incident and Business Continuity Lab 10.4 Identity Modernization and Zero Trust Lab 10.5 Third-Party Breach and Contract Governance Lab 10.6 Secure SDLC Transformation Lab 10.7 Full CISSP Manager Simulation
11 Chapter 11: Final Review, Endorsement, CPE, and Test-Day Strategy
11.1 Final 45-Day CISSP Study Plan 11.2 CAT Timing and Forward-Only Decision Workflow 11.3 Mixed-Domain Remediation and Manager Mindset Review 11.4 Test-Day Checklist and Pearson VUE Readiness 11.5 Endorsement, Associate Path, and Work Experience Documentation 11.6 CPE, AMF, and Three-Year Maintenance Plan 11.7 CISSP Final Mixed Review
4.7 Information System Lifecycle Engineering and Retirement
Key Takeaways Explain This Topic AI
Security engineering must span requirements, architecture, build, test, deployment, operations, change, maintenance, and retirement.
Lifecycle governance makes security evidence available before major decisions rather than after systems are already in production.
Retirement is a security phase that includes data retention, migration, sanitization, contract closure, access removal, and residual dependency review.
Architecture decisions should remain traceable to risks, requirements, controls, tests, exceptions, and accountable owners.
Last updated: May 2026
Engineering Security Across the Lifecycle
A secure system is not created at one review meeting. It is engineered through requirements, design, procurement, build, configuration, testing, deployment, operations, change management, maintenance, and retirement. The CISSP perspective is to make security a governed lifecycle activity with evidence at each decision point.
Requirements should identify business objectives, critical assets, data classifications, users, administrators, interfaces, regulatory obligations, availability needs, privacy expectations, logging needs, and abuse cases. Vague requirements such as secure the data are not enough. The team needs measurable expectations such as encrypt backups, restrict privileged access, and retain audit events for a defined period.
Architecture translates requirements into trust boundaries, data flows, control points, dependencies, and operational assumptions. Data flow diagrams, threat models, misuse cases, and control mappings help stakeholders see where risk enters the system. Architecture should also define what the system will not do, because scope boundaries reduce later ambiguity.
Procurement and sourcing decisions are part of the lifecycle. A vendor product, SaaS platform, open source library, or managed service may inherit risk into the architecture. Security leaders should review assurance reports, support commitments, vulnerability handling, data processing terms, breach notification, logging capabilities, exit rights, and integration controls before adoption.
Build and configuration practices must preserve design intent. Secure baselines, infrastructure as code, protected branches, peer review, secrets management, dependency scanning, signed artifacts, and environment separation reduce the chance that production diverges from approved architecture. Manual exceptions should be visible and approved.
- Phase Security focus Evidence
- Concept Business impact and risk appetite Initial risk assessment and data classification
- Requirements Measurable security needs Security requirements and acceptance criteria
- Design Trust boundaries and control placement Architecture diagrams and threat model
- Build Secure implementation and configuration Code review, baselines, dependency records
- Test Control effectiveness Security test results and remediation records
- Deploy Operational readiness Change approval, runbooks, monitoring
- Operate Ongoing assurance Logs, metrics, access reviews, incidents
- Retire Data and access closure Sanitization, migration, contract closeout
Testing should include more than vulnerability scans. Control testing, configuration review, access testing, failure mode testing, recovery testing, log validation, privacy checks, and abuse case testing all provide evidence that the architecture works. The level of testing should match risk and the criticality of the system.
Deployment readiness asks whether operations can run the system securely. Monitoring rules, alert owners, escalation paths, backup procedures, key rotation, certificate renewal, capacity thresholds, incident playbooks, and rollback plans should be ready before go-live. A system that cannot be operated safely is not ready just because code is complete.
Operations and maintenance require continuous governance. Vulnerabilities are discovered, business use changes, administrators move roles, certificates expire, vendors update services, and threat conditions shift. Access reviews, configuration drift detection, patch management, logging review, change management, and periodic risk reassessment keep the system aligned with its security objectives.
Change management is a security control. Emergency changes may be necessary, but they should be documented, reviewed after the fact, and reconciled with baselines. Normal changes should include impact assessment, testing, approval, backout planning, and communication. Security should focus on high-risk changes rather than slowing every low-risk adjustment equally.
Retirement is often mishandled because teams focus on replacement launch. A retired system may still contain sensitive data, active service accounts, DNS records, firewall rules, certificates, backup copies, vendor access, monitoring alerts, and contractual obligations. If these are not closed, the retired system remains part of the attack surface.
Data migration and retention decisions should be planned before shutdown. Some records must be retained for legal, tax, operational, or regulatory reasons. Other data should be deleted according to policy. The team should document authoritative sources, migration validation, archival access, encryption keys, retention schedules, and destruction evidence.
Secure decommissioning includes removing user and service access, disabling integrations, revoking certificates and tokens, sanitizing media, terminating vendor access, updating asset inventory, closing monitoring exceptions, and confirming that backups meet retention and destruction requirements. Cloud resources also need cost and exposure review so abandoned assets do not persist.
Use this retirement checklist:
Confirm business owner approval and replacement readiness.
Inventory data, integrations, identities, keys, certificates, and vendors.
Decide what to migrate, archive, retain, delete, or destroy.
Remove access paths, network rules, service accounts, and scheduled jobs.
Sanitize or destroy media and document evidence.
Revoke trust relationships and update monitoring and asset records.
Complete lessons learned and close residual risks.
Traceability ties the lifecycle together. A requirement should map to a design decision, a control, a test, an operational metric, and an owner. Exceptions should map to risk acceptance and review dates. This allows leaders to make informed decisions and helps auditors understand why controls exist.
For CISSP study, think beyond development. System lifecycle security is about sustained assurance. The strongest answer is often the one that integrates security into governance and engineering from the first requirement to final disposal.