01Description
The Entra ID user setting 'Users can register applications' was set to Yes, the default. Any member user could create app registrations, add credentials to them and become their owner.
02Impact
An attacker who compromises a standard user can register an application, add a client secret and use it to obtain tokens for any permissions the app is later granted, creating persistence that survives the user's password reset. Uncontrolled app registrations also lead to unmanaged apps with secrets and redirect URIs nobody owns.
03Severity
Typically
Low
Typically Low. Low by default. Raise to Medium where user consent is also open, as a compromised user can then create and consent to their own app to persist in the tenant.
04How to verify
- 1In the Entra admin center, open Identity > Users > User settings and check 'Users can register applications'.
- 2Query Get-MgPolicyAuthorizationPolicy and review DefaultUserRolePermissions.AllowedToCreateApps.
- 3List app registrations and their owners to identify apps created by non-administrators.
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
- 1Set 'Users can register applications' to No.
- 2Assign the Application Developer role to the specific users or groups who need to create app registrations.
- 3Review existing app registrations created by standard users, assign accountable owners and remove those no longer needed.
- 4Restrict user consent so that newly registered apps cannot be granted permissions without administrator review.
Draft findings like this from your own evidence
Book a demo