Fortinet's NSE Certification Program Just Changed Again — Here's What You Need to Know Before July 15, 2026

If you feel like Fortinet’s certification names change every time you check, you’re not imagining it. In October 2023, Fortinet dropped the numbered NSE 1–8 ladder for named, role-based certifications (FCF, FCA, FCP, FCSS, FCX). On July 15, 2026, it’s flipping back — sort of.

Here’s the plain-English version of what’s actually happening.

What’s Changing on July 15, 2026

Fortinet is retiring the named-only structure and reintroducing NSE 1 through NSE 8 as visible exam levels, while keeping role-based certification names as the credential you actually display. In practice:

  • FCF, FCA, FCP, FCSS, and FCX are officially retired as of July 15, 2026.
  • The certification levels expand from 5 to 8, organized under four training tracks: Secure Networking, Security Operations, Cloud Security, and SASE.
  • Certifications are named (so you still say “I hold Fortinet Certified Professional in Secure Networking”), but each is now tied to a specific NSE exam level behind the scenes — professional and specialist certs map to NSE 4 through NSE 7, and the expert-level credential (formerly FCX) is tied directly to NSE 8.
  • Two new industry certifications launch: one for OT Security, one for MSSP Security.
  • Pricing is standardized: single-exam certifications cost $400; two-exam certifications cost $200 per exam.

If you already hold a certification under the current naming, you don’t need to do anything manually — Fortinet issues your NSE 1–8 badge automatically as part of the July 15 transition, based on your existing credentials.

The Big One: NSE 8 (Expert Level) Gets Harder to Earn

The expert tier has seen the most structural change, and it’s already in effect as of April 2026:

  • The legacy written exam (NSE8_812) is no longer required for new candidates.
  • Instead, you now need to pass two separate practical exams: an NSE 8 Core module (hands-on, proctored, real-time configuration and troubleshooting) and one NSE 8 Specialization module aligned to a specific solution domain, completed within a year of the Core.
  • New prerequisites apply: you must already hold valid NSE 4 (v7.6+), NSE 5 or NSE 6, and NSE 7 (v7.6+) before you’re eligible to attempt the Core module.

Translation: NSE 8 is no longer something you can cram for with a study guide. It’s testing whether you can actually operate in a live Fortinet environment under time pressure.

Two New AI-Focused Tracks

Fortinet also added two new specializations sitting at the NSE 6 and NSE 7 levels, both requiring a valid NSE 4 as a prerequisite:

  • FortiAI Analyst Track — deployment and management of Fortinet’s AI-assisted SOC tools, including FortiAI-Detect and FortiDeceptor.
  • Automated Security Operations (ASO) Track — Security Fabric orchestration, SOAR playbook development in FortiSOAR, and AI-driven incident response.

If you already hold NSE 6 or NSE 7, note that you don’t get automatic credit for these new tracks — they require a separate exam attempt.

What This Means for Your Study Plan

  • If you’re mid-preparation for a legacy exam: schedule it before the July 13, 2026 Pearson VUE cutoff for legacy versions. After that, only the updated blueprint is offered.
  • If you’re starting fresh: study directly against the new NSE-level blueprint rather than older FCP/FCSS materials — the underlying content overlaps heavily, but exam numbering and prerequisites have shifted.
  • If you’re targeting NSE 8: confirm your NSE 4/5/6/7 prerequisites are current (v7.6+) well before you attempt to register for the Core practical module.

Getting Ready

Whichever level you’re targeting, working through realistic scenario questions against the current blueprint is still the fastest way to find your weak spots before exam day. DailyDebian’s Fortinet NSE question sets are mapped to the current exam objectives, so you’re not accidentally studying retired content.

Check DailyDebian’s Fortinet NSE practice question sets — built around the current exam blueprint, not the retired FCP/FCSS naming.

Back to blog