The Security Craftsman- October
News & Updates from Pref-Tech – October 2026 You Have a Security System. But Is It Really a System? The uncomfortable questions every technology leader should answer before the call they hop...
If you operate a data center, you already understand the importance of physical security. The harder question is whether the integrator supporting that security understands your operation.
There is a big difference between installing access control and cameras and understanding what it takes to work inside a data center environment.
Before choosing a security integrator, I would ask some direct questions.
This is one of the first things I would want to know.
Will the integrator’s own technicians be performing the work, or will much of it be subcontracted?
That matters in any security project. It matters even more in a data center where access, documentation, accountability, and consistency are critical.
Ask:
You should know who is coming into your facility and who is ultimately accountable for their work.
Experience with enterprise security systems does not automatically equal experience with data centers.
Ask the integrator to explain the environments they have actually supported.
More importantly, ask what they learned.
How do they plan work around live operations? How do they communicate when something changes? How do they reduce the chance that security work creates an operational problem somewhere else?
I would rather hear a specific example than a polished answer.
Data centers don’t stay static for very long.
Doors change. Spaces change. Customers change. Technology changes. Security requirements change.
Your integrator should be able to support that without treating every change like a brand-new project.
Ask:
A system can be technically functional and still become difficult to manage if years of changes are poorly documented.
Don’t spend the whole conversation talking about installation.
Ask about 2:00 AM.
Who answers the phone when an access control issue is affecting a critical entrance? What does escalation look like? Does the service team understand the system that was installed?
The real relationship with an integrator starts after commissioning.
You want to understand how they’re going to support the facility when there isn’t a project manager standing onsite.
Physical security systems are connected systems.
Access control servers, cameras, controllers, workstations, credentials, integrations, and networks all introduce things that have to be managed responsibly.
Your security integrator should be comfortable working alongside your cybersecurity and IT teams.
Ask how they approach:
If an integrator treats cybersecurity as somebody else’s problem, that’s worth paying attention to.
Data center operators don’t need an integrator learning their enterprise platform at their expense.
If you’re standardizing on a platform such as Genetec Security Center, Software House C•CURE or another enterprise security platform, ask specifically about the integrator’s depth with that technology.
Don’t stop at certifications.
Ask how many people can actually engineer it, deploy it and troubleshoot it.
There is a difference between having a qualified person somewhere in the company and having enough qualified people to support your operation.
This becomes important very quickly for data center operators with multiple locations.
The question isn’t simply whether an integrator can install another location.
The question is whether location number ten will be built with the same discipline as location number one.
Ask how they maintain standards around:
Consistency makes an enterprise security program much easier to operate.
“Installation complete” and “system ready” aren’t necessarily the same thing.
Ask what commissioning looks like.
Who verifies the system? What gets tested? How are deficiencies documented and corrected? What documentation do you receive when everything is finished?
The customer shouldn’t be the final quality-control process.
This may be the most important question.
The best integrator relationship isn’t one where the integrator says yes to everything.
Sometimes the right answer is:
We wouldn’t recommend doing it that way.
You want a partner willing to tell you when a design creates unnecessary risk, when something won’t scale well, or when you’re about to spend money solving the wrong problem.
That conversation may be uncomfortable.
It’s also where an experienced integrator provides some of its greatest value.
Ultimately, you’re trying to figure out something pretty simple:
Can I trust this company with my environment?
Technology matters. Certifications matter. Price matters.
But you’re also choosing the people who will work inside critical facilities, make changes to systems your teams depend on, and answer the phone when something isn’t working.
Ask enough questions to understand how they operate before you ask them to operate inside your data center.
That’s usually where you’ll find the difference between a security vendor and a security partner.
