Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Default Consent Policy
Governance, Ownership & Risk

Default Consent Policy

← Back to Glossary
By NHI Mgmt Group Updated November 16, 2026 Domain: Governance, Ownership & Risk

Default Consent Policy is the baseline rule set that decides when an identity provider allows an application to request user consent for access to data or scopes. It governs consent prompts, admin approval, and whether users can grant access to protected resources, reducing uncontrolled app authorisation.

Default consent policy is the control layer that decides whether an application may ask for consent at all, and under what conditions users can approve access to data or scopes. It sits between the identity platform and the app registration experience, so the policy can reduce uncontrolled grants without blocking legitimate delegated access.

In practice, this policy is about setting the baseline for consent rather than reviewing each app manually. A stricter baseline can require admin approval for sensitive permissions, limit user consent to low-risk requests, or disable user consent entirely. A looser baseline improves self-service onboarding, but it also expands the number of apps that can obtain access without a central review step.

Why It Matters for Application Access

The policy matters because consent is often the moment when an application turns a sign-in into durable access. Once a user or administrator approves the request, the app may receive permissions that let it read mail, files, profile data, or directory information, depending on the scopes involved. That makes the policy a boundary control for delegated access, not just a user-interface setting.

Entra ID applications and consent are a useful reference point for understanding how app consent, admin consent workflow, and consent phishing fit together. When organisations do not define a clear baseline, users may approve requests they do not understand, and app developers may assume access will be granted by default.

For privacy-sensitive environments, the policy also shapes how consent aligns with lawful processing and data minimisation. That is especially important when applications request broad access to identity data or special category data, because the consent boundary becomes part of the organisation’s data protection posture, not only its IAM posture.

Common Failure Modes and Abuse Paths

Weak default consent settings can create a path for illicit consent grants, consent phishing, and overbroad delegated access. Attackers and malicious apps do not need to steal a password if they can persuade a user to approve a dangerous permission request that looks routine or legitimate.

CoPhish OAuth phishing via Copilot Studio shows how consent prompts can be abused as an entry point for token theft when the approval experience is not tightly controlled. The underlying problem is not only social engineering, but also policy design: if the platform allows users to grant access too freely, the consent workflow itself becomes part of the attack surface.

Long-lived app grants can also persist after the original business need has passed. That creates a hidden accumulation of access, where old permissions remain active even though the application is no longer reviewed, owned, or justified. The risk is especially acute where consent is tied to broad scopes, tenant-wide permissions, or multiple third-party integrations.

Governance and Control Boundaries

Default consent policy is a governance control because it defines who may authorise apps, what kinds of permissions are allowed, and when an exception must be escalated. It should be treated as part of the organisation’s broader application approval model, alongside publisher verification, admin review, and app inventory.

How to restrict user consent to apps in Entra ID is especially relevant where the policy needs to be translated into enforceable configuration, revocation practice, and review workflow. A policy that is not reflected in the platform settings is only documentation, not control.

EU General Data Protection Regulation (GDPR) is relevant where consent settings affect the collection and sharing of personal data, because policy choices can influence minimisation, purpose limitation, and security of processing. In that context, the consent baseline should be viewed as part of access governance and privacy governance together.

Risk and Threat Considerations

Default consent policy can become a direct security weakness when it allows users to authorise powerful apps without sufficient review. The main risks are consent phishing, excessive delegated permissions, and persistent app access that survives beyond the original business justification.

Failure mechanism: An attacker or malicious publisher steers a user into approving an OAuth request that appears routine, then uses the resulting grant or token access to reach data or act on the user’s behalf.

Impact: Uncontrolled consent can expose mail, files, directory objects, or other protected resources, and can also create a durable foothold that is harder to detect than password-based compromise.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 sets the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5AC-2 — Account ManagementDefault consent policy governs who can obtain app access and approve permissions.
IA-5 — Authenticator ManagementConsent grants can enable token-based access that depends on credential and secret lifecycle control.
AC-6 — Least PrivilegeConsent policy should constrain requested scopes to the minimum access needed.
Recommendation — Limit consent-based access paths through approved account and app lifecycle governance. Rotate and revoke credentials, tokens, and grants when consented access is no longer justified. Restrict delegated permissions to the minimum scopes needed for the approved use case.
ISO/IEC 27001:2022A.5.15 — Access controlConsent policy is an access governance rule deciding who may grant application access.
A.5.16 — Identity managementConsent decisions depend on governed identities, app owners, and approvers.
Recommendation — Define and enforce consent approval rules within the organisation's access control policy. Maintain clear ownership and approval authority for applications that request consent.

Practitioner Guidance

Governance implication: Set the default consent baseline to match the organisation’s tolerance for self-service app access, then enforce it consistently in the identity platform and app review process. If users are allowed to consent at all, keep that scope narrow and make sensitive permissions require administrative approval.

What to watch for: Review patterns of newly granted enterprise applications, high-risk permission scopes, and apps that accumulate access without an active business owner. A good default consent policy should reduce surprise grants, not just document a rule that no one operationalises.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org