Controls / MCSB / IR-1

MCSB IR-1: Incident Response

12 Senserva Microsoft 365 security checks provide evidence for Microsoft Cloud Security Benchmark control IR-1 (Incident Response). Each is checked against your tenant, ranked by Severity, with validated remediation.

12 checksIncident ResponseTop Severity: Critical

What MCSB IR-1 covers

The Microsoft Cloud Security Benchmark is Microsoft's own security baseline for Azure and Microsoft 365, organized into control domains. IR-1 sits in the Incident Response domain. Senserva evidences it with the 12 checks below, so you can see, per tenant, whether the control is actually met rather than assumed.

Ask your own AI about this control

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

The 12 checks that evidence MCSB IR-1

Click any row for why it matters and how to fix it, with a link to the full check page.

Senserva checkSeverityWhat it verifies
Risk Detection Anomalous TokenCriticalAnomalous token usage detected Token properties or usage patterns do not match expected behavior.
Risk Detection Leaked CredentialsCriticalLeaked credentials detected. Credentials for this user were found exposed publicly
Risk Detection Malicious IP AddressCriticalSign-in from a known malicious IP address.
Risk Detection OfflineCriticalRisk detection was discovered offline (retroactively). The compromise predates the detection
Risk Detection State Confirmed CompromisedCriticalRisk detection is confirmed compromised. Immediate action required
Risk Detection Token Issuer AnomalyCriticalToken issuer anomaly detected The token was issued by an unexpected or suspicious authority.
Risk Detection Anonymized IP AddressHighSign-in from an anonymized IP address (VPN, Tor, or proxy)
Risk Detection StaleHighUnresolved risk detection has exceeded the configured stale threshold
Risk Detection State At RiskHighRisk detection is in AtRisk state and has not been remediated
Risk Detection State DismissedHighRisk detection was dismissed without documented remediation
Risk Detection Suspicious IP AddressHighSign-in from a suspicious IP address flagged by threat intelligence
Ir Update Incident Response Plan And ProcessMediumUpdate and maintain the incident response plan and process

Also evidences

The same checks provide evidence for these frameworks, so one fix counts across your obligations:

Every MCSB control and the checks that evidence it: the control reference. The full benchmark crosswalk: MCSB for Microsoft 365.

Sponsored by Senserva

Siemserva by Senserva runs the checks that evidence MCSB IR-1 (Incident Response) across your own tenant: which tenants pass, which fail, ranked by Severity with the evidence attached.

  • 650+ Microsoft 365, Intune, Defender, and Entra ID checks in one scan
  • Findings mapped to SCuBA, CIS, NIST, HIPAA, SOC 2, and MCSB for audit-ready evidence
  • Senserva Trustworthy AI driven configuration remediation: validated, approve-before-apply fixes
  • Multi-tenant and MSP practices, with bulk tenant audits and client-ready reporting
Siemserva by Senserva
Compliance Status Report
MCSB IR-1 (Incident Response) across 2 tenants, ranked by Severity
23
FAILING
87
PASSING
41
OTHER FINDINGS
Estimated report, sample data for illustration
Get Going with Senserva Senserva compliance Built for IT admins, security teams, and auditors, with audit-ready evidence. Senserva is a Microsoft Intelligent Security Association member.
Microsoft 365 compliance and audit evidence
How a control becomes audit evidence, click to play

From finding to audit evidence, in two minutes. Watch page · All videos.

Reference: the compliance frameworks crosswalk, the check reference, and the audit guide.
Data notice: control mappings describe which Siemserva checks provide evidence for a control and are informational only, without warranty. They do not constitute compliance advice or certification; confirm requirements with your assessor. All use is subject to the Senserva EULA.