“Audit” is a word that scares people. It sounds like the tax authority, like someone arriving to look for culprits and leaving behind a list of violations. That is why many companies put it off until something breaks.
A well-done IT audit is the opposite. It is not looking for someone to blame: it is an inventory with judgment. At the end you have a document that says what the company has, what is at risk and what makes sense to do first, in that order and with names.
One clarification first. If your plant is a subsidiary of a corporation, the corporation most likely already audits its systems under its own standards. This article is for the company that decides on its own: the maquiladora’s supplier, the family business that grew, or the plant that runs its own IT without a corporate office behind it.
What it has to review
Seven questions. If an audit does not answer one of them, ask why.
1. What runs, and where. Every server, every application, its version and who supports it. This is where the server on Windows Server 2016, which runs out of patches in January, turns up, or the PC on a test machine that was on nobody’s list.
2. Who has access to what. Accounts belonging to people who no longer work here, shared passwords, how many people are administrators and whether anybody decided that or it just happened.
3. Whether the backups work. Not whether they exist, but when one was last restored and how long it took. A backup that has never been restored proves nothing.
4. What is yours and what is not. Contracts, licenses and expiration dates. Who owns the code of your custom systems, the domain and the DNS. The agency that built your website years ago still controlling your domain looks like a detail, until the day a certificate cannot be renewed because nobody answers.
5. What only one person knows. The report only she builds, the process only he knows how to restart, the system nobody documented. This is not about distrusting anyone. It is about measuring how much the company depends on that person not getting sick.
6. Where each piece of data lives. How many copies there are of the part catalog, the inventory or the customer list, and which one wins when they disagree. If production and finance report different numbers, the cause is almost never technical: it is that nobody owns the data.
7. What your customers are going to ask for. EDI connections, security questionnaires, lot traceability, electronic work-hour records. What works today may not be enough for what you will be required to do next year.
Notice that half of these questions are not technical. That is why an audit that only talks to IT is incomplete. It has to talk to the people who use the systems on the floor, in the warehouse and in finance.
What it has to hand you
The result is not a slide deck. It is a document you can use the next day, in five parts:
- The inventory. The full list of what runs, who owns it and who supports it. Even if you do nothing else, this list is worth having.
- The risks, ranked. Each one with what it costs if it happens, how likely it is and whether it has a date. A risk with a date goes before one without.
- What to do first, what to do next and what not to do. The last list matters as much as the other two: it is the one that saves you money.
- What is process and what is software. Some problems are fixed by an agreement between two departments, not by software. A good audit separates them before anyone quotes anything.
- What can be done without buying anything. Disabling accounts, testing a restore, putting the domain in the company’s name. If the audit has none of this, be suspicious.
And the document is yours. You can use it to get quotes from whoever you want, including someone other than whoever did the audit.
Four signs it is really a sales pitch
- It ends up recommending exactly what the auditor sells, with no alternatives and no list of what not to do.
- It has conclusions but no inventory. If you cannot see the list of what was reviewed, you do not know what was reviewed.
- It only talked to IT. Whoever did not go to the floor knows how the systems are installed, not how they are used.
- It is free and claims to be complete. A free conversation to get to know each other is normal. A complete audit at no cost gets paid for later, usually inside the project it recommends.
What to prepare
The audit moves much faster if before it starts you have on hand:
- The list of technology vendors and their contracts, even if it is incomplete.
- Who holds the admin passwords for email, the domain, the ERP and the servers.
- The last three IT problems that cost the company money, and what was done about them.
- One person from each department who can spare an hour to explain how they work.
Whatever is missing from this list is already a finding.
An audit is a snapshot
The document says how the company stood on the day it was done. Six months later things have changed: someone left, a customer arrived with a new requirement, a contract was renewed. If nobody follows up, the audit ends up in a drawer.
So decide before you start who will take charge of what comes out of it. Sometimes the IT lead and a yearly review are enough. Other times you need someone in the decisions every month, which is what a fractional CTO does.
A warning about us
We do audits and we also build software, so the first sign on the list applies to us. That is why, in our audits, every recommendation to build something comes with the alternative of buying it or not doing it, and the document is yours to take to whoever you want.
Where we come in
Technology audits are part of our technology consulting, and they are almost always the first step when a company asks us for technology leadership. If you want to know what one would cover in your case, book a call. And if you would rather start on your own, Chira gives you a first written assessment at no cost.