Annex A.5.30: ICT readiness for business continuity
The new 27001:2022 control that tripped half the certified companies. What it really takes to clear it.
The new 27001:2022 control that tripped half the certified companies. What it really takes to clear it.
Three things: a DR plan, evidence of drills, change tracking. Everything else is garnish.
52 items grouped into 10 macro-areas. One day of work for the first pass, half a day for subsequent ones.
A backup is necessary but not sufficient for DR. The eight things that have to come after the backup before you can call a system real Disaster Recovery.
How to structure a successful BCDR offering: pricing, SLAs, multi-tenant, runbooks, real margins. Everything an MSP needs to know before selling DR.
BIA usually means endless Excel sheets. Here is a lightweight format that produces useful results in four hours.
AgID, qualifications, ISO 27001 / 27017 / 27018: the updated 2026 map of what is needed to bid in Italian public tenders.
Essential and important sectors, size thresholds and the borderline cases (supply chain, IT providers) that often think they are out of scope.
A step-by-step method to measure a realistic RTO starting from a Business Impact Analysis. Spreadsheet template and the mistakes to avoid.
Why we picked a NanoPi R3S LTS in a CNC case. SoC, real throughput, out-of-band management and why a mini-PC was the wrong call.
Storage pricing is not DR pricing. Hardware, bandwidth, head-count, drills, training: everything missing from your storage vendor's quote.
Everyone has backups. What separates good MSPs is the runbook, the quarterly drill and treating DR as a service, not a product.
What Disaster Recovery is, how it is measured (RTO/RPO), which architectures exist and how to pick the right solution. Sefthy's reference guide.
Cost, RTO, operational complexity, compliance: a head-to-head comparison between cloud DR and a secondary on-prem site. When the second datacentre still makes sense.
SMBs, NIS2, public-tender requirements, cyber insurance: the 2026 picture and three feasible DR tiers for small budgets.
Flipping DNS records under stress is the worst part of L3 DR. With an L2 tunnel you skip it entirely because the IP does not change.
Having DR in a "European" cloud is no longer enough: what changes with NIS2, AgID and Italy's National Strategic Hub, and why an Italian cloud actually matters.
The Annex A controls that directly involve DR and continuity: A.5.30, A.8.13, A.8.14. What auditors actually ask for.
Fourteen questions to ask a cloud provider during selection. Which answers are acceptable, which should stop the deal.
Typical cost (€15-35k year one), concrete sales upside and the two verticals where you cannot bid without certification.
ISO 27001 is the framework. 27017 and 27018 are cloud-specific extensions. Which certification stack you actually need to bid for public-sector contracts.
Legacy apps with hard-coded IPs are the main obstacle to clean DR. An L2 tunnel makes them recoverable without rewriting them.
What a Layer-2 tunnel is, why in DR it matters more than anything else and how this single architectural choice separates a 4-minute RTO from a 4-hour one.
One head office, two branches, one shared DR cloud. How to do it with the Connector without creating IP collisions.
Encryption, tenant isolation, mutual auth: what makes an enterprise-grade L2 tunnel actually secure and the questions to ask vendors.
Real Connector ↔ Sefthy datacentre latency in three setups: fibre, FTTH 2.5G, 5G. What works and what does not.
Layer 3 DR is the historical default, but it brings NAT, DNS reconfiguration and site-to-site VPN. Layer 2 eliminates roughly 70% of that work.
Typical gross margins for managed DR (45-60%), what erodes them over time and the three levers that bring them back above 50% without raising prices.
Article 21 lists ten mandatory areas. We map them to concrete controls already in ISO 27001 and NIST CSF, avoiding duplicate work.
Selling monitoring together with DR raises average revenue per customer by 35% and reduces churn. The three metrics customers want to see every week.
What an MSP risks when a customer gets encrypted. Useful contractual clauses, cyber insurance, operational playbook for the first 24 hours.
The dates that matter (registration, notification, controls) and the actual numbers of fines ACN can issue. What has already happened in 2025-2026.
What NIS2 demands on business continuity and DR. Article 21, Italian deadlines, penalties and a concrete checklist to reach compliance.
NIS2 entities must assess their IT suppliers. What to ask, what to require contractually, what to accept as an attestation.
Concrete differences between essential and important entities: controls, maximum fines, audit frequency. Examples for each category.
Overlaps, differences and the seven areas where a GDPR-compliant company is already halfway to NIS2 readiness.
What to file at each of the three notification deadlines. Early-warning template and the three mistakes that make a filing officially "late".
Day-by-day of a clean DR onboarding: from discovery to first failover drill. Why five days is the right number, not five weeks.
A four-page business continuity policy that passes ISO 27001 audit without questions. Markdown, fully editable.
Three BCDR pricing models (per VM, per GB, per workload), realistic gross margins and the number-one mistake that burns the books at year end.
Five charts, one table, one paragraph of context. How to structure a monthly DR report the IT director can scan in five minutes.
A blended qualitative-quantitative method that yields a usable risk-impact matrix in four hours — not another PDF to file away.
RTO and RPO are the two numbers that define every DR project. We explain what they are, how to calculate them and why in practice they are almost always under-declared.
Mapping the ten Article 21 areas to Sefthy features. What we solve directly, what stays your responsibility.
Availability, RTO, RPO, test windows: how to write a DR SLA that protects both customer and MSP. Template included.
When a 5-minute RPO is enough and when you need sub-second. The difference between interval snapshots, CDP and synchronous replication and what each really costs.
A technical walkthrough (with ARP captures) showing how a Sefthy Connector extends the customer subnet into the Sefthy cloud while preserving original IPs.
Four levels of DR drill (tabletop, walkthrough, partial, full failover), the cadences recommended by NIST and ISO 22301 and an operational checklist.
The six objections you hear from small customers and how to answer them with data, not slides — without racing to the bottom on price.
A site-to-site VPN routes packets between different subnets. An L2 tunnel extends the same subnet. The difference only shows up when something breaks.