Emergency management for security alerts: how your IT service provider should respond
Anyone who buys in IT services has to place a great deal of trust in the provider. Whether your service provider acts quickly and correctly in an emergency is difficult to judge from the outside. This article describes how good emergency management works for security alerts. You can use it as a benchmark and discuss it with your service provider.
Why speed is decisive
As soon as a security vulnerability becomes known, a race begins. Attackers search automatically for systems on which the relevant update is still missing. The time between the publication of a vulnerability and the first attacks has become significantly shorter in recent years. For critical vulnerabilities in firewalls, VPN access points or email servers, it is sometimes only days or hours.
A typical scenario
The management software of a hardware manufacturer reports on the computers of a company: a driver or firmware update must be installed urgently, otherwise protective mechanisms can be bypassed. In everyday work, often nothing happens as a result. The message appears on a screen, is perceived as a nuisance and dismissed, and the service provider never finds out about it.
The process step by step
- Capture automatically: The alert does not just reach the user, but goes directly to the service provider via the monitoring.
- Assess: The severity is classified on the basis of recognised sources, such as the warnings of the BSI, the German Federal Office for Information Security, and the information provided by the manufacturer. The CVSS scale from 0 to 10 is commonly used: scores of 7 and above are considered high, 9 and above critical.
- Create a ticket and inform: The task is recorded, and you are informed about the alert and the next steps.
- Immediate measures: For high and critical vulnerabilities, action is taken immediately, even before an update is available, for example by temporarily disabling affected functions or restricting access.
- Fix: The update is installed, and it is checked whether it is effective on all affected systems.
- Document: What was done and when is recorded. This means the process can be traced later, for example during an audit.
Less critical vulnerabilities are closed as part of regular update planning. What matters is that every alert is captured and assessed and none gets lost in day-to-day business.
More than quick updates
Dealing with security alerts is one part of emergency management. It also includes preparing for the event that something happens nonetheless: an emergency manual with responsibilities and telephone numbers, tested backups and a plan for the order in which systems are restored. BSI Standard 200-4 on business continuity management provides guidance on this. For companies that fall under NIS-2, such emergency management is mandatory.
Questions for your service provider
- How do you find out about security alerts on our devices and servers?
- What criteria do you use to assess how urgent a vulnerability is?
- How quickly do you act on critical vulnerabilities, and how are we informed?
- Where can we look up which updates were installed and when?
- Is there an emergency plan for us, and when was it last reviewed?
It is a warning sign if your employees are repeatedly asked to install updates themselves. This task should be taken on by your service provider.
Related service
Server Management
You get servers that are continuously monitored and maintained. Security updates are installed according to plan and documented.