Status

Unauthorized

Admins 

Name/PWD Age of Admins

Whitelist files Match

Compliant: All users in the Administrators group are in the ComplianceWhitelist.txt file

Not-Compliant: There are users in the local Administrators group that are NOT in the ComplianceWhitelist.txt file.

 If the status shows Not-Compliant this field will show which users are in the endpoint's local Administrators group that are NOT in the ComplianceWhitelist.txt file.

Displays the members of local Administrators group as well as the age of the passwords for each of those users.  This can be useful in determining if any admin-user is violating corporate password policy and creating a potential vulnerability.

Compares the hash of the ComplianceWhitelist.txt file on that endpoint with the hash of the backup file created by the 'Deploy Whitelist' task.  If there is a mismatch then it is likely someone has modified the primary Whitelist file to fool the policy

Primary File hash

Backup File hash

Primary File Date

Backup File Date

The sha1 hash of the primary ‘whitelist’ file.  A difference between this and the hash on other clients or this client’s backup file likely indicates that someone has made unauthorized changes to this file.

The sha1 hash of the backup ‘whitelist’ file.  If someone makes unauthorized changes to the primary whitelist file there will likely be a difference between the hashes of the primary and the backup files.

The modification date of the primary whitelist file.  If the file has a different date than the ‘official’ whitelist file, it will allow an operator to detect that the file on this computer may not be the same as the 'official' version.