300-710 · Question #213
An engainer must add DNS-specific rules to me Cisco FTD intrusion policy. The engineer wants to use the rules currently in the Cisco FTD Snort database that are not already enabled but does not want…
The correct answer is C. Change the rule state within the policy being used. To selectively enable specific DNS rules from the Snort database within a Cisco FTD intrusion policy without enabling more than needed, the engineer must manually change the state of individual rules within the active policy. This allows for granular control and avoids…
Question
An engainer must add DNS-specific rules to me Cisco FTD intrusion policy. The engineer wants to use the rules currently in the Cisco FTD Snort database that are not already enabled but does not want to enable more than are needed. Which action meets these requirements?
Options
- AChange the dynamic state of the rule within the policy.
- BChange the base policy to Security over Connectivity.
- CChange the rule state within the policy being used.
- DChange the rules using the Generate and Use Recommendations feature.
How the community answered
(47 responses)- A9% (4)
- B13% (6)
- C74% (35)
- D4% (2)
Why each option
To selectively enable specific DNS rules from the Snort database within a Cisco FTD intrusion policy without enabling more than needed, the engineer must manually change the state of individual rules within the active policy. This allows for granular control and avoids unnecessary rule activation.
"Dynamic state" refers to how rules behave based on network conditions or global settings, not the primary mechanism for individually enabling or disabling specific rules from the database.
Changing the "base policy" (like to Security over Connectivity) applies a predefined set of rules, which would likely enable many rules beyond the specific DNS ones needed and might disable others.
To add specific DNS-related intrusion rules that are not currently enabled without activating unnecessary rules, an engineer must manually adjust the "rule state" for those particular rules within the active intrusion policy. This allows for precise, granular control over which individual Snort rules are active, ensuring only the required DNS-specific rules are enabled and meeting the requirement of not enabling more than needed.
The "Generate and Use Recommendations" feature automatically suggests rules based on network traffic, which could enable many more rules than just the specific DNS ones desired, potentially exceeding the "not more than needed" requirement.
Concept tested: Cisco FTD intrusion policy rule management
Source: https://www.cisco.com/c/en/us/td/docs/security/firepower/640/configuration/guide/fpmc-config-guide-640/intrusion_policies_and_rules.html#concept_3s4_z5z_v1b
Topics
Community Discussion
No community discussion yet for this question.