Security checks / Check reference / Service principals

Sp Secret Too Long Lived

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

Service principal secret lifetime exceeds the maximum allowed by security policy Long-lived service principal secrets increase exposure time if leaked Shorter lifetimes limit damage from credential theft in pipelines and logs Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Medium SeverityService principalsSCuBA MS.AAD.5.1v1

Check summary

Severity
Medium
Domain
Service principals
Rank in domain
3
Frameworks
6

What this check verifies

Service principal secret lifetime exceeds the maximum allowed by security policy

Why it matters

Long-lived service principal secrets increase exposure time if leaked Shorter lifetimes limit damage from credential theft in pipelines and logs

How to fix it

Reissue secret with shorter lifetime; migrate to managed identity where possible

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:

Common questions

What does the Sp Secret Too Long Lived check verify?

Service principal secret lifetime exceeds the maximum allowed by security policy It is a Medium 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 Too Long Lived finding?

Reissue secret with shorter lifetime; migrate to managed identity where possible 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.

Sponsored by Senserva

Siemserva by Senserva runs this check, Sp Secret Too Long Lived for example, 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
  • Optional AI Enhanced Reporting: plain-language summaries and recommended next steps written into your reports
  • Multi-tenant and MSP practices, with bulk tenant audits and client-ready reporting
Compliance Status Report
Sp Secret Too Long Lived across 2 tenants, ranked by Severity
23
FAILING
87
PASSING
41
OTHER FINDINGS
CHECKSEVERITYSTATUSFINDINGS
Sp Secret Too Long LivedMediumFAILING23
MFA for all usersCritical-11
Legacy authentication blockedHigh-6
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
See this check's evidence trail, click to play

How findings become audit evidence, in two minutes. Watch page · All videos.

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.