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

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more