Security Assurance
Everyone hates downtime.
Everyone is vulnerable to hacks.
What’s your recovery strategy?
Security Assurance gives your business a plan for what happens when something goes wrong — and proves how long it takes to get you back online.
The short answer
Most businesses can tell you they have backups. Very few can tell you how long it takes to actually be back in business — and that second number is the one that costs money while you find it out.
Security Assurance prepares your infrastructure for the bad day, responds when something happens, and measures your recovery so the answer is known in advance rather than discovered during the incident.
- A backup is not a recovery strategy until someone has restored from it and timed it.
- The question is not only "can I get my data back" but "can my business take orders again".
- Security Assurance protects the infrastructure environment — every application running on it is included.
- It does not claim you cannot be hacked. It removes the uncertainty about what happens next.
The outcome
Recovery Readiness
One measurement that answers the question every owner actually has: if it went wrong today, how long would I be down?
Estimated recovery time
How long recovery is currently expected to take, derived from your last measured recovery. An estimate, not a guarantee.
Last verified recovery
What was actually measured, when, and what was proven — along with what was not.
Last rehearsal
Recovery is rehearsed, not assumed. The date is on your dashboard.
Recovery point
Whether the thing you would restore from has been verified, rather than merely written.
Protected applications
Everything discovered running on your infrastructure.
Status
Ready, needs validation, or action required. If your environment changes materially, the estimate is marked stale rather than quietly reused.
If nothing has been measured yet, Recovery Readiness says so. It never shows a number that no evidence supports.
The difference
“I have backups” is not the same as “I know how long it takes”
Backups alone
- A file exists somewhere.
- Nobody has restored from it.
- Nobody knows whether the application comes back, or only the data.
- Nobody knows whether the dependencies, certificates and configuration come back.
- The recovery time is discovered during the emergency.
Recovery Readiness
- The recovery point is verified.
- A real restore has been performed on a clean machine.
- The application was brought back and checked, not just the database.
- Missing dependencies were found in the rehearsal instead of the incident.
- The recovery time is a measurement you already have.
What you see after onboarding
Your Recovery Readiness, on one screen
Recovery Readiness
Estimated time to get the business back online
Example, to show what the dashboard reports. Your numbers come from your own infrastructure.
When something happens
Detect → Contain → Verify → Recover → back in business
Every step is recorded with a time against it, so afterwards you can see exactly what happened and how long each part took.
Detected
A security event is raised against your environment.
Investigated
A suspicion is checked before anything is acted on. A false alarm is a real and expected answer.
Contained
A confirmed problem is shut down at the smallest scope that stops it — an endpoint, not your whole business.
Verified
Containment is independently re-tested. “I fixed it” is not the same as “it is fixed”.
Recovered
If the environment cannot be trusted, it is rebuilt from a verified recovery point and trusted source.
Back in business
Service is restored and the recovery is measured, which updates your Recovery Readiness.
What an incident looks like afterwards
The whole thing, with times against it
Representative example, not a real customer incident. The point is that the outcome is measured rather than described.
How it responds
Four plans, and you control the serious two
Plans A and B run continuously within the scope you agree. Plans C and D touch your environment far more deeply, so they require your explicit authorization every time.
A — Defend
Continuously protects the environment, maintains recovery points, and keeps your Recovery Readiness current. Always on.
B — Respond
Investigates suspicious activity and contains a confirmed threat within the emergency scope you preauthorized. Always on.
C — Verify
Independently checks that containment worked and that a recovery point can be trusted. Requires your authorization.
D — Recover
Treats the environment as untrusted, rebuilds it, and returns your business to service. Requires your authorization.
Extraordinary authority is not standing authority. Nobody at SidRatnam can run Plan C or Plan D on your infrastructure without you releasing it.
One environment
Protect the infrastructure, protect everything on it
Most businesses run more than one thing on one server. Security Assurance is priced and scoped for the environment, not for each application.
One protected environment
Your VPS or infrastructure environment is the unit that is discovered, protected, rehearsed and measured.
Every application included
Whatever discovery finds running on it is covered. Adding another application does not add another subscription.
One recovery strategy
Because when that machine has a bad day, everything on it has the same bad day.
How it actually works
For the people who want the machinery
The recovery authority runs outside your applications, so a compromise inside one of them cannot disable the thing that recovers you.
Extraordinary authority needs three independently held components. No single party — including SidRatnam — can assemble it alone.
You are never handed private cryptographic material to store. There is nothing to copy, leak or misplace.
A recovery point is certified before anything is restored from it, and a point that post-dates the incident is refused.
Every action, and every refusal, is written to an append-only evidence chain. A refusal that is not recorded is indistinguishable from a check that never ran.
Recovery is practised on a clean machine and timed. That is where you find the missing dependency — rather than during the incident.
Straight answers
Questions people actually ask
A managed recovery strategy for your business infrastructure: it prepares for incidents, responds to them, and measures how long recovery takes.
No, and anyone who says otherwise is selling you something. It removes the uncertainty about what happens next.
The event is investigated, a confirmed problem is contained at the smallest scope that stops it, and if the environment cannot be trusted it is rebuilt from a verified recovery point.
That depends on your infrastructure, which is why it is measured rather than quoted. Your estimate comes from your own rehearsed recovery.
A real restore onto a clean machine, timed and checked, without touching your production environment.
No. One protected infrastructure environment is one subscription, and everything running on it is included.
You do. Continuous defence and emergency containment run within the scope you agree; verification and rebuild require your explicit authorization each time.
The recovery path does not depend on it. Recovery material is held off the machine, and the recovery authority operates outside it.
It is independently verified before it returns to service — containment is re-tested rather than taken on trust.
What’s your recovery strategy?
Start with a free business analysis. We look at what you actually run, what would happen to it on a bad day, and what your recovery currently depends on.