Skip to content
AS

Ransomware Readiness

Ransomware readiness asks a simple question: if it happened tonight, what would be lost and how long would recovery take? AS answers it honestly and helps close the gaps.

When you need this

  • Unsure whether backups would survive an attack
  • Exposed remote access or unpatched edge devices
  • No incident plan or contacts prepared
  • Insurance questionnaire needs evidence
  • Leadership asking for assurance

What we do

Entry point review

Remote access, email, patching and identity controls checked against common attack paths.

Blast-radius review

How far an attacker could move: segmentation, admin rights, backup access.

Backup survivability

Whether backups are isolated, immutable and restorable.

Response preparation

Contacts, decisions and first steps documented before they're needed.

How it works

  1. Step 1

    Protect

    Reduce the attack surface: hardening, patching, access controls, endpoint protection and isolated backups.

  2. Step 2

    Detect

    Monitoring and alerting so suspicious activity is noticed early, not after encryption.

  3. Step 3

    Respond

    A prepared, structured response that contains the incident and preserves evidence.

  4. Step 4

    Recover

    Verified, isolated backups and a tested plan so the business can come back quickly.

What affects the outcome

Outcomes are never guaranteed. Every case is assessed on its own condition, and we tell you what is realistic before you commit.

  • No control eliminates risk entirely; the aim is to reduce likelihood and impact
  • Existing patch levels, configurations and legacy systems that cannot be changed quickly
  • User behaviour and the strength of identity and access controls
  • Visibility: what is logged and monitored today
  • Isolation and verification of backups, which determine recoverability after an incident

Frequently asked questions

Can you make us immune to ransomware?

No one can. Readiness reduces the likelihood, limits the damage and makes recovery faster — which is what determines whether an incident is a bad week or a business-ending event.

Request assessmentEmergency