Attack-path and dependency review
Map critical services, privileged paths, dependencies, likely disruption scenarios and the controls that constrain spread.
Ransomware resilience
Make recovery a tested capability—not an assumption.
A structured readiness review connecting likely attack paths, identity, segmentation, backups, restore evidence, suppliers and incident roles.
Request a scoping call
Containment and recovery depend on identity, segmentation, protected backups and tested decision routes.
Who this helps
Built around a buying situation.
- Boards and operational risk owners
- IT and security leaders
- SMEs dependent on recoverable digital services
Useful when
The trigger is already visible.
- Backups exist but restore evidence is weak
- Identity or administration paths could enable destructive access
- Incident roles and recovery priorities have not been exercised
The position
Resilience is the ability to contain, recover and learn.
Ransomware readiness is more than endpoint protection. Pegasus connects attack paths to the services the organisation must recover, then reviews identity, privilege, segmentation, configuration, backup isolation, restore evidence, suppliers, communications and decision rights as one resilience system.
01
A defined scope and accountable decision owners
02
Controls matched to the real operating context
03
Evidence that can be reviewed, tested and improved
Scope
What the work includes.
Every engagement is scoped around authority, operating context, available evidence and the decision that must be made.
Backup and recovery assurance
Test whether recovery priorities, protected backups, credentials, configuration and restore evidence support an achievable recovery route.
Tabletop, action and verification
Exercise decision-making, assign improvements and verify the controls most likely to change containment and recovery outcomes.
Method
A controlled route from exposure to evidence.
Decision points, responsibilities and verification stay visible from the start.
Discover
Define the exposure, context, evidence, owners and decision that matters.
Design
Select proportionate controls and make responsibilities and hold points visible.
Implement
Embed the agreed system into the real operating workflow.
Verify
Test whether controls work and whether the evidence supports the conclusion.
Improve
Close actions, learn from exceptions and strengthen the system over time.
Outputs
Evidence designed for use.
Critical-service and recovery dependency map
Ransomware readiness and control-gap report
Backup isolation and restore-test evidence plan
Prioritised containment, recovery and exercise roadmap
Professional boundaries
Precision includes saying what the work does not claim.
- The service reduces exposure and strengthens recoverability; it does not promise that an incident cannot occur.
- Live incident response, forensics, negotiation or legal notification support is separately scoped or referred to an appropriate specialist.
Questions answered
Before you scope the work.
Does this guarantee protection from ransomware?
No. It is a scoped assessment intended to reduce exposure and strengthen recoverability. Threats, systems and dependencies change, so residual risk remains.
Do you test backups?
The scope can review backup architecture, protection and restore evidence, and can define or observe controlled restoration tests. Production changes and destructive testing require separate authorisation and safeguards.
Is this an incident-response retainer?
Not by default. Active incident response, digital forensics, extortion negotiation and legal notification require explicitly agreed specialist capability and response terms.
Authoritative references
External references support context; they do not imply endorsement of Pegasus.
Start the conversation
Bring the exposure. Leave with a controlled route forward.
A first conversation is used to understand context, authority and the decision required—not to force a predetermined package.
Request a scoping call