nerdexam
Fortinet

NSE4_FGT-7.0 · Question #172

A network administrator has enabled SSL certificate inspection and antivirus on FortiGate. When downloading an EICAR test file through HTTP, FortiGate detects the virus and blocks the file. When…

The correct answer is B. SSL/SSH Inspection profile is incorrect. The FortiGate fails to detect a virus over HTTPS despite having SSL certificate inspection enabled because the SSL/SSH Inspection profile is not correctly configured for deep inspection. This prevents the FortiGate from decrypting and inspecting encrypted traffic for threats.

Security Profiles

Question

A network administrator has enabled SSL certificate inspection and antivirus on FortiGate. When downloading an EICAR test file through HTTP, FortiGate detects the virus and blocks the file. When downloading the same file through HTTPS, FortiGate does not detect the virus and the file can be downloaded. What is the reason for the failed virus detection by FortiGate?

Options

  • AApplication control is not enabled
  • BSSL/SSH Inspection profile is incorrect
  • CAntivirus profile configuration is incorrect
  • DAntivirus definitions are not up to date

How the community answered

(54 responses)
  • A
    4% (2)
  • B
    70% (38)
  • C
    7% (4)
  • D
    19% (10)

Why each option

The FortiGate fails to detect a virus over HTTPS despite having SSL certificate inspection enabled because the SSL/SSH Inspection profile is not correctly configured for deep inspection. This prevents the FortiGate from decrypting and inspecting encrypted traffic for threats.

AApplication control is not enabled

Application control's primary role is to identify and control applications, not directly decrypt SSL/TLS traffic for antivirus scanning.

BSSL/SSH Inspection profile is incorrectCorrect

For FortiGate to inspect encrypted HTTPS traffic for viruses, it must be able to decrypt the traffic. While SSL certificate inspection is enabled, the specific SSL/SSH Inspection profile must be configured for 'deep inspection' (full SSL inspection) to perform this decryption and allow security profiles like antivirus to inspect the content. If it's configured for 'certificate inspection' or 'no inspection,' the encrypted content remains uninspected.

CAntivirus profile configuration is incorrect

The antivirus profile is correctly configured as it detects the virus over HTTP, indicating the profile itself is functional, but it cannot apply to uninspected HTTPS traffic.

DAntivirus definitions are not up to date

Antivirus definitions are up to date since the EICAR file is detected and blocked over HTTP, proving the definitions are current and effective when traffic is visible.

Concept tested: FortiGate SSL/SSH Deep Inspection requirements for threat detection

Source: https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/330588/ssl-ssh-inspection-profile

Topics

#SSL inspection#HTTPS inspection#antivirus#security profiles

Community Discussion

No community discussion yet for this question.

Full NSE4_FGT-7.0 Practice