Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi Everyone,
Recently we were made aware of a TETRA AV definition update which caused the Windows AMP for
Endpoints service to crash.
Note: Customers who do NOT have TETRA enabled are not affected by this issue.
While we have already remov...
Wednesday January 17, 2018
This document outlines compatibility details and product update information of AMP for Endpoints regarding the Microsoft Security Updates and Knowledge Base articles (KB4072699, KB4056892) released on January 3, 2018 to a...
Hi Everyone,In version 5.0 we made changes to the way files and paths are stored. Our existing articles will be updated soon and we apologize for the delay. The files and paths are now stored in an referential structure in the historyex.db file. Atta...
Hello Everyone,
This script was designed to make up for the changes made to the history.db file after v5.0 was released. The goal is to help you identify what A4E is scanning in order to determine the best exclusions for your environment.
The attache...
This indicates that the quarantine action did not take place. The primary cause for this event is when the FireAMP connector is configured in Audit Mode. FireAMP is detecting a malicious file, but is not permitted to quarantine it per the policy sett...
It is important to consider that the amount of traffic you can inspect with the SFR module will be inherently limited by how much traffic the ASA itself can pass. There are standalone (bare metal) appliances that can inspect substantially more traffi...
The exclusion looks like a valid wildcard. Be sure that your endpoint policy has actually updated and has the exclusion you have added to your list (you can check this under the settings in the UI).
If you have any detection events you will want to ...
