Compliance Reports

A compliance report is an HTML document that summarizes all audit log activity for a specified date range. It includes summary statistics, an audit log integrity verification, a per-user activity breakdown, and a detailed table of every operation. The report is designed for auditors, compliance officers, and IT management.


Generating via GUI

Compliance reports can be generated from the Dashboard by navigating to the reporting feature. Select a date range and click Generate. The report is saved to the report folder and opened in the default browser.


Generating via CLI

Use the --generateComplianceReport flag with optional date parameters:

AppProfileSafe.CLI.exe --generateComplianceReport --reportFrom 2026-01-01 --reportTo 2026-01-31
Parameter Required Default Description
--generateComplianceReport Yes Triggers compliance report generation mode
--reportFrom No First day of previous month Start date (ISO format, e.g. 2026-01-01)
--reportTo No Last day of the reportFrom month End date (inclusive, ISO format)

If no date parameters are provided, the report covers the entire previous calendar month. The CLI returns exit code 0 on success or 2 on failure.


Report Contents

The generated HTML report contains the following sections:

  1. Header — Hostname, report period, and generation timestamp (UTC).
  2. Summary — Eight metrics in a grid layout: total operations, successful, failed, critical events, export operations, import operations, unique users, and unique machines.
  3. Audit Log Integrity — Result of the hash chain verification (PASSED or FAILED) with details. This runs the same integrity check used in the Audit Log Viewer.
  4. Active Users — Table listing each user with their total operations, successes, and failures.
  5. Operation Details — Full table of all audit entries in the date range, sorted chronologically. Columns: Timestamp (UTC), Action, Severity, User, Machine, Target, Result, Duration, OperationId. Severity levels are color-coded (critical/error in red, warnings in orange).
  6. Footer — Application version, generation timestamp, and total entry count.


Severity Classification

Each audit entry in the report is assigned a severity level based on its action and outcome:

Severity Condition Display
Critical IntegrityCheckFailed, UnauthorizedAccess Red text, counted in "Critical Events" metric
Error ExportFailed, ImportFailed, or Success = false Red text
Warning CompletedWithErrors, schema validation failures Orange text
Info All other successful operations Normal text


Output File

The report is saved to the report folder (configured via <ReportFolder> in settings.xml) with the file name ComplianceReport_{HOSTNAME}_{yyyyMMdd_HHmmss}.html. The HTML is self-contained with embedded CSS and optimized for printing with page breaks between the summary and the detail table.