Menu

1 / 5

The playbook that was supposed to block the account ran zero times

DEV Community: azure·CD Security Lab·10 days ago
#EXgo85Xo
#devtoazure#devto#dev#microsoft#rule
Reading 0:00
15s threshold

Source: CD's readiness notes Sentinel-Readiness/Analytics rule.md (the Automation / SOAR notes: lab 2 "5 failed logons in 20 minutes → incident, reset password, block user, email the manager", lab 3 "how to stop a rule firing for one analytics rule"), rebuilt as a lab story and cross-checked against Microsoft Learn on 2026-10-28. Lab names only; screens are drawings.

In the spring Contoso's SOC built the automation from my notes: five failed sign-ins to the Azure portal in twenty minutes → incident → playbook pb-block-user disables the account, resets the password and emails the manager. It was demoed to the CISO. It worked.

In October a contractor's account takes 1,400 password guesses in an hour, then one success. The incident is created at 23:12. The account is disabled at 00:05, by hand, by the on-call analyst who happened to look. The playbook's run history for the last five months: 0 runs .

Nothing was broken on the night.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.