01
Discovery Connectors
Lightweight, read-only collection of infrastructure, replication, backup, application and dependency evidence.
◎DEEPER INTO MMT RESILIENCE
Recovery assurance. From design to evidence.
Discover your systems and dependencies, measure recovery objectives, run approved validation exercises and retain the evidence. Explore the architecture and safeguards that make every result traceable.
◎MMT ResilienceARCHITECTURE
DiscoverAssets + dependencies
01MeasureRTO / RPO
02ValidateControlled exercises
03ProveEvidence + reports
04CONTROLLED BY DESIGN
Four layers. One consistent control model.
Separating read-only observation from active tests keeps recovery assurance understandable and auditable. A control plane governs which checks can execute in the target environment.
READ ONLY
02
Validation Agents
Controlled active validation when a recovery exercise requires execution inside an approved target environment.
03
Synthetic Application Probes
Check applications, APIs and business transactions, rather than treating server availability as proof of recovery.
04
Resilience Control Plane
Orchestration, approvals, RTO/RPO measurements, evidence integrity, standards mapping and executive reporting.
DEPLOYMENT MODELS
Your policies. Your deployment choice.
Deploy the control model as a managed service, within a private environment or in a hardened isolated setup, depending on technical and security requirements.
☁CLOUD
MMT Resilience Cloud
A managed control plane with secured connectors and validation orchestration.
Designed forStandard enterprise SaaS adoption
▧PRIVATE
MMT Resilience Private
Deployment in a customer VPC or private cloud, keeping control and data inside the customer boundary.
Designed forRegulated or private cloud environments
▣AIR-GAPPED
On-Prem / Air-Gapped
A hardened appliance or virtual machine for environments that cannot use an external SaaS service.
Designed forSovereign and isolated environments
RECOVERY VALIDATION
Measure actual recovery. Not assumptions.
RTO
Recovery Time Objective
Compare elapsed recovery time observed during exercises against the declared recovery-time target.
Actual time ↔ Target time
RPO
Recovery Point Objective
Validate recovered data recency and replication evidence against the permitted recovery-point target.
Recovered point ↔ Allowed loss
CORE ASSURANCE COVERAGE
✓DR/DC readiness validation
✓Application and service recovery
✓Replication and RPO assurance
✓Backup and restore validation
✓Disaster recovery site readiness
✓Actual RTO measurement
✓Dependency validation
✓Recovery exercise orchestration
✓Evidence and regulatory reporting support
Regulatory note: Standards- and SAMA-aligned validation support does not mean regulator certification or automatic compliance. Applicability must be assessed for each organization.
SAFETY BY DEFAULT
Intrusive testing stays off.
Optional stress and failure-injection tests are distinct from normal read-only discovery. They require explicit customer authorization, approved scope and change control before activation.
CPU / RAM pressure testingDisabled by default
Storage stress testingDisabled by default
Bandwidth, latency and packet-loss simulationDisabled by default
Synthetic high-user loadDisabled by default
Chaos and failure injectionDisabled by default
MEASUREMENT TO PROOF
Turn each exercise into useful evidence.
MMT ResilienceILLUSTRATIVE
Recovery evidence record
ApplicationBusiness service
ValidationControlled exercise
RTO / RPOMeasured during test
EvidenceTimestamp + integrity record
ReviewApproval workflow
Beyond uptime checks
Check transactions, service dependencies and recovered business capability—not merely whether a server responds. Each validated exercise can form a baseline for the next assurance cycle.
✓
Measured recoveryCompare what actually recovered and how long the recovery took.
▤
Traceable evidenceRetain exercise timelines, timestamps and integrity records.
▧
Application confidenceCheck application transactions, APIs and underlying dependencies.
↻
Repeatable assuranceRepeat controlled exercises and compare readiness over time.
◇
Deployment choiceUse deployment patterns that match customer security policies.
MMT Resilience
Recovery should be tested. Not assumed.
Define the scope, validate your recovery objectives, and build an evidence-backed resilience baseline.