Cyber Detector – Cybersecurity, Training & Compliance

Cyber Detector Book a meeting
Menu

100% PARTNER-ONLY ISCP FOR MSPS

Information System Contingency Plan Software For MSPs

CyberLearn helps MSPs structure critical systems, recovery targets, ownership, deadlines, evidence and change history in one connected Information System Contingency Plan workspace.

RTO & RPO   ·   Clear ownership   ·   Deadlines & files   ·   Audit history

ISCPOperational plan
RTORecovery time
RPOData loss
OWNOwnership
LOGAudit trail

FROM STATIC DOCUMENT TO LIVING PLAN

A Clear Workflow From System Mapping To Documented Follow-Up.

Build the operational record step by step and keep every responsibility, target and change visible over time.

01

Map the system

Structure systems, suppliers, dependencies, departments and applicable requirements.

02

Set RTO and RPO

Define recovery time, data-loss tolerance, impact, likelihood and scenario type.

03

Assign ownership

Connect primary, secondary and additional contacts, approvers and test responsibility.

04

Follow up continuously

Use deadlines, files, notifications, escalation, change logs and filtered reporting.

FLEXIBLE ISCP TEMPLATE

Build The Plan Around The Business — Not The Other Way Around.

CyberLearn provides a structured ISCP template, while the organisation decides how the plan should be built. Create the areas that reflect the business, add relevant topics beneath each area and define the detailed rules that guide ownership, risk, recovery and follow-up.

AREA Hosting One business-critical domain
TOPIC Critical Infrastructure Systems, suppliers and dependencies
RULE 01Server 1RTO, RPO and ownership
RULE 02Server 2Recovery plan and escalation
RULE 03Supplier outageCommunication and fallback
Printable IT Contingency PlanChoose what to include and keep an offline copy available.
01

Area → Topic → Rule

Create areas such as Hosting, Brand, Production or Critical Operations. Add topics beneath each area and then define the individual rules required by that part of the business.

02

Guided Template With Operational Detail

Each rule can contain applicable law or standards, associated systems, department, external partners, approval, revision ID, impact, likelihood, RTO, RPO, contacts, recovery references, communication plans and supporting files.

03

Deadline Notifications And Escalation

Set deadlines and review intervals, attach files and enable email notifications. Overdue activities can be directed to the responsible contact or escalated to a secondary contact, helping the plan remain active after it has been created.

04

Print A Practical IT Contingency Plan

Select the areas that should be included and print the emergency response plan. This provides an offline paper copy that can remain accessible when normal systems or online documentation are unavailable.

OPERATIONAL CONTROL

Keep Recovery Responsibilities Visible Before Disruption Happens.

CyberLearn brings the practical contingency record together, so teams can see what must be recovered, who owns the task, when it must be reviewed and what changed.

Contingency Control CentreLIVE PLAN
Recovery target2.5 hRTO
Data tolerance4 hRPO
Review cycle90 dACTIVE
1System
2Risk
3Owner
4Evidence
Done
Recovery plan referenceReviewed by system owner
Open
Communication plan reviewSecondary contact assigned
Due
Supplier dependency testAutomatic escalation enabled

BUILT FOR REPEATABLE MSP DELIVERY

Make Preparedness A Managed Customer Service.

CyberLearn is supplied exclusively through partners. The MSP keeps the customer relationship, agreement and invoice while using the platform to structure, review and develop the customer’s contingency work.

Operate Across Customers

Create a consistent ISCP service model while maintaining customer-specific systems, owners and recovery requirements.

Keep The Customer Relationship

Cyber Detector never sells CyberLearn directly to end customers. The partner leads the relationship and advisory process.

Build Recurring Value

Use reviews, deadlines, evidence and change history to create an ongoing customer dialogue instead of a one-off document.

WHAT IS ISCP SOFTWARE?

Move From A Static Contingency Plan To A Managed Operational Process.

ISCP software turns an Information System Contingency Plan from a static Word or PDF document into a living workspace. Instead of relying on manual updates, teams can structure systems and dependencies, define RTO and RPO targets, assign ownership, attach evidence, set deadlines and document changes over time.

For MSPs, this creates a repeatable service model across customers while each organisation keeps its own systems, recovery requirements and responsibilities. CyberLearn supports that partner-led process without replacing the organisation’s legal, regulatory or standards assessment.

New to the subject? Read our guide to what an Information System Contingency Plan is, explore the broader CyberLearn platform, or review our frequently asked questions.

Static ISCP template
  • Manual updates in Word, Excel or PDF
  • Ownership can become unclear
  • No automatic reminders or escalation
  • Reporting requires manual collection
  • Often becomes a one-off document

FREQUENTLY ASKED QUESTIONS

Information System Contingency Planning For MSPs.

Explore the most common questions about ISCP work, RTO, RPO, partner-led delivery and how CyberLearn supports structured contingency planning.

What is an Information System Contingency Plan?

An ISCP describes how a specific information system should be recovered after disruption. It connects systems, dependencies, recovery priorities, people, communication routes and practical recovery actions.

What is the difference between RTO and RPO?

RTO describes the target time for restoring a system. RPO describes the acceptable amount of data loss measured in time. CyberLearn makes both targets visible at rule level.

Can an MSP manage ISCP work for several customers?

Yes. CyberLearn is designed for partner-led delivery. Each customer can have its own systems, owners, recovery requirements, deadlines, files and change history while the MSP maintains a repeatable service model.

Does CyberLearn guarantee compliance with NIS2, DORA or ISO standards?

No. CyberLearn supports structured preparedness, documentation and follow-up, but it does not guarantee legal or standards compliance. The relevant scope and obligations must always be assessed for the individual organisation.

Can teams document changes and generate reports?

Yes. The platform can record field changes, users and timestamps, and supports filtered reporting for review and customer follow-up.

An ISCP describes how a specific information system should be recovered after disruption. It connects systems, dependencies, recovery priorities, people, communication routes and practical recovery actions.

RTO describes the target time for restoring a system. RPO describes the acceptable amount of data loss measured in time. CyberLearn makes both targets visible at rule level.

Yes. CyberLearn is designed for partner-led delivery. Each customer can have its own systems, owners, recovery requirements, deadlines, files and change history while the MSP maintains a repeatable service model.

No. CyberLearn supports structured preparedness, documentation and follow-up, but it does not guarantee legal or standards compliance. The relevant scope and obligations must always be assessed for the individual organisation.

Yes. The platform can record field changes, users and timestamps, and supports filtered reporting for review and customer follow-up.

Want To See CyberLearn In Practice?

Book a short partner demo and see how MSPs can structure contingency planning, ownership, deadlines and recovery follow-up inside CyberLearn.