Skip to content

Compliance Automation — Trivia & Interesting Facts

Surprising, historical, and little-known facts about compliance automation.


SOC 2 audits were originally designed for accounting firms, not tech companies

SOC 2 (System and Organization Controls 2) evolved from SAS 70, an auditing standard created for accounting and financial services. Its adaptation to tech companies was driven by cloud computing — customers needed assurance that SaaS providers were handling data properly. The standard was never designed for modern software systems, which explains many of its awkward requirements.


Compliance-as-Code was pioneered by Chef with InSpec in 2015

Chef's InSpec framework, launched in 2015, was the first widely adopted tool that expressed compliance rules as executable code. Each compliance control became a test that could be run automatically. This shifted compliance from "filling out spreadsheets annually" to "running tests continuously," though many organizations still rely on spreadsheets.


PCI DSS compliance costs an average of $5.5 million per year

According to a 2022 Ponemon Institute study, achieving and maintaining PCI DSS (Payment Card Industry Data Security Standard) compliance costs large organizations an average of $5.5 million annually. This includes technology, personnel, and audit fees. Automation can reduce this by 40-60%, but many organizations haven't invested in it.


The "evidence collection" phase consumes 60% of audit effort

A 2023 survey of IT compliance teams found that collecting evidence — screenshots, log exports, configuration dumps, policy documents — consumed approximately 60% of the total effort in a compliance audit. Tools like Drata, Vanta, and Tugboat Logic exist specifically to automate this evidence collection.


HIPAA was written in 1996, before cloud computing existed

The Health Insurance Portability and Accountability Act was signed into law in 1996, a decade before AWS launched. Its security requirements were written for an era of physical servers, paper records, and dial-up modems. Mapping HIPAA requirements to modern cloud architectures requires creative interpretation that has spawned an entire consulting industry.


Open Policy Agent handles compliance checks at Netflix, Goldman Sachs, and the DoD

OPA (Open Policy Agent), created by Styra and donated to the CNCF, is used for compliance enforcement at organizations ranging from Netflix to the U.S. Department of Defense. It evaluates policies written in Rego, a purpose-built language, against infrastructure state — turning compliance rules into programmatically enforced guardrails.


FedRAMP authorization takes 12-18 months on average

Achieving FedRAMP (Federal Risk and Authorization Management Program) authorization to sell cloud services to the U.S. government takes 12-18 months and costs $2-5 million. The process is so burdensome that only about 300 cloud products have achieved authorization, creating a significant barrier to entry for government cloud markets.


Compliance drift is detected within hours by modern tools but fixed in weeks

Modern compliance automation tools can detect configuration drift within minutes to hours. However, the average time to remediate a compliance finding is 2-4 weeks because fixes require change approval processes, impact assessments, and scheduled maintenance windows. Detection speed has outpaced remediation speed dramatically.


CIS Benchmarks started as NSA hardening guides

The Center for Internet Security (CIS) Benchmarks — the most widely used compliance baselines for operating systems, cloud platforms, and databases — evolved from hardening guides originally published by the NSA and DISA (Defense Information Systems Agency) in the 1990s. CIS formalized and maintained them as an independent, community-driven effort.


GDPR fines have exceeded 4 billion euros since 2018

Since the General Data Protection Regulation took effect in May 2018, cumulative fines have exceeded 4 billion euros. The largest single fine — 1.2 billion euros against Meta in 2023 — demonstrated that compliance automation isn't just a cost center but a risk mitigation necessity. Organizations that can demonstrate automated compliance controls receive more favorable treatment.