Incident Response Policy
This page explains how a security incident is identified, classified, contained, declared, eradicated, escalated, recovered from and reviewed, so customers and responders know what happens at each stage and what information to provide when reporting a problem.
Plan and overview
This policy is a guide for employees and responders who believe they have found, or are handling, a security incident. The first tasks are to assess how much information is exposed and, where possible, trace where the problem came from. Affected customers are then contacted by the most suitable channel, with follow-up updates as work continues. Executive-level review applies to all suspected or confirmed security incidents, and communication with affected customers is coordinated according to the nature of the incident. The legal entity responsible for this policy is recorded in the owner's internal records and is not stated here as a public fact; readers who need the contracting entity should request it through the official contact channel before relying on this page for contractual purposes. The plan exists to give a clear, organised method for dealing with threats to computers and data, including cases where an intrusion at a third party is traced back to the private network. It sets out the roles and responsibilities of the Security Incident Response Team. Preventive controls, logging and monitoring are intended to detect problems early, but incidents can still occur. The response process below is designed so everyone knows what to do at each stage.
Who responds and how roles work
For immediate help with a security incident, use the security incident contact published on the official contact page. The availability window for that contact is not stated here; check the official contact page for current hours before relying on any response-time expectation. The Security Incident Response Team brings together technical and support staff trained to respond quickly and in an orderly way to hacker attempts and break-ins, service interruptions, breaches of personal information and other events with serious information-security implications. The team may take steps it considers necessary to contain, mitigate or resolve an incident, investigate suspected intrusions promptly and cost-effectively, and report findings to appropriate authorities where necessary. The specific team roles are not listed here as public facts; the owner maintains the current roster internally. Each incident is led by a Senior Engineer, who makes security-related decisions, oversees the response and allocates internal tasks. Incident analysts lead investigation and analysis, supported by other roles as needed. Where an incident spans more than one location, two Senior Engineers may be assigned so accountability and containment or recovery work are not delayed by time differences. Responsibility labels used in the process: Responsible: the party that does the work to achieve the task. Accountable: the party ultimately answerable for correct and thorough completion. Consulted: the party whose opinions are sought, with two-way communication. Informed: the party kept up to date on progress, with one-way communication.
What counts as an incident or breach
Examples that may require team activation include breach of personal information, denial of service or distributed denial of service, and firewall breach or virus outbreak.
A security breach means unauthorised acquisition of data that compromises the security, confidentiality or integrity of personal information maintained by the customer. Good-faith acquisition by an employee or agent for business purposes is not a breach, provided the information is not used or subject to further unauthorised disclosure.
Stages of incident response
- Identification — Checks are performed to decide whether a reported abnormality is an incident. If confirmed, report and error logs are collected, passed to the relevant team for investigation, and measures are taken to fix the incident as early as possible. Every potential incident is classified as Severity 1, Severity 2 or Severity 3 to guide the actions that follow. Severity 1: Functionality of the service is impaired, or some users cannot access or use some functionality. Example: unauthorised system access. Response and fix timing for this level is not stated here; the owner maintains the current commitment internally and it should be confirmed through the official contact channel before being relied on. Severity 2: Incidents with potential monumental impact on use or functionality of the service. Example: password cracking attempt. Response timing for this level is likewise not stated here and should be confirmed through the official contact channel. Severity 3: Low impact to users of the service. Example: firewall scanning. Response timing for this level is also not stated here and should be confirmed through the official contact channel. Classification: The team assigns severity and criticality to each incident and handles the most important incidents first. Classification also groups incident types so metrics can be created and long-term remediation opportunities identified. Severity levels and scores: Informational 0, Action Item 1, Adverse Event 2, Basic Incident 3, Moderate Incident 4, Major Incident 5. Criticality levels and scores: Unknown 1, Low 2, Medium 3, High 4, Critical 5. 2. Containment — The team performs the initial investigation to determine whether an incident has occurred. The checklist includes: collection and review of log files; review of installed or running privileged programs; inspection for system file tampering; sniffer or network monitoring program reports; detection of unauthorised services installed on systems; review of system and network configurations; detection of unusual files; and examination of other hosts. Shut-down note: It may be prudent to shut down any or all systems to stop an attack in real time and/or preserve potential forensic evidence. 3. Declare — Once the coordinator determines an incident has occurred, an incident is declared and the response plan is invoked. The coordinator decides which roles are needed and assigns them. 4. Eradication — The incident is reported to the concerned team with documentation. After reviewing documentation and code, eradication undergoes testing to ensure the incident is no longer in the system and will not recur. 5. Escalation — If a team member is not reachable within the escalation window set by the owner, the potential incident is escalated to the Senior Coordinator. That window is not stated here as a public fact and should be confirmed through the official contact channel. If that coordinator is not reachable, escalation continues to the next level of management or the Chief Executive Officer until someone is reached. The coordinator also decides whether outside parties need to be notified. 6. Recovery — Remediation and recovery aim to cleanse systems of malicious or illicit content and return them to use. Areas considered include patching and hardening system images, reimaging systems, implementing password changes, and improving monitoring and defences. 7. Lessons — After every incident, documentation is reviewed in meetings and standards are set to follow. The lessons learned help avoid repeat incidents and secure systems against past incident patterns.
Reporting checklist
When reporting an incident, include what you observed, when it happened, which systems or accounts are affected, and any logs or evidence you can share. This helps the team classify severity and criticality correctly and start containment without delay. The method used to notify and update affected customers is not stated here as a public fact; the owner maintains the current notification procedure internally and it should be confirmed through the official contact channel before being relied on.
Frequently asked questions
How do I report a security incident?
Use the security incident contact published on the official contact page for immediate help. The availability window for that contact is not stated here; check the official contact page for current hours before relying on any response-time expectation.
What do the severity levels mean?
Severity 1 covers impaired functionality or inability to access or use some functionality, for example unauthorized system access. Severity 2 covers incidents with potential monumental impact on use or functionality, for example a password cracking attempt. Severity 3 covers low impact to users, for example firewall scanning. Response timing for each level is not stated here as a public fact; the owner maintains the current commitment internally and it should be confirmed through the official contact channel before being relied on.
What counts as a security breach?
A security breach is defined as unauthorized acquisition of data that compromises the security, confidentiality or integrity of personal information maintained by the customer. Good-faith acquisition by an employee or agent for business purposes is not a breach, provided the information is not used or subject to further unauthorized disclosure.
| Severity Level | Score |
|---|---|
| Informational | 0 |
| Action Item | 1 |
| Adverse Event | 2 |
| Basic Incident | 3 |
| Moderate Incident | 4 |
| Major Incident | 5 |
| Criticality Level | Score |
|---|---|
| Unknown | 1 |
| Low | 2 |
| Medium | 3 |
| High | 4 |
| Critical | 5 |