Managing data center activism – a practical guide

Why are data centers attracting opposition?

As demand for data centers is increasing and organizations expand AI and cloud computing usage, data center developments are attracting greater scrutiny. There are widening concerns over energy and water use, land development, local impacts, data privacy and the wider effects of AI.

Most opposition takes the form of planning objections, petitions, community campaigns and peaceful protest, which are legitimate forms of stakeholder participation and should not be treated as security threats. However, when activities escalate into intimidation, trespassing, site occupation, infrastructure damage or threats against personnel, organizations involved in developing, operating and supporting data center projects will need to manage the resulting risks.

What do recent data center activism examples tell organizations?

Recent incidents demonstrate the range of activities your organization may need to consider. Protests in Mexico, Malaysia and the U.K. have focused on issues including water consumption, pollution and the environmental or social impacts of AI-enabled infrastructure.

Other reported incidents in Europe and the U.S. have involved attempts to damage construction assets and threats against officials involved in approving data center developments and attacks at properties associated with people connected to project decisions.

These examples identify credible scenarios for security and resilience planning. They also tell organizations involved in delivering data center projects how their exposures extend beyond facility perimeters.

Disruption outside the primary site – whether due to power connections, fiber routes, water and cooling systems, transport links, suppliers or key personnel – can delay construction or interrupt services, even if your facility remains secure.

How can data center activism disrupt across the project lifecycle?

Activism-related disruption can affect your data center project at each stage of its lifecycle:

• Planning – Preliminary documents, supplier's communications and social media may reveal schedules, dependencies or details about key personnel
• Construction – Obstruction or direct action may delay site access and works, while temporary boundaries and exposed equipment can create specific vulnerabilities
• Operating – Facilities may remain physically secure but still experience disruption if an incident affects things like power or cooling system, potentially leading to service interruption, additional costs, contractual exposure and loss of customer confidence

How can organizations prepare for activism-related disruption?

Build a project-specific picture of the threat

Develop a security threat and risk assessment that’s specific to your project, its location and its stage of development. Incorporate groups or individuals active locally, nationally and internationally. What are they trying to achieve; what are their tactics and capabilities and are these evolving?

Your assessment should examine how a project may be perceived, for example how closely it might be associated specifically with AI, environmental concerns or local pressure on energy, water and land. This assessment should extend to contractors, facilities, connecting infrastructure and key personnel, so you can develop credible scenarios, identify vulnerabilities and decide what intelligence you need to monitor.

Indicators over the lifecycle of your project may include changes in activist narratives, mobilization around planning or construction milestones and signs that publicly available information is being used to support disruption.

Protect the operation, not just the site

To protect your people, critical assets and operations effectively, bring together physical security, cyber security, HR and operational teams. If you treat the risks in silos, you can create gaps between what your organization knows, the decisions it makes and the action it takes.

A layered physical security strategy that employs multiple complementary measures to address vulnerabilities, across all points of your operations, will better enable your organization to deter, detect, delay, withstand and respond to threats. Ultimately, your aim is to make it more difficult for activists to disrupt your operations, so put measures in place that discourage opportunistic action, spot suspicious behavior early, slow access to critical areas and give your teams time to respond.

Just as importantly, make sure the right people can assess, escalate and act on alerts quickly, as detection and delay will only help if your people know what to do next.

Address digital exposures in parallel to physical security challenges, considering moves like enhanced cyber security controls, appropriate information-removal requests and awareness training so employees, executives and contractors alike know how to spot threats and act on them.

Plan for disruption and operational recovery

You can't stop every incident from happening. Assume someone will eventually find a way around your controls and build your response and continuity plans around realistic disruption scenarios.

For example, think through how your team would respond if activists accessed a site, occupied equipment, interfered with power or fiber connections or threatened personnel. Decide who makes key decisions, when issues escalate, who communicates with stakeholders and how you'll coordinate with contractors, emergency services, utilities and other external partners.

Look beyond the project itself. A local incident can quickly become an enterprise-wide issue if it attracts media attention or triggers regulatory scrutiny. Your crisis management team should prepare for these possibilities and practice how the business would respond.

Decide which services you need to keep running, what they depend on and what you'll need to restore them if disruption occurs. Think about alternative site access, backup suppliers, spare critical components, tested backup systems, temporary security measures, manual workarounds and clear communications protocols.

Invest where disruption would hurt most, focusing on operations and the areas that would take the longest to recover and the risks your organization can tolerate least.

Test whether insurance reflects credible disruption scenarios

Don't think about insurance only as a source of financial recovery. Depending on your cover, you may also have access to crisis-management, legal, communications, cyber or recovery support. Review what's available, understand how to activate it and make sure your response teams know when and how to use it, incorporating those services into your exercises and response plans.