Auditing & Compliance

Complete Insight

LogInspect can help you achieve a complete insight to your network, and help meeting common regulations such as PCI, Sarbanes Oxley, HIPAA, Basel-II, ISO-17799 (auditing and monitoring) and ISO27001 which includes DS-484:2005. The LogInspect provides prebuilt templates for most common use-cases like compliance and security reports. But reports can also be custom made with the modular report engine so it matches your needs.

Reports on Asset Security Modifications. Security changes to a system asset is registered in a "Security Modification" category.

Reports on User Authentication. User authentication are stored for reporting in administrator successful and failed attemps, plus user successful and failed attempts.

Reports on Security Incidents. Security Incidents and system errors are automatically detected and reported by the LogInspect intelligence.

Besides presentation the findings in easily to read reports we also meeting other requirements put forward by the regulations such as.

Integrity of Logs. Log data collected are stored in a secure archive which protects against data modifications and audit logs disappears (with checksums and double timestamps).

Access to Original Log Data. The original log format is accessible for backup, forensic usage and statistical usage. This gives a big flexibility when integrating with third party vendors or investigators.

Asset Owners. Each asset defined can have a primary owner and a list of secondaries. This makes the process of incident respond and incident management more smooth since there can be set a default assigned person ( or group ).

Role Based Access. LogInspect has a very complex Role Based Access model which can be used if needed. Every view can be defined whether they are allowed to be presented or not for a user and each object can have its own settings too. A good use-case example of this is; to let a user view (but not modifiy) all pages, and only present the systems which he/she is responsible for.

Audit Logs. Every authentication attempt and user action made which results in a modification is logged in an audit log. This audit log can be used to track changes to discover errors based on configuration, who made the changes and from where.