Whitelisting can be applied to both agents and appliances. Appliance whitelists are implemented via monitoring policies; this whitelisting tells the appliances to ignore (not process) the received traffic. Agent whitelisting is implemented via assignment policies; this whitelisting prevents an agent from sending IP traffic over the network and is useful when trying to reduce the overall traffic load on the network.
Articles in this section
- Can agents white-list traffic?
- Can the Alert Logic agent transport network traffic to the Alert Logic appliance on a customizable port?
- Do whitelisting policies in the Alert Logic console get applied to appliances and agents?
- Does an agent lose cache data if it is restarted?
- Does the Alert Logic agent require a reboot after installation?
- How can I handle large-scale deployment of agents?
- How can I install an Alert Logic agent on a Linux Auto Scaling Instance?
- How can I tell if my agent is directed to an appliance or going straight over Port 443 to Alert Logic?
- How do agents auto-update?
- How do agents cache data?