Security Incident Response and Reporting

Last updated: 16 October 2026

Version 1.0, approved by Suleman Siddiqui, Advisor to the CEO, on 16 October 2026.

This policy explains how anyone can report a security problem to Sthenos, how we handle a security incident, and when we tell clients and others about it. It sits under our Information Security Policy.

How to report a security concern

If you think you have found a security weakness in a Sthenos system, or you believe information we hold may have been exposed, email contact@sthenostechnologies.com with “Security incident” in the subject line. Please include what you saw, when, and how we can reach you.

We acknowledge every report within one business day.

If you are researching a weakness in our systems, please do not access, change or delete data that is not yours, do not disrupt our services, and give us a reasonable chance to fix the problem before you tell anyone else. We will not pursue anyone who reports a weakness to us in good faith and follows these rules.

Everyone who works for Sthenos must report a suspected incident to the Security Officer straight away. Nobody is ever penalised for reporting something that turns out to be harmless.

What counts as an incident

A security incident is any event that does, or could, compromise the confidentiality, integrity or availability of information or systems we are responsible for. Examples are a lost or stolen device, a phishing email that someone acted on, malware, someone using an account who should not, information sent to the wrong person, or a client system we work on behaving in a way that suggests compromise.

How we respond

The Security Officer leads the response, with the Chief Executive Officer involved in any serious incident. Every incident goes through these steps:

  1. Record. We log the incident with the time it was reported and who reported it.
  2. Assess. We decide how serious it is, using four levels: critical, high, medium and low. The level depends on whose information is affected, how sensitive it is, and whether the problem is still going on.
  3. Contain. We stop the damage from spreading. That can mean disabling accounts, isolating devices, changing passwords and keys, or taking a system offline.
  4. Investigate and fix. We find the root cause, remove it, and restore systems from trusted backups where needed. We keep the evidence.
  5. Notify. We tell the people who need to know (see below).
  6. Learn. After every incident rated medium or higher we write up what happened, why, and what we are changing so it does not happen again.

This process is to be tested at least once a year with a practice exercise.

Telling clients and others

  • Clients. If an incident affects a client’s information or systems, we tell that client without undue delay and in any case within 72 hours of confirming it, unless the contract with that client sets a shorter time, in which case the contract applies. We keep the client updated until the incident is closed.
  • Individuals and regulators. Where the law requires us to tell affected individuals or a regulator, we do so within the time the law sets.
  • Law enforcement. We report criminal activity to the appropriate authorities when it is right to do so.

Records

We keep a record of every incident and how it was handled for at least three years.

Questions

Email contact@sthenostechnologies.com with “Security” in the subject line.

Contact us
Talk to an engineer

We’re happy to answer any questions you may have and help you determine which of our services best fit your needs.

Rates and delivery
What happens next?
1

We schedule a call at your convenience

2

We run a short, bounded discovery, scoped per engagement

3

We give you a costed roadmap before committing to a build

Request a Free Consultation

By submitting this form you agree to our privacy policy.

We aim to reply within one business day

SBA-certified WOSB and EDWOSB, active through March 2029. Rated 5.0 across 43 reviews on Clutch.