Question 590
The deployment team is preparing a sign-off for: A security team relies on an external URL category feed to block newly registered phishing URLs but the Security rule is not scoped to the user group. Which mistaken assumption should be rejected before approval?
Explanation
Correct Answer
The risky assumption is treating a dynamic URL feed as a replacement for validating the identity and order of matching rules. In this particular incident, a security team relies on an external URL category feed to block newly registered phishing URLs but the Security rule is not scoped to the user group. The safer path is to compare URL EDL matching, rule user scope, category action and log behavior during test requests and then, when verified, to reference the URL EDL in an appropriately targeted policy and confirm the matching rule order. The risk statement matters because it would obscure the true mechanism, broaden permissions, or falsely certify that the required outcome had been achieved.
Incorrect Answers
Equating retained cached list entries with successful retrieval of the latest threat intelligence. The check concerns equating retained cached list entries with successful retrieval of the latest threat intelligence, not confirming that treating a dynamic URL feed as a replacement for validating the identity and order of matching rules.
Treating IP addresses, domains and URL strings as interchangeable list entries. This assesses treating IP addresses, domains and URL strings as interchangeable list entries; it does not determine the reported condition—a security team relies on an external URL category feed to block newly registered phishing URLs but the Security rule is not scoped to the user group.
Assuming creating an EDL object automatically enforces a block without a referencing policy. The case-specific requirement is confirming that treating a dynamic URL feed as a replacement for validating the identity and order of matching rules, which that option does not establish.