Security checks / Check reference / Service principals

Sp Risk State At Risk

High Severity Microsoft 365 security check in the Service principals domain.

Service principal risk state is "at risk", active investigation recommended Active risk state means this service principal needs investigation Until cleared, its API activity should be treated as potentially attacker-controlled Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

High SeverityService principalsSCuBA MS.AAD.5.1v1

Check summary

Severity
High
Domain
Service principals
Rank in domain
4
Frameworks
6

What this check verifies

Service principal risk state is "at risk", active investigation recommended

Why it matters

Active risk state means this service principal needs investigation Until cleared, its API activity should be treated as potentially attacker-controlled

How to fix it

Rotate credentials and investigate; treat as compromised until confirmed safe

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.

Compliance framework mappings

Findings from this check serve as evidence for:

Related Entra ID guides

This is an Entra ID and identity check. See the broader guidance and the exact checks Siemserva runs in this area:

Common questions

What does the Sp Risk State At Risk check verify?

Service principal risk state is "at risk", active investigation recommended It is a High Severity check in the Service principals domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a Sp Risk State At Risk finding?

Rotate credentials and investigate; treat as compromised until confirmed safe 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 SCuBA, MCSB, NIST, SOC2, CIS, HIPAA, including SCuBA policy MS.AAD.5.1v1, MS.AAD.5.2v1, MS.AAD.5.3v1, and MCSB control LT-3. 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.

Reference: the compliance and audit guide, and the full checks catalog.
Data notice: check definitions describe what Siemserva verifies and are provided as is, for informational purposes only, without warranty of any kind. Framework mappings are informational and do not constitute compliance advice; confirm requirements with your assessor. All use of this data is subject to the Senserva EULA.