Security checks / Check reference / App registrations
App Application Registration Has A Client Secret
Medium Severity Microsoft 365 security check in the App registrations domain.
Application registration has client secret (password) credentials configured. Secrets are less secure than certificates and should be monitored Client secrets are easier to steal than certificates (they appear in logs, config files, and code repos) A leaked secret gives full app-only access until rotated Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
Application registration has client secret (password) credentials configured. Secrets are less secure than certificates and should be monitored
Why it matters
Client secrets are easier to steal than certificates (they appear in logs, config files, and code repos) A leaked secret gives full app-only access until rotated
How to fix it
Migrate to certificate authentication; move remaining secrets to a vault with aggressive rotation; audit app permissions and remove unused scopes
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:
References
Related App registrations checks
Common questions
What does the App Application Registration Has A Client Secret check verify?
Application registration has client secret (password) credentials configured. Secrets are less secure than certificates and should be monitored 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 Application Registration Has A Client Secret finding?
Migrate to certificate authentication; move remaining secrets to a vault with aggressive rotation; audit app permissions and remove unused scopes 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.