A customer would like to use FortiGate fabric integration with FortiCNP.

Comprehensive and Detailed Explanation From FortiOS 7.6, FortiWeb 7.4 Exact Extract study guide:

According to theFortiCNP 24.x Administration Guideand theFortiOS 7.6 Security Fabric Integrationdocumentation, integrating a FortiGate-VM with FortiCNP requires specific local configurations on the FortiGate to ensure the cloud security platform can ingest and analyze traffic data.

Configuring Logging (Option C):Before adding the FortiGate VM to FortiCNP, the administrator mustEnable Send Logson the FortiGate. This allows the FortiGate to forward the necessary security telemetry and traffic logs to the FortiCNP cloud endpoint for threat correlation and risk analysis.

Policy and Inspection Setup (Option D):The integration relies on the FortiGate's ability to identify and block threats at the network layer. Specifically, the administrator mustCreate a FortiGate IPS SensorandCreate a FortiGate Firewall Policy. The IPS sensor detects malicious patterns, while the firewall policy dictates which traffic is subjected to this inspection.

Deep Packet Inspection (Option E):To provide visibility into encrypted traffic—which is critical for identifying threats hidden in HTTPS flows—the administrator mustCreate an SSL/SSH Inspection Profileon the FortiGate. Without this profile, FortiCNP would lose significant visibility into potential attack vectors utilizing encrypted channels.

Why other options are incorrect:

Option A:While pre-shared keys are used in VPN and some Fabric setups, they are not listed as one of the specific mandatory steps for the initial FortiGate-to-FortiCNP fabric integration workflow.

Option B:While certificate exchange is part of the overall trust relationship, the primary "mandatory configuration stepson FortiGate" defined in the official setup guide focus on the logging and security profile components required to generate the data FortiCNP needs.