Question 860
At Kingsford Biotechnology, the FortiGate 7.6 security administration team encounters the following authorized operational case: a proprietary application suffers a documented protocol attack that lacks an applicable default IPS signature. They need a defensible FortiOS configuration, diagnosis, validation or prevention decision. Which recurring review is most relevant to the same root risk?
Explanation
Correct Answer
Version custom signatures and test false positives after app updates. This recurring practice addresses ips custom signature deployment because a custom protocol risk may need a precise signature when standard databases do not identify it. It reinforces the supported change to create and validate a supported narrowly scoped custom IPS signature for the authorized environment rather than relying on an unrelated periodic audit.
Incorrect Answers
Track changes to internal certificate authorities and chain distribution reduces recurrence of untrusted certificate chain, rather than the observed ips custom signature deployment issue. The relevant preventive control for Kingsford Biotechnology is: Version custom signatures and test false positives after app updates. This distinction matters because a custom protocol risk may need a precise signature when standard databases do not identify it.
Review privacy exclusions and inspection purposes during policy recertification reduces recurrence of endpoint ssl inspection privacy boundary, rather than the observed ips custom signature deployment issue. The relevant preventive control for Kingsford Biotechnology is: Version custom signatures and test false positives after app updates. This distinction matters because a custom protocol risk may need a precise signature when standard databases do not identify it.
Review security exceptions for unintended shared-host effects reduces recurrence of webfilter exemption policy scope, rather than the observed ips custom signature deployment issue. The relevant preventive control for Kingsford Biotechnology is: Version custom signatures and test false positives after app updates. This distinction matters because a custom protocol risk may need a precise signature when standard databases do not identify it.