Large Single-Site Deployment
Table of Contents
4.2 (EoS)
Expand all | Collapse all
-
- Set Up the Endpoint Infrastructure
- Activate Traps Licenses
-
- Endpoint Infrastructure Installation Considerations
- TLS/SSL Encryption for Traps Components
- Configure the MS-SQL Server Database
- Install the Endpoint Security Manager Server Software
- Install the Endpoint Security Manager Console Software
- Manage Proxy Communication with the Endpoint Security Manager
- Load Balance Traffic to ESM Servers
-
- Malware Protection Policy Best Practices
- Malware Protection Flow
- Manage Trusted Signers
-
- Remove an Endpoint from the Health Page
- Install an End-of-Life Traps Agent Version
-
-
- Traps Troubleshooting Resources
- Traps and Endpoint Security Manager Processes
- ESM Tech Support File
-
- Access Cytool
- View the Status of the Agent Using Cytool
- View Processes Currently Protected by Traps Using Cytool
- Manage Logging of Traps Components Using Cytool
- Restore a Quarantined File Using Cytool
- View Statistics for a Protected Process Using Cytool
- View Details About the Traps Local Analysis Module Using Cy...
- View Hash Details About a File Using Cytool
Large Single-Site Deployment
This single-site deployment scenario supports up to 150,000 Traps
agents and consists of the following components:
- One dedicated database server
- One ESM Console in the same location as the database for managing the security policy and Traps agents
- One ESM Server for every 30,000 Traps agents (for a maximum of 150,000 agents).
- One forensic folder for each ESM Server that is accessible by all endpoints for storing real-time forensic details about security events
- (Recommended) WildFire integration
- (Optional) Load balancer for distributing traffic across ESM Servers
- (Optional) External logging platform such as an SIEM or syslog
In this example, up to 150,000 Traps agents can connect to the
Endpoint Security Manager. To support this scenario, the endpoints
connect to five ESM Servers through an optional load balancer. Each
ESM Server connects to a central database that is managed by a dedicated
ESM Console.