Yes. Most are digitally signed by known vendors on the TVL.
For example, mbam.sys, mwac.sys,…
A few are not; for example, some Windows OS dlls, etc.
The files are Unrecognized, but I assume since the vendor is on the TVL the files are not treated as Unrecognized (e.g. autosandboxed).
However, there have been a few isolated cases - that seem to be system dependent - where a digitally signed file from a vendor on the TVL - generates Unrecognized alerts (HIPS, autosandbox, firewall).
For example, MRT.exe on my AMD system, and MdCmdRun.exe, System32\dllhost.exe and SysWOW64\dllhost.exe on my Intel system.
I am continually having to submit files to be white-listed, change rating locally, etc - which is no big deal - just trying to understand how CIS is supposed to work versus how it actually works.
When you get these detections again can you double check if the digital signature of the files is on the TVL? The reason for asking is that incidentally vendors may change their signature. When checking look at the name and that the name completely matches.
It can be set as a shell extension. Download this zip archive and unpack it to C:\Program Files\SysinternalsSuite\ . When done run sigcheck.reg to add it to the registry.
When this is done navigate to the system32 folder, look up and select the file you want to check, click right and choose Signature from the context menu. A black command box will pop up. See if it is signed or not.
Coincidentally it just happened with lpremove.exe - which evidently is a digitally unsigned Microsoft system application.
lpremove.exe was added to the File List and rated as Trusted on 04/20.
A few moments ago - on 05/04 - Defense+ generated a HIPS alert for lpremove.exe when it attempted to execute conhost.exe.
Images attached.
This type of behavior is occurring randomly and vast majority are either is System32 or SysWOW64 directories… on both AMD and Intel systems.
So it appears the problem is that there are a bunch of System32 and SysWOW64 files that are digitally unsigned… and while CIS recognizes the vendor as Microsoft and the file is rated as Trusted in the File List, CIS will treat those files as Unrecognized ???
What do you think?
In the case of MBAM.sys the file is digitally signed by a TVL vendor, but a Rating Scan indicated the file was Unrecognized; it was not blocked but I had to transfer it to the Trusted file list.
Best Regards,
HJLBX
PS - Thanks a million EricJH for pointing out SI SigCheck… I did not think to use it. I will continue to monitor the situation.
When submitting a bug report you will be asked to clean install CIS following ]Chiron’s guide. An important step is to remove possible traces of previously installed security programs.
Are there other security programs running in the background that could interfere? What security programs do you have installed?
Edit. I noticed you had a bug report about the same problem in which you are working with settings that differ from the default settings. I responded there: