Security checks / Check reference / Service principals

Sp Secret Non Expiring

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

Service principal secret has no expiration date. Non-expiring secrets remain valid indefinitely if compromised A secret with no EndDateTime never expires, giving attackers unlimited use of a stolen credential. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Critical SeverityService principalsSCuBA MS.AAD.5.1v1

Check summary

Severity

Critical

Domain

Service principals

Rank in domain

Frameworks

What this check verifies

Service principal secret has no expiration date. Non-expiring secrets remain valid indefinitely if compromised

Why it matters

A secret with no EndDateTime never expires, giving attackers unlimited use of a stolen credential. This is the worst-case credential lifecycle for automation accounts

How to fix it

Reissue the secret with a finite lifetime; prefer managed identity for Azure-hosted workloads; enforce app management policy to prevent non-expiring secrets

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 "Sp Secret Non Expiring" (source: https://senserva.com/check/asspsecretnonexpiring.html):
- Verifies: Service principal secret has no expiration date. Non-expiring secrets remain valid indefinitely if compromised
- Severity: Critical; domain: Service principals
- Risk: A secret with no EndDateTime never expires, giving attackers unlimited use of a stolen credential. This is the worst-case credential lifecycle for automation accounts
- Remediation guidance: Reissue the secret with a finite lifetime; prefer managed identity for Azure-hosted workloads; enforce app management policy to prevent non-expiring secrets
- Compliance frameworks: SCuBA, MCSB, NIST, SOC2, CIS, HIPAA; SCuBA MS.AAD.5.1v1, MS.AAD.5.2v1, MS.AAD.5.3v1; MCSB IM-3
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:

SCuBAMCSBNISTSOC2CISHIPAASCuBA MS.AAD.5.1v1 SCuBA MS.AAD.5.2v1 SCuBA MS.AAD.5.3v1MCSB IM-3

References

learn.microsoft.com: /security/benchmark/azure/mcsb-identity-management...www.cisa.gov: /sites/default/files/2023-12/Azure%20Active%20Dire...

Related Service principals checks

Sp Assigned To Disabled User Sp Certificate Expired Sp Certificate Expiring Soon Sp Certificate Non Expiring Sp Certificate Too Long Lived Sp Critical Graph Permission Sp Disabled Sp High Risk Permissions

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:

Entra ID security best practices Azure AD and Entra ID security All Service principals checks

Common questions

What does the Sp Secret Non Expiring check verify?

Service principal secret has no expiration date. Non-expiring secrets remain valid indefinitely if compromised It is a Critical 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 Secret Non Expiring finding?

Reissue the secret with a finite lifetime; prefer managed identity for Azure-hosted workloads; enforce app management policy to prevent non-expiring secrets 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 IM-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.