Security checks / Check reference / App registrations

App Certificate Too Long Lived

Medium Severity Microsoft 365 security check in the App registrations domain.

Application certificate has a lifetime exceeding the maximum allowed by security policy Long-lived certificates remain valid if the private key is compromised. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.

Medium SeverityApp registrationsSCuBA MS.AAD.5.1v1

Check summary

Severity
Medium
Domain
App registrations
Rank in domain
3
Frameworks
6

What this check verifies

Application certificate has a lifetime exceeding the maximum allowed by security policy

Why it matters

Long-lived certificates remain valid if the private key is compromised. Shorter lifetimes force regular rotation and reduce the window of abuse

How to fix it

Reissue certificate with shorter lifetime per policy; automate rotation

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 App Certificate Too Long Lived check verify?

Application certificate has a lifetime exceeding the maximum allowed by security policy It is a Medium Severity check in the App registrations domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.

How do I fix a App Certificate Too Long Lived finding?

Reissue certificate with shorter lifetime per policy; automate rotation 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.

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.