Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
A security SLA sets measurable commitments for security services: how fast an alert is triaged, an incident notified, a vulnerability fixed, and what happens when the target is missed.

What Is a Security SLA?
A security service level agreement commits a provider, or an internal team, to measurable performance: notification within so many minutes, containment within so many hours, a critical vulnerability remediated within so many days. Its purpose is to replace a vague expectation of diligence with a number somebody is accountable for.
Badly written, it does the opposite. An SLA promising 99.9% platform availability and a four-hour response to P1 tickets tells you nothing about whether an intrusion would be caught, and gives a provider every incentive to classify incidents downwards.
For detection and response services, four metrics carry most of the weight:
| Metric | Definition | Typical commitment |
|---|---|---|
| Time to detect | Event occurs to alert raised | Often excluded; depends on data sources in scope |
| Time to triage | Alert raised to analyst decision | 15 minutes for critical, 1 hour for high |
| Time to notify | Confirmed incident to customer contact | 15–30 minutes for critical, by phone not email |
| Time to contain | Notification to containment action | 1 hour where the provider holds authority to act |
Time to notify is the clause to negotiate hardest. Under UK GDPR you have 72 hours to report a reportable personal data breach to the ICO from becoming aware of it, and a provider who notifies you on the next business day has consumed a large share of that window before you knew anything had happened.
Containment commitments only mean something if the provider is authorised to act. Agree in advance whether they may isolate a host or disable an account without waiting for approval, and record which systems are excluded from automatic action.
Internal security SLAs usually govern vulnerability management and patching, with deadlines set by severity and exposure:
Two refinements make these workable. First, let exposure override the raw CVSS score: a critical rating on an isolated internal system is less urgent than a high rating on a public API. Second, publish the clock rules, stating when the timer starts, whether it pauses for change freezes, and who can grant an extension. Teams that miss undefined deadlines quietly stop reporting against them.
The operative parts of a security SLA are rarely the headline numbers:
Several rules push specific terms into security contracts. UK GDPR Article 28 requires processors to assist the controller and to notify breaches without undue delay, which an SLA should turn into a stated number of hours. For financial entities, DORA prescribes contractual content for ICT third-party arrangements, including service levels, incident reporting, and exit strategies, while the PRA’s Supervisory Statement SS2/21 sets similar expectations for UK firms. Under the NIS Regulations, operators remain responsible for incident reporting to their competent authority regardless of who detected the incident.
None of those rules lets you transfer accountability, which is the point many contracts miss. The SLA buys you a mechanism for holding a supplier to account; the regulator still holds you.
Review SLA performance quarterly against outcomes rather than volumes. Useful questions: how many genuine incidents were found by the provider versus by you or a third party, what proportion of alerts proved actionable, and how often notification targets were met during out-of-hours periods rather than on average. A purple team exercise is the most direct test available, because it generates known attacker behaviour and measures what the agreement actually delivered.
If you want these commitments met by a team that reports against them transparently, our managed security services operate to defined detection and notification targets.
An SLA is a contractual commitment with consequences for failure, such as service credits. An SLO is an internal target the team aims for, usually stricter than the contractual figure so there is headroom. A KPI is a measure reported to management to show how a function is performing, which may or may not have a target attached. Security SLAs typically sit on top of tighter internal SLOs.
Providers usually resist it, with some justification: detection depends on which log sources were onboarded and what the customer’s environment generates. A reasonable compromise commits to time to triage and time to notify, which the provider fully controls, alongside an agreed list of in-scope data sources and periodic validation that known attack techniques produce an alert.
The contract normally provides service credits, typically a percentage of the monthly fee, plus escalation to a governance forum and, after repeated failures, a right to terminate. Credits rarely cover the real cost of a missed incident, so the valuable clauses are the ones requiring root cause analysis, a remediation plan, and increased reporting until performance recovers.
Article 33 requires a processor to notify the controller without undue delay after becoming aware of a personal data breach, but it sets no fixed number of hours. Since the controller has 72 hours to report to the ICO, contracts should specify a concrete figure, commonly 24 hours or less, so that you retain enough of the window to investigate and decide.
You May Be Interested In These
Cybersecurity Terms
17 November 2026
What Is the Difference Between Nessus and Tenable.io?
Read More
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.