Check for identity, network, data risks

Along with identity-based access control, network-based access control is a top priority for protecting assets.

Monitor identity-related risk events using adaptive machine learning algorithms, heuristics quickly before the attacker can gain deeper access into the system. Also, monitor all communications between segments to detect potential security threats flowing over the wire.

This article describes some considerations that can help monitor the workload for those risks.

Key points

  • View identity related risks in Azure Active Directory (Azure AD) reporting and Azure AD Identity Protection.
  • Obfuscate personal information in application logs.
  • Enable logs (including raw traffic) from your network devices.
  • Set alerts and gain access to real-time performance information at the packet level.

Review identity risks

Most security incidents take place after an attacker initially gains access using a stolen identity.

Suppose an attacker gains access using a stolen identity. Even though the identity has low privileges, the attacker can use it to traverse laterally and gain access to more privileged identities. This way the attacker can control access to the target data or systems.

Does the organization actively monitor identity-related risk events related to potentially compromised identities?


Monitor identity-related risk events on potentially compromised identities and remediate those risks. Review the reported risk events in these ways:

Azure AD uses adaptive machine learning algorithms, heuristics, and known compromised credentials (username/password pairs) to detect suspicious actions that are related to your user accounts. These username/password pairs come from monitoring public and dark web and by working with security researchers, law enforcement, security teams at Microsoft, and others.

Remediate risks by manually addressing each reported account or by setting up a user risk policy to require a password change for high risk events.

Mask personal information

Is personal information detected and removed/obfuscated automatically?


Be cautious when logging sensitive application information. Don't store personal information such as contact information, payment information, and so on, in any application logs. Apply protective measures, such as obfuscation. Machine learning tools can help with this measure. For more information, see PII Detection cognitive skill.

Enable network visibility

One way to enable network visibility is by integrating network logs and analyzing the data to identify anomalies. Based on those insights, you can choose to set alerts or block traffic crossing segmentation boundaries.

How do you monitor and diagnose conditions of the network?


Enable logs (including raw traffic) from your network devices.

Integrate network logs into a security information and event management (SIEM) service, such as Azure Sentinel. Other popular choices include Splunk, QRadar, or ArcSight ESM.

Use machine learning analytics platforms that support ingestion of large amounts of information and can analyze large datasets quickly. Also, these solutions can be tuned to significantly reduce the false positive alerts.

Here are some ways to integrate network logs:

Proactive monitoring

How do you gain access to real-time performance information at the packet level?


Take advantage of packet capture to set alerts and gain access to real-time performance information at the packet level.

Packet capture tracks traffic in and out of virtual machines. It gives you the capability to run proactive captures based on defined network anomalies including information about network intrusions.

For an example, see Scenario: Get alerts when VM is sending you more TCP segments than usual.

Next steps