Examine the IPS sensor configuration shown in the exhibit, and then answer the question below. An administrator has configured the WINDOWS_SERVERS IPS sensor in an attempt to determine whether the…

While IPS sensors can have filters, the absence of a 'Protocol: HTTPS' option in an IPS filter is not typically the primary reason for IPS failing to log any attack attempts within HTTPS traffic. IPS generally inspects based on signatures, not a global protocol switch.

Although the absence of relevant HTTPS signatures would prevent specific attack detection, the more fundamental issue preventing any IPS logging for HTTPS traffic is the inability to decrypt the traffic for inspection, which full SSL inspection provides.

A DoS policy is designed to mitigate denial of service attacks by rate-limiting or blocking excessive traffic, which is a different function than an IPS sensor's role of detecting and preventing exploit attempts or malicious content within the traffic payload.

For the FortiGate IPS engine to effectively inspect the content within encrypted HTTPS traffic for attack attempts, it must be able to decrypt the traffic. If the firewall policy handling this HTTPS traffic is not configured to use a 'Full SSL inspection' profile, the traffic remains encrypted, and the IPS sensor cannot inspect the payload, thus not generating any logs for potential threats within it.