symantec endpoint protection management 12.1 to 14

19 Ways to Bypass Software Restrictions and Spawn a Shell.

Top 16 Active Directory Vulnerabilities.

Top 10 Vulnerabilities: Internal Infrastructure Pentest.

Install Nessus and Plugins Offline (with pictures).

Detailed Overview of Nessus Professional.

CMS Vulnerability Scanners for WordPress, Joomla, Drupal, Moodle, Typo3.

Top 20 Microsoft Azure Vulnerabilities and Misconfigurations.

Please let me know if you have any ideas how to achieve this goal. Ideally we would like to be able to throttle the amount of traffic used per client for SEP updates. We'd like to implement some change at the OS or application level to throttle the traffic without needing some heavyweight QoS deployment at 100s of offices. However, that won't guarantee any bandwidth for management traffic. So far, to mitigate flooding the entire network, we have throttled the SEPM traffic externally (at VM and switching level), which works to prevent congestion at the head-end network.

We need some way of reducing the amount of bandwidth used by the SEPM to update clients natively, so that there is headroom on its network connection for management traffic (remote in, check the SEP console, etc). We found that the SEPM will practically accept 1000s of client check-in requests, and will send all clients updates at the maximum data rate possible. It needs to send a 'full' definition update to every client, some hundreds of Mbyte in size.

What our sysadmins have reported is that the SEP software does not have any native way to throttle its use of network bandwidth. We do have many remote clients designated as Group Update Providers (GUPs) where possible. My organization has a large deployment of Symantec Endpoint Protection (SEP) (~20k clients) with a single SEPM instance running in an ESX VM.

Symantec endpoint protection management 12.1 to 14