IT support plays a far bigger role in ISO accreditation than most businesses realise. Standards such as ISO 27001 and ISO 9001 require organisations to prove consistent, documented control over their systems, and most of that proof lives inside IT: who has access to what, whether devices are patched, whether backups actually work, and what hardware and software is running. i90 isn't ISO accredited ourselves, but every year we play an integral role in helping several of our clients achieve and maintain their own accreditation, by keeping their IT systems and processes audit-ready throughout the year, not just in the weeks before an assessor arrives.
What role does IT support play?
The honest answer is that it's mostly invisible until audit time. Throughout the year we're monitoring and maintaining good working practices as a matter of course, which means that when an audit does come around, our clients are already in a strong position rather than starting from scratch. In the run-up to the audit itself, we shift into a more deliberate phase: collating evidence, pulling logs and reports, and running our own inspections to confirm compliance before the auditor does.
Our involvement doesn't stop once the evidence is prepared. We're often expected to join the audit itself, attending online meetings directly with the assessor to talk through how systems are configured, explain the reasoning behind our approach to best practice, and demonstrate live systems in real time rather than relying on documentation alone. An assessor asking pointed follow-up questions about a control is a very different experience from a report sitting untested in a folder, and having someone who actually manages the systems in the room to answer those questions in the moment makes a real difference to how an audit goes.
That distinction matters. Evidence gathered under pressure in the final week tends to be thin and easy to challenge. Evidence built up as a natural by-product of good IT management throughout the year is thorough, consistent, and far harder for an auditor to pick apart.
-
01
Access control records
Who can reach which systems, and whether that is still right
-
02
Patch management logs
Microsoft updates and third-party software
-
03
Backup and recovery evidence
Including proof of a tested restore
-
04
Asset register
Software and hardware, accurate and current
-
05
User restriction proof
Admin rights, USB, MFA and password policy
What IT evidence do ISO auditors check?
The specifics vary by standard and by organisation, but five categories come up again and again in our clients' audits.
Access control records. Who has access to which systems, and whether that access is still appropriate. This is one of the first things an auditor will probe, and one of the easiest places for gaps to appear quietly over time.
Patch management logs, covering both Microsoft updates and third-party software. Cyber Essentials asks for much the same evidence, so clients working towards both tend to find the two reinforce each other.
Backup and recovery evidence, with testing. A backup that has never been tested is a promise, not a control, and auditors increasingly want to see proof of a successful test restore, not just a green tick on a backup job. We've written separately about what proper backup evidence actually looks like.
A software and hardware asset list. You can't demonstrate control over something you can't show you know exists. An accurate, current asset register is unglamorous but foundational.
Proof that end-user abilities are appropriately restricted: limited admin access, controlled USB device use, multi-factor authentication enforced on all logins, and password policies backed by recognised best practice guidance rather than whatever felt reasonable at the time.
A real example: when communication breaks down
Not every gap is a technical failure. One of the more instructive moments in our own experience involved a staff leaver who simply hadn't been reported to us, so our normal leaver process was never triggered. In that particular case, no harm was done, the access in question was restricted to a single onsite workstation rather than anything more exposed. But it easily could have gone worse, and it's a useful reminder that IT compliance isn't purely an IT problem. It depends on two-way communication between us and the client. We can build every control correctly and still be working from incomplete information if a client doesn't tell us someone has left.
The strongest audits aren't the ones with the most impressive tooling. They're the ones where the client and their IT provider are actually talking to each other.
Does every business need this?
No, and it's not really a question of business size. In our experience it comes down to industry, contractual obligations, and compliance needs, a handful of our clients need it because a customer or regulator requires it, while others pursue and maintain ISO accreditation simply because they take pride in being the best they can be. That's worth taking seriously: ISO accreditation still carries real weight, across audiences and generations, as a visible signal of consistent quality and control. Whether the driver is contractual or simply a commitment to doing things properly, the underlying IT work looks much the same. It's also, not coincidentally, what a properly run managed IT support contract should be doing for you anyway, audit or no audit.
Common questions
Do you need to be ISO accredited yourselves to help with this?
No. Our role is supporting the IT systems and processes that sit underneath our clients' accreditation, not holding the certification ourselves. i90 is not ISO accredited, and we're upfront about that. What we bring is the year-round discipline of keeping systems in a state that stands up to scrutiny, whenever the audit lands.
Does the IT provider attend the audit itself?
Often, yes. We're regularly expected to join online meetings directly with the assessor, to explain how systems are configured, talk through our approach to best practice, and demonstrate live systems rather than leaving the client to answer technical questions alone or rely purely on paperwork.
How far in advance should ISO IT preparation start?
Ideally, it never really stops. The clients who find audits least stressful are the ones whose IT provider treats good practice as a continuous baseline rather than a seasonal task. A dedicated evidence-gathering push in the weeks before the audit still matters, but it's confirmation of existing good practice rather than a rescue mission.
What's the biggest cause of ISO audit problems on the IT side?
In our experience it's rarely a missing tool or an unpatched server, it's communication. Gaps tend to appear where a client hasn't told their IT provider about a change, a leaver, a new system, a shift in working practice, rather than where the technical controls themselves have failed.
Working towards ISO accreditation?
If your business holds or is pursuing ISO certification, we can help make sure your IT systems and processes are ready whenever the audit lands, not just in the final fortnight. Get in touch for a plain-English conversation about what your auditor will expect.
Get in touch