Security 101

What Should You Monitor While a Security Fix Is Waiting?

A known gap stays open until the fix lands. Here is how to watch for anyone using it in the meantime, with a detection rule tied to the finding.

While a security fix is waiting, monitor for the specific activity the open gap would allow. A detection rule aimed at that activity tells you if someone uses the gap before the fix is in place.

The Accelerynt Security Platform pairs posture findings with compensating detection rules you deploy into your Microsoft Sentinel workspace. Each rule is mapped to the threat its finding enables, so if someone exploits the gap before the fix is in place, the rule fires.

Cover the gap

  • Fixes take time. Testing and change approval both stretch the window between finding a gap and closing it.
  • Watch the specific gap. A rule tied to one finding is easier to act on than a broad alert.
  • Give every rule an end date. Retire the interim rule once the fix is confirmed.
  • Keep the fix moving. An interim rule covers the wait and still leaves the fix to do.

Why do security fixes take time?

Many fixes change how people sign in or how systems connect. Blocking legacy authentication is a common example. Microsoft’s guidance is to check sign-in logs first for users whose apps still depend on it, and that review takes time.

97%

Of credential stuffing attacks use legacy authentication, based on Microsoft’s analysis in block legacy authentication with Conditional Access on Microsoft Learn.

The review is necessary work, and it leaves a window where the gap is known and still open. Our post The Change Management Wall looks at why security changes stall in change control, and how to get security changes through a change advisory board covers the process side.

How do you match a detection rule to an open finding?

Start from what the gap lets someone do, then find the log that would show it. The examples below show the pattern.

Open findingWhat to watch while it is openWhere the signal lives
Legacy authentication is not blockedSign-ins that use legacy authentication protocolsEntra sign-in logs, filtered by client app
An account is excluded from a Conditional Access policySign-ins by the excluded account, especially from unfamiliar locationsEntra sign-in logs
An app registration holds risky permissionsNew consent grants and new credentials added to that appEntra audit logs
Admin rights are standing instead of time-boundRole assignments and sign-ins by those admin accountsEntra audit and sign-in logs
Examples for illustration. Microsoft’s steps for finding legacy authentication sign-ins are in block legacy authentication with Conditional Access.

Each rule watches a narrow activity tied to one finding. That keeps the alert quiet until it matters.

How do you set up interim monitoring step by step?

  1. Rank the open findings. Start with gaps an attacker could reach from outside and gaps that touch privileged accounts.
  2. Name the activity each gap allows. Write down what an attacker would do through it, such as signing in with a legacy protocol.
  3. Point a rule at that activity. Build or deploy a Microsoft Sentinel analytics rule that watches for it in the logs you already collect.
  4. Give the alert an owner. Make sure the people watching the queue know the rule exists and what to do when it fires.
  5. Retire the rule with the fix. Once the fix is confirmed, remove the interim rule or fold it into your standing detections.

Interim rules need the same care as any other rule. Read how to tune Microsoft Sentinel detection rules. For how to order the fixes themselves, read how to build a remediation roadmap.

Who should own an interim detection rule?

Two teams touch an interim rule. The team that watches the Sentinel queue owns the alert, and the team fixing the finding owns the date the rule comes out.

If a provider watches your Sentinel, share the open findings with them so each rule lands with someone who is watching. Accelerynt MDR builds detection rules directly in your Sentinel workspace, and your team can see and change them.

How does the Accelerynt Security Platform handle interim detection?

  • Rules come with the finding. Posture findings include compensating detection rules for your Sentinel workspace.
  • Your team deploys them. Each rule goes in with a single copy and paste. The platform itself is read-only.
  • Each rule fits its threat. Rules are mapped to the threat the finding enables, so the alert means something specific.
  • The fix comes too. Findings also carry remediation guidance. Some fixes are scripts you review and run, and others are step-by-step walkthroughs linked to Microsoft Learn.

Where to go next

When a rule fires, the next question is how fast you can contain it. Read how to automate incident containment in Microsoft Sentinel, and see our post on automating identity threat response.

For how detection rules kept in your own workspace work with an MDR provider, read what MDR with custom detection rules means.

Frequently asked questions

What should you monitor while a security fix is waiting?

Monitor for the specific activity the open gap would allow, using a detection rule tied to that finding. The Accelerynt Security Platform pairs posture findings with compensating detection rules you deploy into Microsoft Sentinel, so if someone exploits the gap before the fix is in place, the rule fires.

What is a compensating detection rule?

It is a detection rule that watches for use of a known gap until the fix is in place. It covers the waiting period and is retired once the fix is confirmed.

Can Microsoft Sentinel alert on legacy authentication sign-ins?

Yes, when your Entra sign-in logs flow into Sentinel. The client app field in those logs shows which legacy protocol a sign-in used, and an analytics rule can watch for it.

Should interim detection rules stay after the fix?

Remove them or fold them into your standing detections once the fix is confirmed. A rule left in place after its gap is closed adds to the queue without adding protection.

Who should own interim detection rules?

The team that watches your Sentinel queue should own the alert, and the team fixing the finding should own the end date. If an MDR provider watches your Sentinel, share the open findings with them. When a finding comes from the Accelerynt Security Platform, it includes compensating detection rules you can deploy into your Sentinel workspace while the fix is in progress.

Talk to a Microsoft security engineer

We work inside your Microsoft environment, with your team, and show you where to focus first.