The Safeguard Chrome extension does not export audit evidence. It opens Safeguard's search in a side panel next to any tab, which helps when you are working through an audit request list in another tool. Evidence itself comes from your systems, compliance connectors and the records you keep, and the auditor decides what is sufficient.
What the extension is
Per Safeguard's documentation, the extension adds an Open Safeguard toolbar icon and opens a side panel in Chrome that loads the search page of the web app. Login and search happen inside the embedded page. The extension stores no credentials and calls no Safeguard APIs itself, and it requests only the sidePanel permission. It needs Chrome 114 or later. Install it from the Chrome Web Store, pin the icon and sign in.
Nothing in the documentation says the extension collects, packages or exports evidence. So this article does not claim that. What it offers is proximity: Safeguard's chat and search sit beside the page you are working in.
Where does audit evidence come from?
The documentation lists Compliance Connectors, which bring in evidence from other systems, and an Audit Trail and Alerts page. Read those pages in the docs for what they cover. As a general rule for any audit, evidence falls into three kinds:
- Configuration evidence: screenshots or exports showing a setting, such as multi-factor authentication enforced.
- Activity evidence: logs and tickets showing something happened, such as access reviews completed.
- Policy evidence: documents showing what you said you would do, approved and dated.
Auditors prefer activity evidence with dates, since it shows the control operated repeatedly.
How can the side panel help during prep?
Use it where a question-and-answer window is useful.
Reading the request list. Auditors send a spreadsheet of requests. Keep it open in one tab and use the panel to look up terms and ideas you are unsure about.
Understanding a control. If a request references a framework requirement you do not recognize, ask for a plain explanation. Confirm it against the framework text before relying on it.
Software evidence. For requests about vulnerability management or inventories, ask about dependency findings and fixes, and pull the underlying records from the platform for the auditor.
Answers from a chat interface are leads. For anything you hand to an auditor, export or cite the original record, not the chat.
Open the framework mapping demo
What stays your job?
Deciding which controls exist, who owns them and whether they operated is your job. No tool or extension certifies you. Compliance automation can reduce collection work, and your auditor still judges sufficiency. Keep each evidence item dated, attributed and stored in a single place.
If the panel will not open or is blocked, an administrator may have switched off the browser extension for your tenant, which Safeguard allows for any client type.
What to do
- Install the Chrome extension and confirm you stay signed in after a restart.
- Read the Compliance Connectors and Audit Trail pages in the Safeguard docs.
- Load the auditor's request list in one tab and the panel beside it.
- For each request, name the source system, the owner and the date range.
- Export or cite original records, never chat answers, for the auditor.
- Track open requests and gaps in a shared sheet.
- Date and store every item in one location.
Quick check
Does the extension collect compliance evidence?
No. The documentation describes it as a side panel that loads the Safeguard search page. Evidence comes from connectors, platform records and your own systems.
Can a chat answer be given to an auditor as evidence?
Treat it as a lead. Give the auditor the underlying record, such as an export, log or ticket, with its date.
Sources
Last reviewed: 18 October 2026.
