How ContraForce automates detection rule tuning for Microsoft Defender and Sentinel
Reviewed by ContraForce
Video · Video · Beginner · 1:49
A short explainer on keeping one set of baseline detection rules across every customer workspace, catching drift, and having a Security Delivery Agent review a noisy rule before a person approves the change. Watch on YouTube.
Key takeaways
- Every new customer adds detection rules to tune. Tuned by hand, that work grows with every tenant you add.
- Content Management Center keeps your baseline rules in one versioned repository and deploys them to every covered workspace at once.
- A drift scan shows when someone has edited a rule directly in a tenant. You choose whether to keep that change, adopt it for everyone, or put the baseline back.
- Agent Rule Reviews hands a noisy rule to a Security Delivery Agent, which studies the rule's recent incidents and writes a report: a conclusion, the exact query change, why it helps, what a real threat could slip past, and how to test it.
- The agent only advises. Every change goes through a change request that a person reviews and approves before it deploys.
Chapters
- 0:00 Detection rules, explained
- 0:23 One set of baseline rules for every customer
- 0:38 Drift detection
- 0:55 Ask an agent to review a noisy rule
- 1:11 The rule review report
- 1:26 Nothing changes until a person says yes
- 1:38 Handled for you, decided by you
Go deeper in the docs
Related lessons
- Configuring Security Delivery Agents: On Queue, policies and shifts. Set which severities a Security Delivery Agent picks up On Queue, gate its Gamebooks with a confidence threshold, add investigation policies and shifts, link SOPs and check Run History.
- Writing incident response SOPs that analysts and AI agents can both follow. A structure for incident response SOPs that analysts and AI agents can follow the same way: decisions as explicit conditions, per-customer exceptions, versioning and a suspicious sign-in example.
- Getting started: connect your first customer workspace. Pre-onboard a customer in the Workspace Center, send the invite, have their admin grant the core and module consents, then confirm the workspace is live with the onboarding checklist.
