This incident response simulation case study on SAMA CSF forensic evidence describes a live ransomware drill at a regulated financial institution in the Kingdom. The details are anonymized and generalized. The pattern, however, is common: the team contained the attack in time, yet lost volatile memory, left log timestamps unsynchronized and missed an internal reporting deadline. Each gap is a failure of evidence and communication, not of technical containment, and each can be traced to the incident management expectations of the SAMA Cyber Security Framework.
Why containment alone is not a pass
Many institutions judge a drill by one question: was the spread stopped? That matters, but a regulated institution is also expected to understand what happened, prove it, and tell the right people at the right time. SAMA CSF expects incident management to cover detection, response, escalation and lessons learned, and it expects the institution to be able to report to its regulator. A team that isolates hosts quickly but cannot reconstruct the intrusion has solved only part of the problem.
The scenario in outline
The simulation presented a ransomware infection that began on a workstation, moved to file servers and triggered encryption alerts. Participants played their real roles: SOC analysts, the incident lead, IT operations, legal and compliance, and a communications contact. Injects arrived over several hours of exercise time, including a ransom note, a request from management for an update and a prompt to consider notifying the regulator.
The team isolated affected segments, disabled compromised accounts and began recovery planning within the exercise window. By the usual measure, it did well. The debrief then turned to evidence.
Gap one: volatile memory was lost
To contain quickly, analysts powered off several affected machines. Running memory on those machines held information that disk images cannot provide, such as active processes, network connections and, sometimes, encryption material. Once the machines were off, that information was gone.
The link to SAMA CSF is the expectation that incident handling includes the collection and protection of evidence, so that root cause can be established and, where needed, action can be taken. The issue was not carelessness. The playbook said "isolate" but did not say "capture memory first where feasible," and nobody had practiced the order of operations.
What changed: the team rewrote the containment step to separate network isolation from power-off, and assigned a named person to decide when memory capture is worth the delay.
Gap two: log timestamps did not agree
When analysts assembled the timeline, events from the endpoint protection console, the firewall and the directory service did not line up. Some sources used local time, others used UTC, and at least one device had drifted from its time source. A sequence that should have shown the attacker's path became a debate about which clock to trust.
This matters because SAMA CSF expects logging and monitoring that supports investigation and event correlation. Logs that cannot be correlated weaken both the internal investigation and any account given to a regulator or, later, to a court. Unsynchronized time also undermines the credibility of the chain of custody.
What changed: the team added time-source verification to its readiness checks and recorded the time zone and offset of every evidence source at the start of each investigation.
Gap three: the internal reporting deadline was missed
The playbook set an internal deadline for escalating a confirmed incident to senior management and compliance. During the drill, the technical team was absorbed in containment and assumed someone else had made the call. Compliance learned of the incident late, which compressed the time available to prepare any regulatory notification.
SAMA CSF expects defined escalation paths and timely communication with stakeholders and the regulator. The institution's own internal deadline is how that expectation becomes operational. Missing it in a drill is inexpensive. Missing it in a real incident is not.
What changed: the team assigned notification ownership to a named role with a deputy, and set a recurring prompt in the incident lead's checklist rather than relying on memory.
A readiness test you can run
Before planning a simulation, ask your team these questions and note how long the answers take.
- Does your containment playbook say when to capture memory before shutting a machine down, and who decides?
- Can you show that every key log source is synchronized to a trusted time source today?
- Does each evidence item have a recorded handler, time and storage location from the moment of collection?
- Who owns notification to senior management, compliance and the regulator, and who covers if that person is unavailable?
- When did your team last practice these steps together, rather than reading them?
If several answers are uncertain, a live simulation will probably expose the same kinds of gaps described above.
When an organization needs this kind of training
Certain signs suggest it is time to run a live simulation:
- Your playbooks have not been exercised end to end with real roles under time pressure.
- Your last drill measured containment only, not evidence or reporting.
- New analysts or incident leads have joined since the last exercise.
- Recent audit or assessment findings point to incident management or logging.
- Your team has not practiced notifying a regulator within a set window.
What a good outcome looks like
A good outcome is not a flawless drill. It is a team that finds its gaps in a controlled setting and leaves with concrete changes: a playbook that sequences containment and evidence correctly, named owners for notification, and a shared understanding of how roles work under pressure. It also leaves written lessons that leaders can track to closure.
How Incident Response & Digital Forensics Training is run
Our Incident Response & Digital Forensics Training uses live simulations to practice containing an attack, preserving evidence and reporting to regulators on time. The content covers the incident lifecycle and roles under pressure, containment, eradication and recovery steps, evidence preservation and chain of custody, disk, memory and log forensics basics, and regulator and stakeholder notification. It is aligned to SAMA CSF and NCA ECC.
Delivery follows four steps. First, we agree the audience, level, language and dates. Second, we tailor examples and labs to your institution. Third, we deliver instructor-led sessions on site or online, with self-paced lessons where offered. Fourth, we assess with quizzes or practical exercises, then issue certificates with CPE hours.
Training runs from one to five days, on site or online. Deliverables include course materials and simulation scenarios, a tabletop exercise report with lessons learned, a certificate with CPE hours and updated playbook suggestions.
On level, Foundation suits people new to the topic, Intermediate suits those who do the work, and Advanced suits leads and specialists. We can mix levels in one program after a short skills check.
Next step
If your team has never tested memory capture, time synchronization and notification ownership together, a simulation is a sensible place to start. Speak with us about Incident Response & Digital Forensics Training, and we can scope the audience, level and dates around your institution's playbooks and your SAMA CSF obligations.