Account/Authentication - Azure Active Directory - Ensure that Collaboration Invitations are Sent to Allowed Domains Only

By Ashwin Venugopal -

 






Summary

Users should be able to send collaboration invitations to allowed domains only.

Reason

If the allowed domains for collaborations are specified, external companies can be explicitly identified. Additionally, this prevents internal users from inviting unknown external users like personal accounts and give them access to resources. 

What If?

This could make harder collaboration if the setting is not quickly updated when a new domain is identified as "allowed".

How to?

From the Azure portal:
  1. Go to Azure Active Directory.
  2. Go to Users.
  3. Go to User Settings.
  4. Under External users, click on Manage external collaboration settings.
  5. Under Collaboration restrictions, choose allow invitations only to the specified domains (most restrictive), check the Target domains setting, and specify the domains allowed to collaborate.
Default Value: It is Allow invitations to be sent to any domain (most inclusive) and thus no domain is specified.

Monitor:

From the Azure portal:
  1. Go to Azure Active Directory.
  2. Go to Users.
  3. Go to User Settings.
  4. Under External users, click on Manage external collaboration settings.
  5. Under Collaboration restrictions, make sure that Allow invitations only to the specified domains (most restrictive) is selected. After this, ensure that Target domains is checked and that allowed domains are specified.













































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