Cloud & Telecom Security

This is an old topic, but it’s not an easy one. For everyday, IT managers are facing the questions : how to make sure the business continuity? what’s the proper redundancy to balance between continuity and cost? You know the redundancy and complexity themselves can introduce additional potential failures and issues. So redundancy is not the silve bullet for continuity, not mentioning the cost.

I have been working on this for a while. I don’t have budget to have a consulting project to help me to get a comprehensive and holistic picture. I have to do it by myself.

As the first step, I am considering the mothodology. The below diagram is the draft in my brain.

1 Prioritize
Prioritize the applications and users and user communities
identify the critical path
Prioritize the paths and elements
Build profiles of top critical applications
2 Critical Path
Find the critical path and dependency, both logically and physically.
3 Identify Risks
Identify potential risks and failure scenarios
Build business cases
4 Redundancy Check
P1: The least things that make the core business alive.
e.g..fibers along the critical path
5 Fix the Gaps
Fix the gaps according to prioritization
6 Drill
Create scenarios and testing plan