Threat protection product names from Microsoft are changing. Read more about this and other updates here. We'll be updating names in products and in the docs in the near future.
Azure Advanced Threat Protection (ATP) can collect accounting information from VPN solutions. When configured, the user's profile page includes information from the VPN connections, such as the IP addresses and locations where connections originated. This complements the investigation process by providing additional information on user activity as well as a new detection for abnormal VPN connections. The call to resolve an external IP address to a location is anonymous. No personal identifier is sent in this call.
Azure ATP integrates with your VPN solution by listening to RADIUS accounting events forwarded to the Azure ATP sensors. This mechanism is based on standard RADIUS Accounting (RFC 2866), and the following VPN vendors are supported:
- Check Point
- Cisco ASA
To enable VPN integration, make sure you set the following parameters:
- Open port UDP 1813 on your Azure ATP sensors and/or Azure ATP standalone sensors.
By enabling Radius Accounting, the Azure ATP sensor will enable a pre-provisioned Windows firewall policy called Azure Advanced Threat Protection Sensor to allow incoming RADIUS Accounting on port UDP 1813.
The example below uses Microsoft Routing and Remote Access Server (RRAS) to describe the VPN configuration process.
If you're using a third-party VPN solution, consult their documentation for instructions on how to enable RADIUS Accounting.
Configure RADIUS Accounting on the VPN system
Perform the following steps on your RRAS server.
Open the Routing and Remote Access console.
Right-click the server name and click Properties.
In the Security tab, under Accounting provider, select RADIUS Accounting and click Configure.
In the Add RADIUS Server window, type the Server name of the closest Azure ATP sensor (which has network connectivity). For high availability you can add additional Azure ATP sensors as RADIUS Servers. Under Port, make sure the default of 1813 is configured. Click Change and type a new shared secret string of alphanumeric characters. Take note of the new shared secret string as you'll need to fill it out later during Azure ATP Configuration. Check the Send RADIUS Account On and Accounting Off messages box and click OK on all open dialog boxes.
Configure VPN in ATP
Azure ATP collects VPN data that helps profile the locations from which computers connect to the network and to be able to detect suspicious VPN connections.
To configure VPN data in ATP:
In the Azure ATP portal, click on the configuration cog and then VPN.
Turn on Radius Accounting, and type the Shared Secret you configured previously on your RRAS VPN Server. Then click Save.
After this is enabled, all Azure ATP sensors listen on port 1813 for RADIUS accounting events, and your VPN setup is complete.
After the Azure ATP sensor receives the VPN events and sends them to the Azure ATP cloud service for processing, the entity profile will indicate distinct accessed VPN locations and activities in the profile will indicate locations.