Applies to: Azure Advanced Threat Protection
Azure ATP capacity planning
This article helps you determine how many Azure ATP sensors and standalone sensors you need.
The sizing tool has two sheets - one for ATA and one for Azure ATP. Make sure you are on the correct sheet.
Using the sizing tool
The recommended and simplest way to determine capacity for your Azure ATP deployment is to use the Azure ATP Sizing Tool. Run the Azure ATP Sizing Tool and from the Excel file results, use the following fields to determine the memory and CPU that used by the sensor:
- Azure ATP sensor: Match the Busy Packets/sec field in the Azure ATP sensor table in the results file to the PACKETS PER SECOND field in the Azure ATP standalone sensor table or the Azure ATP sensor table, depending on the sensor type you choose.
If for some reason you cannot use the Azure ATP Sizing Tool, manually gather the packet/sec counter information from all your Domain Controllers for 24 hours with a low collection interval (approximately 5 seconds). Then, for each Domain Controller, you must calculate the daily average and the busiest period (15 minutes) average. The following sections present the instruction for how to collect the packets/sec counter from one Domain Controller.
In an Azure ATP deployment any combination of the Azure ATP standalone sensor types is supported:
- Only Azure ATP standalone sensors
- Only Azure ATP sensor
- A combination of both
When deciding the sensor deployment type, consider the following benefits:
|sensor type||Benefits||Cost||Deployment topology||Domain controller use|
|Azure ATP standalone sensor||The Out of band deployment makes it harder for attackers to discover Azure ATP is present||Higher||Installed alongside the domain controller (out of band)||Supports up to 100,000 packets per second|
|Azure ATP sensor||Doesn't require a dedicated server and port-mirroring configuration||Lower||Installed on the domain controller||Supports up to 100,000 packets per second|
Consider the following issues when deciding how many Azure ATP standalone sensors to deploy.
Active Directory forests and domains
Azure ATP can monitor traffic from multiple domains within a single Active Directory forest for each workspace you create. To monitor multiple forests, you need to create multiple Workspaces.
Port mirroring considerations might require you to deploy multiple Azure ATP standalone sensors per data center or branch site.
An Azure ATP standalone sensor can support monitoring multiple domain controllers, depending on the amount of network traffic of the domain controllers being monitored.
An Azure ATP sensor can support the monitoring of one domain controller based on the amount of network traffic the domain controller generates. The following table is an estimate, the final amount that the sensor parses is dependent on the amount of traffic and the distribution of traffic.
The following CPU and memory capacity refers to the sensor's own consumption – not the domain controller capacity.
|Packets per second*||CPU (cores)||Memory (GB)|
- Total number of cores that the sensor service will use.
It is recommended that you don't work with hyper-threaded cores.
- Total amount of memory that the sensor service will use.
- If the domain controller does not have the resources required by the Azure ATP sensor, domain controller performance is not affected, but the Azure ATP sensor might not operate as expected.
- When running as a virtual machine dynamic memory or any other memory ballooning feature is not supported.
- For optimal performance, set the Power Option of the Azure ATP sensor to High Performance.
- A minimum of 2 cores and 6 GB of space is required and 10 GB is recommended, including space needed for the Azure ATP binaries and logs.
Domain controller traffic estimation
There are various tools that you can use to discover the average packets per second of your domain controllers. If you do not have any tools that track this counter, you can use Performance Monitor to gather the required information.
To determine packets per second, perform the following steps on each domain controller:
Open Performance Monitor.
Expand Data Collector Sets.
Right click User Defined and select New > Data Collector Set.
Enter a name for the collector set and select Create Manually (Advanced).
Under What type of data do you want to include? select Create data logs, and Performance counter.
Under Which performance counters would you like to log, click Add.
Expand Network Adapter and select Packets/sec and select the proper instance. If you are not sure, you can select <All instances> and click Add and OK.
To perform this operation in a command line, run
ipconfig /allto see the name of the adapter and configuration.
Change the Sample interval to five seconds.
Set the location where you want the data to be saved.
Under Create the data collector set, select Start this data collector set now, and click Finish.
You should now see the data collector set you created with a green triangle indicating that it is working.
After 24 hours, stop the data collector set, by right-clicking the data collector set and selecting Stop.
In File Explorer, browse to the folder where the .blg file was saved and double-click it to open it in Performance Monitor.
Select the Packets/sec counter, and record the average and maximum values.