Application Permissions - Ensure Users Installing Word, Excel, and PowerPoint Add-ins is Not Allowed

By Ashwin Venugopal -

 







Summary

Users can install add-ins in their Microsoft Word, Excel, and PowerPoint applications by default, which allows data access within the application.

Users should not be permitted to install add-ins in Word, Excel, or PowerPoint.

Reason

Generally, attackers use vulnerable and custom-built add-ins to access data in user applications. 

Although permitting users to install add-ins by themselves helps them in acquiring useful add-ins (that can integrate with Microsoft applications) easily, it can also pose risk if not used and monitored carefully.

Future user's ability to install add-ins in Microsoft Word, Excel, or PowerPoint should be disabled as it helps in reducing the threat surface and mitigate risks.

What If?

This change can impact both end users and administrators. End users will not be able to install add-ins that they may want to install.

How to?

To prohibit users from installing Word, Excel, and PowerPoint add-ins, use the Microsoft 365 Admin Center:
  1. Select Settings from the navigation pane.
  2. Select Org Settings from the navigation pane.
  3. Under Services select User owned apps and services.
  4. Now, de-select Let users access the Office Store and Let users start trials on behalf  of your organization.
  5. Click Save.

Monitor:

To verify that users installing Word, Excel, and PowerPoint add-ins are not allowed, use the Microsoft 365 Admin Center:
  1. Select Settings from the navigation pane.
  2. Select Org Settings from the navigation pane.
  3. Under Services select User owned apps and services.
  4. Verify Let users access the Office Store and Let users start trials on behalf  of your organization are Not Checked.






































































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

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can...
Read more