A useful way to think about it
Check the evidence behind a quiet history
Some important controls work in the background. If nobody reviews their status, a problem may go unnoticed until a service, device or person is needed. A system can appear to work while relying on an unsupported version or an undocumented workaround.
This does not mean that a hidden problem is inevitable. It means that incident history and management evidence answer different questions. One tells you what has happened; the other helps explain what is in place and whether it is still suitable.
- When was a restore last tested, and what did it demonstrate?
- Which user accounts and devices are supported and kept up to date?
- Who has administrator access, and how is supplier access reviewed?
Look for visibility, not just a list of devices
A useful view includes user accounts and devices, infrastructure, cloud services, networks, suppliers and the support processes that connect them. It should show who owns each area and how changes are recorded.
Visibility helps people notice when an account, device or supplier no longer fits the expected setup. Without it, organisations can accumulate technical debt: old systems, undocumented dependencies or manual workarounds that make future changes harder.
Check support, security and recovery evidence
Ask how updates are managed, which devices are still supported and how exceptions are handled. Review sign-in protections, administrator access, supplier access and how unusual activity is reported and investigated.
Then test the assumptions around backup and recovery. A successful backup report does not necessarily show that the right information can be restored in the time the business needs. The recovery plan should connect systems with people and decisions, and recovery steps should be understood by more than one person.
Supported systems
Can you identify operating systems, applications and equipment that are approaching end of support or depend on a specialist workaround?
Security controls
Can someone explain which controls are enabled, who checks them and how exceptions are reviewed?
Recovery readiness
When was a restore last tested, what was learned and who would authorise recovery during an incident?
Documentation
Can a suitably authorised colleague find current system, network, supplier and recovery information when needed?
Make reviews routine and proportionate
A review does not need to turn into a large transformation project. Record what is known, identify uncertainties, assess business impact and agree owners and dates for actions. Some items may simply need monitoring; others may warrant a plan.
A practical IT health check guide describes the areas to examine. If you need a tailored current-state view, an IT health check can help establish a baseline and prioritise what to address.
Questions to ask your team or provider
- What do we rely on that is not included in our current asset or service records?
- Which systems are unsupported, nearing end of support or dependent on one person's knowledge?
- How are security alerts, updates and exceptions reviewed and recorded?
- What evidence shows that important information can be recovered?
- When were our access, supplier and continuity arrangements last reviewed?
- What are the next three practical improvements, and who owns each one?
