trio.so
Templates

IT Audit Checklist (Free Excel, PDF + Word Template)

Free IT audit checklist template in Excel, PDF and Word: 66 checks in 8 areas, an audit questionnaire, a findings tracker and a filled-in example.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

An IT audit asks a simple question: do the controls you say you have actually work? Answering it takes more than a list of good intentions. You need to know what to check, what evidence to ask for and how to write up what you find so it gets fixed.

This free IT audit template gives you all three. The Excel tracker holds 66 checks in 8 areas, each with a control question, what good looks like and the evidence to request, plus an audit plan, an interview questionnaire, a findings tracker and a dashboard. The PDF and Word versions add a findings report page and a one-page small-business version.

In short

  • An IT audit tests whether your IT controls are designed well and working, using evidence rather than opinions.
  • Run it in six steps: plan, scope, collect evidence, test, report and follow up.
  • Cover eight areas: governance, access, data and backup, infrastructure and network, disaster recovery, assets, vendors and endpoints.
  • Write findings with a risk rating, an owner and a target date, then track them until they close.

What Is an IT Audit?

An IT audit is a structured review of how your organization runs and protects its technology. The auditor compares what is in place with what should be in place, tests a sample of the controls, and reports the gaps with a risk rating. The point is an honest view of where IT could fail, and a list of fixes in order of risk.

A checklist keeps the audit consistent: the same questions every year, so results can be compared area by area.

Types of IT Audit

  • Internal or external. An internal audit is run by your own people to find and fix problems early. An external audit is run by an independent firm, often for a customer, investor, regulator or financial statement audit. This template is built for the first and helps you prepare for the second.
  • General controls or application controls. IT general controls (ITGC) apply across systems: who gets access, how changes are made, how systems are run and backed up. Application controls sit inside one system, such as input checks or approval steps in an ERP. This checklist focuses on general controls.
  • By scope. An infrastructure audit looks at servers, networks and cloud platforms; a security audit at access, patching and incident response; a framework-focused audit at one standard, such as ISO/IEC 27001.
  • Regulated industries. Banks, healthcare providers and other regulated businesses add the checks their regulator names. Keep this checklist as the base and add those rows at the bottom.
IT general controls apply across all systems; application controls sit inside one system
IT general controls apply across all systems; application controls sit inside one system

Audit teams commonly describe IT general controls in four areas: access to programs and data, program changes, program development and computer operations. The checklist covers all four, mostly in the access and infrastructure areas, so the same file works whether your auditor talks in ITGC terms or in plain IT language.

How to Run an IT Audit in Six Steps

The six steps of an internal IT audit, from planning to follow-up
The six steps of an internal IT audit, from planning to follow-up
StepWhat you doWhat you end up with
1. PlanAgree why you are auditing, who leads it, the dates and who signs off the report. Read last year's findings.Audit plan with objective, lead auditor and dates
2. ScopeList the systems, sites and processes in scope, rate each area's risk and decide where to look hardest.Scope table with a risk rating per area
3. Collect evidenceSend the evidence request list early, interview owners with the questionnaire and pull samples (for example 10 leavers from the last quarter).Evidence log, interview notes, samples
4. TestCompare what you find with what good looks like. Mark each check Pass, Partial, Fail or N/A and rate the risk.Completed checklist
5. ReportWrite each finding with its risk, cause and a recommendation, and agree an owner and a target date.Findings report signed by management
6. Follow upTrack actions to closure and retest what you fixed. Start next year's audit from the open items.Findings tracker with closure evidence

Planning and scoping decide where your time goes. Rate each area's risk on the Audit Plan and Scope tab before you start: high-risk areas get more samples and more interviews, low-risk areas can carry forward last year's result if nothing has changed. Send the evidence requests a week or two before fieldwork.

Testing means comparing evidence with the "what good looks like" column. A policy not reviewed in three years is a Partial. A leaver account still active after a month is a Fail, whatever the policy says. That gap between paper and practice is what an audit is for.

The Checklist: Eight Areas, 66 Checks

The checklist keeps the seven classic audit areas and adds an eighth for endpoints. Each check below is written as a control question. In the workbook, each one also has what good looks like, the evidence to request, a framework reference and columns for owner, status, risk and due date.

The eight areas of the IT audit checklist and the number of checks in each
The eight areas of the IT audit checklist and the number of checks in each

1. Governance and Policy

Is IT run on purpose, with policies, owners and management oversight? Start here, because every other area depends on policies, owners and a current risk assessment. Our IT governance policy template covers roles and oversight.

  • Is there an approved IT or information security policy, reviewed in the last 12 months?
  • Are IT roles defined, including an owner for each key system?
  • Is there an IT risk assessment from the last 12 months, with an owner and a treatment for each risk?
  • Do you know which laws, contracts and frameworks apply to your IT?
  • Have staff acknowledged the policies, and does every exception have an approver and an end date?
  • Does management get regular IT and security reports, and act on them?
  • Are last audit's findings closed or still tracked?

2. Security and Access Management

Can only the right people reach systems and data, and do you know who can? Access is where ITGC testing usually starts, and where gaps between policy and practice show up fastest. Pull a sample of joiners and leavers and trace each one. Our user access review template and access control policy template help with both.

  • Is access granted through an approved request, based on role and least privilege?
  • Is access removed on the last day when people leave, and old rights removed when they change roles?
  • Are user access reviews done on a schedule for key systems?
  • Are admin accounts few, named and separate from everyday accounts?
  • Is multi-factor authentication required for remote access, email, cloud apps and admin accounts?
  • Do password rules follow your policy, with no shared personal accounts?
  • Are shared and service accounts listed, owned and their passwords changed on a schedule?
  • Is logging on for key systems, with logs kept for a set period and reviewed?
  • Do staff complete security awareness training when they join and every year?

3. Data Protection and Backup

Is data handled by its sensitivity, backed up, and recoverable? A backup that has never been restored is a hope, not a control. Ask for restore test records, not the backup schedule. See the data backup and recovery policy template.

  • Is data classified, and do people know how to handle each class?
  • Is sensitive data encrypted at rest and in transit?
  • Are critical systems backed up on a schedule, with one copy offline or off site?
  • Are restores tested, with results recorded?
  • Is there a retention schedule, and is expired data disposed of securely?
  • Is there an incident response plan, tested in the last 12 months?
  • Are incidents logged with times, actions and lessons learned?

4. IT Infrastructure, Network and Operations

Are servers, networks and cloud services documented, supported, secured and run under control?

Infrastructure is the biggest area in the checklist. It covers three layers, plus the operations around them:

LayerWhat to look atEvidence that settles it
NetworkDiagram, firewall rules, network device firmware, admin access, segmentation, Wi-Fi, remote accessFirewall rule export with review sign-off; device list with firmware versions
Servers and cloudSupported operating systems, patching, hardening baseline, cloud admin roles and settingsServer list with OS versions and patch dates; cloud admin role list
FacilitiesLocked server rooms and network closets, entry records, power and coolingAccess list, entry log, UPS test record
OperationsChange control, go-live testing, job and backup failure handling, availability alertsSample of change records; failed job tickets

Change control and job monitoring are the ITGC areas of program changes, program development and computer operations in practical form. For server settings, our server hardening checklist goes deeper, and the configuration management policy template sets the baseline you audit against.

  • Is there a current network diagram showing sites, internet links, firewalls, network segments and cloud connections?
  • Are firewall rules documented, justified and reviewed at least once a year?
  • Do firewalls, switches, routers and access points run supported firmware, with default passwords changed?
  • Is admin access to network devices limited to named people and logged?
  • Is the network segmented, keeping guest Wi-Fi, servers and sensitive systems apart?
  • Is Wi-Fi secured with WPA2 or WPA3, with the guest network separate?
  • Is remote access protected with MFA and reviewed?
  • Do servers run supported operating systems, patched on a schedule and hardened to a baseline?
  • Are availability, capacity and performance of key systems watched, with alerts acted on?
  • Are changes to production systems requested, tested, approved and recorded, including emergency changes?
  • Are new systems and major upgrades tested and signed off before go-live?
  • Are scheduled jobs, backups and integrations checked for failures, with failures followed up?
  • Are cloud platforms and SaaS admin settings configured to a baseline, with admin roles reviewed?
  • Are server rooms and network closets locked, with access limited and recorded, and power and cooling protected?
  • Are external vulnerability scans or penetration tests run on a schedule, with findings fixed?

5. Disaster Recovery and Business Continuity

Can the business keep going, and recover IT, after a serious outage? The question is not whether a plan exists but whether it has been tested and whether the recovery targets were reached. Our disaster recovery plan template gives you a format.

  • Is there a disaster recovery plan for critical systems, reviewed in the last 12 months?
  • Are recovery time and recovery point objectives set for each critical system?
  • Has the plan been tested, and were the targets met?
  • Are there redundant systems or failover for services that can't wait?
  • Is there a business continuity plan covering people, sites and suppliers, not only IT?

6. IT Asset Management

Do you know what you own, who has it and when it retires? You can't protect, patch or retire what you don't know you have. Compare the register with what your device management, network scans and cloud consoles actually see. Our IT asset management policy template sets the rules.

  • Is there one asset register covering hardware, software, cloud services and licenses?
  • Does each asset have an owner, a site and a lifecycle status?
  • Are software licenses tracked against installs and renewal dates?
  • Are end-of-life hardware and software identified, with a plan to replace them?
  • Are retired assets wiped and disposed of with a record kept?
  • Is the register checked against discovery data (device management, network scans, cloud consoles) at least every quarter?

7. Vendor and Third-Party Management

Are the companies that run or reach your IT chosen, contracted and watched with care? Vendors run more of your IT every year, so their controls are part of yours. Check the contract terms and the access, not just the questionnaire. See the vendor management policy template.

  • Is there a list of IT vendors and service providers, with what each can reach?
  • Are vendors rated by criticality?
  • Are critical vendors assessed for security before signing and on a schedule after?
  • Do contracts include security requirements, breach notification, audit rights, service levels and exit terms?
  • Are service levels and vendor performance reviewed?
  • Is vendor access to your systems limited, logged and removed when the work ends?

8. Endpoints and Devices

Are the laptops, desktops and phones your staff use known, encrypted, patched and configured? Many checklists stop at servers and networks, but much of your data lives on laptops and phones. These checks make the device fleet its own area. For a deeper review of your device management setup, use the MDM audit checklist.

  • Is every laptop, desktop and phone that holds company data in an inventory with its owner and serial number?
  • Is installed software inventoried, with unapproved software found and removed?
  • Are laptop disks and phones encrypted, with encryption status shown for each device?
  • Are OS and third-party app patches applied on set timelines by severity, with patch status for each device?
  • Are vulnerabilities on devices tracked and prioritized, for example by CVSS, EPSS and the CISA KEV list?
  • Do devices follow a configuration baseline (screen lock, firewall, supported OS), with failed settings followed up?
  • Is malware protection running and up to date on every endpoint?
  • Is USB storage blocked where it isn't needed?
  • Can a lost or stolen company device be locked or wiped, with a record kept?
  • Are devices returned and wiped when people leave, and disposed of securely at end of life?
  • Do personal devices used for work follow a policy that keeps company data separate?

IT Audit Questionnaire: Questions to Ask Owners

Interviews tell you how things are supposed to work and where to look. The questionnaire tab has 30 questions across the eight areas. A few that tend to surface real gaps:

  • Walk me through how a new starter gets access. Who approves it?
  • How do you know a leaver's accounts were disabled on their last day?
  • When did you last restore from backup, and how long did it take?
  • How fast do critical patches reach every device, and how do you check?

Treat every answer as a lead, not as evidence. If the owner says leavers are removed on the last day, the next step is to compare the HR leaver list with active accounts.

What Evidence IT Auditors Ask For

A check passes on evidence, not on a yes in an interview. Most evidence falls into five kinds:

KindExamplesTip
Exports and reportsDevice inventory, user lists, admin role lists, patch status per device, MFA enrollmentAsk for the export with a date, not a screenshot of a dashboard
SamplesJoiners and leavers, change records, access requests, incidentsPick the sample yourself from the full population, for example 10 to 25 items
Signed recordsAccess reviews, policy approvals, firewall rule reviews, restore testsLook for a name, a date and what was decided
ConfigurationPassword and MFA settings, encryption, backup jobs, firewall rulesSee it in the system, or ask for a configuration export
WalkthroughsServer rooms, a live change, a restoreWatch it happen and write down what you saw

Record where each piece of evidence is kept in the Evidence reference column. Next year you'll know exactly what to pull again.

Writing Up Findings

A finding that just says "access reviews not done" rarely gets fixed. Write each one in five parts so the owner understands what went wrong and why it matters:

PartWhat to write
ConditionWhat you found (the fact, with evidence)
CriteriaWhat good looks like (your policy, a framework or a contract)
CauseWhy it happened
EffectWhat could go wrong, which sets the risk rating
RecommendationWhat to do, with an owner and a target date

Then rate the risk. The template uses three levels with suggested fix times: High (fix within 30 days), Medium (within 90 days) and Low (within the year). Agree them with management before the audit, not after. The Findings and Actions tab flags overdue actions and counts days open, and the Dashboard rolls it up for your report.

How Often to Audit, and Who Should Do It

Many organizations run a full internal IT audit once a year, with lighter checks in between on the areas that change fastest, such as access, patching and backups. Audit again after a major change, such as a merger, a new core system or a serious incident. If a regulator, customer contract or framework sets a frequency, that comes first.

Who runs it depends on your size:

  • An internal audit team, if you have one, gives the most independence inside the business.
  • The IT team itself can run a self-assessment. It's cheaper, but have someone outside the team review the results.
  • An external firm brings independence and specialist skills, and is required for some customer, investor and financial statement audits.

Between full audits, our IT health check template is a shorter, quarterly look at the same areas.

A Short Version for Small Businesses

A 20-person company doesn't need 66 checks and a findings committee. It needs the basic controls that prevent common problems. The PDF and Word files include a one-page short version; here it is:

  • Write a one-page IT and security policy and have every employee read it.
  • Keep a list of every laptop, phone and account the business pays for, with who has it.
  • Turn on multi-factor authentication for email, banking, cloud apps and admin accounts.
  • Remove access on the day someone leaves, and collect their devices.
  • Encrypt every laptop and phone that holds business data.
  • Turn on automatic updates for operating systems and apps, and check they install.
  • Run malware protection on every computer.
  • Back up important data, keep one copy off site or offline, and test a restore every quarter.
  • Change default passwords on the router and Wi-Fi, use WPA2 or WPA3, and keep guests on a separate network.
  • Know who to call and what to do if a device is lost or you get hacked.
  • List the vendors who hold your data and check their security terms.
  • Replace hardware and software that no longer gets security updates.
  • Give staff a short security briefing when they join and once a year.
  • Review this list once a year and write down what you fixed.

Move to the full checklist when you grow or a customer asks for evidence.

Using It With ISO 27001, NIST CSF, CIS Controls and COBIT

The checklist isn't tied to one framework, but each check carries a general reference so you can see where it fits. The reference names an ISO/IEC 27001:2022 Annex A theme, a NIST CSF 2.0 function and, where one fits, a CIS Controls v8.1 Control number.

FrameworkWhat it is
COBIT 2019 (ISACA)A governance and management framework for enterprise IT: 40 governance and management objectives in five domains (Evaluate, Direct and Monitor; Align, Plan and Organize; Build, Acquire and Implement; Deliver, Service and Support; Monitor, Evaluate and Assess).
IT general controls (ITGC)As audit teams commonly describe them: access to programs and data, program changes, program development, and computer operations.
NIST Cybersecurity Framework 2.0Published 26 February 2024, with six functions: Govern, Identify, Protect, Detect, Respond and Recover.
ISO/IEC 27001:2022 Annex A93 controls in four themes: organizational (37), people (8), physical (14) and technological (34).
CIS Controls v8.1Released June 2024: 18 Controls, from inventory of enterprise assets (1) to penetration testing (18).

These are pointers, not a mapping: a framework-focused audit needs the framework's own requirements. Read the publisher's text at NIST, ISO, CIS and ISACA. Our ISO 27001 checklist walks through that standard, and the compliance checklist template tracks any framework you report against.

What's in the Download

The workbook's Example tab: a made-up company's checklist results, pass rate by area and findings
The workbook's Example tab: a made-up company's checklist results, pass rate by area and findings
  • Excel workbook (IT-Audit-Checklist-trio.so.xlsx): an audit plan, the 66-check checklist, the questionnaire, findings and actions, a filled-in example for a made-up company, a dashboard and sources. Formulas only, no macros.
  • PDF (IT-Audit-Checklist-trio.so.pdf): the six steps, an audit plan page, the checklist with tick boxes, the questionnaire, a findings report template and the small-business short version.
  • Word file (IT-Audit-Checklist-trio.so.docx): the same checklist, ready to edit.
The IT audit checklist PDF: cover, the six steps and the checklist pages
The IT audit checklist PDF: cover, the six steps and the checklist pages

Where trio.so Fits

trio.so does not run the audit, assess vendors, test disaster recovery, audit networks or firewalls, or issue certifications. Those stay with your auditors, your IT team and your other tools.

What it gives you is evidence for the endpoint part of the audit: the laptops, desktops and phones your staff use every day. trio.so is device management for Windows, macOS, Linux, iOS/iPadOS and Android, from one console. For the endpoint and asset checks in this list, it gives you:

  • A device inventory for Windows, macOS, Linux, iOS/iPadOS and Android with each device's owner, serial number and installed apps.
  • Disk encryption enforcement on Windows and Mac laptops (BitLocker, FileVault) and on iPhones and Android phones, with each device's encryption status.
  • Vulnerability findings matched to CVEs with CVSS, EPSS and CISA KEV data; OS updates through Auto Patch policies and third-party fixes through remediation plans, with the result for each device (Secure and Zero Trust plans).
  • Policy status for each device (applied, failed or pending) and compliance evidence export for your auditor.
  • Console roles, and a CSV export of console members with their roles, status and last-active dates, for reviewing who can manage your devices.
  • Multi-factor authentication at user sign-in and single sign-on (Zero Trust plan).
  • Remote lock for lost Macs, iPhones and Android devices.
  • Remote wipe of lost or stolen company-owned devices.
  • USB storage blocking on Windows, macOS and Linux.

See how the device inventory and patch management work, or how compliance automation exports evidence. Plans start at $5 per device.

Start free trial Book a demo

14-day free trial. No credit card required.

Related Templates

Sources. Last reviewed November 2026. Framework references are general pointers to ISO/IEC 27001:2022 Annex A themes, NIST Cybersecurity Framework 2.0 functions and CIS Controls v8.1 Control numbers; the wording of every check is ours. trio.so is not affiliated with or endorsed by ISO, NIST, the Center for Internet Security or ISACA.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Get the endpoint evidence your auditor asks for

trio.so keeps a device inventory with owners and serial numbers, shows encryption, patch and policy status for each device, and exports compliance evidence for your auditor.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

A list of the controls an IT audit tests, written as questions, with the evidence to request for each. A good one covers governance, access, data and backup, infrastructure and network, disaster recovery, assets, vendors and endpoints, and records a result, a risk rating and an owner for every check.

Six steps: plan the audit (objective, auditor, dates), set the scope and rate each area's risk, collect evidence through requests, interviews and samples, test each control against what good looks like, report findings with risk ratings and owners, and follow up until every action is closed.

Controls that apply across your systems rather than inside one application. Audit teams commonly group them into four areas: access to programs and data, program changes, program development and computer operations, which includes job monitoring, backup and recovery, and incident handling.

Many organizations run a full internal IT audit once a year, with lighter quarterly checks on fast-changing areas such as access, patching and backups. Audit again after major changes such as a merger, a new core system or a serious incident, and follow any frequency your regulator, contracts or framework set.

An internal audit team, the IT team as a self-assessment, or an external firm. Internal audits find and fix problems early; external audits add independence and are often required by customers, investors or regulators. If IT audits itself, have someone outside the team review the results.

Exports and reports (user lists, device inventory, patch status), samples the auditor picks (leavers, changes, access requests), signed records (access reviews, policy approvals, restore tests), configuration settings and walkthroughs. Dated exports beat screenshots, and an interview answer alone is not evidence.

The basics that prevent common problems: a short security policy, a list of devices and accounts, multi-factor authentication, prompt removal of leavers, encryption on laptops and phones, automatic updates, malware protection, tested backups, a secured router and Wi-Fi, and a plan for a lost device or a breach.

Related

From the blog

The related industry news, interviews, technologies, and resources.