Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

In The Know

In The Know artwork

IT Meets The Door: Making Your Systems Talk to Each Other

Aug 17, 202611 minAudio
ShareXLinkedInFacebookWhatsAppEmail

Episode 4: Making Systems Talk Without Making a Mess One click, one screen, everything talking to everything. It looks beautiful in the demo. Then six months later no one knows which system is in charge, something breaks after an update, and the whole thing is being held together by hope and one heroic integrator who stopped answering calls in 2024. In this episode, Tim and Kaz look at how to connect the right systems in the right way, without turning your environment into an accidental science experiment. The trick isn't asking what can be connected, it's deciding what should be. What we cover: Why integration projects go sideways, starting with the wrong question: "can it integrate?" instead of "what problem are we actually solving?" The one decision that saves the most pain: where does the truth live for identity, access rules, visitors and incidents Hub and spoke over a tangle of point-to-point links, with Command Centre as the hub bringing alarms, access, video and visitors together The integrations people ask for first: video call-up on alarms, and visitor management that cuts double entry and clipboard theatre When security data starts helping the whole building, lift control, occupancy and energy decisions, after-hours responses, perimeter, and APIs into your SOC/SIEM, HR and identity systems Treating it like an architecture project, not magic: clear ownership, data flows, and measuring the outcome, not just that two systems now shake hands, plus two things you can do this week Resources: This episode is part of a six-part blog series on physical security for IT leaders. Read the companion post here. Hosts: Tim Orr, South Island Sales Manager, Gallagher Security Kaz Cairns, South Island Channel Manager, Gallagher Security Music (Intro, Transition, Outro): Original soundtrack by Tim Hunt Instagram: @timofthehunt

Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.

Transcript

From the show. Tap a time to play from there.

Kaz: Tim, did you know, everyone Kaz: loves the integrations and the Kaz: demo? Tim: Of course they do. Tim: One click, one screen. Tim: Everything talking to everything, beautiful. Kaz: Then six months later, no one knows which system is in charge. Kaz: Something breaks after an update and the whole thing is being Kaz: held together by hope. Tim: And one heroic integrator who stopped answering calls in 2024. Kaz: So this part is part four: integrations. Tim: We're looking at how to connect Tim: the right systems in the right Tim: way without turning your

Tim: environment into an accidental Tim: science experiment. Tim: Quick recap: episode one was modern physical security is full Tim: of network devices, so the usual IT disciplines apply. Kaz: And episode two was: the data those systems produce can Kaz: support comfort, safety and space planning as long as you Kaz: apply good guardrails. Tim: And then in episode three, we covered the boring habits that

Tim: fix scary risks: ownership, patching, segmentation, remote Tim: access, backups, runbooks. Kaz: So now we get to the part where everyone gets enthusiastic. Tim: Which is usually where the trouble starts. Kaz: Because someone says, "great, Kaz: let's connect everything to Kaz: everything." Tim: Which sounds efficient right up until it becomes a support Tim: problem with a long tail. Kaz: So let's start with the trap. Kaz: Why do integration projects so often go sideways?

Tim: Usually there's three reasons. Tim: First, people start with the wrong question, asking can it Tim: integrate with something, instead of, what problem are we Tim: actually trying to solve? Kaz: So they start with the product, not the story. Tim: Exactly. Tim: They get excited about the connection before they've Tim: defined the outcome. Kaz: What about when two systems both think they're in charge? Kaz: Nobody decides where the truth lives. Tim: Yeah, that's a problem. Tim: Identity, access levels, visitor status, you name it. Tim: If two systems both think they're authoritative, you get a Tim: lot of confusion fast.

Kaz: And then there's the issue of Kaz: having millions of point to Kaz: point links. Tim: Yeah. One connection's manageable. Tim: Ten connections is maintenance. Tim: Thirty connections is a lifestyle. Kaz: So what's the healthier model here? Tim: Well, I recommend hub and spoke where you can. Tim: In the Gallagher World, Command Centre is designed to be that Tim: hub: bringing together alarms, access control, video events and Tim: visitor workflows and then exposing what you need through Tim: supported interfaces and APIs. Kaz: Great. Kaz: So this is where you'll get Kaz: fewer bespoke links, more Kaz: deliberate architecture.

Kaz: That makes it predictable and way easier to support. Kaz: Alright. Kaz: Well, let's get specific. Kaz: Let's talk about some areas we see constantly. Kaz: I think we should start with the Kaz: one most people picture first, Kaz: video. Tim: Yeah. And that's because it's usually the first integration Tim: people ask for. Tim: The goal is simple. Tim: If something happens at the door Tim: or on the perimeter, the Tim: operator should see the right Tim: video straight away, not have to Tim: go hunting through fifty camera Tim: tiles. Kaz: What does that look like when it's done well?

Tim: Well, usually that means that the live or recorded video is Tim: visible inside the same security client, so the operator is not Tim: bouncing between systems. Tim: If an alarm or an event fires, Tim: the relevant camera pops up Tim: automatically. Kaz: Cool. So, less where's Wally and more instant context. Tim: Exactly. And from an IT point of Tim: view, it still needs the usual Tim: discipline. Tim: User access controls, audit logs, bandwidth and storage Tim: planning and patching the VMs like any other platform. Kaz: So, another one that gets overlooked a bit is visitors. Tim: Yeah. And it matters more than people think because visitors

Tim: are really just temporary identities, and temporary Tim: identities are where chaos likes to sneak in. Kaz: Okay, so what does a good integration actually improve? Tim: Well, for starters, it lets you pre-register visitors and link Tim: them to the right host. Tim: Then when they arrive, you can Tim: issue the right credential with Tim: the right time limits, keep a Tim: proper record of who was Tim: expected and who actually turned Tim: up, and avoid the same details Tim: being typed into two different Tim: systems. Kaz: So you're cutting out double Kaz: entry and making things more Kaz: secure. Tim: Exactly.

Tim: It saves time, reduces mistakes Tim: and makes the front desk Tim: experience smoother. Kaz: So, less printing, less clipboard theater. Tim: And fewer "I'm here to see someone" moments. Kaz: Let me get into the building Kaz: itself and how security can work Kaz: alongside operations. Tim: Yeah, this is where physical security starts adding value Tim: beyond security alone and becomes part of how the building Tim: runs day to day. Kaz: Which is where things can get really useful.

Tim: Very much so. Tim: Done well, these integrations can make the building more Tim: responsive, more efficient and easier to manage. Tim: You can use access events to Tim: support lift control, use Tim: occupancy signals to help with Tim: comfort and energy decisions, Tim: and use alarm states to trigger Tim: sensible after hours building Tim: responses. Kaz: So, this is where security data Kaz: starts helping the wider Kaz: business? Tim: Exactly. Tim: It's not just about protecting the site, it's also about Tim: helping the building behave in smarter, more useful ways. Kaz: And I assume the key is making

Kaz: sure each system plays its part Kaz: properly. Tim: You got it. Tim: You want clear boundaries, clear ownership and clear rules. Tim: So the integration is helpful, predictable and easy to support. Kaz: Then there's the outer layer Kaz: before anyone even gets near the Kaz: building. Tim: Yeah. Perimeter is where you can Tim: buy time, detect earlier, Tim: respond faster. Kaz: So again here, what does a good integration look like? Tim: Well, it should line things up quickly. Tim: If something happens at the perimeter you want the sensor Tim: event, the camera view and the operator response steps to

Tim: appear together straight away. Kaz: So the operator is not trying to piece it together manually while Kaz: the gate is already open. Tim: Right. Tim: These integrations often tie Tim: together gates, barriers, Tim: perimeter sensors, alarms, Tim: camera call ups, and response Tim: workflows. Kaz: And sometimes it's not just security, it's operations, too. Tim: Absolutely. Tim: Vehicle access, delivery Tim: windows, and a bit of discipline Tim: around not opening the gate just Tim: because someone's pressed a Tim: button. Kaz: And then there's the plumbing underneath all of this, which is Kaz: how these systems connect into the wider IT world.

Tim: Yeah, exactly. Tim: This is the category that usually makes IT teams breathe a Tim: bit easier because open interfaces are a lot healthier Tim: than brittle workarounds. Kaz: So let's talk about APIs. Kaz: They always sound really technical. Kaz: In plain English, what are they buying you? Tim: Usually they're how you get the security events into the tools Tim: your organization already uses. Tim: That might mean feeding events into a SOC or SIEM, integrating Tim: with HR or identity systems for joiners and leavers, or to do

Tim: time and attendance. Tim: You could be connecting to incident workflows or building Tim: dashboards that show trends without somebody exporting Tim: spreadsheets every Friday. Kaz: So this is flexibility, but without improvising nonsense? Tim: Exactly. Tim: But it still needs discipline. Tim: An API is not a free for all. Tim: You still want authentication, least privilege, rate limits, Tim: logging, and change control. Kaz: So here's the bit for CIOs Kaz: because it's very easy to get a

Kaz: demo that looks impressive, but Kaz: you can still end up with a Kaz: mess. Tim: Yeah. So the real job here is deciding what should talk, not Tim: just what can. Kaz: So where do you start? Tim: Well, you start with a story, not a product. Tim: Pick one workflow that you really care about. Kaz: Can you give me an example? Tim: Well, something like this. Tim: When an after hours alarm triggers, the Tim: operator immediately sees the right camera, the right door Tim: history, and a clean incident Kaz: So that's an outcome, not a feature list.

Tim: Exactly. Tim: Then write down the systems that are involved. Tim: Your access control, your video Tim: management system, your visitor Tim: management, your building Tim: management systems, HR identity, Tim: SOC tooling, whatever is part of Tim: that story. Kaz: Which is where you'll also spot overlap and double entry. Tim: Right, and then, you make one really important decision. Tim: Where does the truth live? Kaz: Identity? Kaz: Access rules? Kaz: Visitors? Kaz: Incidents? Tim: Yeah. Usually identity lives in HR or your identity provider.

Tim: access rules live in the access Tim: control platform, visitor truth Tim: lives in the visitor management Tim: system and incident truth lives Tim: in your workflow or your SOC Tim: tool. Kaz: So that one decision can save a lot of pain. Tim: Yeah, it really can. Tim: Then where possible, use your Tim: hub and spoke instead of Tim: creating lots of point-to-point Tim: links. Tim: In our world, Command Centre is Tim: the hub and is designed exactly Tim: for that. Kaz: And then the glamorous bit: ownership. Tim: Always. Tim: Who owns the integration Tim: lifecycle, who patches it, who Tim: changes it when one side

Tim: updates? Tim: If the answer is: "we'll work it out later." Tim: Congratulations, you've just gifted future you a problem. Kaz: Alright, well, let's give people something they can actually take Kaz: into a meeting. Kaz: Where should they begin? Tim: Well, start by sorting out your master data. Tim: Decide where people data lives and where space data lives. Kaz: Great. Kaz: So right away you're reducing arguments about which Kaz: spreadsheet is real. Tim: Exactly. Tim: For most organizations, people Tim: data should come from HR and the Tim: identity provider. Tim: Space data should come from some sort of building or space

Tim: register, even if it is basic. Kaz: Okay, what comes next? Tim: Work out which systems should feed the hub and which ones just Tim: need to listen to it. Kaz: Again, got an example? Tim: Sure do. Tim: Access control and alarms might need to feed the hub. Tim: Video might need to integrate into the same operator workflow. Tim: Visitor management might feed temporary identity details and Tim: the SOC or SIEM might just listen for events. Kaz: So then, just pick one use case, not seven. Tim: Yeah, just one.

Tim: Video call up on alarms is a classic. Tim: Visitor management is another. Tim: Pick the one that proves value quickly. Kaz: So treat it like architecture. Tim: Yeah, not magic. Tim: Work with your integrator or Tim: partner like it's an Tim: architecture project. Tim: Ask for diagrams, data flows, Tim: ownership, support expectations Tim: and what happens when versions Tim: change. Kaz: And when it goes live measure Kaz: the result, not just the fact Kaz: that two systems now shake Kaz: hands. Tim: Exactly. Tim: Measure reduced operator handling time, fewer manual

Tim: steps at reception, faster alarm response, cleaner audit trails. Tim: Not just, we connected two things and now we're done. Kaz: Okay, we're back to giving people two things they can Kaz: actually do this week. Tim: Yeah, right. Tim: Well, first, write down your top Tim: three security workflows and Tim: circle the one that would Tim: improve most if systems talk to Tim: each other. Kaz: Second one? Tim: Do a quick source of truth check. Tim: For people, visitors and access rules. Tim: Write down which systems should be authoritative. Tim: If you get stuck, it is probably

Tim: your integration project right Tim: there. Kaz: Love it. Kaz: Nice and practical. Tim: So our next episode is part five: turning access data into Tim: safety and compliance. Tim: We'll talk about audits, investigations, and how to make Tim: reporting less painful. Kaz: Thanks for listening everyone. Kaz: Again, the link to the blog post is in the show notes below. Tim: Catch you next time.

Open the transcript file

Hosts and Guests

Nobody is credited on this episode yet.

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. IT Meets The Door: Phones, Cloud and What Comes Next

    Oct 4, 202612 minAudio

    Episode 6: Phones, Cloud and What Comes Next You're halfway to work when you realise your access card is sitting on the kitchen bench. You're not turning around, you're going to badge in on someone else's card, or talk...

    Credit the people on this episode

  2. IT Meets The Door: Turning Access Data into Safety and Compliance

    Sep 21, 202610 minAudio

    Episode 5: Turning Access Data into Safety and Compliance The fire alarm goes off. Can you say who's on site in under two minutes? And if someone turns up in a restricted area, can you answer the harder question, were...

    Credit the people on this episode

  3. IT Meets The Door: Boring Habits that Fix Scary Risks

    Jul 13, 202610 minAudio

    Episode 3: Boring Habits that Fix Scary Risks The biggest wins in security are rarely exciting, no one ever got a trophy for keeping an asset register updated. But those boring habits are the reason nothing explodes at...

    Credit the people on this episode

  4. IT Meets The Door: Making Friends With Your Security Data

    Jun 15, 20268 minAudio

    Episode 2: Making Friends With Your Security Data Your access control system isn't just opening doors - it's logging a trail of small facts all day long. This person. This place. This time. This action. In this episode,...

    Credit the people on this episode

  5. IT Meets The Door: Why Physical Security is Now Your Job Too

    May 11, 202613 minAudio

    Episode 1: Why Physical Security is Now Your Job Too (And Why That's Not Terrible) If you're a CIO, CISO, or IT leader who's suddenly inherited physical security - welcome. You're not alone, and it's more manageable...

    Credit the people on this episode