Windows: Inspection engine verification

S-TAP verification confirms that the STAPs and their inspection engines in your environment are running and actively monitoring database activity. Understand verification, and define a schedule to regularly verify S-TAPs.

Verification checks sniffer operation and communication between the Guardium system and the inspection engines. You can enable verification for all S-TAP clients on your system, or individual S-TAP clients, or individual inspection engines.

Verification is supported for these database types:
  • DB2
  • DB2 Exit (DB2 version 10)
  • FTP
  • Kerberos
  • Mysql
  • Oracle
  • PostgreSQL
  • Sybase
  • Windows File Share
  • exclude IE
  • MSSQL
  • named pipes
There are two types of verification:
Standard verification
Checks the sniffer operation, and the communication between the S-TAP and the inspection engine. It submits invalid login request and verifies that the appropriate error message is returned.
Advanced verification
Use advanced verification to avoid failed login requests, and manage individual IEs. For avoiding failed login requests, you must identify or create a datasource definition associated with the target database. The datasource definition includes credentials, which the verification process uses to log in to the database. Then it submits a request to retrieve data from a nonexistent table in order to generate an error message.
For both types of verification requests, the results are displayed in a new dialog that provides information about the tests that were performed and recommended actions for tests that failed.
Parent topic: Windows: Configuring S-TAP