Logical security for data centers: a comprehensive guide for CIOs
Your data center may have the thickest walls on the market, the most precise cameras, and biometric access control worthy of a spy movie. If the system controlling the air conditioning runs on a default password, all of that hardware is worth very little.
In our physical security guide, we detailed everything that protects a data center in the physical world: badges, cages, generators, fire zones. This second installment tackles the other half of the equation: logical security everything that protects the operator's own digital infrastructure.
Because a data center is more than just a building. It is also a management network, supervision tools, industrial controllers, customer portals, and hundreds of connected sensors. And each of these elements is a potential entry point for an attacker.
The context leaves no room for doubt. In 2025, France recorded over 17,500 cyberattacks, a 4% increase over 2024. ANSSI handled 4,386 security events in 2024 alone, including 1,361 qualified incidents. DDoS attacks surged to unprecedented levels, with a global record of 31.4 Tbps in late 2025. As critical infrastructure, data centers are on the front line.
This article gives you the keys to understanding what your data center operator must implement in terms of logical security, and most importantly, the right questions to ask.
I. The fundamentals of operator logical security
1. Securing data center management systems
Behind every data center lies a set of critical software systems that control the infrastructure: the DCIM (Data Center Infrastructure Management) for monitoring racks, power, and cooling; the BMS (Building Management System) for managing air conditioning, fire detection, and access; and often a customer portal for remote operations.
These systems are the brain of the data center. If an attacker takes control, they can shut down air conditioning in midsummer, disable fire alarms, or open physical access remotely. This is not science fiction: in 2021, attackers took control of BAS (Building Automation Systems) in an office complex in Germany, locking lighting, motion detection, and other systems, then changing passwords to prevent recovery. In 2024, an attack targeting connected surveillance cameras compromised the main network of a data center in Asia.
Key point: The problem is often structural. Many BMS systems rely on legacy industrial protocols BACnet, Modbus, LonWorks that include neither encryption nor authentication. According to a Claroty study published in 2025, 75% of organizations with BMS systems are affected by actively exploited vulnerabilities. Among them, 51% combine these vulnerabilities with an unsecured internet connection.
2. Infrastructure network segmentation
If physical security relies on compartmentalization cages, zones, airlocks logical security relies on network segmentation. The principle is identical: preventing a breach in one zone from spreading across the entire infrastructure.
A well-designed data center separates at least three distinct networks:
The building management network (BMS, sensors, controllers, video surveillance)
The internal administration network (DCIM, monitoring, operator IT tools)
The customer network (tenant traffic, cross-connects, telecom operator access)
This separation is not a luxury. It is the barrier that prevents a compromised IoT temperature sensor from serving as a bridge to the administration portal, or a neighboring rack from "seeing" your network traffic. Technologies used include VLANs (Virtual LANs) for logical isolation, VRFs (Virtual Routing and Forwarding) for separate routing, and micro-segmentation for granular flow control between zones.
Key point: The OT (Operational Technology) risk is particularly underestimated in data centers. Air conditioning equipment, UPS units, generators all these industrial systems are now connected for monitoring. But they were not designed with cybersecurity in mind. Without strict segmentation, they become a considerable attack surface.
3. Logical access control for operator systems
In our physical security guide, we emphasized badge, biometric, and PIN access control. Its logical equivalent is Identity and Access Management (IAM) applied to operator personnel.
The fundamental question is the same: who among the operator's staff has access to what? A maintenance technician does not need access to network monitoring tools. A network administrator does not need to modify air conditioning settings. This is the principle of least privilege: each employee is given only the access strictly necessary for their role.
The topic of privileged accounts (PAM, Privileged Access Management) is critical. Administrator accounts with full access are a prime target. A mature operator uses digital vaults to store these credentials, with automatic password rotation and video recording of sensitive administration sessions.
Key question: Access revocation must be immediate. When a technician leaves the company or a contractor completes their assignment, their logical access must be disabled in real time just like recovering a physical badge. A 48-hour delay in revocation is a window of opportunity for an attacker.
II. Protecting the data center's network infrastructure
4. Securing network services offered to customers
A data center does not just provide physical space. It also offers critical network services: cross-connects between customers, access to the Meet-Me Room (where telecom operator fibers converge), and sometimes shared firewalls or IP transit services.
The Meet-Me Room is the nerve center of the data center on the connectivity side. All interconnections are concentrated there. Its logical security is just as important as its physical security: traffic monitoring, anomaly detection, strict control of authorized connections.
Key point: Network-level isolation between customers is fundamental in colocation. Your neighboring rack should not be able to intercept or even "see" your traffic. Mechanisms such as 802.1Q (VLAN tagging), VRF, and Private VLANs ensure this isolation provided they are properly configured and regularly audited.
5. DDoS protection at infrastructure level
Distributed denial-of-service (DDoS) attacks have reached unimaginable levels. In 2025, Cloudflare blocked a record attack of 31.4 Tbps the equivalent of millions of 4K video streams sent simultaneously to a single target. In 2025 alone, network DDoS attacks tripled compared to 2024. Europe is particularly exposed, accounting for 48.4% of attacks claimed by hacktivist groups according to the Radware 2026 report.
The problem for a data center: a massive DDoS attack targeting a single customer can saturate the shared network infrastructure and impact all other tenants. It is like a neighbor in an apartment building receiving so much junk mail that the shared mailbox overflows and blocks the postman for everyone.
An operator deploys multiple layers of protection:
Scrubbing centers: traffic cleaning centers that filter malicious flows before they reach the infrastructure
Targeted black-holing: redirecting traffic to a "black hole" to protect the rest of the infrastructure, as a last resort
Anti-DDoS partnerships: with specialized providers (Cloudflare, Akamai, Arbor, ...)
Oversized capacity: bandwidth calibrated to absorb peaks of both legitimate and malicious traffic
6. Operator infrastructure vulnerability management
A data center relies on dozens of network devices (switches, routers, firewalls), monitoring systems, and industrial controllers. Each of these devices may contain vulnerabilities and each unpatched vulnerability is an open door.
ANSSI confirms this in its 2024 Cyber Threat Overview: the exploitation of vulnerabilities on edge devices (firewalls, VPNs, gateways) was one of the most commonly used intrusion vectors. Data center network equipment falls squarely into this category.
Patch management the process of regularly updating equipment is a sensitive issue for operators. Patching a core switch in production risks a brief outage. Not patching it leaves a known vulnerability open. The balance between availability and security is delicate.
Key point: The specific problem with OT equipment (air conditioning, UPS, access controllers) is that they often cannot be patched as easily as a Linux server. Firmware updates are rare, support cycles are long, and some manufacturers discontinue support after a few years. A rigorous operator compensates through network isolation of these devices and enhanced monitoring of their behavior.
III. Monitoring, detection, and threat response
7. SOC and infrastructure monitoring
In the physical world, 24/7 video surveillance is standard. Its logical equivalent is the SOC (Security Operations Center): a team and tools dedicated to real-time monitoring of the digital infrastructure.
A mature SOC in a data center relies on several technology components:
SIEM (Security Information and Event Management): centralized correlation of security events
IDS/IPS (Intrusion Detection/Prevention System): detection and blocking of suspicious activity on the network
NDR (Network Detection and Response): behavioral analysis of network traffic to detect anomalies
The major benefit of a SOC in a data center is the correlation between physical and logical events. Remember the example from our physical security article: three failed badge attempts at 3 a.m. on your cage. Now add a suspicious connection attempt on the management network at the same time. In isolation, each event is unremarkable. Correlated, they form a clear attack pattern.
Best practice: This physical-logical convergence is what distinguishes a data center SOC from a standard SOC. Physical security and cybersecurity teams must not work in silos. The badge alert + the network alert must appear on the same screen, analyzed by the same people.
8. Operator-side logging and traceability
If video recordings are proof of what happens physically in a data center, logs are proof of what happens digitally. In the event of an incident, they are your only objective evidence for reconstructing the timeline of events.
An operator must maintain detailed logs covering:
Access to administration systems (who connected, when, from where, to do what)
Network events on common infrastructure (connections, failed attempts, traffic anomalies)
Configuration changes on equipment (firewall rule change, VLAN addition, firmware update)
Security events (IDS alerts, intrusion attempts, privilege escalations)
Key point: Retention period is a negotiable but crucial point. A minimum of 90 days is recommended, 12 months for sensitive environments. Beyond duration, it is log integrity that matters: they must be protected against tampering (cryptographic chaining, certified timestamps, immutable storage). An attacker who compromises a system will always try to cover their tracks.
9. Cyber incident management and response plan
What happens when the operator detects a breach on its own systems? This is the exact mirror of the crisis communication discussed in our physical security article but on the cyber side.
An incident response plan (IRP Incident Response Plan) must clearly define:
Internal escalation procedures (who is alerted, in what order, at what priority level)
Notification deadlines for affected customers (a contractual commitment, not goodwill)
The level of detail communicated (nature of the incident, affected scope, measures taken, recommendations)
Coordination with competent authorities (ANSSI, CNIL if personal data is involved)
NIS 2: new obligations
The NIS 2 directive, currently being transposed into French law via the "Resilience Act," significantly strengthens obligations. Data center service providers are explicitly classified as essential entities in highly critical sectors.
- • Incident notification within 24 hours for the initial alert
- • 72 hours for the interim report
- • Penalties of up to €10 million or 2% of global turnover
Logical DRP/BCP complements the physical DRP/BCP already discussed in our previous article. On the logical side, this includes backups and replication of critical configurations, the definition of an RPO (Recovery Point Objective how much data can you afford to lose) and an RTO (Recovery Time Objective how quickly does the operator commit to restoring service), and regular cyber incident simulation exercises.
IV. Compliance and logical governance
10. Certifications and qualifications: the logical dimension
Our physical security article already detailed ISO 27001, SOC 2, PCI-DSS certifications, and Tier classifications. But these certifications also have a logical dimension that must be examined closely. And two specifically French qualifications deserve particular attention.
ISO 27001: logical controls
ISO 27001 covers the entire information security management system, including logical aspects: access management, encryption, network security, incident management, business continuity. Verify that the certified scope includes the operator's IT systems (DCIM, network, customer portal) and not just the building.
SOC 2 Type II: confidentiality and integrity
The SOC 2 Type II report evaluates internal controls over 12 months. The confidentiality and processing integrity criteria are directly related to logical security: how the operator protects customer data, and how they ensure that processes are not tampered with.
SecNumCloud: the sovereign qualification
The SecNumCloud qualification, issued by ANSSI, has become the French benchmark for cloud service security. Based on ISO 27001 but significantly more prescriptive, it covers encryption, key management, network isolation, access control, and full traceability of actions. Version 3.2, currently in force, also imposes sovereignty requirements: data must remain in France, operated by European personnel.
In 2025, the SecNumCloud landscape expanded considerably. OVHcloud obtained the qualification for its Bare Metal Pod platform, Orange Business for Cloud Avenue SecNum deployed from its Grenoble data center, and S3NS (Thales-Google Cloud alliance) for its PREMI3NS offering. Driven by the French government's "Cloud au centre" doctrine and the upcoming NIS 2 directive, SecNumCloud is becoming a mandatory selection criterion for organizations handling sensitive data.
HDS: health data hosting
The HDS (Hébergeur de Données de Santé / Health Data Host) certification, issued by COFRAC-accredited bodies, is mandatory for any operator hosting personal health data in France. It imposes specific requirements for encryption, access control, traceability, and incident management. If your business involves the healthcare sector, this certification is non-negotiable.
11. The shared responsibility model
This is arguably the most important and most misunderstood concept in colocation security. Who is responsible for what? The answer is not always obvious, and the gray areas are numerous.
The general rule is simple in theory:
The operator secures: the building, power supply, cooling, shared network infrastructure, management tools, physical and logical access within its scope
The customer secures: their servers, operating systems, applications, data, and user access
But in practice, boundaries blur. Who is responsible for the security of a cross-connect between two customers? The online portal you use to manage your operations? A shared firewall offered as an option? These gray areas are where vulnerabilities emerge.
Best practice: Demand a clear, formalized responsibility matrix, ideally integrated into the contract. It should cover every infrastructure component: network, power, cooling, physical security, logical security, backup. For each component: who is responsible for implementation, operation, and security updates?
Conclusion: data center security is a whole
Logical security is not a separate topic. It is the other side of the same coin. A data center with impregnable walls but vulnerable management systems is a fortress with a wide-open back door.
The regulatory landscape is accelerating this awareness. The NIS 2 directive now classifies data centers as essential entities, with strengthened security obligations and significant penalties. The SecNumCloud qualification is establishing itself as the benchmark for organizations handling sensitive data. The era when logical security was a checkbox is over.
For CIOs, this means one thing: don't stop at cages and cameras. During your audits or procurement processes, ask logical questions with the same rigor as physical ones. Network segmentation, vulnerability management, SOC monitoring, log traceability each of these topics deserves a precise and documented answer.
This is precisely Datalok's mission.
Our platform centralizes data center security information physical and logical so you can objectively compare protection levels, identify operators that meet your requirements, and make informed decisions. In just a few minutes, you move from intuition to data. Visit the Marketplace and find the perfect colocation space.
To go further
Did you enjoy this article? Discover these additional resources to deepen your thinking on data center security and optimization: