TOTAL: {[ getCartTotalCost() | currencyFilter ]} Update cart for total shopping_basket Checkout

Privacy Perspectives | Technical Regulation Is Here—Are You Ready or Just Gambling? Related reading: With Data Protection Enforcement Action, What’s in a Fine?


We should expect regulatory systems to develop in sophistication over time, as the regulatory body gains both experience and qualifications.

In some zones of regulation, the regulatory body eventually acquires market prestige and then it becomes both a magnet and a staging post for talent of all types. The best regulators will have subject matter experts at hand, drawn from a wide variety of disciplines, whose talents they can tap when setting priorities, creating guidance and taking action.

Naturally, the intellectual capability of the regulator will compound and increase with each new expert hire and with each new case, and eventually the tipping point is reached when regulation becomes technical. At that stage, the regulator poses a real threat to all entities within the scope of regulation.

Technical regulation is an indicator of regulatory maturity and focus. The evidence that technical regulation is now upon us in the data privacy and cybersecurity fields is mounting up day by day. In a short blog like this, the challenge is not what to include by way of reference and example, but what to leave out.

If data protection regulation in the UK is considered as an example, it's clear from a review of the continuum of regulatory initiatives and enforcement activities over the past 10 years that the momentum towards technical regulation has built up rapidly in the last two. Eight to ten years ago the regulatory focus was neither broad nor deep. People would be warned now and again to check their credit scores held by the Credit Reference Agencies and there was a big push to tackle the “blagging” of personal data by private investigators—that is “data theft,” achieved through pretexting and social engineering—but that didn't concern big business or big government too much.

However, the focus shifted dramatically about seven years ago, when the first wave of “data loss” cases made their way through the UK system. Naturally, the focus started to become more technical in its nature, as issues like data encryption were examined, and broader in its scope and effect, as more parts of the economy were sucked into investigations.

Looking back at my own case notes from that time and comparing them with my work load right now, I'm impressed by just how far the regulatory focus has shifted towards technical matters since 2012. Simply put, the regulatory focus, including investigations, is much more complex and deeper. It is now highly technical and the regulator as investigator is now a completely different animal to the one it was just a few short years ago. The regulator knows the hard questions to ask and where the skeletons are buried. The regulator is technically adept.

The shift towards technical issues is also apparent within the regulatory guidance. App development, big data, BYOD and privacy seals have all featured recently within the regulatory narrative. The subject matter itself is technical, and it is safe to assume that the work below the surface is more technical still. An iceberg metaphor would be apt.

On the talent point, the evidence is equally clear. The UK Information Commissioner's Office has a technical function in house for technology and forensics issues, plus an advisory board containing additional technical expertise. The investigators are technically competent on evidence-gathering, chain of custody and so on. The case for technical regulation continues to build up.

The message for organisations that fall within the scope of privacy and security regulation is simple: Complacent ones, those who assume a superiority over the regulators, are the ones that can become seriously unstuck in an environment of technical regulation. Complacent organisations will not have a narrative on the issues that are being flagged up for attention right now. They will not have built a deep enough defensive shield against probing examination, because they will not have benchmarked themselves against the current regulatory standards and styles. They will not have scenario-planned or war-gamed for a technically focused regulatory investigation.

Indeed they are likely to be hopeless on the basics of regulation—olicies, procedures, governance, etc.—making them like lambs to the slaughter on technical points.

Ending with an old adage, prevention is better than cure. Too right! Sure, you upfront the cost, but it's better to deal with the new realities of privacy and security regulation in the safe and quiet confines allowed by the law for "good" organisations rather than after an incident under the twin spotlights of scrutiny and transparency. Or you can take your chances and place your bets. That's fine if you're that way inclined, but you don't get good odds of success in a technically astute regulatory environment.


If you want to comment on this post, you need to login.