Verisys - How it Works
File Integrity Monitoring
A baseline snapshot of the current system state is taken and according to your configuration Verisys will automatically compare the system against this baseline to detect any changes. Using the console, you can also start an integrity check manually at any time.
The Verisys agent examines a number of properties and attributes of each file (shown below) to ascertain whether any changes have been made. Rather than simply check basic object properties, Verisys performs a complex cryptographic hashing algorithm on the actual data contained within each file - if files are altered in any way, Verisys will detect it.
- Object Name
- Creation Time
- Last Modified Time
- Last Accessed Time
- Size
- Flags
- CRC-32
- SHA-256 Hash
- Owner
- Primary Group
- Permissions
- Audit Rules
Using the Verisys console, agents can be configured to monitor specific files or groups of files using wildcards, and can recurse through a directory structure. You may have different monitoring requirements for some objects (for example you may wish log files to be able to grow but want to detect any alterations to previously logged data).Verisys accordingly allows to you configure different monitoring levels to give you control over what properties are observed.
In your environment some system objects may be more critical than others, so Verisys allows you to set a priority for each monitoring rule, enabling different actions to be taken automatically. To find out more about Verisys reporting and alerting capabilities, click here.
Templates for Rapid Deployment
Operating system and application templates for common system configurations are included to help you get started:
- Microsoft Windows Server 2003
- Microsoft Windows Server 2008
- Microsoft Windows XP
- Microsoft Windows Vista
- Microsoft Windows 7
- Microsoft SQL Server 2000
- Microsoft SQL Server 2005
- Microsoft SQL Server 2008
- Microsoft IIS 5
- Microsoft IIS 6
- Microsoft IIS 7
- Apache HTTP Server 2.0
- Apache HTTP Server 2.2


