SecurePoint Visitor audit logs
Audit logs that application users can't edit or delete.
Check-ins, host approvals, screening decisions, badge prints and check-outs go into an append-only, hash-chained audit log that application users cannot edit or delete, with a verifier that checks the chain. Evidence packs export it for the date range and sites your assessor asks about.
Pictured: a visit record from a demo organization, with a fictional visitor.

- Append-only
- Application users can't edit or delete an entry.
- Hash-chained
- Each entry is linked to the one before it with SHA-256, per organization.
- Checked every day
- A verifier checks the chain daily, and again when a pack that includes the audit trail is exported.
- 10-year decision records
- Screening and review records can't be deleted for 10 years.
- Evidence packs with checksums
- Pick the date range and sites. Each file in the ZIP has a SHA-256 checksum.
- Exports you keep
- The ledger as CSV or PDF, the visitor log as CSV, and evidence packs.
What goes on the record.
Each entry has a timestamp, the action, its target and who did it.
Reading the log is on the log too.
The rows pictured record someone opening the audit ledger: the permission check, then the report view. Check-ins, host approvals, screening decisions, badge prints and check-outs are recorded the same way, and the ledger filters by actor, action and entity type.
Events with no signed-in user are recorded as System, not credited to a person.

Find a past visit and export the visitor list.
Search Visitor Audit by name, email, company or host, open the visit's record, and export the list as a CSV file with one row per visit.
By default, only org admins and compliance managers can export.
Read the transcript
Step 1. Open Reports Overview, then Visitor audit. Each row is one visit.
Step 2. Search by name, email or company, or filter by host.
Step 3. Select the row to see its purpose, check-in and check-out times, host, and screening decision.
Auditor accounts can do all of this. By default, only org admins and compliance managers can export.
Step 4. To export the whole list, empty the search box and select Export CSV. Then select Download.
The file has a row for each visit, with check-in and check-out times in UTC.
Screen visitors at check-in. Keep the decisions on record.
Evidence packs for an assessor.
Templates are organized for CMMC Level 2 physical protection, DFARS 252.204-7012 and ITAR/EAR reviews.
Watch an evidence pack get built.
Pick a template, a date range and the sites. The CMMC L2 Audit Pack is a ZIP of screening activity, adjudication decisions and the audit trail, with a manifest that lists a SHA-256 checksum for each file; the PE Visitor Evidence pack holds visits, escorts and badges. The chain check runs again when a pack with the audit trail is exported.
Read the transcript
When an auditor asks how visitors were screened, an admin opens the Evidence Center and picks a template and a date range.
SecurePoint builds a ZIP file with screening results, review decisions and audit records from that period, and its manifest lists an SHA-256 checksum for each file.
Evidence Pack History keeps each sealed pack, so a later download is the same file, with the same checksum.
The audit ledger shows who did what, and when: check-ins, screening results, reviewer decisions, and exports.
Users can't edit or delete ledger records, and exports from this page come with an SHA-256 checksum.
SecurePoint Visitor. Screen visitors at check-in, and keep the decisions on record.
Rebuild the pack for a past visit.
Find the check-in date, generate a pack whose dates cover the visit, check each file against its checksum, and download the same pack again later from Evidence Pack History.
Read the transcript
Step 1. In Reports overview, open Visitor audit, and find the visitor's check-in date.
Step 2. Back in Reports overview, open Evidence packs. Pick a template, and dates from before the visit to a few days after.
Step 3. Select Generate to download a ZIP of screening results, review decisions and audit records for those dates.
Step 4. Open the ZIP's manifest. It lists an SHA-256 checksum for each data file, so you can check each one.
Step 5. Need it again later? Select Download ZIP in Evidence Pack History. You get the original sealed file, with the same checksum.
Screen visitors at check-in. Keep the decisions on record.
What the audit log does, and where it stops.
Each line says what is built in and what is not offered. SecurePoint supports your compliance program; it does not certify it.
| Area | Status | What it means |
|---|---|---|
| Append-only entries | Built in | Application users cannot edit or delete an entry. Update and delete are refused at the database. |
| SHA-256 hash chain | Built in | Each entry's action, actor, target and time are chained to the entry before it, per organization, so a deleted, inserted or reordered entry shows up when the chain is checked. |
| Chain verifier | Built in | Checks the chain every day, and again when a pack that includes the audit trail is exported. |
| Decision records | Built in | Screening and review records can't be deleted for 10 years. |
| IP addresses | Hashed at 180 days | After 180 days, the IP address on each entry is replaced with a salted hash. |
| Exports | Built in | The ledger exports as CSV or PDF, the visitor log as CSV, and evidence packs as ZIP files with checksums. |
| Sending logs to a SIEM | Not offered | Nothing is pushed to your SIEM. Keep the exported files in your own systems. |
Related pages
Bring your assessment scope. We'll export the pack.
We'll check in a visitor, hold a possible match, and export the evidence pack with its checksums and the audit trail.
Frequently asked questions
- What makes SecurePoint audit logs different from application logs?
- They are a compliance record, not developer telemetry. Entries go into an append-only, hash-chained audit log that application users cannot edit or delete, with a verifier that checks the chain, and the same entries go into the evidence packs you export.
- Can someone just edit or delete an audit record?
- Not from the application. It is an append-only, hash-chained audit log that application users cannot edit or delete, with a verifier that checks the chain every day and again when a pack that includes the audit trail is exported. Screening and review records can't be deleted for 10 years.
- How long are records kept?
- Screening and review records can't be deleted for 10 years. After 180 days, the IP address on each audit entry is replaced with a salted hash.
- Is this only for visitor logs?
- It records SecurePoint Visitor activity: check-ins, screening, adjudication decisions, badge prints, check-outs and administrative actions, including screenings run through the screening API. SecurePoint Education keeps its own case records and evidence packs.
- Can we send the audit log to our SIEM?
- Not directly. Nothing is pushed to a SIEM. Export the ledger as CSV or PDF, or export an evidence pack, and keep the files in your own systems.