Scan History
Short local scan history for EA delta review, not a long-term archival subsystem.
Veridominus keeps a bounded local history of EA scan snapshots for each server profile. The current implementation is designed to support recent change review and current-versus-previous delta calculation.
Local onlyUp to 5 snapshots per server profileCurrent-versus-previous delta
What is saved
- The app stores up to five EA scan snapshots per server profile.
- Snapshots are local to the Mac and scoped to the Jamf server profile that produced them.
- The saved history is used to compute the current scan delta against the most recent previous snapshot.
What the current delta shows
- New extension attributes in the current scan
- Removed extension attributes compared with the previous saved snapshot
- Changed extension attributes where the classification state changed
The current implementation compares the latest scan against the immediately previous saved snapshot. It is not an arbitrary compare-any-two-snapshots workflow.
Storage and retention notes
Scan history is stored locally by the app. It is not uploaded to a Veridominus backend because normal product operation does not include one.
Bounded retention is intentional
Scan history is not retained indefinitely. The current implementation keeps a short rolling history instead of presenting itself as a full audit archive.
What this page does not claim
- It does not claim a long-term immutable audit log.
- It does not claim arbitrary offline comparison across any two historical snapshots.
- It does not document a stable on-disk file path as part of the product contract.