Passing the CISSP exam is the hard part. Keeping the certification active requires ongoing effort, but nothing close to the intensity of exam preparation. ISC2 requires certified professionals to earn Continuing Professional Education credits throughout their certification cycle. That means 120 CPE credits every three years, and ISC2 suggests about 40 per year. The ISC2 CPE policy defines what counts, how to document activities, and what happens if you fall short.
The CPE requirement exists because security changes constantly. Frameworks get revised and regulations keep piling up, and the threats and tools look different every year. A certification earned in 2020 means little if the holder stopped learning in 2020. CPE credits keep CISSPs engaged with the field so they aren’t coasting on a credential earned years ago.
Most CISSPs find the requirement manageable once they understand how broadly ISC2 defines qualifying activities. Reading security articles, attending webinars, participating in professional groups, and even work projects can generate credits. Finding enough activities is rarely the problem. The harder part is documenting them properly and spreading the effort across the year instead of scrambling before deadlines.
The Annual and Cycle Requirements
ISC2 structures CPE requirements around a three-year cycle total, with a suggested annual pace. ISC2 suggests earning about 40 CPE credits every year, but full members have no annual minimum. You could earn 80 credits in year one and fewer in year two. The suggested pace is there to nudge you toward steady learning instead of cramming it into a few bursts.
Over your three-year certification cycle, you need 120 total CPEs: at least 90 in Group A and the other 30 in Group A or B. Keeping the suggested pace of 40 a year satisfies the cycle total. Credits earned in any year of the cycle count toward the 120, though only up to 40 Group A credits earned in the final six months of a cycle can roll over to the next one. If you earn 60 credits in year one, you need only 60 more over the rest of the cycle.
Your certification cycle starts when you earn CISSP, not January 1st. If you were certified on March 15th, your first year runs through March 14th of the following year. ISC2 tracks your cycle dates and sends reminders as deadlines approach, but keeping track of your own credits and staying compliant is your job.
Beyond CPE credits, you pay an Annual Maintenance Fee of $135 to ISC2 each year. This fee funds ISC2 operations, exam development, and member services. Missing the AMF payment suspends your certification regardless of how many CPE credits you’ve earned. You have to meet both requirements, credits and payment, to stay active.
Why ISC2 Requires Continuing Education
In cybersecurity, knowledge that stops moving goes stale, and the CPE requirement is built around that. When CISSP launched in 1994, the internet was barely commercial, cloud computing didn’t exist, and mobile devices meant pagers. A certification testing 1994 knowledge would be worthless today without mechanisms forcing ongoing learning.
ISC2 updates the CISSP exam every three years through Job Task Analysis studies, surveying thousands of security professionals about actual work activities. The exam outline shifts accordingly. Domain weights change, topics come and go, and the emphasis moves toward current practice. CPE requirements keep certified professionals moving with the exam content so their credential still reflects what they know.
From an employer perspective, CPE compliance signals that a CISSP holder remains engaged with the profession. Anyone can pass an exam once, but keeping the certification for years shows sustained commitment. When organizations require CISSP for positions, they’re partly buying assurance that the credential holder continues learning, not just that they once knew enough to pass a test.
The requirement also serves professional liability purposes. CISSPs bound by the ISC2 Code of Ethics commit to providing competent service. Continuing education supports that commitment by keeping practitioners current on threats, technologies and practice. A CISSP advising on cloud security should understand current cloud architectures as well as the concepts tested when they originally certified.
CPE Credit Categories and Values
ISC2 divides CPE activities into Group A (directly related to CISSP domains) and Group B (general professional development). All 120 cycle credits can come from Group A activities. A maximum of 30 credits per cycle can come from Group B, which covers activities that build professional skills without directly addressing CISSP domain content.
Education: Courses, Seminars, and Training
1 CPE per hour of instruction
Formal training generates one credit per contact hour. A 40-hour training course yields 40 CPEs. This includes vendor training, college courses, professional seminars, and structured online learning. The training must relate to CISSP domains for Group A credit. A project management course counts as Group B, while a threat intelligence course counts as Group A. Retain certificates of completion or transcripts as documentation.
Conferences and Events
1 CPE per hour of attendance
Security conferences like RSA, Black Hat, or regional events generate credits based on actual session attendance. A three-day conference with six hours of sessions daily yields 18 CPEs. Exhibitor hall time and networking don’t count. Only educational sessions do. ISC2’s own events, including Security Congress and chapter meetings, qualify. Keep your badge, registration confirmation, and ideally a log of which sessions you attended.
Self-Study: Reading and Research
1 CPE per hour of study (capped at 5 per book or magazine)
Reading security books, research papers, articles, and technical documentation counts as self-study. One hour of reading equals one CPE. You can earn your entire suggested annual total through self-study alone, though ISC2 may request documentation of what you studied. Maintain a reading log with titles, authors, dates, and time spent. The NIST publications library has plenty of free material that clearly qualifies.
Professional Contributions: Writing and Speaking
Variable: up to 40 CPEs depending on contribution
Publishing articles, whitepapers or books earns a lot of credit. A published article can earn up to 20 CPEs and a book up to 40. Speaking at conferences or leading training sessions earns credits based on preparation and delivery time, with the specific amounts defined in the ISC2 CPE Handbook. You learn while preparing, and other people learn from what you produce.
Volunteer Work and Mentoring
1 CPE per hour
Serving on ISC2 committees, volunteering for chapter activities, mentoring candidates preparing for CISSP, or contributing to security community projects generates credits at one per hour. This includes reviewing exam questions for ISC2, participating in working groups for standards bodies, or mentoring through formal programs. Document your hours and the organization you supported.
Unique Work Experience
Up to 10 CPEs per entry for qualifying projects
Work projects that push you into new security areas can qualify for CPE credit. Implementing a new security technology, leading an incident response for a novel threat, or developing a security program from scratch involves learning that ISC2 recognizes. Routine job duties don’t count, but projects requiring you to learn new skills or apply existing knowledge in new ways can qualify. Document the project scope, what you learned, and hours invested.
Tracking and Submitting CPE Credits
ISC2 provides an online portal through your member account for tracking CPE credits. You submit activities as you complete them, entering descriptions, dates, credit hours claimed, and the applicable CISSP domain. The system tracks your running total against the cycle requirement, showing exactly where you stand at any moment.
You don’t need to submit documentation with each entry, but ISC2 advises keeping supporting evidence for at least 12 months after the end of your certification cycle. ISC2 conducts random audits where they request proof of claimed activities. Acceptable documentation includes certificates of completion, conference badges, transcripts, publication copies, and detailed logs for self-study activities. Failed audits can result in credit rejection and certification suspension.
The domain mapping matters because ISC2 wants to see engagement across the CISSP body of knowledge instead of a narrow focus on one area. While there’s no requirement to earn credits in every domain, spreading activities across domains demonstrates broad ongoing competence. If all your credits come from network security training, consider branching into governance, risk management, or software security topics.
Submit credits as you go instead of batching entries at year end. Regular submission creates an audit trail showing consistent engagement throughout the year. It also prevents the frustration of trying to remember activities from months earlier when documentation details have faded from memory.
Free and Low-Cost CPE Opportunities
Earning 40 CPEs annually doesn’t require expensive training or conference attendance. Plenty of free resources produce legitimate credits if you put in the time.
- ✓ISC2 webinars and online events run throughout the year at no cost to members. Each hour of attendance generates one CPE. Topics cover current threats, emerging technologies, career development, and detailed sessions on individual CISSP domains. The ISC2 webinar archive contains hundreds of recorded sessions available on demand.
- ✓Vendor webinars and training often qualify when focused on security topics. Microsoft, AWS, Google Cloud, and most major vendors offer free security training. Their motivation is product adoption, but the content often covers real security concepts that apply beyond their own platforms. Document the security focus when submitting these credits.
- ✓Government publications are a large pile of free reading material. NIST Special Publications cover everything from risk management frameworks to cryptographic guidelines. CISA resources address current threats and defensive practices. Working through them builds CISSP knowledge and earns self-study credits at the same time.
- ✓Security podcasts count toward self-study credits when you engage actively. Passive listening while commuting doesn’t qualify, but focused attention with note-taking does. Shows like Darknet Diaries, Security Now, and Risky Business cover current events and technical topics that reinforce CISSP knowledge. Document episodes and key takeaways in your study log.
- ✓Local ISC2 chapter meetings often occur monthly and are free for members. Chapters host speakers on various security topics, and attendance generates one CPE per hour. Chapters also give you networking and a local professional community, which online learning can’t really replace. Find your nearest chapter through the ISC2 chapter directory.
Strategies for Consistent CPE Accumulation
The CISSPs who struggle with CPE requirements typically share a pattern: they ignore professional development for eleven months, then panic-search for activities in month twelve. Those who find CPEs effortless integrate learning into their regular routine.
Set a monthly target of 3-4 CPEs rather than thinking annually. At 3.5 CPEs per month, you exceed the suggested 40 credits a year without any single month demanding significant time investment. Four hours of security reading, one webinar, or half a day at a local chapter meeting satisfies a month’s worth of credits. At that pace it stops feeling like a chore.
Tie CPE activities to actual work needs. If your organization is evaluating SIEM platforms, research the options thoroughly. That investigation earns self-study credits while serving your job. If you’re preparing a security awareness presentation, the preparation time counts toward professional development. You get paid time and credits out of the same hours.
Use a few high-yield activities. Attending a two-day security conference generates 12-16 CPEs in concentrated time. Earning a new certification in a related field yields credits based on study hours. Writing an article for publication can generate 10+ CPEs while building your professional reputation. One of these can cover several months of requirements.
Build a CPE calendar at the start of each year. Identify conferences you’ll attend, certifications you might pursue, regular chapter meetings, and webinar series you’ll follow. Things that are on the calendar early tend to happen, and things that aren’t get pushed aside by daily urgencies. Review progress quarterly and adjust if you’re falling behind pace.
When CPE Requirements Become Challenging
Some circumstances make CPE compliance hard. Extended illness, family emergencies, military deployment, or career transitions can disrupt professional development activities. ISC2 recognizes that life happens and provides accommodation processes for members facing hardship.
If you anticipate difficulty meeting CPE requirements, contact ISC2 before your deadline passes. They may grant extensions, accept alternative documentation, or work with you on modified requirements. Reaching out early shows good faith. If you wait until after a deadline to explain, it reads like excuse-making even when the hardship is real.
Career changes that take you outside security temporarily create CPE challenges. A CISSP who moves into general IT management, product development, or a non-technical role may find fewer natural opportunities for security-specific learning. Keeping credits up through that kind of move takes deliberate effort: scheduling webinars, blocking out reading time, and attending events you might otherwise skip.
Some CISSPs question whether maintenance is worthwhile if they’re no longer working directly in security. The answer depends on your likelihood of returning to security roles. Letting certification lapse means retaking the exam from scratch if you later want credentials. If there’s any reasonable chance you’ll want CISSP on your resume in the future, maintaining it is far easier than re-earning it.
Consequences of Non-Compliance
Missing CPE requirements or AMF payments doesn’t immediately revoke your certification. ISC2 provides a grace period and a remediation process. However, consequences escalate quickly if you don’t address deficiencies.
Initial non-compliance results in suspension. Your certification becomes inactive, you can no longer use the CISSP designation, and ISC2’s member directory won’t confirm your credentials. Employers verifying certification status will see you as non-current. Suspension lasts until you satisfy outstanding requirements and pay any back fees.
Extended non-compliance leads to certification revocation. Once it’s revoked there’s no reinstatement path. You would need to pass the current exam and restart the endorsement process as if you’d never held the certification. After everything it took to earn CISSP in the first place, that’s a painful loss.
Beyond formal consequences, CPE non-compliance signals professional disengagement. Job applications asking about certification status require honesty about suspended credentials. Interview questions about recent professional development become awkward when you haven’t engaged with the field in years. Part of the credential’s value is what it says about ongoing commitment, and a lapsed one says the opposite.
Making CPEs Work for Your Career
The CISSPs who handle this best treat CPEs as a nudge toward learning they’d do anyway, not as paperwork. Forty hours of professional development a year is modest, less than one hour per week. It feels very different when you think of it as time to invest in yourself instead of a debt to ISC2.
Use the requirement to explore areas outside your daily work. A security analyst focused on detection might use CPE activities to learn governance and risk management, broadening skills toward management roles. A GRC specialist might dig into technical security architecture, building credibility with engineering teams. CPEs provide justification for learning that immediate job pressures might otherwise crowd out.
Pick some activities that get you noticed. Publishing articles and speaking at conferences build your professional reputation, and mentoring grows your network and your leadership skills. The career payoff from these is usually worth far more than the credits.
If your employer supports professional development, align CPE activities with available resources. Many organizations fund conference attendance, training programs, and certification pursuits. If your company will pay for it, there’s no reason to pay for it yourself.
A practical first step: open the CPE portal in your ISC2 member account, check where your cycle dates fall, and log whatever you’ve already done this year before the details fade.
✓ Reviewed against official ISC2 sources. The exam facts on this page are checked against ISC2’s official CISSP Exam Outline and other primary sources. Last verified August 2026. certifiedcissp.com is an independent resource and is not affiliated with, endorsed by, or sponsored by ISC2.
Leave a Reply