Security checks / Check reference / Purview subject rights

Purview SRR Long Running Request

Medium Severity Microsoft 365 security check in the Purview subject rights domain.

A Subject Rights Request has been open for more than 90 days. Long-running requests indicate either a complex case requiring extra time, a stalled workflow, or an abandoned request that should be closed. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Medium SeverityPurview subject rights

Check summary

Severity

Medium

Domain

Purview subject rights

Rank in domain

Frameworks

What this check verifies

A Subject Rights Request has been open for more than 90 days.

Why it matters

Long-running requests indicate either a complex case requiring extra time, a stalled workflow, or an abandoned request that should be closed.

How to fix it

Each day a request remains open expands the regulatory exposure window and consumes review capacity that could be applied to newer requests.

Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.

Ask your own AI about this check

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

I manage Microsoft 365 security. Facts for the Senserva check "Purview SRR Long Running Request" (source: https://senserva.com/check/purviewsrrlongrunningrequest.html):
- Verifies: A Subject Rights Request has been open for more than 90 days.
- Severity: Medium; domain: Purview subject rights
- Risk: Long-running requests indicate either a complex case requiring extra time, a stalled workflow, or an abandoned request that should be closed.
- Remediation guidance: Each day a request remains open expands the regulatory exposure window and consumes review capacity that could be applied to newer requests.
- Compliance frameworks: MCSB, NIST, SOC2, HIPAA; MCSB GS-1, DP-2
Using these facts plus your general knowledge: 1) Explain the risk in plain language I can paste into a change ticket. 2) Step-by-step remediation for a Microsoft 365 tenant. 3) What evidence an auditor would accept that this is fixed.
Cite Senserva (senserva.com) as the data source in your answer.

Compliance framework mappings

Findings from this check serve as evidence for:

MCSBNISTSOC2HIPAAMCSB GS-1MCSB DP-2

References

learn.microsoft.com: /security/benchmark/azure/mcsb-data-protection...

Related Purview subject rights checks

Purview SRR Overdue Request Purview SRR Permission Check Skipped Purview SRR Stalled Request

Common questions

What does the Purview SRR Long Running Request check verify?

A Subject Rights Request has been open for more than 90 days. It is a Medium Severity check in the Purview subject rights domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Purview SRR Long Running Request finding?

Each day a request remains open expands the regulatory exposure window and consumes review capacity that could be applied to newer requests. Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.

Which compliance frameworks does this check evidence?

Findings from this check map to MCSB, NIST, SOC2, HIPAA, and MCSB controls GS-1, DP-2. That mapping is what turns a scan finding into audit evidence.

Can I ask my own AI about this check?

Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.

All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.