Colour theme
Book a consultation

Preparing for a useful IT review

Scope an IT review around important business services, available evidence, recovery checks and an assigned action list with clear acceptance criteria.

A person using a keyboard and mouse at a desktop computer on a white desk

An IT review is useful when it answers defined business questions and produces work someone can complete. Before booking one, decide which services matter, what evidence is available and who can sign off on changes.

A review can identify gaps within its agreed scope. It doesn’t certify every system or guarantee that equipment won’t fail afterwards.

Choose the questions before the checklist

Start with the work the business needs to support. Can staff reach essential applications? Who owns administrator access? Can a required record be recovered? What changes are planned?

Select a scope that fits those questions. Include relevant sites, remote users, cloud services and supplier connections. Record areas that won’t be examined and why.

The Cyber Centre’s baseline controls can inform a security review, alongside the operational and contractual needs specific to the business.

Gather existing records safely

Prepare an inventory, support contacts, licences, recent incidents and available configuration records. Identify which documentation is current and where ownership is uncertain.

Give the reviewer their own account or delegated access. Don’t email passwords or recovery codes to make the review easier. State how temporary access will be removed.

Include user reports with dates and business effects. A recurring problem needs more context than a general statement that the computers are slow.

Agree on verification and disruption

Ask which checks are read-only and which involve testing, scanning or a change. Get the owner’s go-ahead before testing a shared service or equipment used in physical operations.

Define a sample and acceptance criteria for important controls. An update policy can be checked against each device’s reported update status; a recovery arrangement can be checked with a sample restore.

Record evidence limitations. A point-in-time review may not observe an intermittent failure or include every device that was offline.

Include recovery and handover

Choose a representative business task and verify the recovery route with IT. Check the resulting record, permissions and the steps needed to resume work. Don’t test using a destructive incident.

Ask a second person with access to find supplier contacts and follow the documentation. Note procedures that depend on one person’s memory or personal account.

Use the monthly IT review for ongoing management after the initial scope has been established. The frequency should fit the business and its changes.

Require a usable findings record

For each finding, ask for the affected service, supporting evidence, business consequence and recommended action. Distinguish a confirmed gap from an untested possibility.

Assign an owner, priority and verification step. Include costs or dependencies as estimates with their assumptions. An item that needs a business decision should say which decision and who makes it.

Schedule follow-through

Agree on how completed actions will be checked and how deferred items remain visible. Revisit accepted exceptions when their conditions change.

Keep the review’s evidence and limits with the action list. Use a new service, major change or unresolved recurring issue as a reason to reassess the relevant scope.


Featured Image Credit