My Custom Security check will not score correctly against a Binary Data Value registry key. (NETIQKB44388)

fact
NetIQ Vulnerability Manager 5.0

fact
NetIQ Vulnerability Manager 5.5

symptom
My Custom Security check will not score correctly against a Binary Data Value registry key.

cause
The cause of the Custom Security Check not scoring correctly is that the entry of the binary value comparison is not correct.  When the custom security check runs, it compares the binary value in the check to the binary value found in the registry and they will not match unless entered correctly, causing a constant violation in the report and the score.

fix

When creating a Custom Security Check against a Binary Registry Value, you must enter the Binary Value in the filter with Curly Braces {} around the numeric value.  For example, if you are querying  'HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing\Policy', you would enter the filter as the following:

Attribute      Operator       Type       Criteria     AND/OR

ValueName     Equals             Value          Policy          AND

BinaryData     Not equal to    value          {01}

Formerly known as NETIQKB44388