SMSMC Blog

The auditor asked for evidence you do not have: how to respond, and how to stop it happening again

When an auditor requests proof of a control you did not consistently perform or record, the right response is honest and specific. What to send, what never to do, and how to build evidence as you go.

By Jim Venuto

The request list arrives

Three weeks into a SOC 2 Type 2 audit, the audit firm sends its sample request. For the access review control, it wants the quarterly user access reviews for all four quarters of the audit period, with the reviewer’s sign-off and the tickets showing that access was removed where the review said so. The company did the review in the first and third quarters. In the second quarter the person responsible was on leave. In the fourth, it was done in a meeting and nobody wrote it down.

The control description in the system description says “quarterly.” The evidence shows two of four.

This is common in first audits, and it happens in later ones too. How the company responds over the next 48 hours matters more than the gap itself.

What the auditor is doing

It helps to understand what the request is for. NIST SP 800-53A Rev. 5, the federal guide to assessing security and privacy controls, describes three assessment methods that are a useful way to think about any audit request: examine (reviewing documents, records and activities), interview (discussing with people to understand or clarify), and test (exercising a mechanism or activity to compare its actual state with the expected one). A request for four quarterly reviews is the examine method applied to records. The auditor needs those records to conclude that the control operated as described across the period.

An interview cannot replace a missing record for a control that is supposed to leave one. “We did it, we just did not write it down” is, from the auditor’s side, a control that cannot be shown to have operated.

The 48-hour response

1. Confirm what exists, precisely

Before replying, search properly. Evidence often exists in places nobody thought of: a calendar invitation for the review meeting, a chat thread where the reviewer approved removals, tickets in the help desk that removed accounts that quarter, an export someone saved to a personal folder. Collect whatever is genuine and dated.

Check system logs too, and check them quickly. Some evidence disappears on a schedule. Microsoft, for example, states that Audit (Standard) records in Microsoft 365 are kept for 180 days by default; for users with E5-level licensing, Exchange, SharePoint, OneDrive and Entra records are kept for one year by default. If the proof of an account change sits in a log, it may be gone if you wait.

2. Tell the auditor the truth, in writing

Send a short, factual response:

  • what you have, with the files attached,
  • what you do not have, stated plainly,
  • why, in one sentence, without excuses,
  • what you are doing about it.

For example: “Reviews for Q1 and Q3 are attached. The Q2 review was not performed because the control owner was on leave and no backup was assigned. The Q4 review was held on December 12 but not documented; the attached help desk tickets show the access removals agreed at that meeting. We have assigned a backup reviewer and moved the review into the ticketing system with required sign-off, starting this quarter.”

Auditors work with gaps all the time. They cannot work with evidence they later find out was not real.

3. Never create evidence after the fact

Do not backdate a spreadsheet, recreate a sign-off with an old date, or edit a document’s history to cover a quarter. Beyond the ethical problem, it puts the whole report at risk: an auditor who finds one fabricated item has no reason to trust the rest. It is also the kind of act that turns an exception in a report into a serious problem with customers who rely on that report.

Completing a review now, and dating it today, is fine. Label it for what it is: a current review, not a past one.

4. Ask how the gap will be treated

Ask the auditor how the gap will appear in the report, whether other controls that cover the same risk will be considered, and whether management can include a response. Ask early, so there are no surprises when the draft arrives.

5. Write management’s response

If the report will describe the gap, prepare a short management response: what happened, what changed, and from when. Keep it factual. A believable fix, with a date, is what a reader of the report needs to see.

Why it happened, and how to stop it

Most evidence gaps come from four causes:

CauseFix
The control depends on one personName a backup for every recurring control
The control happens in a meeting or a conversationMove it into a system that records it: a ticket, a form, a task with required sign-off
Nobody checks that it happenedA monthly five-minute review of recurring controls by someone other than the owner
The description promises more than the company doesDescribe the control as it actually runs; “semi-annually” done reliably is better than “quarterly” done sometimes

The last row deserves attention before the next audit period starts. The system description and control list are yours to write. Promising a frequency you cannot keep turns a reasonable practice into an exception.

Build evidence as you go

A simple discipline prevents most of this:

  • Every recurring control produces an artifact: a ticket, a signed form, an export, a screenshot with a date.
  • Artifacts go to one place, named by control and period, the day they are created.
  • A calendar shows each recurring control, its owner and its backup.
  • A pre-audit check a month before the period ends confirms that every control has its full set of artifacts, while there is still time to fix the process for the next period.
  • Log retention is set to cover the audit period plus a margin, or logs are exported on a schedule, so system evidence outlives the default retention.

A compliance automation platform can do some of this through integrations, but only for systems it can read. Meetings, sign-offs and reviews still need a person to record them.

When to get help

If you are in an audit with gaps now, an experienced advisor can help you sort genuine evidence from noise, write the response and management’s statement, and redesign the controls so the next period is clean.

Want to talk it through? Book a free 30-minute call with Security Medic Consulting.

Sources