the artemis-test file is a Little bit Special, because it is an test file.
How your TIE Module is configured? Observation Mode or Enforcement mode.
Try the following.
- Set TIEM to enforcement mode.
- Change the Enterprise Reputation for Artemis Test File to "known malicious".
Afterwards the file should be blocked.
Can you also take a look which Reputation Level under TIE Reoutations is set for the file??
Note, if there is any info about this file like "known trusted" and ATD detects malware, the file is not blocked. This makes sense, because you have no guarantee that the ATD detection is not a false/positives. At the Moment we are also testing what changes the reputation score of a file in TIE.
You might take a look at the PDF. The TIE Module collects Meta Data (TIE Content in Repository) and uses the TIE Rules from ePO. All this information is collected in TIE. TIE also uses some internal "Rules" to generate the final Reputation Score. Also ATD sends information which can change the Reputation Score.....
As you can see, the whole solution is much more "dynamic" than signature based technology. Let´s see which information will be available in the future. I hope McAfee (Intel Security) will give us some more detail.
I have seen the tie reputation in epo that you refer to. There is one rule said that 31. Identify file atd report as susspicious to be most likely malicious. Do you know what does suspicious refer to [might be malicious most likely maliciouse or known malicious ]