For years, many IT leaders have outlined and executed security and disaster recovery plans as two separate programs. Now as IT evolves in a cloud era, this approach is beginning to cause serious issues for organizations.

The original rationale for separating plans is founded on the idea that security prevents man-made disasters from occurring, with zero focus on recovery. This approach was in no way coordinated with the recovery plans. While the protocols for each might be unique unto themselves, it’s risky to keep security and disaster recovery as separate entities.

Even with the best preventative security technology, man-made disasters can and will happen. We see examples of this time and again as major brands are headlined across the globe from widespread outages or ransomware, leaving CIOs scrambling to regain true IT resilience by combining cybersecurity with disaster recovery.

IT departments have to assume security breaches and cyber attacks will happen. Expecting preventative measures to cover every possible threat is the definition of insanity and gives far too little credit to cyber criminals. And while IT organizations need a thoughtful strategy to prevent security issues, they also need a plan B that equates to no unscheduled downtime.

Incorporating both of these elements in one cohesive IT resilience strategy is becoming increasingly crucial, particularly as organizations transition more of their infrastructure to the cloud.

The risks of running plans separately

Organizations, no matter how large or small, are frequently exposed to ransomware or breaches when they rely solely on security plans. While security technologies help identity and thwart many attacks, inevitably a breach will occur.

According to the Symantec 2017 Internet Security Threat Report, more than 100 new malware families have been introduced to the public this year. This is more than triple from previous years, with a 36 percent increase in ransomware attacks worldwide. Even large organizations such as the pharmaceutical company Merck & Co. and Britain’s WPP, the world’s largest advertising agency, reported being attacked as late as last June.

When organizations such as these, with ample resources, are vulnerable to attacks, it’s clear security plans that detect breaches sooner are not sufficient for all of today's sophisticated cyber attacks.

True IT resilience plans include a “keep-out” security strategy and a recovery plan that guarantees it will take a few minutes at most to return to normal operations. In other words, the first line of defense should always be a modern security tool that work to keep attacks from penetrating vital systems and data. But in the event an attack does penetrate beyond the firewall, it is critical that organizations have a plan that allows for the rapid recovery and resumption of normal business operations.

Three simple steps for a consolidated resiliency plan

Any organization that wants to consolidate security and recovery should consider these three basic steps to prevent intrusions and be ready to respond quickly when a breach occurs.

1. Plan and maintain a consistent update schedule.

It is essential to update and upgrade more frequently. Issuing updates once a month will not suffice. Addressing the threat landscape as categories rather than specific threats can help focus on what kit gets what patches, updates and upgrades at what time. This requires constant vigilance across the organization.

With ransomware, a prevent strategy is a failure to prepare, as it straddles the fence of security and disaster recovery. Having a “DVR-like” capability to “rewind” to the seconds before the encryption occurred and address the specific flaw is a key enabler to a recovery plan.

2. Coordinate testing and supervision, and then practice reducing recovery times.

Modern disaster recovery plan testing can no longer be an annual drill. Frequent and continuous testing must be conducted to guarantee that the disaster recovery plan enables organizations to recover quickly and resume business as usual.

As these two plans converge into a single IT resilience strategy, they should be governed as a single team and staffed by individuals with specific expertise. As both plans target the same objective of uninterrupted IT, it is only logical to merge the group supervising them.

Both teams are needed to create and manage a consolidated security and disaster recovery plan to produce a recovery time objective (RTO) of just a few minutes.

3. Create an alignment to include a three-prong approach.

Security and disaster recovery strategies should broadly align with a three-prong approach to IT resiliency – protect, detect and respond. This method covers all the bases - anti-intrusion prevention, detection and disaster recovery - to neutralize cyber attacks and other business disruptions quickly after the infrastructure has been infiltrated.

Many companies realize that they are not in the "IT Business" and are increasingly adopting cloud-based strategies to implement this approach. Others are leveraging expertise through managed service providers to combine IT security and disaster recovery paradigm as a service.

Consolidation is inevitable

As organizations become more reliant on their data and applications, security and disaster recovery plans must be more coordinated and even converge. It’s becoming increasingly evident for CIOs and CEOs that their IT investments under-perform when hit by a hack, ransomware or a natural disaster. They’re quickly realizing that their operations will be exposed if they don’t correctly integrate disaster recovery and security solutions across a heterogeneous technology stack and test both together in a coordinated and ongoing manner.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access