drj logo
drj logo

Welcome to DRJ

Already registered user? Please login here

Create new account
(it's completely free). Subscribe

x

The Audit After: Compliance and Disaster Recovery

Business Continuity ManagementCyber Resilience & IT Disaster RecoveryData Protection: Backup & RecoveryGovernance: Compliance & Regulatory ReadinessRisk Management & Quantification

179540We all know the story. Calamity, large or small, befalls data center. IT scrambles to save the day by ensuring systems fail over rapidly and functionally. Nowadays, modern IT DR systems are, to a great extent, cloud-based. So the failover happens five seconds later to a data center at the cloud in, say, Houston. After checking a few configurations, updating some DNS tables and ensuring things are copacetic, IT wipes the sweat from their collective brow. Whew.

Crisis averted.

That hero tale never gets old – at least, not as long as the memories of tape-backups and decamping to New Jersey data centers loom large in the mind of IT leadership. That story also has an inevitable – and far less glamorous – sequel called "The Audit."

Many IT organizations are part of companies that are bound by all kinds of compliance. Some is regulatory, some is industry-specific, some governs data types and others cover regions. Regardless of the source of the mandate, fulfilling compliance obligations is not optional.

So, we pick up the tale of our fearless heroes, having vanquished the disaster and returned the workloads back on-premise to the comfort of their own data center. Enter the auditor – just as they are settling down to a sandwich and chips.

Can you show me the audit paperwork for the month of April?

April?

The month you had that disaster. You sent the workloads to the cloud. Houston, I think?

This is where the ominous music begins in the background and the fast-talking and shuffling of proverbial papers on the desk. Because, in fact, our heroes don't have that paperwork.

What is worse, some members of the team did not recognize compliant workloads even existed in the environment. This happens all too often, as highlighted in a recent study by Enterprise Management Associates that uncovered a significant gap in IT's understanding of compliance requirements and compliance-related workloads (see Figure 1).

While 96 percent of the security personnel surveyed reported their organization has compliance-related workloads in the cloud, only 69 percent of IT personnel reported the same. These types of oversights and misunderstandings can expose companies to risks and fines should they fail over to non-compliant cloud.

Schoenbeck-1 opt

Securing the DRaaS
The primary items on the wish list of most disaster-recovery-as-a-service enthusiasts are around recovery times and recovery points, locations, service levels, and ease of implementation. All these are rational, solid requirements. But a big area is missing: security.

What happens to your workloads once they have failed over? Once the dust has settled, the continuity has been achieved, and they hum along in the cloud for days or weeks or months until it's safe to bring them home?

Ideally:

  • All the same security safeguards – or more – would be protecting your workloads in the cloud.
  • Implementing these controls would be seamless as part of the failover since no one has time in an emergency to configure anti-virus.
  • Documentation of all of the security
  • technologies would be built-in and available to you.

Since a large part of most IT audits has to do with verifying the presence, use, and success of security technologies, this eschews a great deal of the struggle. Armed with this data, our heroes would be most of the way to vanquishing the auditor.

Except for one thing: is the cloud itself compliant?

The Web Site Says Compliance
You own the workloads in the cloud. They are yours. No cloud worth it's vapor would tamper with, disable, or destroy your workload. So, as discussed above, the security of your workloads is up to you. The cloud facilitator can embed the tools and provide the reports, but at the end of the day, it's your virus to remove.

The platform, however, is not yours. It's the cloud itself. While the prevailing myth of 2005 was that as a cloud user, you wouldn't have to bother with the underlying cloud – not the brand of server, not the type of hypervisor, and not the security of the data center. Unfortunately, that's patently wrong.

In the domain of compliance, providers can achieve various levels of certification of their platform against varying regulations. While compliance badges feel like they are distributed like candy across the industry, the reality is far more convoluted:

  • Some compliance standards (ISO27001, PCI) require vigorous third-party audit but can be targeted at the entire organization or at a specific location or data center.
    • If the data center is targeted, only that location is compliant and not many of the overarching corporate practices like HR or accounting.
    • If the entire organization is targeted, then it all must comply.
  • Some compliance standards (HIPAA) have no third-party governance organization but can be evaluated in an attestation from a third party.
    • Organizations can claim to comply with HIPAA without having any oversight.
    • Others choose to be evaluated and then have attestation paperwork to prove their alignment with the standard.
  • Some compliance standards are still too hairy to have solid guidelines.

Regardless of whether the standard has a certification, requires an audit, or has any official controls in place, rest assured a badge is available somewhere on the Internet and is often peppered across the websites of cloud providers with reckless abandon.

Beyond the Compliance Badge
The reality is in the eventuality of an actual disaster, followed by an audit, the auditors would want to see some relevant compliance paperwork during that period. The best way to assess whether you could deliver that data is by asking for audit information up-front.

When you ask, "Can you give me some documentation of your XYZ compliance status?" you're likely to get one of three types of answers:

  1. The logo is on our website. That is sufficient.
  2. Here's a signed letter that says we comply, from a third-party auditor.
  3. Here is the full audit report. As you can see, we passed with a 95 percent grade, having mild issues ensuring our HR department sent global emails regarding the snack room policy.

The first response is clearly suspect. The second is sufficient, but vague. It's like hiring someone who got a "pass" on their college education but who will not report their GPA. A 2.5 is a pass and a 4.0 is a pass, but wouldn't you like to know if the guy failed calculus? The third option is obviously the most open stance, but it is also not prevalent.

These responses, however, are a barometer for the ease with which you'll get their part of the audit paperwork in the event of an actual audit. Ideally, the reports that document compliance status are as accessible and on-demand as those on your own workloads.

Assembling the Documents
Returning to our heroes in their disaster movie sequel, we find them happily clicking through their cloud console and printing off a few reams of profoundly boring security and compliance paperwork for the eager auditor in the room.

Just as the moviegoer is considering using this boring lull in the action to refill her popcorn, the auditor innocently asks:

Uh – this file integrity monitoring report on the Nexus System – is it showing an unaddressed error in the system files?

Our heroes, while diligent in their cloud selection, can't even pretend to be well-versed in every page of the output, from months ago, no less.

Does that impact our audit?

It may...

Now, while this drama doesn't begin to parallel the original movie's tense water-seeping-through-the-door-jam climax, the tension is palpable.

Most cloud teams are, at their core, infrastructure experts or developers. They are rarely trained security people and are almost never compliance officers. When auditors raise flags and ask questions, this can be a costly one, as time is usually money with auditors.
Who might know how the cloud reporting should work and how it impacts an audit? Cloud facilitators who play in compliant domains have their own in-house compliance teams, ensuring they pass the aforementioned audits and supporting customers when these esoteric questions come up.

As cloud audits become more commonplace, it's safe to bet the auditors themselves will become more sophisticated consumers of cloud reporting. But in the interim years, having the support of a compliance team during audits can be a game changer. They can interpret the questions of auditors, help craft the answers, or even speak directly to them to clarify reports or data.

A Documented, Peaceful End
Without hesitating, our heroes pick up the phone and call their compliance team, who quickly sort out the misunderstanding. Of course, the issue was addressed and documented further down on page six of the report.

The auditor, satisfied with the documentation during the April disaster, moves on to look into the key-card system on the south door of the data center. Our heroes crack open a can of Diet Coke and breathe a sigh of relief. Fade to black.

Of course, the post-disaster audit movie is one that will never hit the big screen. But, to an organization bound by compliance, it can be as costly and as stressful as the initial disaster. Fines for being out of compliance can be very expensive, and the costs could be much higher if any data breach occurred during the period in question.

Not unlike disaster recovery planning itself, planning for the security and compliance of your workloads once they are in the cloud is very possible in advance of the disaster itself.

Confidence in your business continuity plan is critical when danger strikes, but confidence in the safety of your workloads for the duration of their stay in the cloud enables a smooth, unhurried transition back home.

Schoenbeck Lilac optLilac Schoenbeck has more than 18 years of experience with product strategy, business development, marketing and software engineering in the grid, virtualization, and cloud domains. She is vice president of product management and marketing at iland, a global enterprise cloud hosting provider. Lilac holds an MBA from MIT Sloan School of Management and a computer science degree from Pacific Lutheran University.

Latest News
DRJ HOT ITEMS
Webinar Spotlight
Fetching Upcoming Webinars...
Journal Categories

AI: Automation & Innovation

Business Continuity Management

Crisis Management & Emergency Response

Cyber Resilience & IT Disaster Recovery

Leadership: Culture & Workforce Resilience

Operational Resilience

Risk Management & Quantification

Sector-Specific & Critical Infrastructure Resilience

Supply Chain & Third-Party Resilience

Governance: Compliance & Regulatory Readiness

Incident Management & Response Coordination

Resilience Strategy & Program Maturity

Data Protection: Backup & Recovery

Exercises: Testing & Scenario Planning

Emerging Threats: Geopolitical & Climate Risk

Contact Us

Newsletter

The Journal, right in your inbox.