What is wrong with the Microsoft Safety Scanner status information and logging?

  • Thread starter Thread starter The Victim
  • Start date Start date
T

The Victim

EXAMPLE #1

MSS reported it found 19-infected files during the scan. When the scan was complete, it said no infections were found.

Here's the log:

-----------------------------------------------------------

Microsoft Safety Scanner v1.333, (build 1.333.203.0)
Started On Thu Mar 11 23:15:09 2021
Engine: 1.1.17900.7
Signatures: 1.333.203.0
MpGear: 1.1.16330.1
Run Mode: Interactive Graphical Mode
Results Summary:
----------------
No infection found.
Successfully Submitted MAPS Report
Successfully Submitted Heartbeat Report
Microsoft Safety Scanner Finished On Fri Mar 12 10:33:14 2021

Return code: 0 (0x0)

-----------------------------------------------------------

Where are the 19-infections it found when scanning and what did it do with them?


EXAMPLE #2

MSS reported it found 3-infected files during the scan. When the scan was complete it only reported 2-infections. One was removed and the other needed a restart to complete removal. Here's the log:

-----------------------------------------------------------

Microsoft Safety Scanner v1.333, (build 1.333.203.0)

Started On Fri Mar 12 00:16:11 2021

Engine: 1.1.17900.7
Signatures: 1.333.203.0
MpGear: 1.1.16330.1
Run Mode: Interactive Graphical Mode
Results Summary:

----------------
No infection found.
Successfully Submitted Heartbeat Report
Microsoft Safety Scanner Finished On Fri Mar 12 00:18:56 2021
Return code: 0 (0x0)
-----------------------------------------------------------

Not only did it not report infections in the log after reporting them in the scan results, but it also says the scan took 2-seconds when it took over 10-hours.

At this point, I have zero trust in the Microsoft Safety Scanner. There is no such thing as security without accountability, which, in this case, would mean having an accurate and complete log file.


Does anyone know why MSS is misreporting infections and not logging them when found? Maybe there is another log hidden somewhere?


Continue reading...
 
Back
Top