An administrator is configuring a DLP rule for FTP traffic. When adding the rule to a DLP sensor, the administrator notes that the Ban Sender action is not available (greyed-out), as shown in the exhibit. Which of the following is the best explanation for the Ban Sender action NOT being available?

Question

Accepted Answer

A. The Ban Sender action is never available for FTP traffic. The 'Ban Sender' action within FortiGate DLP is exclusively designed for email protocols (like SMTP, POP3, IMAP) to identify and block problematic email addresses. Since FTP is a file transfer protocol and does not involve email senders, this action is technically irrelevant and therefore never available for FTP DLP rules.

Answer

B. The Ban Sender action needs to be enabled globally for FTP traffic on the FortiGate unit before There is no global setting on a FortiGate to enable the 'Ban Sender' action for FTP traffic, as the feature is not designed for that protocol.

Answer

C. Firewall policy authentication is required before the Ban Sender action becomes available. Firewall policy authentication does not govern the availability of specific DLP actions; rather, it controls user access, while DLP actions are protocol-specific.

Answer

D. The Ban Sender action is only available for known domains. No domains have yet been added to The 'Ban Sender' action targets email addresses, not general domains, and its availability is not contingent on pre-adding domains to the FortiGate for FTP traffic.

An administrator is configuring a DLP rule for FTP traffic. When adding the rule to a DLP sensor, the administrator notes that the Ban Sender action is not available (greyed-out), as shown in the…

Question

Exhibit

Options

How the community answered

Why each option

Topics

Community Discussion