10-22-2018 02:41 PM - edited 02-20-2020 09:06 PM
Is there a way to either whitelist or create an exclusion in Cisco AMP so that anything coming from that IP address or server is ignored by the Cisco AMP agent? We have a KACE appliance that downloads Windows updates to the clients and I would like to make an exception so that anything coming from our KACE appliance is accepted by Cisco AMP. We find that Cisco AMP takes a significant percentage of the client-side CPU when KACE agent is downloading Windows updates.
Solved! Go to Solution.
10-24-2018 12:56 PM
There is no way to tell AMP to ignore everything by specifying an IP address or domain. The IP Whitelist feature (under Outbreak Control in the AMP console) is just for overriding a block based on the Cisco intelligence feed.
Based on your description, what you need here is a way to reduce or eliminate the performance impact when the KACE agent on an endpoint performs updates, correct?
If so, the generally recommended way to do that is with an exclusion (found under Management in the console) instead of a whitelist. That's what the original link talked about, and you can set an exclusion based either on a location in the file system, or the process that is performing the operations.
If you need assistance with the exclusion process, or with other performance issues, my advice is to open a support case, and be sure that it gets routed to the AMP TAC specialists.
10-22-2018 10:46 PM
10-23-2018 06:39 AM
I don't see anything in that article that talks about excluding IP addresses. Can you point me in the right direction?
10-24-2018 12:56 PM
There is no way to tell AMP to ignore everything by specifying an IP address or domain. The IP Whitelist feature (under Outbreak Control in the AMP console) is just for overriding a block based on the Cisco intelligence feed.
Based on your description, what you need here is a way to reduce or eliminate the performance impact when the KACE agent on an endpoint performs updates, correct?
If so, the generally recommended way to do that is with an exclusion (found under Management in the console) instead of a whitelist. That's what the original link talked about, and you can set an exclusion based either on a location in the file system, or the process that is performing the operations.
If you need assistance with the exclusion process, or with other performance issues, my advice is to open a support case, and be sure that it gets routed to the AMP TAC specialists.
10-24-2018 01:01 PM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide