A network administrator has configured FortiGate to send files to FortiSandbox for analysis. However, files are not being submitted. The administrator checks the FortiGate configuration and sees that the FortiSandbox server IP is correctly entered. What is the most likely cause of the issue?
Trap 1: The FortiSandbox is not licensed for file submission
Licensing issues would typically appear in logs, but the network connectivity check is more fundamental.
Trap 2: The file type is not supported by FortiSandbox
Unsupported file types would be excluded based on configuration, not silently fail submission.
Trap 3: The FortiGate antivirus profile is set to flow-based inspection
D is incorrect because flow-based inspection does not prevent file submission to FortiSandbox; file submission works with both flow-based and proxy-based inspection. The most common cause is a firewall blocking UDP/TCP port 514.
- A
A firewall policy is blocking communication to FortiSandbox on port 514
FortiGate communicates with FortiSandbox via TCP port 514 (or custom). A missing or blocking policy would prevent file submission.
- B
The FortiSandbox is not licensed for file submission
Why wrong: Licensing issues would typically appear in logs, but the network connectivity check is more fundamental.
- C
The file type is not supported by FortiSandbox
Why wrong: Unsupported file types would be excluded based on configuration, not silently fail submission.
- D
The FortiGate antivirus profile is set to flow-based inspection
Why wrong: D is incorrect because flow-based inspection does not prevent file submission to FortiSandbox; file submission works with both flow-based and proxy-based inspection. The most common cause is a firewall blocking UDP/TCP port 514.