In a remote audit, the problem usually isn’t the evidence itself but the way it’s shown: the wrong window is shared, a Teams notification pops up on screen, the tablet drops off Wi-Fi during the site walk. These issues, which solve themselves in an on-site audit, need separate preparation in a remote or hybrid audit run via video conference and screen sharing. Which screen will be shared, how will confidential information be protected, will it be recorded, how will physical controls be verified? Below, step by step, we explain this setup for ISMS owners and IT teams.
When is a remote audit used?
ISO 19011:2018, which guides management system audits, classifies audit methods as on-site and remote in Annex A, and contains separate guidance for auditing virtual activities and locations. On the accreditation side, IAF MD 4 is the mandatory document on using information and communication technology for auditing purposes. The decision belongs to the certification body: the suitability of the organization’s IT infrastructure for a remote audit, the nature of the scope and previous audit history are assessed, and the method is written into the audit plan.
Scenarios seen in the field: fully remote surveillance audits, hybrid audits where document review is remote and site review on-site, and remote audits of small branches in multi-site organizations. In TISAX assessments, the method depends on the assessment level and the labels chosen; for details, rely on ENX documents.
On-site vs remote audit comparison
| Topic | On-site | Remote | Preparation note |
|---|---|---|---|
| Document review | On screen or printed | Shared folder or screen sharing | Read-only, time-limited access |
| Process interview | In a meeting room | Video call | Participant list and connection test |
| System demonstration | At the user’s desk | Window sharing | Notifications off, separate profile |
| Physical security | Direct observation | Live video walk, records | Mobile device, coverage test |
| Random staff interviews | On the spot on site | Scheduled call | The choice must stay with the auditor |
Don’t skip the last row. In a remote audit too, the auditor must be able to choose which staff to interview. The organization presenting “prepared” people in advance lowers the value of awareness evidence, and the auditor notices. Content preparation for interviews is covered separately in the guide preparing for auditor interviews.
Technical preparation: platform, connection, backup channel
The platform (Microsoft Teams, Zoom or the certification body’s preferred tool) should be settled at the audit planning stage. If your corporate policy restricts joining external platforms, get the exception approval in advance; a meeting link stuck at the proxy on the audit morning eats up the first hour. Hold a short trial session with the auditor a few days before the audit. Let audio, screen sharing and file access problems come up that day, not on audit day.
- Connection: The main presentation computer should be on a wired connection. Wi-Fi and mobile coverage inside the facility should be tested in advance by walking it with the tablet or phone to be used for the site walk; concrete- and metal-heavy areas such as warehouses and server rooms are typical blind spots.
- Backup channel: A phone bridge or second meeting link to use if the platform drops, and both sides’ contact numbers, should be written into the audit plan.
- Hardware: A headset microphone, a second screen (one shared, one for notes) and one connected device per room to avoid echo.
- Document access: Evidence should be shared in an audit-specific folder, with view-only permission and a time-limited link. In SharePoint, an expiry date and download blocking can be added to a sharing link; verify against your tenant settings.
Set up the evidence folder structure in advance; searching for files on audit day wastes time and increases the risk of the wrong folder opening on screen. For this structure, the folder and permission model in the article evidence management with SharePoint can be used.
Confidentiality and data minimization in screen sharing
The most common incident in a remote audit is sharing the wrong screen or a notification. The auditor is under a confidentiality obligation; that doesn’t justify showing out-of-scope confidential information or unnecessary personal data. Rules you can apply:
- Share only the relevant application window, not the whole screen.
- Turn off operating system and application notifications before sharing (“Do not disturb” in Windows 11, “Focus assist” in Windows 10; including Teams’ and the email client’s own notifications).
- Use a separate browser profile for the audit; bookmarks, autocomplete and open tabs leak personal and confidential information.
- Clean the desktop and downloads folder; file open dialogs show folder contents.
- When showing lists containing personal data, use a filter to open only the sample rows or use a masked view.
- If a password manager or admin console is going to be opened, stop sharing first.
This approach is also consistent with KVKK’s (Law No. 6698) principle that personal data be relevant, limited and proportionate to the purposes for which it’s processed. The data the auditor sees should be just enough to verify the control. Anything more is risk.
Live system demonstrations and recording rules
The auditor may want to see a control working in the live system: the job history in the backup console, conditional access policies in Entra ID, the firewall rule base. A.8.34 (Protection of information systems during audit testing) in ISO/IEC 27001:2022 Annex A requires that audit activities don’t affect operational systems and that access is planned and limited. In a remote audit, this principle turns into these rules:
- Organization staff use the system; the auditor isn’t given remote control or direct access.
- If possible, an account with read-only permissions is used for the demonstration.
- No configuration changes are made during the demonstration; if the auditor wants to see the effect of a setting, a test environment is used.
- The date and system name are visible on the screen shown; that way the auditor’s note becomes meaningful evidence on its own.
A common mistake at the console is opening the rule editing screen on the production firewall to “just show it quickly”. One wrong click turns the audit into incident response. Session recording must also be agreed separately. If it will be recorded, its purpose, the party keeping it, the retention period and the disposal method must be settled in writing before the audit. Asking for recording to be paused in parts where confidential information will be shown is a reasonable request. Screenshots the auditor takes for their own notes are subject to the same rule; at the end of the audit, list which copies of evidence remain with the auditor.
Verifying physical controls remotely
Physical security controls (theme 7 in ISO 27001 Annex A) are the hardest area to verify remotely. The auditor usually combines several sources: a live site walk via tablet or phone, badge access system records, visitor records, the server room access list, environmental monitoring and maintenance records, photos with date information. For the content of the controls, see the Annex A people and physical controls guide.
On the live walk, the person holding the camera should follow the auditor’s directions. Pre-recorded video doesn’t replace observation evidence. Filming itself carries risk too: alarm panel codes, notes on a whiteboard or customer prototypes may come into frame. Under TISAX, filming in prototype protection areas is usually restricted; the method for these areas should be agreed with the auditor in advance. Controls for which sufficient assurance can’t be obtained remotely can be noted in the audit report and left to the next on-site visit. Where these decisions fit in the certification stages is explained in the article Stage 1 and Stage 2 audits.
Preparation checklist
- Remote and on-site parts, the platform and backup channel are written in the audit plan.
- A trial session was held; audio, video and sharing were tested.
- The evidence folder is ready with read-only, time-limited access.
- Separate profile on the presentation computer, notifications off, desktop clean.
- Filtered or masked views are ready for reports containing personal data.
- Read-only accounts are defined for live demonstrations.
- Recording and screenshot rules were agreed with the auditor in writing.
- The site walk device is charged, coverage was tested; no-filming areas were identified.
- It was confirmed that staff who may be called for interviews are reachable during audit hours.
Our audit evidence management with SharePoint service for setting up the evidence space, and our ISO 27001 certification audit preparation service for overall preparation of the certification process, support setting up this arrangement.
Frequently asked questions
Who decides on a remote audit, the organization or the certification body?
The certification body decides, based on accreditation rules and its own risk assessment; the method is stated in the audit plan. The organization’s job is to provide the infrastructure and access needed to run it remotely, and to report in advance topics that can’t be verified remotely. In programs such as TISAX, an on-site review may be mandatory depending on the assessment level; verify the current rule in ENX documents.
What should we do if the auditor wants to record the session?
Clarify recording in writing before the audit: the purpose of the recording, who will keep it, the retention period and the disposal method. You can ask for recording to be paused in parts where confidential information or personal data will be shown. Screenshots the auditor takes for their own notes should be subject to the same rule.
Should we give the auditor remote access to our systems or screen control?
Generally no. Organization staff use the system, the auditor watches the screen and says what they want to see. ISO 27001 A.8.34 requires that audit tests don’t affect operational systems and that access is planned and limited. If direct access is really needed, it should be given through a read-only, time-limited and logged account.
How are physical security controls verified remotely?
A site walk via live video, badge access and visitor records, dated photos and maintenance records are used together. If the auditor doesn’t find these sufficient, the related controls can be left to the next on-site visit. For areas where filming is prohibited, such as a prototype area, an alternative method should be agreed in advance.