Auditing and Reporting

The PortalGuard server handles myriad types of authentication requests and events.It is possible to save these events and perform reporting or auditing on them to better understand the actual user scenarios that are occurring in your environment.

Usage Scenarios

 

Security Auditing or ROI Reporting

If you wish to report on the PortalGuard activity or save the events for auditing or compliance reasons, PortalGuard can be configured to save its event data to the Windows Event Viewer, a text file or SQL database.From this data store, it is possible to create custom reports on this data using 3rd party reporting software such as Crystal Reports.

How It Works

PortalGuard can be setup to write XML-based event data for each event it processes.This includes all login attempts, password changes and password recoveries.

Event auditing support can be enabled in the PortalGuard bootstrap configuration.This will cause PortalGuard to build a XML-based event data object in memory for each request and write it to a text file, SQL database or both.This data is written in real-time.

PortalGuard uses both data formats itself for different purposes.The file-based data is read by the PortalGuard Alerts Engine which is a simple rule engine that can monitor incoming data and send alerts when pre-defined rules or conditions are met.The SQL-based data is utilized by PortalGuard’s Credibility-based Authentication feature which allows for dynamic authentication requirements based on the user’s location, network and device.

Requirements

The Auditing and Reporting option has the following requirements:

  • Microsoft SQL Server 2005 or later if a SQL back-end is utilized.This can be the Express or Full editions.