Skip to content
StrikeOps

Stale Privileged Applications With Long-Lived Secrets

MediumTypical severity Cloud and Microsoft 365CWE-262ATT&CK T1078.004

01Description

App registrations with privileged permissions had client secrets with very long or effectively unlimited lifetimes, and several showed no recent sign-in activity. Secrets were not rotated and the applications had no documented owner.

02Impact

A client secret is a password for an application, and it is not protected by MFA or Conditional Access for users. A secret copied into a script, configuration file or old repository remains valid for years, and an attacker who finds it can authenticate as the application and use all of its permissions. Unused privileged applications are easy to overlook in incident response.

03Severity

Typically

Medium

Typically Medium. Medium by default. High where the application holds privileged Graph permissions or Azure roles, the secret has been shared or stored in code, or the application is unused but still enabled.

04How to verify

  1. 1In the Entra admin center, open Identity > Applications > App registrations and review Certificates & secrets for each application, noting expiry dates.
  2. 2List credentials with Microsoft Graph PowerShell, for example Get-MgApplication -All -Property DisplayName,AppId,PasswordCredentials,KeyCredentials, and flag secrets with distant end dates.
  3. 3Check service principal sign-in activity in the sign-in logs, and the permissions and Azure role assignments held by each application.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Disable or delete applications with no recent activity or current owner, after confirming with the business.
  2. 2Replace client secrets with certificates or, for workloads running in Azure, managed identities or workload identity federation.
  3. 3Where secrets remain, set short lifetimes and rotate them before expiry, storing them in a secrets manager such as Azure Key Vault.
  4. 4Use app management policies to restrict secret lifetimes across the tenant (custom policies require Microsoft Entra Workload ID licensing).
  5. 5Assign owners and review application credentials on a set schedule.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo