Contoso will run a two-week penetration test, and the SOC expects many noise incidents from known analytics rules during that period. The SOC wants those incidents closed and tagged as they're created, without writing a playbook, and the automation must stop on its own when the test ends. What should you configure?
Show answer and explanation
Answer: B
Explanation
Automation rules can resolve known false or benign positive incidents without playbooks, and a time-limited rule can close them as they’re created while tagging them with the cause.[1] A rule is disabled after its expiration date passes, which suits planned, time-limited activities such as penetration testing, so B is correct.[1]
A closes and tags the incidents, but someone has to remember to disable it, while an expiration date disables the rule at the end of its relevancy without that step.[1] C uses the update trigger, which runs on events such as status, owner, or severity changes rather than on incident creation, so new incidents aren’t closed as they’re created.[1] D requires a playbook, and playbooks that use the Microsoft Sentinel entity trigger can’t be called by automation rules.[2]