Part of the Administration reference. API Restrictions | Admin Tools | Audit Logs | Compliance
Overview
Track configuration changes, detect unauthorized modifications, and generate integrity reports. The Compliance sub-tab of the Audit Log tab in the Admin Panel provides tools for monitoring configuration integrity:
- Quick Integrity Report - one-shot CSV snapshot of all scripts and settings with SHA-256 hashes
- Drift Monitoring - baselines (approved configuration snapshots) and drift checks that compare the current state against a baseline
Creating, refreshing and deleting baselines, running drift checks and changing auto-check are recorded in the Settings audit log.
Integrity report
Generates a CSV report of the entire system state: one row per script, and one row per section - settings, custom whitelists, custom blacklists, global variables, labels and folders. Each row includes a SHA-256 hash for verification.
| Column | Description |
|---|---|
category |
Data category (scripts, settings, labels, etc.) |
entity_name |
Entity name or identifier |
property_summary |
Key properties snapshot |
hash |
SHA-256 hash of the entity data |
Click Generate Integrity Report to download the CSV file. The report captures the current state - it is not stored.
Baselines
A baseline is a point-in-time snapshot of your configuration. Use baselines to detect changes over time.
Creating a baseline
- Click Create Baseline in the Drift Monitoring section
- Enter a Name (required, max 200 characters) and optional Description (max 2,000 characters)
- Configure the Scope - which sections to include:
- Scripts (with a Script Filter, see below)
- Settings (trigger types, event types, audit trigger types, Run As, API whitelist and API blacklist)
- Custom Whitelists
- Custom Blacklists
- Global Variables
- Labels
- Folders
- Optionally enable Auto-check daily for scheduled drift monitoring
- Click Create Baseline
The baseline captures the current state and computes SHA-256 hashes for all included data. The script count is displayed on the baseline card.
Script filtering
When including scripts in the baseline scope, you can filter by:
| Mode | Description |
|---|---|
| All scripts | Include every script |
| By folder | Include scripts in specific folders (up to 50 folders) |
| By label | Include scripts with specific labels (up to 50 labels) |
| Select specific | Pick individual scripts (up to 200 scripts) |
Managing baselines
Each baseline card shows:
- Name, script count and description
- Creation date, and the date of the last refresh
- The key of the open drift issue, if drift notifications created one
- Auto-check daily toggle
- View Details - show the baseline’s settings and scope
- Refresh - capture the current state as the new approved snapshot of the baseline
- Check Now - run a drift check immediately
- Delete - remove the baseline and all its drift results (asks for confirmation)
Baseline limit
Up to 20 baselines. When the limit is reached, you must delete an existing baseline before creating a new one.
Drift checks
A drift check compares the current system state against a saved baseline to detect what has changed.
Running a check
Click Check Now on any baseline card. The check:
- Captures the current system state using the same scope as the baseline
- Computes SHA-256 hashes for all current data
- Compares baseline vs. current hashes to detect additions, modifications, and removals
- Stores the result with detailed property-level diffs
Result status
| Status | Meaning |
|---|---|
| Clean | No changes detected - current state matches the baseline |
| Drifted | Changes detected - one or more items differ from the baseline |
Viewing results
Expand a baseline card to see its drift check results (25 per page):
| Column | Description |
|---|---|
| Date | When the check was run |
| Status | Clean or Drifted |
| Trigger | Manual or Scheduled |
| Changes | Summary of added/modified/removed items |
| Duration | Execution time |
Click a result to see detailed changes grouped by category (scripts, settings, labels, etc.). For modified items, individual property changes are shown with baseline and current values side by side.
Result pruning
Up to 50 drift results are kept per baseline. The oldest results are automatically removed when the limit is reached.
Auto-check
Enable auto-check on a baseline to run drift checks automatically once a day. Scheduled checks store results the same way as manual checks and are shown as Scheduled in the Trigger column; they do not require an active user.
Toggle Auto-check daily on a baseline card or during baseline creation.
Drift notifications
When a Service Project is configured with drift notifications enabled, drift detection (manual or scheduled) automatically creates Jira issues:
- First detection creates a new issue in the service project with a summary table of the changes and a CSV attachment with the full report
- Subsequent detections add a comment to the existing issue instead of creating a duplicate, with a new CSV attachment
- Unchanged drift is skipped - if the drift hasn’t changed since the last notification, no comment is added
- Deleted issues are detected automatically - if someone deletes the drift issue, a new one is created on the next detection
- Clean check - when a check of the baseline comes back clean, the link to the drift issue is cleared, so the next drift creates a new issue
The issue description includes a table of changed entities grouped by category, with up to 50 changes. If there are more changes, or the table would exceed Jira’s description size limit (about 32 KB), the table is shortened or replaced by a note pointing to the attached CSV with the full report.
At most 100 issues per day (UTC) are created for all notification types together (errors + drift).
CSV export
Each drift result can be exported as a CSV file. The file starts with comment lines naming the baseline, the check time and the status, followed by the data:
| Column | Description |
|---|---|
category |
Data category (scripts, settings, labels, etc.) |
entity_id |
Entity UUID |
entity_name |
Entity name |
property |
Changed property name |
baseline_value |
Value in the baseline |
current_value |
Current value |
status |
Change type (added, modified, removed) |
detected_at |
Timestamp of the drift check |
Click Export CSV on a drift result to download the export.
Next steps
- Administration - All admin configuration
- Audit Logs - Settings and script execution audit
- Service Project Integration - Drift notification settings
- Admin Tools - Import/export, health check, diagnostics
