we have find one vulnerability mismatch on the Vulnerability scan result. After we open case from support, they told us said McAfee fixed that mismatch. question is how can we prove McAfee already fix those and what mobule Mcafee to fix it?
I'd implement the registry fix that adds a column to the CSV report that shows what the output the FASL script recieved from the system. That way you can see why MVM failed a specific check. I'd compare that to the value your expecting and, if you find a match, then you know that the false positive still exists.
I found an old post in the forums that tells you how to implement FASL output in the CSV file:
[HKEY_LOCAL_MACHINE\SOFTWARE\Foundstone\ReportServer] (for 32-bit host) or
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Foundstone\ReportServer] (for 64-bit host)