Study guide

11.6 CPE, AMF, and Three-Year Maintenance Plan

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

11.6 CPE, AMF, and Three-Year Maintenance Plan

Key Takeaways Explain This Topic AI

Maintaining CISSP requires CPE credits and annual AMF payment under ISC2 member policies.

CISSP requires 120 CPE credits over a three-year cycle, including 90 Group A credits.

The suggested annual pace is 40 total CPE credits, including 30 Group A credits.

A sustainable maintenance plan ties learning activities to job responsibilities, evidence, and renewal deadlines.

Last updated: May 2026

Maintenance Begins Before the Celebration Ends

CISSP certification maintenance is part of professional accountability. The source brief states that members must earn continuing professional education credits and pay annual maintenance fees to maintain certification or associate status. For CISSP, the three-year requirement is 120 total CPE credits. Within that total, 90 Group A credits are required over three years, and 30 additional Group A or Group B credits are required over three years.

The suggested annual pace is 40 total CPE credits, including 30 Group A credits and 10 Group A or B credits. This suggested pace matters because deferring maintenance work creates unnecessary risk. A professional who waits until the end of the cycle may struggle to find relevant activities, reconstruct evidence, or align learning to practice. The better approach is to run maintenance as a lightweight quarterly program with records, goals, and review.

Group A credits should relate directly to the domains of the certification. For CISSP, that means activities connected to governance, asset security, architecture, networks, identity, assessment, operations, or software development security. Group B credits can support broader professional development. The exact activity eligibility should always be checked against current ISC2 policies, but the management habit is stable: record what you did, when you did it, how long it took, why it is relevant, and what evidence supports it.

  • Requirement Three-year amount Suggested annual pace Planning note
  • Group A CPE 90 30 Tie directly to CISSP domains
  • Group A or B CPE 30 10 Use for domain or broader professional growth
  • Total CPE 120 40 Track quarterly to avoid deadline risk

Certified member AMF U.S. $135 annually U.S. $135 annually Members with multiple covered certifications pay one AMF

Associate AMF U.S. $50 annually U.S. $50 annually Applies to Associate of ISC2 status

The source brief states that certified members holding CISSP, SSCP, CCSP, CGRC, CSSLP, ISSAP, ISSEP, or ISSMP pay a U.S. $135 annual maintenance fee. Associates of ISC2 pay U.S. $50. Members with multiple certifications pay one AMF, due on the earliest certification anniversary. These numbers are logistics, but they also create a planning requirement. Put AMF dates and CPE checkpoints on the calendar as soon as the credential is active.

A strong CPE plan is not a random stack of webinars. It should improve the professional practice that CISSP represents. If your role is moving into cloud governance, plan activities around shared responsibility, identity federation, data protection, logging, resilience, and supplier risk. If your organization is improving software security, plan learning around secure SDLC, threat modeling, code review, CI/CD controls, and vulnerability management. Maintenance should make you better at the work, not merely compliant on paper.

Evidence discipline is essential. Keep certificates of completion, agendas, notes, attendance records, publication links, presentation materials, or other supporting records as appropriate. Store them in a structured folder by cycle year and activity type. Record the date, provider, topic, duration, domain relationship, and claimed credit. This is the same mindset used in security assessment: if a control or requirement matters, evidence should be retrievable, accurate, and understandable.

Three-Year Maintenance Workflow

Record certification cycle start and anniversary dates.

Add annual AMF due dates and quarterly CPE review checkpoints.

Set a target of at least 10 CPE credits per quarter to maintain margin.

Prioritize Group A activities tied to current job risks and CISSP domains.

Store evidence immediately after each activity.

Review totals twice a year for Group A, Group B, and overall progress.

Adjust the learning plan when job duties, technology, or risk priorities change.

Consider a security manager responsible for a new identity governance program. A strong maintenance plan could include a course on identity lifecycle controls, a conference session on privileged access governance, an internal presentation on access review metrics, and a tabletop exercise involving account compromise. The manager records each activity, maps it to IAM, Security and Risk Management, and Security Operations as appropriate, and retains evidence. The CPE record then reflects actual professional growth.

Do not treat CPE as separate from ethics and competence. CISSP professionals are expected to keep learning because security risk changes. Regulations evolve, architectures shift, attackers adapt, and business processes move. Maintenance is the mechanism that keeps the credential connected to current practice. A three-year plan should therefore include both depth in your current role and breadth across domains you touch less often.

The final study chapter includes maintenance because certification is not the end state. It is the beginning of a documented professional cycle. The same habits that helped during study, source control, evidence, risk mapping, and disciplined review, continue after certification. A candidate who understands this before test day will be better prepared for the full credential lifecycle.