FCP FortiAnalyzer 7.4 study plan
FCP FortiAnalyzer 7.4 · Give each week a clear focus.
8 weeks · About 7 hours per week
Deployment and System Configuration
Map the FortiAnalyzer 7.4 deployment topologies (standalone, HA primary/secondary, collector/analyzer split) and write a one-paragraph tradeoff note for each
Diagram the ADOM concept and list the ADOM modes (normal, backup, collector, analyzer) with the operational role of each
Identify the licensing and VM resource sizing inputs (log rate, retention days, disk) that drive hardware or VM selection
Walk through the initial setup wizard steps in a lab VM and record every decision point you had to make
Your checkpoint
A one-page deployment decision matrix covering topology, ADOM mode, and sizing inputs, with your lab VM configured and reachable via GUI and CLI
Deployment and System Configuration
Configure administrative profiles, admin users, and remote authentication (LDAP/RADIUS) in the lab and verify role separation
Set up an HA pair of FortiAnalyzers in the lab and force a failover to observe what state transfers
Configure system settings that affect operations: NTP, DNS, mail server, and FortiAnalyzer logging of its own events
Practice backup and restore of configuration and explain what is and is not included in a config backup
Your checkpoint
A working HA pair in the lab plus a written failover test log showing pre- and post-failover state, and a successful config backup/restore cycle
Log Collection, Parsing, and Storage
Register a FortiGate to FortiAnalyzer and confirm logs arrive, distinguishing device registration from log forwarding authorization
Compare log forwarding modes (real-time vs. store-and-forward, reliable vs. best-effort) and predict behavior when the analyzer is unreachable
Configure disk quotas and log retention settings per ADOM and verify the effect on stored log volume
Trace a single session's logs from FortiGate through to FortiAnalyzer and confirm the fields survive the trip
Your checkpoint
A log pipeline diagram with the FortiGate-to-FortiAnalyzer path annotated, backed by a lab capture showing a session's logs stored and searchable on the analyzer
Log Collection, Parsing, and Storage
Explain log parsing: how FortiAnalyzer identifies log type, maps fields, and where parsers or log-type definitions matter
Use log search filters and structured queries to isolate traffic, event, and security logs by device and time window
Configure and verify a log-forwarding destination from FortiAnalyzer to a syslog or secondary analyzer target
Practice troubleshooting a device that registers but produces no searchable logs, listing the checkpoints in order
Your checkpoint
A troubleshooting runbook for 'device registered but logs missing' with at least five ordered checkpoints, each verified against a deliberately broken lab condition
Reports and Report Management
Build a custom report from scratch: choose a dataset, bind it to a chart, and lay out the report page
Create a scheduled report with a defined time period, output format, and email delivery, then confirm it fires
Differentiate built-in datasets from custom SQL datasets and write one simple custom dataset against your lab logs
Configure report templates and explain how templates differ from finished reports in reuse
Your checkpoint
A scheduled custom report delivered by email to your lab inbox, plus the custom dataset definition saved and documented
Reports and Report Management & Incident Investigation, Events, and Automation
Design a report pack for a compliance-style audience and justify each chart against a security question it answers
Explain report output formats and storage locations, and verify where generated reports are retained and for how long
Configure an event handler that triggers on a log condition and sends an alert, then tune it to reduce noise
Distinguish events, incidents, and alerts in FortiAnalyzer 7.4 and map which console area handles each
Your checkpoint
A report pack plus one working event handler with an alert, and a short note mapping events, incidents, and alerts to their console locations
Incident Investigation, Events, and Automation
Investigate a simulated incident end to end: start from an alert, pivot into logs, build a timeline, and record findings
Use the incident investigation workflow to attach evidence, add notes, and change incident status
Configure automated playbooks or automation stitches that respond to a detected event and verify the action fires
Explain how indicators of compromise and threat feeds feed into event detection on FortiAnalyzer
Your checkpoint
A completed incident investigation record for a simulated compromise, with timeline, evidence attachments, and the automation action that fired
Deployment and System Configuration & Log Collection, Parsing, and Storage & Reports and Report Management & Incident Investigation, Events, and Automation
Re-run every lab from weeks 1 to 7 from a clean snapshot without notes and log each step you could not recall
Build a one-page cheat sheet of commands, settings paths, and limits that you kept forgetting
Take a timed practice set across all four domains and review every wrong answer back to the source concept
Rehearse explaining three configuration choices out loud as if defending them to a colleague
Your checkpoint
A personal cheat sheet plus a scored practice run with a written review of every missed item and the concept it traced back to
Milestones
Week 2: You can stand up a FortiAnalyzer VM, register it in HA, fail over, and restore a config backup without consulting notes
Week 4: A FortiGate's logs arrive, are parsed, are searchable by filter, and you can explain why each step in the pipeline is needed
Week 6: A scheduled custom report lands in your inbox and an event handler alert fires on a condition you defined
Week 8: You complete an end-to-end incident investigation and score your practice run, with every miss traced to a domain