IT documentation: why it is decisive in an emergency
As long as everything is running, missing documentation is hardly noticed. It becomes a problem when the IT stops working, access credentials cannot be found and the person responsible cannot be reached. Good IT documentation shortens outages, makes audits easier and makes your business less dependent on individual people.
What happens without documentation
Three situations that occur again and again in practice:
- Lengthy troubleshooting: A program no longer starts. Because nobody knows how it is set up and which systems it is connected to, troubleshooting takes days instead of hours. Orders are left unprocessed.
- Delayed help after attacks: After a security incident, specialists first have to find out which systems exist, which versions are running and where the passwords are kept. Every hour spent searching prolongs the outage.
- Time-consuming audits: For audits, customer enquiries or NIS-2 inspections, information has to be gathered laboriously. The effort is then often greater than ongoing documentation would have been.
What should be documented
Useful IT documentation answers the question: what do we have, how does it fit together and who is allowed to access it? This includes:
- Devices, servers and network components with location and version
- Software, cloud services and interfaces in use
- Permissions: who has access to which systems and data
- Contracts, licences and contact persons at manufacturers and providers
- Backup: what is backed up when and where to, and how restores are tested
On this basis, a risk assessment can be carried out. Only when you know what is there can you judge where the greatest weaknesses lie.
Managing access credentials securely
Passwords stored in Excel lists, on slips of paper or only in the browser are a considerable risk. For businesses, a password manager with central administration, roles and logging is suitable. This way, each person only sees the credentials they need, and access can be cleanly revoked when employees leave.
It is also important where the access credentials are kept. If they are only stored in the same system that can fail, they are not accessible in an emergency. The most important emergency credentials should therefore also be kept in a separate, protected place, for example sealed in a safe.
Documenting automatically instead of maintaining by hand
Documentation in Word or Excel is better than none, but it quickly becomes outdated. A management platform that automatically records new devices and software, captures versions and serial numbers and logs changes is easier. The documentation thus stays up to date without anyone having to add every change manually.
Two levels and three manuals
Splitting the documentation into two parts has proven effective: one for IT management, covering strategy and architecture, and one for day-to-day operations. This way, each person receives the information they need for their task. In addition, three manuals are useful:
- Operations manual: regular tasks, processes and responsibilities
- Risk management: known risks, their assessment and the agreed measures
- IT emergency manual: who does what in an emergency, whom they inform and in which order systems are restored
For companies that fall under NIS-2, emergency preparedness and recovery are explicitly part of the required measures. Well-maintained documentation is the basis for this.
Related service
IT support and Managed Services
Every support engagement begins with complete documentation of your IT. You get an overview of systems, weak points and next steps.