This month, I am taking a look at the differences between ‘Regulatory Compliance’ and ‘Operational Readiness’ through a series of videos.
|
Regulatory Compliance The efforts to check the boxes before audits – often mandated by an industry (e.g. HIPAA), corporate (SOX) or legal (DOD 5.015.2-STD). |
Operational Readiness The IT efforts to ensure that key IT systems and data are resilient through high availability (HA), disaster recovery (DR) or business continuity (BC) technologies and services. |
|
|
|
For the next four weeks, I’ll take a look at some regulatory mandates and try to glean some pragmatic IT ideas for data protection from them. So come back each Tuesday in April.
Week 1: Overview of Regulatory Compliance vs. Operational Readiness
The rest of the series (blog post edited):
vblog-regulatory-compliance-vs-operational-readiness-part-2-of-4-for-public-companies-and-financial-institutions-through-sarbanes-oxley-sox/index.html">Part 2: Publicly traded companies (Sarbanes-Oxley / SOX) and Financial Institutions (SEC)
vblog-regulatory-compliance-vs-operational-readiness-part-3-of-4-hipaa/index.html">Part 3: Healthcare organizations (HIPAA)
vblog-regulatory-compliance-vs-operational-readiness-part-4-of-4-government-co-op/index.html">Part 4: Federal agencies and contractors (Continuity of Operations / CO-OP)
Thanks for watching.
