- 01
Market
Saudi Arabia
- 02
Written for
CISO, CIO, COO
- 03
Languages
EN · AR
The work
The four working fronts of hands-on breach support
The order flexes with the incident — a spreading ransomware event forces containment forward — but the discipline does not: know the reach, save the evidence, then act.
01
Scope before sweeping
Establish what the intruder touched — accounts, hosts, data stores, persistence — because a containment that misses one foothold does not end the incident; it restarts it with a warier adversary.
- Identity logs
- EDR
02
Preserve what cannot be recreated
Memory captures, disk images and log exports taken with a chain-of-custody record — done early, because these basics cannot be performed retroactively on a rebooted machine.
- Forensic storage
03
Contain without trampling
Isolation, credential resets and egress blocks, sequenced so each action lands after the evidence it would destroy has been captured — and privileged credentials rotate before the intruder learns the response has begun.
- Network controls
- Identity
04
Rebuild from known-good
Compromised systems come back from trusted images and verified backups rather than being cleaned in place, with the intruder's persistence assumed present until disproven, and services restored in the order the business depends on them.
- Golden images
- Backups
Where counsel and the authorities come in
Decisions about notifying regulators, engaging law enforcement and protecting legal privilege belong to your counsel and leadership. Our part is the accurate technical record — timelines, custody logs, scoped impact — those decisions rely on.
Support can join at any front, including after containment, when the questions become rebuild order and hardening.
After containment
Rebuilt is not the same as cleaned
The tempting path after containment is to clean in place: remove the malware the tools can see, patch the entry point, and declare the environment recovered. The problem is what the tools cannot see. A competent intruder plants persistence beyond the obvious — an extra credential, a scheduled task, a modified image, an OAuth grant — precisely so that cleaning removes the visible infection and leaves the way back. So the discipline is to rebuild from known-good: systems restored from trusted images, backups verified against the intrusion timeline before use, every credential the intruder could have reached rotated, and re-entry watched for with detections written from this intrusion's own indicators.
The incident's last deliverable is a backlog, not a report. Every weakness the intrusion used or exposed — the initial access, the flat network segment it crossed, the over-privileged account it rode, the log source that was missing, the detection that stayed silent — goes onto a ranked hardening backlog, ordered by its role in this attack, and worked through in the weeks after recovery. Organisations that skip this step have paid an intrusion's full tuition and kept none of the lesson; the same door is standing open for the next visitor.
The shape of it
From a ransom note to a rebuilt estate, front by front
Illustrative engagement — a composite, not a client case
A mid-size organisation arrives at work to encrypted file servers and a ransom note. Backups exist but nobody knows whether they are clean, the intruder's reach is unknown, and leadership is deciding in the same hour whom to call and what to switch off.
- 01Scoping first, even under pressure: identity and endpoint records establish which accounts and hosts the intruder touched and when the intrusion began, so the response addresses the whole foothold — and so leadership's advisers know what the incident actually is before external notifications are drafted.
- 02Preservation and containment interleaved in the right order: forensic copies of the key systems are taken as isolation proceeds, privileged credentials rotate before service accounts, and the backup platform is checked against the intrusion timeline before anything is restored from it.
- 03The rebuild runs in business-dependency order: systems return from trusted images, restores come only from backups that predate the intrusion or are verified clean, and the estate comes back tier by tier with new detections watching for the intruder's return.
What an engagement like this leaves behind: an operation running on rebuilt systems, a documented technical record its advisers and insurers can rely on, and a ranked hardening backlog the organisation works through in the following months. That is the shape of the work — stated as its shape, not as a promised result.
Our role
What our engineers carry in an incident and what stays with your advisers
- 01
Engineering hands under your incident lead
We work inside your incident command, not above it — scoping, preservation, containment engineering and rebuild work, with every action logged and every finding reported to the person running the response.
- 02
Forensic preservation basics done to a usable standard
Captures, images and exports taken with custody records, so that if your counsel later brings in specialist forensic investigators, they inherit intact evidence rather than the archaeology of a hasty cleanup.
- 03
The rebuild and the backlog
Known-good restoration in dependency order, and the ranked post-incident hardening backlog — so the engagement ends with the estate stronger where this intrusion proved it weak.
Legal exposure, notification duties, ransom decisions and any contact with law enforcement are matters for your counsel and leadership; we keep the technical record accurate and the estate recoverable while those decisions are made, and we say plainly what we do not know yet.
Common questions
What buyers ask
Does isolating infected systems destroy the evidence an investigation needs?+
It can, which is why sequence is the heart of the craft. Powering a machine off destroys its memory — running processes, network connections, keys, sometimes the only trace of a fileless intrusion — while leaving it fully connected lets the attack continue. The middle path usually exists: network isolation that severs the machine from everything while it stays powered, memory captured before any state-destroying action, disk images taken before reimaging. Where the incident forces a harder trade — ransomware actively encrypting is stopped first, full stop — the trade is made knowingly and recorded, so your counsel later knows what evidence exists and why the rest does not.
Can you advise us on whether to pay a ransom?+
We do not make or recommend that decision — it belongs to your leadership with legal counsel, and depending on your sector it may involve regulators or the authorities. What we contribute is the technical ground the decision stands on, established quickly and stated without optimism: whether backups genuinely exist for the affected systems and whether they predate the intrusion, how far the encryption actually reaches, whether there is evidence of data exfiltration alongside it, and what rebuild without the attacker's cooperation would involve. Those facts change the decision materially in both directions, and getting them wrong — usually by trusting a backup nobody has verified — is more dangerous than either answer to the ransom question.
What should happen in the weeks after a breach is contained?+
Three strands, run deliberately rather than left to exhaustion. First, the hardening backlog: every weakness the intrusion used or revealed, ranked by its role in the attack and worked through while the memory is fresh and the budget willing. Second, detection repair: the intrusion demonstrated precisely which activity your monitoring missed, and detections written from its indicators and techniques turn the worst day into permanent coverage. Third, an honest retrospective on the response itself — what slowed the first hours, which authorities were unclear, what evidence was lost — feeding directly into the incident plan and, ideally, a rehearsal. The organisations that emerge stronger treat the incident as tuition already paid; the rest schedule a repeat.
In this cluster
Talk to us — before or during
A direct conversation — ideally before you need it, honestly welcome during — about how engineering hands would slot into your incident, under your lead and alongside your counsel.
Start the conversation
