Create a Post
Showing results for 
Search instead for 
Did you mean: 

Identity Collector Scale

I've read in various Identity collector documents that the following is true:

  • Identity Collector can process up to 1900 AD events per second. (sk108235)
  • Identity Collector is based on security events which are logged on the Domain Controller servers (events 4624, 4768, 4769 and 4770). (sk86441)

Based on that,

1. Is 1900 AD events per second the maximum number of eps for all event IDs?  Or only 1900 eps for event IDs of type 4624, 4768, 4769 and 4770 (aka other event IDs are filtered out and don't apply to the 1900 eps limit)?

2. If we were concerned that we may be close to the 1900 eps limit, can we spin up multiple IDC servers and split the domain controllers across them?  For example, IDC server A handles only DC1 and DC2, while IDC server B handles only DC3 and DC4?  Then for redundancy, you'd want to have a total of 4 (2 that handle DC1 and DC2, and 2 that handle DC3 and DC4).  Would this make sense?  Or would this cause other issues not anticipated?

What designs have you seen for customers with very large AD deployments?

Thanks for your thoughts!

0 Kudos
1 Reply

You should be able to spin up multiple Identity Collectors and assign them to different security gateways.

The security gateways would then share this data with other gateways. 

0 Kudos


Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events