Account/Authentication - Azure Active Directory - Ensure that LinkedIn Contact Synchronization is Disabled

By Ashwin Venugopal -

 





Summary

Integration with LinkedIn should be disabled in order to prevent phishing scams. 

Reason

Office 365 have always been a prime target for phishing scams that are a subset of social engineering strategy that imitate a trusted source and concoct a seemingly logical scenario for handing over sensitive information. Social networking sites have made social engineering attacks easier to conduct.

LinkedIn integration is enabled by default in Office 365 and may lead to a risky scenario where an external party could accidentally disclose sensitive information.

What If?

Users will not be able to sync contacts or use LinkedIn integration.

How to?

To disable LinkedIn account data sharing, perform the following steps via the Azure AD admin center:
  1. Navigate to https://admin.microsoft.com and login as a Global Admin.
  2. Expand Admin centers then choose Azure Active Directory.
  3. After the Azure AD admin center is opened select Users followed by User Settings then User settings.
  4. Under LinkedIn account connections click No.
  5. Now, you can click Save at the top of the page.

Monitor:

To verify that LinkedIn contacts synchronization is disabled, perform the following steps via the Azure AD admin center:
  1. Navigate to https://admin.microsoft.com and login as a Global Admin.
  2. Expand Admin centers then choose Azure Active Directory.
  3. After the Azure AD admin center is opened select Users followed by User Settings then User settings.
  4. Under LinkedIn account connections make sure that No is highlighted.


































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