Application Permissions - Ensure User Consent to Apps Accessing Company Data on their Behalf is not Allowed

By Ashwin Venugopal -

 










Summary

Users can generally consent to the applications accessing an organization's data, by default, although only for some permissions. For example, by default a user can consent to allow an app to access their own mailbox or the Teams conversations for a team the user owns, but cannot consent to allow an app unattended access to read and write to all SharePoint sites in your organization.

Users should not grant consent to apps accessing company data on their behalf.

Reason

Attackers often use custom applications to trick users into granting them access to company data.

When users are allowed to consent by themselves, they become capable of acquiring useful applications that integrate with Microsoft 365, Azure and other services, it can also represent a risk if it is not used and monitored carefully.

Future user consent operations must be disabled to help reduce the threat-surface and mitigate risks. However, even if the user consent is disabled, previous consent grants will still be honored while all the future consent operations must be performed by an administrator. 

What If?

Even if the user consent is disabled, previous consent grants will still be honored while all the future consent operations must be performed by an administrator. Tenant-wide admin consent can be requested through an integrated administrator consent request workflow or through organizational support processes.

How to?

To prohibit user consent to apps accessing company data on their behalf, use the Microsoft 365 Admin Center:
  1. Select Admin centers and Azure Active Directory.
  2. Select Enterprise Applications from the Azure navigation pane.
  3. Under Security, pick consent and permissions.
  4. Now, under User consent for applications select Do not allow user consent.
  5. Click the Save button at the top of the window.

To prohibit user consent to apps accessing company data on their behalf, use the Microsoft Online PowerShell module:

  1. Connect to Microsoft Online service using Connect-MSOLService.
  2. Run the following command:

Set-MSOLCompanySettings -UsersPermissionToUserConsentToAppEnabled $False

Monitor:

To verify that user consent to apps accessing company data on their behalf is not allowed, use the Microsoft 365 Admin Center:
  1. Select Admin centers and Azure Active Directory.
  2. Select Enterprise Applications from the Azure navigation pane.
  3. Under Security, pick consent and permissions.
  4. Now, verify User consent for applications is set to Do not allow user consent.

To verify that user consent to apps accessing company data on their behalf is not allowed, use the Microsoft Online PowerShell module:

  1. Connect to Microsoft Online service using Connect-MSOLService.
  2. Run the following command:

Get-MSOLCompanyInformation | Select-Object
UsersPermissionToUserConsentToAppEnabled

      3. Verify the value for UsersPermissionToUserConsentToAppEnabled is set to False.

























































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more