GUIDE · GOVERNANCE AND RISK

External IT audit: what reviewers ask and how to prepare

By the end of this guide you will know how to define the purpose and scope of an external IT audit, which documents and evidence to prepare in advance, which questions to expect and how to turn findings into a remediation plan. The aim is to reach the review with clear answers, not with documents to reconstruct.

Updated october 2026
7 min read
Altovar Technical Editorial Team

1. Why an external IT audit matters

An external IT audit is a review carried out by an independent party that checks whether the company's systems, processes and controls work as stated. It may be requested by a customer, an insurer, a certification body, an authority or be an internal decision by senior management. Each reason leads to different questions, but the preparation method is the same.

The value of an audit does not lie in the final judgement. It lies in the fact that it forces the company to demonstrate, with documents and evidence, what it says it does. A company that arrives prepared gets a useful review. One that arrives unprepared gets a list of problems it could have anticipated. Those who understand this early can turn the review into an opportunity for improvement. The tone of the whole preparation depends on this awareness.

2. Prerequisites: purpose, scope and owner

Before any preparation, you need to know what is being checked. An audit of the whole company is different from an audit of a single system or process. The purpose must be requested in writing from whoever commissions the review, and the scope must be confirmed, because it determines which documents to gather and which people to involve. Also appoint a single point of contact for the audit. The reviewer needs a counterpart who coordinates requests and knows where to find information. Without one, questions bounce between departments and timescales stretch.

3. Steps to prepare

Preparation works best as a short project with a clear sequence. Start with the documents that already exist, check that they are up to date, then carry out an internal rehearsal. Only after that gather the evidence and prepare the people who will speak with the reviewer. These steps cover most cases. Adapt them to the purpose of the audit and the size of the company, without adding activities the review does not need.

  1. Define the purpose and scope: which systems, sites and processes will be examined.
  2. Gather the main documents, such as policies, the risk register, the systems inventory and supplier contracts.
  3. Carry out an internal check before the audit, using the same questions the reviewer is likely to ask.
  4. Prepare an evidence folder, ordered by topic and with the date of each document.
  5. Appoint an owner for each area and agree who answers which questions.
  6. Re-read the findings from previous reviews and check whether they were closed with evidence.

4. What reviewers usually ask

Reviewers try to establish whether controls exist, whether they work and whether anyone checks them. For this reason their questions almost always start from a statement by the company and ask for proof. If you say backups are tested, they will ask for the record of the last test. If you say access is revoked when employment ends, they will ask for the list of revoked accesses.

The table summarises the most common areas and the evidence usually required. Not every area is covered in every audit, but it is useful to know in advance which documents would be requested. If a question has no documented answer, flag it in your preparation plan before the reviewer does. Every area should have at least one concrete piece of evidence.

AreaTypical questionEvidence to show
AccessWho can access sensitive data, and how are access rights revoked?List of users with elevated permissions and register of revocations
BackupCan the data really be restored?Record of the last restore test with date and systems involved
ChangesHow are changes to systems approved?Change requests with approval and tests carried out
IncidentsHow are security events managed and recorded?Incident register with closure status and lessons learned
TrainingDo staff know the rules that apply to them?Training log and acknowledgement of policies

5. The most common mistakes during preparation

The first mistake is preparing documents that describe a different process from the real one. A reviewer notices this almost immediately, because they ask to see the process in action and compare what they see with what is written. Documentation must describe what is actually done, even if reality is not perfect. The second mistake is hiding a known problem. A defect that is already known and has a correction plan is a manageable observation. A defect discovered by the reviewer and not declared becomes a credibility problem. The most frequent errors are these:

  • Having one person who does not know all the systems involved answer every question
  • Handing over evidence collected at the last moment, without a history that shows continuity
  • Presenting procedures as active when they were written but never applied
  • Answering a question with an opinion instead of a document

6. During the audit: how to respond

During the review, answer questions directly. If you do not know the answer, say so and indicate who can provide it, rather than improvising. An incorrect statement made in a meeting is harder to correct than an answer that arrives later with the right document. Note each request from the reviewer and the date it was received. Agree with your point of contact the timescales for providing missing evidence, and keep to them. An undeclared delay weighs more than incomplete but timely information.

7. After the audit: findings and the remediation plan

At the end of the review the auditor presents the findings. Read each one calmly and turn it into an action with an owner and a date. Not all findings carry the same weight, so distinguish between those that concern a real risk and those that concern the form of the documentation. The remediation plan should be entered into the risk register and checked at subsequent meetings. When a finding is closed, keep proof of the closure, because the next review will ask for it. A well-managed audit leaves an improvement path, not just a list of problems.

8. How to start

The first concrete action this week is to ask the commissioning party, in writing, for the purpose and scope of the review. Without these two elements nothing useful can be prepared. Even a brief answer is enough to define the next steps. Immediately afterwards, appoint your point of contact and make a list of the documents that already exist, with the date of their last update. Missing documents become the work plan for the following weeks, and the internal check can start with the highest-risk areas.

Frequently Asked Questions

Is an external IT audit mandatory?

It depends on the sector, the legal form and the commitments made to customers or insurers. Some regulations and certifications require independent reviews, others do not. If a customer or a contract asks for one, treat the request as an obligation. Check with your consultant which reviews apply to your company.

Can I prepare for the audit myself, or do I need a consultant?

You can prepare many aspects internally, especially gathering documents and carrying out the preliminary check. An external consultant is useful for the more complex technical areas and for an independent check before the actual audit. The choice depends on the complexity of the scope and the skills available.

How long before the audit should I start?

It depends on the state of the documentation. If documents exist and are up to date, preparation is short. If processes, records and evidence are missing, the work takes longer and must be planned with a margin. The later you start, the more likely it is that the evidence will look hastily assembled.

Can the reviewer ask for access to my systems?

They can ask for evidence, interviews and, in some cases, direct verification, but the scope of access must be defined within the audit scope and agreed in writing. Do not grant access that was not foreseen, and record each access granted and its duration. Ask in writing what access is really needed and for how long.

What if I find a problem before the audit?

Treat it as an improvement action. Document the problem, assess the risk, decide the treatment and keep proof of the correction. A problem found and fixed before the review is an excellent result. Do not conceal it, because the reviewer will still ask whether anything similar came up in the past.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →