Last week, Microsoft announced Advanced Threat Analytics 1.6. In fact, I even wrote a blog on how to upgrade to it!
Today, we’ll walk through installing the new Lightweight gateway.
In the past, Microsoft required that you deploy a full ATA Gateway, which requires a dedicated server as well as port-mirroring setup to that Gateway server. Keep in mind that you only need Gateways pulling traffic from Read/Write Domain Controllers.
It is still our recommendation to deploy a traditional Gateway in a traditional datacenter or large branch office scenario. One of the biggest reasons, is that by having port-mirroring, it provides a truly separate attack vector (access to network switches) than the traditional hackers that typically are breaching the weakest thing in your environment…passwords. That being said, Lightweight Gateways do have their place:
- Small/Medium offices with physical infrastructure where the capital cost to deploy ATA would be too high
- Small/Medium offices with a small virtual footprint
- Domain controllers in a Private Cloud/Managed IT environments (ie Rackspace, IBM, etc
- Domain controllers in Public Cloud (Azure, AWS, Google Cloud, etc)
As far as sizing, you should follow the new documentation here.
ATA Lightweight Gateway Sizing
It is recommended that you use an ATA Lightweight Gateway rather than an ATA Gateway whenever possible, as long as your domain controllers comply with the sizing table listed here.
An ATA Lightweight Gateway can support the monitoring of one domain controller based on the amount of network traffic the domain controller generates.
|Packets per second*||CPU (cores**)||Memory (GB)***|
*Total number of packets-per-second on the domain controller being monitored by the specific ATA Lightweight Gateway.
**Total amount of non-hyper threaded cores that this domain controller has installed.
While hyper threading is acceptable for the ATA Lightweight Gateway, when planning for capacity, you should count actual cores and not hyper threaded cores.
***Total amount of memory that this domain controller has installed.
If the domain controller does not have the necessary amount of resources required by the ATA Lightweight Gateway, the domain controller performance will not be effected, but the ATA Lightweight Gateway might not operate as expected.
Let’s first login to the ATA console and grab the latest Gateway installer
Unpack the ZIP and run the installer
You can see the new ATA Lightweight Gateway option
Select your cert (hopefully your CA issued Computer cert) and your domain account
Now the install is complete!
And you can see the Gateway appear (with a nice icon) auto-populated with some of the options for collection.