Skip to content
cyberhux

Ransomware in Africa: a practical defence and recovery guide

A scenario-led guide to common access routes, intelligence-led preparation and the recovery decisions that determine how disruptive a ransomware incident becomes.

12 min readcyberhux research team
In this article

Plan for the organisation's real operating context

African organisations are not a single market or maturity level. A regional bank, a hospital group, a logistics operator and a public agency have different dependencies, connectivity constraints and response resources. Ransomware preparation works best when it reflects those realities rather than copying a generic checklist.

Start by identifying the services that must continue and the maximum disruption the organisation can tolerate. A branch network may depend on a central identity platform; a distributor may depend on a single warehouse application; a hospital may rely on third-party diagnostic systems. Recovery priorities should follow those dependencies, not simply the order in which servers appear in an inventory.

Reduce the most useful initial access routes

Ransomware operators and their access suppliers commonly look for exposed remote services, compromised credentials, unpatched internet-facing systems and weaknesses in third-party access. Phishing remains useful because it can provide both credentials and a foothold, but preventing every malicious email is not a realistic strategy on its own.

Focus on controls that limit what one compromised account or device can achieve. Require phishing-resistant authentication for privileged and remote access where feasible, restrict management interfaces, remove unused services and make patching decisions based on exposure and observed exploitation. Monitor for new external assets so an unknown system does not bypass the process.

  • Inventory internet-facing services and assign an accountable owner to each one.
  • Protect remote and privileged access with strong, centrally managed authentication.
  • Prioritise remediation by exposure, exploit activity and potential business impact.
  • Review supplier and support access for shared accounts and unnecessary persistence.

Use threat intelligence to make better decisions

Useful intelligence answers a specific question: which actors target our sector or region, what access methods are being sold or discussed, which vulnerabilities are actively exploited and what signs should our monitoring team look for? A feed of indicators without context rarely changes the organisation's risk.

Combine external reporting with internal evidence from email security, authentication, endpoint alerts and incident cases. When intelligence suggests a relevant campaign, translate it into concrete actions such as checking a particular exposure, tightening a rule or hunting for a behaviour. Record whether the action found anything so future intelligence requirements become sharper.

  • Define intelligence requirements around your sector, technology and critical services.
  • Favour behavioural detection and control improvements over indicator collection alone.
  • Share relevant findings quickly with the teams able to act on them.
  • Review expired indicators and stale requirements rather than accumulating them indefinitely.

Limit the blast radius

Once attackers obtain a foothold, their opportunities depend on privilege, trust and segmentation. A workstation administrator should not automatically control servers; a compromised user account should not administer the backup platform; a remote site should not have unrestricted access to every internal network.

Segmentation does not need to begin as a multi-year transformation. Start with the highest-value boundaries: privileged administration, backups, critical applications, operational environments and third-party connections. Use separate administrative identities and tightly controlled management paths so everyday account compromise does not immediately become an enterprise-wide event.

Prove recovery, not just backup completion

A successful backup job is not evidence that the business can recover. Attackers may target backup consoles, credentials and repositories, while untested restores can fail because of missing dependencies, corrupted data or insufficient capacity. Critical backups need protection from ordinary administrative actions and from the identities used for daily operations.

Run restoration exercises against realistic service objectives. Include identity, network configuration, application dependencies, encryption keys and the people who know how the service works. Measure the time from starting the exercise to delivering a usable service, and document what would happen if the primary data centre or cloud control plane were unavailable.

  • Keep an isolated or immutable copy with separately controlled administrative access.
  • Test full service restoration, including dependencies and operational validation.
  • Agree recovery time and recovery point objectives with service owners.
  • Maintain accessible offline recovery procedures and current emergency contacts.

Manage the first hours of an incident

The first response decisions can preserve options or accidentally destroy evidence. Establish who declares an incident, who can isolate systems, how teams communicate if normal channels are untrusted and when external specialists, legal counsel or insurers should be engaged. Avoid rushed, organisation-wide shutdowns unless the agreed authority and safety implications are clear.

Build a timeline of affected identities, devices and systems while containing the most urgent paths. Preserve relevant logs before retention expires or devices are rebuilt. Communications should distinguish confirmed facts from working assumptions, and staff should receive practical instructions rather than rumours or silence.

  • Activate a known incident command structure and an out-of-band communication channel.
  • Contain affected accounts and network paths while preserving essential evidence.
  • Assess safety, legal, regulatory and customer-notification obligations with the right advisers.
  • Track decisions and timestamps so the response can be reviewed and improved.

Rehearse executive decisions and measure readiness

Severe incidents create business decisions that technical teams cannot make alone: which services to suspend, how to support customers, when to involve authorities and how to communicate uncertainty. Tabletop exercises should put those choices in front of executives with realistic incomplete information and operational pressure.

Measure readiness through observed outcomes. How quickly can the organisation revoke compromised privileged access? Can it restore a priority service within its objective? Do business leaders know their roles? Are supplier contacts current? These measures provide a more useful picture of resilience than the number of alerts collected or documents written.