NEWS

us security data compliance lessons from european GDR

What US Security Managers Can Learn from European Data Protection

When I joined Evolution, I came in with 17 years of experience in the US electronic security and life safety sector. I knew access control. I knew surveillance infrastructure. I knew critical environments (including data centres, financial services, pharma, defence). What I did not know, until I started working within a company headquartered in the UK and operating across Europe, was quite how differently the people on the other side of the Atlantic think about the relationship between physical security and data protection.

The gap surprised me. And after spending time working alongside colleagues in the UK, Netherlands, Norway, and Ireland, all operating inside one of the world’s most stringent data protection frameworks, I have come to believe it is a gap that US security managers cannot afford to ignore for much longer.

This is not a compliance lecture. It is a practical observation from someone who now sits in both worlds. Here is what I have learnt, and why it matters for anyone running or specifying a physical security programme in the US today.

The fundamental difference in starting position

Unlike the European Union’s GDPR, the United States does not have a single, comprehensive federal privacy law that applies to all types of data and all US companies. Instead, American law takes a more fragmented approach, with various regulations governing different sectors and types of data.

That fragmentation is the core issue. In Europe, every camera installed on a non-domestic premises, every access control credential enrolled, every piece of footage stored is subject to the same overarching framework. The GDPR governs how personal data of individuals in the EU may be processed and transferred, and applies across sectors and to companies of all sizes. The starting point is not “what does our sector require?”, it is “what are the individual rights of every person whose data this system will touch?”

In the US, we have tended to work in reverse. We start with the security requirement and work backwards to consider data implications, if we consider them at all. That produces secure buildings, but it increasingly produces legal exposure, reputational risk, and in some states, significant financial liability.

As of April 2025, 21 US states have passed comprehensive consumer data privacy laws, creating a complex regulatory landscape for businesses operating across multiple states, and the direction of travel is clear. The proposed American Privacy Rights Act aims to establish a unified, comprehensive data protection law for all US federal states, comparable to the General Data Protection Regulation in Europe. The federal framework is coming. The only question is whether your security programme will be ready when it does.

Your CCTV system is a data management system

This is perhaps the single most important reframe I carried back from working within the European context, and it is the one that lands hardest with US security managers when I share it.

CCTV footage counts as personal data whenever it captures identifiable individuals. Every rule that applies to personal data, lawful basis, purpose limitation, storage limitation, security applies to your cameras.

Under the UK and EU frameworks, you need to identify and document a lawful basis for any use of surveillance systems. It is often difficult to obtain genuine consent from individuals in public spaces, so most organisations rely on legitimate interests, but you must demonstrate that the monitoring is necessary and proportionate, and that this has been formally assessed.

What this means in practice is that every CCTV installation our teams work on in the UK and Europe begins not with a camera count or a hardware specification, but with a documented purpose. Why is this camera here? What is it intended to do? Who can access the footage and under what circumstances? How long will it be retained, and how will it be securely deleted? In 2025, regulators increasingly expect encryption and role-based access controls as part of the appropriate technical and organisational measures for any CCTV system.

Contrast that with many US installations I have encountered, where footage is retained indefinitely on on-site storage, access logs are non-existent, and no-one in the organisation could articulate how they would respond if an employee or visitor requested to see footage of themselves.

That is not a technology failure. It is a governance failure and it is a failure that is increasingly likely to attract legal and regulatory attention. Data Subject Access Requests involving CCTV footage are on the rise in 2025, and failure to comply has led to fines and enforcement notices across the UK and EU. State attorneys general in the US are watching these enforcement patterns closely.

The practical takeaway for US security managers is straightforward. Before your next system installation or renewal, ask three questions: What is the documented lawful basis for this surveillance? Who has access to the footage, and is that access logged? What is the defined retention period, and how is deletion enforced? If you cannot answer those three questions, the system is not fully governed, regardless of how technically sophisticated it is.

Access control data is more sensitive than most organisations treat it

Access control systems generate a continuous, timestamped record of where every enrolled individual has been, when they were there, and how long they stayed. In a modern integrated system, that data can be correlated across dozens of locations, linked to visitor management records, and in some deployments, enriched with video analytics.

European organisations treat this as what it is: highly sensitive personal data with significant privacy implications. The GDPR’s approach imposes accountability, privacy by design, data minimisation, and risk-based security measures on all data controllers. Specific categories of sensitive data require extra protection, often necessitating a Data Protection Impact Assessment.

What I see in the US is that access control data tends to be treated as an operational tool rather than as a privacy asset. The data exists, it accumulates, and it is rarely subject to the same rigour as, say, financial or health records, even though the same individual rights considerations apply.

This matters enormously when biometric access control is in scope. In 2025, more than 20 US states have enacted or proposed biometric privacy laws, making legal compliance a critical concern for security integrators.

Illinois’ Biometric Information Privacy Act requires written consent, clear data retention policies, and secure storage. Violations can result in substantial fines and class-action lawsuits. The case law is accumulating rapidly. 2025 saw a company settle facial recognition litigation for an amount equivalent to a 23% equity stake (approximately $51.75 million) and another technology company settle for $47.5 million over alleged collection of face models from 150,000 individuals.

The Illinois legislature recognised a key principle that European regulators had long held: biometrics are unlike other unique identifiers used to access sensitive information. A social security number, when compromised, can be changed. Biometrics are biologically unique to the individual; once compromised, the individual has no recourse and is at heightened risk for identity theft.

European practice in this area is instructive precisely because it starts from this principle and works forward, rather than deploying the technology and hoping the governance catches up. Any organisation planning a biometric access control deployment like facial recognition, fingerprint, iris etc should be treating that programme with the same rigour as a financial data system. Documented consent, clearly defined retention, role-based access to the biometric template database, and a fully documented Data Protection Impact Assessment before go-live.

The cyber-physical convergence is a data protection story

One of the most significant shifts I have witnessed working within Evolution’s European operations is the recognition that physical security systems are no longer physically bounded. The access control server, the CCTV management platform, the integrated security management software. These are all networked, internet-accessible systems that handle sensitive personal data and that carry cyber vulnerabilities alongside physical ones.

European regulators recognised this connection early. The GDPR imposes accountability, privacy by design, and risk-based security measures on all data controllers, and a CCTV server is a data controller. The practical implication is that any organisation operating connected security systems in the UK or EU is expected to have addressed the cyber exposure of those systems as part of its data protection obligations, not as a separate IT concern.

In the US, the physical security team and the IT security team still operate in silos in many organisations I encounter. The physical security manager specifies and manages the cameras and access control; IT manages the network and cyber posture; and the intersection between the two is often a gap that nobody formally owns.

That gap is where risk lives. An access control system that runs on unpatched firmware, with default credentials and an unmonitored remote access port, is both a physical security liability and a data protection liability. A CCTV management platform that stores footage without encryption and without access logging fails both the security purpose it was installed to serve and the privacy obligations that come with the personal data it holds.

The European approach, which Evolution applies across all of its deployments, is to treat these as a single discipline rather than two separate ones. Every connected security system we design is assessed for its cyber posture alongside its physical capability. That means firmware patch management, role-based access controls, remote access authentication, and documented retention and deletion procedures are part of the specification, not afterthoughts.

Privacy by design is a commercial advantage, not a compliance burden

The framing I most often hear in the US around data protection is one of compliance burden, an obligation imposed from outside that adds cost and complexity to a programme that would otherwise be simpler. I understand that framing. I held it myself before I spent time in an environment where privacy by design is the default.

What changes when you make that shift is not that the work becomes easier, it is that the work becomes more defensible, more trusted, and increasingly, more competitive.

Clients who operate across multiple jurisdictions (the kind of global enterprise clients that Evolution serves across the UK, Europe, and now the US) are subject to GDPR on the European side of their operations. When they evaluate a US security integrator, they are increasingly asking whether that integrator can demonstrate the same governance standards domestically that are required of their European operations. An integrator who cannot answer that question credibly is at a disadvantage.

Beyond enterprise clients, the regulatory environment is tightening regardless of whether a federal framework arrives. As of April 2025, 21 US states have passed comprehensive consumer data privacy laws. The American Privacy Rights Act, if passed, would establish a unified legal framework comparable to the GDPR. The direction is set. The timeline is uncertain but the destination is not.

Organisations that build data-protective practices into their physical security programmes now – documentation, purpose limitation, retention controls, access governance, cyber hygiene – will not need to retrofit them when regulation requires it. They will already be there.

Five questions every US security manager should be asking now

Working within Evolution’s European operational framework has given me a practical lens that I now apply to every US client conversation. These are the five questions I believe every US security manager should be working through in 2026.

  1. Do we have a documented lawful basis for every surveillance system we operate? Not a vague reference to security purposes, a written document that states why the system exists, what it is intended to achieve, and why that purpose justifies the privacy implications of the monitoring.
  2. Who has access to our security data, and is that access logged? CCTV footage, access control records, and visitor management data should all have defined access controls and audit trails. In most US organisations, this governance does not exist.
  3. Do we have a defined and enforced retention policy? Data that is retained beyond the period necessary for its stated purpose is both a privacy liability and, increasingly, a legal one. Every system should have a documented retention schedule and an automated or regularly audited deletion process.
  4. If we use biometric access control, are we compliant with applicable state law in every jurisdiction where we operate? The answer to this question is rarely straightforward given the current patchwork of state legislation. If you operate in Illinois, Texas, Washington, California, or Colorado, the answer needs to be specific and documented.

What this means for Evolution in the US

When I joined Evolution, I inherited thirty years of European operating practice built around exactly these principles. Our teams in the UK, Netherlands, Norway, and Ireland design, install, and maintain physical security systems with data protection embedded from the outset because it is the professional standard.

That same approach is what we bring to every engagement in the United States. Our clients here operate globally, face growing domestic regulation, and increasingly need a security partner who can demonstrate governance standards that match their own risk management requirements. European practice is not a constraint on what we do, it is a differentiator in what we offer.

The gap between where US physical security practice currently sits and where the regulatory and commercial environment is heading is real, and it is closing. The organisations that close it deliberately, on their own terms, will be better positioned than those who close it reactively under legal or regulatory pressure.

I spent seventeen years in this industry before I understood the full picture. I am glad I do now.

Shannon Ritchie is Country Manager — USA at Evolution (Electronic Security Systems) Inc, based in Austin, Texas. Evolution is an employee-owned electronic security and life safety systems integrator with operations across the UK, Netherlands, Norway, Ireland, and the United States. To find out more about Evolution’s US operations, visit evolutionsecurity.com/usa.