FCSS FortiSASE 25 Administrator study plan
FCSS FortiSASE 25 Administrator · Give each week a clear focus.
8 weeks · About 7 hours per week
FortiSASE Deployment and Initial Configuration
Map the FortiSASE administrative hierarchy (account, organization, tenant, and per-region deployment) and diagram how a tenant relates to FortiCloud identity and licensing
Walk through the deployment wizard end to end in a lab tenant and record every prerequisite it demands before the tenant becomes usable
Configure at least two administrator accounts with distinct role-based profiles and verify which UI areas each profile can reach
Explain in writing how the point-of-presence (POP) selection model affects user latency, and identify the settings that constrain or override automatic POP selection
Your checkpoint
A one-page deployment runbook listing prerequisites, admin roles, and POP-selection decision points, validated against a working lab tenant
FortiSASE Deployment and Initial Configuration & Secure Private Access and SD-WAN Integration
Configure a FortiGate as a secure private access (SPA) edge and register it to the FortiSASE tenant, capturing the trust and certificate steps required
Define internal subnets and destinations that should be reachable through the private access path, and verify traffic actually traverses the tunnel instead of the public internet
Distinguish the deployment modes available for private access (for example agent-based versus tunnel-based) and select the correct one for a stated branch scenario
Document the outbound ports and connectivity requirements that must be allowed on the on-premises firewall for the tunnel to establish
Your checkpoint
A working site-to-site private access tunnel from a lab FortiGate to FortiSASE, with a screenshot-free written test result showing an internal host reached through the tunnel
Secure Private Access and SD-WAN Integration
Configure SD-WAN on the FortiGate side so that private access traffic prefers a healthy WAN link and fails over when that link degrades
Build at least two SD-WAN health-check targets and interpret the resulting SLA log entries when a link is artificially degraded
Describe how FortiSASE handles traffic steering for private versus internet-bound traffic and where the decision is enforced
Troubleshoot a deliberately broken tunnel by checking certificates, routing, and policy order in sequence
Your checkpoint
A written failure-analysis report of one induced SD-WAN failover, including the health-check evidence and the exact configuration change that resolved the induced fault
Secure Internet Access and Web Filtering
Configure a web filter profile with category-based blocking, URL override entries, and safe-search enforcement, then verify each behavior with test requests
Explain the difference between allow, block, monitor, and warning actions and predict which page a user sees for each
Set up HTTPS inspection exclusions for categories that must not be decrypted and justify each exclusion
Compare the available content-filtering enforcement points and state which one applies to roaming users versus on-premises users
Your checkpoint
A web-filter test matrix of at least ten URLs across five categories, each with the configured action and the observed result, plus a note on every mismatch
FortiSASE Security Services (SSL Inspection, DNS, Antivirus, IPS, Application Control)
Configure SSL inspection with a custom certificate and a deep-inspection exemption list, then prove that an exempted site is not decrypted
Enable DNS filtering and demonstrate blocking of a known-malicious test domain at the DNS layer rather than the HTTP layer
Tune antivirus and IPS profiles so that a benign test file and a known test signature produce the expected log entries without excessive false positives
Apply an application control profile that blocks a specific application category while permitting a business-critical application in the same category
Your checkpoint
A security-profile configuration summary covering SSL inspection, DNS filter, antivirus, IPS, and application control, each with the log evidence that proves the control fired
Client and Endpoint Management (FortiClient, FortiSASE Client, ZTNA)
Deploy the FortiSASE client to a test endpoint and enroll it into the tenant, confirming that the endpoint appears in the management view
Configure ZTNA access rules that grant one user group access to one internal application and deny a second group, then verify both outcomes
Explain how endpoint posture (for example OS version or antivirus state) can gate access and configure one posture check
Distinguish FortiClient EMS management from FortiSASE client management and state which tasks belong to each
Your checkpoint
An end-to-end ZTNA demonstration write-up: one allowed user, one denied user, and the posture check that was evaluated, with the rule logic explained
Monitoring, Logging, and Troubleshooting
Navigate the logging views to isolate traffic for a single user across web filter, IPS, and private access logs
Configure log forwarding or a syslog destination and confirm events arrive at the collector
Use the built-in diagnostic and troubleshooting views to identify why a user session was blocked
Build a short triage checklist that orders investigation steps from client status to policy evaluation to log confirmation
Your checkpoint
A triage checklist applied to three seeded faults (a blocked site, a failed tunnel, a denied ZTNA rule), each resolved with the log line that identified the cause
FortiSASE Deployment and Initial Configuration & Secure Private Access and SD-WAN Integration & Secure Internet Access and Web Filtering & FortiSASE Security Services (SSL Inspection, DNS, Antivirus, IPS, Application Control) & Client and Endpoint Management (FortiClient, FortiSASE Client, ZTNA) & Monitoring, Logging, and Troubleshooting
Re-run every lab from weeks 1 through 7 in a fresh tenant without consulting notes, noting every step that required recall
Review the weakest two domains identified during the re-run and close the specific gaps with targeted reading
Practice explaining the private access and SD-WAN architecture aloud in under five minutes, as if to a colleague
Confirm familiarity with the administrative tasks most likely to appear in scenario form, such as POP selection, inspection exemptions, and ZTNA rule ordering
Your checkpoint
A personal gap list with every item either resolved or explicitly flagged as remaining risk, plus a completed timed self-assessment across all six domains
Milestones
Week 2: You can describe, without notes, the full path a packet takes from a roaming user to an internal server through the private access tunnel, naming each component it crosses
Week 4: You can predict the user-visible outcome of any web filter action and have verified at least ten predictions against real requests
Week 6: A denied ZTNA request and an allowed ZTNA request both produce the expected log entries, and you can explain which rule matched and why
Week 8: All seven labs have been rebuilt from scratch in a clean tenant, and your remaining gap list contains only items you have consciously accepted as risk