However tidy the documents are, the auditor forms their view largely in interviews with process owners. If a system administrator says they’ve never heard of the backup policy, or an HR specialist describes the leaving process differently from the document, the value of an evidence file prepared over weeks drops in an instant. Below, step by step: how process owners in IT, HR, purchasing and facility management should prepare for the interview, how to show evidence at the table and how to handle a question you don’t know the answer to.
What does the auditor verify in an interview?
An interview isn’t a knowledge test, it’s a verification technique. Under ISO 19011 guidance, the interview is one of the main methods of gathering information, together with document review and observation, and the information obtained is cross-checked with other sources wherever possible. When talking to a process owner, the auditor usually tests three things at once:
| Verified | What the auditor looks for | Typical question |
|---|---|---|
| Design | Is the process defined, are roles clear? | “How is a new user account opened?” |
| Implementation | Is what’s described visible in the records? | “Can you show the request for an account opened last month?” |
| Awareness | Does the person know the security responsibilities of their role? | “What do you do if you notice a security incident?” |
This trio is why preparation can’t be built on memorization. The auditor asks for a random example from the process described and opens the record themselves. Every difference between the description and the record shows one of two things: either the document doesn’t reflect reality, or the process isn’t followed. Both are findings.
Interview plan and choosing participants
The certification body usually shares the audit plan before the audit; the plan states which process and which controls will be reviewed at what time. On the day you receive the plan, do two things:
- Process–participant mapping: For each session, set a primary participant (the person who actually runs the process) and a backup. The primary participant isn’t the manager but the person doing the work; if the manager is needed, they give a short framing at the start of the session and step back.
- Evidence preparation: Pull each session’s checklist from the evidence matrix and test that the related records can actually be accessed. How evidence items are mapped to controls is explained in the evidence matrix guide.
A crowded session lowers productivity. With more than three or four participants, answers start correcting each other and the auditor sees inconsistency. It helps for the ISMS manager to attend every session; but their role isn’t to answer, it’s to speed up access to evidence and take notes. The person who does the work should be the one talking.
Role-based preparation: IT, HR, purchasing, facility management
Each role’s preparation is built around the controls that role owns and the records it produces. The topics below are the ones most often raised in interviews, by ISO/IEC 27001:2022 Annex A theme.
IT and system administration
- The flow for opening, changing and closing user accounts; related sample tickets.
- Who holds privileged accounts and how they’re reviewed.
- Backup scope, how failed jobs are followed up, the latest restore test.
- Patch and vulnerability management: how a critical update is assessed and applied.
- Change records: the request, approval and test trail of the latest significant change.
Human resources
- Pre-employment screening, and at what stage the confidentiality agreement is signed.
- How and how quickly IT is notified about leavers.
- How awareness training is given on joining and periodically.
- Whether the disciplinary process covers information security violations.
Purchasing
- How suppliers with access to information are identified and when their security assessment is done.
- Confidentiality and security clauses in contracts; a sample contract.
- How security requirements are assessed when buying a cloud service.
Facilities and administration
- The visitor registration and escort process; review of badge access permissions.
- The server room access list and access logs.
- Retention period and access permissions for camera recordings.
In the rehearsal meeting, ask each person to describe their own process in five minutes, then open a record from the last three months. A picture you may come across: the description follows the procedure, while the record shows the shortcut the team actually takes. Seeing this difference before the audit is the cheapest chance to fix it.
Sample questions and how to answer
A good answer is short, factual and tied to evidence. A risky answer contains generalization, assumption or explanation that strays out of scope.
| Question | Strong answer | Risky answer |
|---|---|---|
| When is a leaver’s account closed? | “A ticket comes from HR and we close it the same day. Let me show you the ticket for the latest leaver.” | “We always close them right away, it’s never been a problem.” |
| Are backups tested? | “We do a monthly restore test; here’s the latest test record.” | “The backup software says successful, so there’s no problem.” |
| Is security considered when choosing a supplier? | “If they’ll access information, an assessment form is filled in. I can open the latest assessment.” | “We work with big companies, they’re secure.” |
| What do you do if you notice an incident? | “I write to the incident reporting address and call IT.” | “I try to sort it out myself first.” |
Absolute words like “always” and “never” push the auditor to widen the sample. When a single exception turns up, the absolute statement becomes evidence that the process isn’t under control. A realistic answer covers the exception too: “We usually close them the same day; if one is closed late, it’s caught in the weekly reconciliation report.” That sentence builds trust. An absolute sentence raises doubt.
Rules for showing evidence during the interview
- Open only the evidence requested. Bringing the whole evidence folder onto the screen leads the auditor toward records they didn’t ask for but that catch their eye.
- Show evidence from its source. If possible, open the record live in the system; showing it from the ticketing system or management console is stronger than a copied file.
- The auditor chooses the sample. Instead of saying “let me show you this one” and picking the cleanest record, present the list and leave the choice to the auditor. A hand-picked sample creates distrust.
- Filter out confidential information in advance. On screens containing personal data or customer information, only the necessary fields should be visible. Additional rules for remote sessions are covered separately in the remote audit preparation guide.
- Record the evidence shown. Note which file was shown in which version; this list becomes the reference in discussions about findings.
The right approach to a question you can’t answer
Not every participant can answer every question, and expecting that isn’t realistic. What should be clear is what they’ll do when they don’t know. The right approach has three steps: say clearly that you don’t know, say who has the information or which document it’s in, and if needed offer to bring the answer during the audit. “The backup owner can give clearer information on this; they’ll be at the afternoon session” is better than any guessed explanation.
Wrong information given as a guess can turn into an inconsistency finding when it contradicts someone else’s description in a later session. Don’t guess. Raising topics that weren’t asked about, or talking at length about future improvements, also pulls the interview into out-of-scope areas.
Awareness questions need separate preparation: people aren’t expected to memorize policy clauses but to know the security behavior relevant to their own work. How this competence is built and evidenced is explained in the training and awareness evidence article; for role-based training programs, our ISMS awareness and role-based training service can also be designed as part of this preparation.
Notes and follow-up after the interview
At the end of each session, the ISMS manager writes a short session note: the topics the auditor asked about, the evidence shown, additional information requested afterwards and possible finding signals. This note is used both at the daily wrap-up and in the closing meeting to assess how findings are worded.
- Additional evidence the auditor requests is listed with an owner and a delivery time.
- Observations the auditor raises at the daily wrap-up are recorded; if a topic was misunderstood, it’s clarified with evidence the same day.
- After the audit, a short review is held with participants: which questions were hard, and in which process the description and the records diverged.
The output of this review feeds the preparation list for the next audit. For the structure of the initial certification audit, see the article the ISO 27001 Stage 1 and Stage 2 process, and for a comprehensive preparation program, our ISO 27001 certification audit preparation service. The general framework of audit techniques is defined in the ISO 19011:2018 guidelines.
Frequently asked questions
Who should attend the auditor interview?
The person who actually runs the process is the primary participant; a backup and the ISMS manager, who speeds up access to evidence, can be with them. Attendance above three or four people leads to answers correcting each other and an impression of inconsistency.
Is it right to give process owners sample answer scripts?
No. Memorized scripts fall apart at the first follow-up question and give the impression that the process exists only on paper. Instead, rehearse with the person describing their own process and showing a record from the latest period.
What should I do if I don’t know the answer to the auditor’s question?
Say clearly that you don’t know, say who has the information or which document it’s in, and if needed offer to bring the answer during the audit. A guessed answer can turn into a finding when it contradicts what was said in another session.
Who chooses the evidence sample in the interview?
The auditor should choose the sample. Presenting the list of records and leaving the choice to the auditor is more reassuring, and more in line with audit technique, than showing a clean sample chosen in advance.