• Advanced verification with correct DB credentials - the Test conenction works and successfully connects to the DB but still cannot verify.
• Tried different policies to catch the Login failed and/or the SQL error (also check the inspection engine config where the box to log login failed is ticked. Also tried different criterias to catch from that certain server with both host name and host ip.
• The firewall accepts the connection 
• Upgrading the S-TAP
• Different ports 
• Check the reports if there is any session for the server

Described behavior can be tied with timeout or policy issue

STAP verification bases on correlation generated traffic and audit events gathered by agent.

Please check few things:

- does your policy gathers events generated by verification? If you see them in report probably you have problem with timeout. If the events are not visible you must change policy to audit them

- does standard verification works?

- do you see login error generated by standard verification?

Verification process waits a while for audited events and if they are not visible the error is generated in the last stage.

To solve problem the best solution would be expansion of this timeout - unfortunatelly not available in Guardium settings.

If my suggestion is correct - you should receive successful verification from time to time.

• Advanced verification with correct DB credentials - the Test conenction works and successfully connects to the DB but still cannot verify.
• Tried different policies to catch the Login failed and/or the SQL error (also check the inspection engine config where the box to log login failed is ticked. Also tried different criterias to catch from that certain server with both host name and host ip.
• The firewall accepts the connection 
• Upgrading the S-TAP
• Different ports 
• Check the reports if there is any session for the server

Described behavior can be tied with timeout or policy issue

STAP verification bases on correlation generated traffic and audit events gathered by agent.

Please check few things:

- does your policy gathers events generated by verification? If you see them in report probably you have problem with timeout. If the events are not visible you must change policy to audit them

- does standard verification works?

- do you see login error generated by standard verification?

Verification process waits a while for audited events and if they are not visible the error is generated in the last stage.

To solve problem the best solution would be expansion of this timeout - unfortunatelly not available in Guardium settings.

If my suggestion is correct - you should receive successful verification from time to time.

• Advanced verification with correct DB credentials - the Test conenction works and successfully connects to the DB but still cannot verify.
• Tried different policies to catch the Login failed and/or the SQL error (also check the inspection engine config where the box to log login failed is ticked. Also tried different criterias to catch from that certain server with both host name and host ip.
• The firewall accepts the connection 
• Upgrading the S-TAP
• Different ports 
• Check the reports if there is any session for the server

Described behavior can be tied with timeout or policy issue

STAP verification bases on correlation generated traffic and audit events gathered by agent.

Please check few things:

- does your policy gathers events generated by verification? If you see them in report probably you have problem with timeout. If the events are not visible you must change policy to audit them

- does standard verification works?

- do you see login error generated by standard verification?

Verification process waits a while for audited events and if they are not visible the error is generated in the last stage.

To solve problem the best solution would be expansion of this timeout - unfortunatelly not available in Guardium settings.

If my suggestion is correct - you should receive successful verification from time to time.

• Advanced verification with correct DB credentials - the Test conenction works and successfully connects to the DB but still cannot verify.
• Tried different policies to catch the Login failed and/or the SQL error (also check the inspection engine config where the box to log login failed is ticked. Also tried different criterias to catch from that certain server with both host name and host ip.
• The firewall accepts the connection 
• Upgrading the S-TAP
• Different ports 
• Check the reports if there is any session for the server

Described behavior can be tied with timeout or policy issue

STAP verification bases on correlation generated traffic and audit events gathered by agent.

Please check few things:

- does your policy gathers events generated by verification? If you see them in report probably you have problem with timeout. If the events are not visible you must change policy to audit them

- does standard verification works?

- do you see login error generated by standard verification?

Verification process waits a while for audited events and if they are not visible the error is generated in the last stage.

To solve problem the best solution would be expansion of this timeout - unfortunatelly not available in Guardium settings.

If my suggestion is correct - you should receive successful verification from time to time.

• Advanced verification with correct DB credentials - the Test conenction works and successfully connects to the DB but still cannot verify.
• Tried different policies to catch the Login failed and/or the SQL error (also check the inspection engine config where the box to log login failed is ticked. Also tried different criterias to catch from that certain server with both host name and host ip.
• The firewall accepts the connection 
• Upgrading the S-TAP
• Different ports 
• Check the reports if there is any session for the server

Described behavior can be tied with timeout or policy issue

STAP verification bases on correlation generated traffic and audit events gathered by agent.

Please check few things:

- does your policy gathers events generated by verification? If you see them in report probably you have problem with timeout. If the events are not visible you must change policy to audit them

- does standard verification works?

- do you see login error generated by standard verification?

Verification process waits a while for audited events and if they are not visible the error is generated in the last stage.

To solve problem the best solution would be expansion of this timeout - unfortunatelly not available in Guardium settings.

If my suggestion is correct - you should receive successful verification from time to time.

• Advanced verification with correct DB credentials - the Test conenction works and successfully connects to the DB but still cannot verify.
• Tried different policies to catch the Login failed and/or the SQL error (also check the inspection engine config where the box to log login failed is ticked. Also tried different criterias to catch from that certain server with both host name and host ip.
• The firewall accepts the connection 
• Upgrading the S-TAP
• Different ports 
• Check the reports if there is any session for the server

Described behavior can be tied with timeout or policy issue

STAP verification bases on correlation generated traffic and audit events gathered by agent.

Please check few things:

- does your policy gathers events generated by verification? If you see them in report probably you have problem with timeout. If the events are not visible you must change policy to audit them

- does standard verification works?

- do you see login error generated by standard verification?

Verification process waits a while for audited events and if they are not visible the error is generated in the last stage.

To solve problem the best solution would be expansion of this timeout - unfortunatelly not available in Guardium settings.

If my suggestion is correct - you should receive successful verification from time to time.

• Advanced verification with correct DB credentials - the Test conenction works and successfully connects to the DB but still cannot verify.
• Tried different policies to catch the Login failed and/or the SQL error (also check the inspection engine config where the box to log login failed is ticked. Also tried different criterias to catch from that certain server with both host name and host ip.
• The firewall accepts the connection 
• Upgrading the S-TAP
• Different ports 
• Check the reports if there is any session for the server

Described behavior can be tied with timeout or policy issue

STAP verification bases on correlation generated traffic and audit events gathered by agent.

Please check few things:

- does your policy gathers events generated by verification? If you see them in report probably you have problem with timeout. If the events are not visible you must change policy to audit them

- does standard verification works?

- do you see login error generated by standard verification?

Verification process waits a while for audited events and if they are not visible the error is generated in the last stage.

To solve problem the best solution would be expansion of this timeout - unfortunatelly not available in Guardium settings.

If my suggestion is correct - you should receive successful verification from time to time.

• Advanced verification with correct DB credentials - the Test conenction works and successfully connects to the DB but still cannot verify.
• Tried different policies to catch the Login failed and/or the SQL error (also check the inspection engine config where the box to log login failed is ticked. Also tried different criterias to catch from that certain server with both host name and host ip.
• The firewall accepts the connection 
• Upgrading the S-TAP
• Different ports 
• Check the reports if there is any session for the server

Described behavior can be tied with timeout or policy issue

STAP verification bases on correlation generated traffic and audit events gathered by agent.

Please check few things:

- does your policy gathers events generated by verification? If you see them in report probably you have problem with timeout. If the events are not visible you must change policy to audit them

- does standard verification works?

- do you see login error generated by standard verification?

Verification process waits a while for audited events and if they are not visible the error is generated in the last stage.

To solve problem the best solution would be expansion of this timeout - unfortunatelly not available in Guardium settings.

If my suggestion is correct - you should receive successful verification from time to time.

• Advanced verification with correct DB credentials - the Test conenction works and successfully connects to the DB but still cannot verify.
• Tried different policies to catch the Login failed and/or the SQL error (also check the inspection engine config where the box to log login failed is ticked. Also tried different criterias to catch from that certain server with both host name and host ip.
• The firewall accepts the connection 
• Upgrading the S-TAP
• Different ports 
• Check the reports if there is any session for the server

Described behavior can be tied with timeout or policy issue

STAP verification bases on correlation generated traffic and audit events gathered by agent.

Please check few things:

- does your policy gathers events generated by verification? If you see them in report probably you have problem with timeout. If the events are not visible you must change policy to audit them

- does standard verification works?

- do you see login error generated by standard verification?

Verification process waits a while for audited events and if they are not visible the error is generated in the last stage.

To solve problem the best solution would be expansion of this timeout - unfortunatelly not available in Guardium settings.

If my suggestion is correct - you should receive successful verification from time to time.

• Advanced verification with correct DB credentials - the Test conenction works and successfully connects to the DB but still cannot verify.
• Tried different policies to catch the Login failed and/or the SQL error (also check the inspection engine config where the box to log login failed is ticked. Also tried different criterias to catch from that certain server with both host name and host ip.
• The firewall accepts the connection 
• Upgrading the S-TAP
• Different ports 
• Check the reports if there is any session for the server