IT Meets The Door: Making Friends With Your Security Data
8 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, Tim and Kaz show you how to turn those everyday events into useful stories for operations, safety, and cost control. No fancy analytics platform required. What we cover: Why access control logs are basically an analytics platform you already own Three starter stories you can build with data you already have Using occupancy data to reduce wasted energy (the one that gets the CFO's attention) How access data can support safer, smarter evacuations and muster processes Simple privacy guardrails so it supports people, not surveillance A lightweight workshop you can run with IT, facilities, and health & safety 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: True or false? Kaz: Your access control system is just there to open doors. Tim: False. Tim: It also creates a trail of tiny facts all day long. Kaz: Okay. And those facts are. Tim: This person, this place, this time, this action. Kaz: So basically it's the world's Kaz: least glamorous analytics Kaz: platform. Tim: Yeah, exactly. It's like Google Analytics, but for real humans Tim: and real doors, which is why we need to be sensible about it.
Tim: Our last episode was the big shift. Tim: Doors, cameras, alarms, intercoms. Tim: They now behave like small computers on your network that Tim: pulls physical security into the technology world, which means Tim: governance, patching, ownership, and the usual IT disciplines. Kaz: And today we're talking about those things the systems produce Kaz: all day long: security events. Kaz: Specifically access control logs. Kaz: Most organizations already have them, and they're easier to use Kaz: than people think. Kaz: So let's define what we mean by Kaz: security data, before we get
Kaz: carried away. Tim: Well, think about it like this. Tim: Every time someone badges in, Tim: uses a mobile credential, types Tim: a PIN, opens a door, triggers an Tim: alarm, or a camera records an Tim: event, the system logs Tim: something. Kaz: So on its own, it's a small fact? Tim: Yeah, but when you group those facts, you get a story. Tim: And CIOs are already good at this. Tim: They do it with application Tim: logs, web analytics, and service Tim: desk trends. Kaz: And we're not asking you to become a security analyst. Kaz: Maybe just treat the logs like Kaz: you would any other operational
Kaz: data source. Tim: Exactly. Tim: The magic is not the tool. Tim: The magic is the question. Kaz: Mhm. Can you give us some Kaz: examples of questions worth Kaz: asking? Tim: Yeah, sure. Tim: You could ask things like how does a typical day start and end Tim: at each site? Tim: Which entrances carry most of the load? Tim: Where are the morning pinch points? Tim: Are there any areas that are almost always empty but still Tim: heated, cooled, and lit like they're hosting a concert? Kaz: Oh, that sounds spendy. Tim: Yeah. We'll give you three starter stories.
Tim: Most organizations can build with what they already have. Tim: No fancy analytics platform required. Kaz: So this is the story where the CFO becomes your biggest fan? Tim: Maybe. Tim: Or at least slightly less suspicious of your budget. Tim: See, access events can tell you Tim: when a building is actually in Tim: use. Tim: You can use the first person in and last person out times to Tim: guide when heating or cooling starts or stops. Tim: You can bring areas to comfort Tim: when people actually arrive, not Tim: when the calendar says they Tim: should. Tim: And you can spot patterns where equipment runs for hours in
Tim: spaces that are rarely used. Kaz: And to be clear, you don't need named people for this. Tim: Yeah, exactly. Tim: Anonymized data to counts and trends are usually enough. Kaz: What's a simple starting point? Tim: Well, you can pick one building Tim: and look at one month of Tim: activity. Tim: Pull the daily chart showing the first credential use and the Tim: last credential use. Tim: And then compare that against the BMS schedules. Tim: More often than not, you'll spot Tim: at least one moment that makes Tim: you ask, "why are we paying for
Tim: this?". Kaz: HMM. Okay, Well, let's talk about safety and muster. Kaz: Classic question for evacuation is who's still inside and where Kaz: might they be? Tim: Yeah. Muster lists based on access control are not always Tim: perfect, but they're often a far better starting point than Tim: clipboards and guesswork. Tim: With the right design, access Tim: data can provide a live view of Tim: people who have entered but not Tim: yet exited. Tim: It can help fire wardens focus on people rather than paperwork
Tim: and support after action reviews, so teams can understand Tim: what actually happened. Kaz: And we're not replacing people on the ground. Tim: No, we're giving them better information. Kaz: So this is also where you want Kaz: alignment with like, your health Kaz: and safety teams, because the Kaz: process matters as much as the Kaz: tech, right? Tim: Absolutely. Tim: When you start to look at occupancy and fair chargeback, Tim: the conversation usually turns to shared spaces. Tim: If multiple teams or business units use the same site, it is
Tim: only a matter of time before questions come up about who is Tim: using what and who should really be paying for it. Kaz: Usually at the exact moment that someone wants to cut costs. Tim: Yeah, exactly. Tim: If you join access control events with simple business Tim: attributes like department or cost center, you can build Tim: straightforward occupancy reports that show which teams Tim: use which buildings and when. Tim: It supports fair chargeback for Tim: space services or parking, and Tim: you can back up space planning Tim: decisions with facts instead of Tim: feelings. Kaz: And this means you might actually discover that, that
Kaz: 'busy' floor rarely goes above forty percent occupancy. Tim: Yeah. Which is a polite way of Tim: saying that your space plan is Tim: based on perception, not Tim: reality. Kaz: So now for a practical question. Kaz: Where is this data actually sitting? Tim: Uh, it usually sits in three places. Tim: You've got the live system where Tim: the events are created as people Tim: move and sensors trigger; they Tim: get moved into the main database Tim: and are stored there for Tim: reporting and search; and then Tim: any copies of that data that are Tim: pushed to other systems like
Tim: building management, HR, Tim: payroll, visitor management, or Tim: safety tools. Kaz: So from an IT lens, that's just Kaz: an application plus a database Kaz: and storage. Tim: Exactly. Tim: The twist is the content because it can include details about who Tim: was where and when. Tim: Good practice means knowing Tim: which systems hold that data and Tim: who owns each one, agreeing on Tim: how long events and reports Tim: should be kept and why, and Tim: making sure any copies held in Tim: other systems follow the same Tim: rules. Kaz: So let's maybe talk about guardrails here. Kaz: We should slow down a bit
Kaz: because this data is about Kaz: people. Tim: Yeah. And when used well, it Tim: supports safety and a smoother Tim: workplace. Tim: Used badly, it feels like Tim: surveillance and it damages Tim: trust. Kaz: So what are the guardrails? Tim: Well, a few simple ones make a big difference. Tim: You want to be clear on purpose, Tim: decide what you will and won't Tim: use the data for and write that Tim: down. Tim: You want to limit the access, so only give detailed event access Tim: to people who genuinely need it. Tim: You want to watch the detail, Tim: often counts and trends are Tim: enough. Tim: Use anonymized data.
Tim: You want to set retention rules. Tim: Keep it long enough to be Tim: useful, not so long it becomes a Tim: risk. Tim: And you want to communicate honestly. Tim: Clarity reduces rumors. Kaz: And if you already involve privacy or legal teams for HR Kaz: and CRM systems... Tim: Bring them into this too. Tim: Some good habits. Kaz: Okay, so how does someone start without turning this into an Kaz: eighteen month program? Tim: Yeah, it sounds big, but you can just run a simple workshop. Tim: You get one person from IT, one
Tim: person from facilities or Tim: property, and one from health Tim: and safety. Tim: The agenda is easy. Tim: Pick one site, list the questions people argue about. Kaz: Okay, things like, "when are we the busiest?" or, "where are Kaz: those morning pinch points?" Tim: Yeah, exactly. Tim: And then mark which questions you can answer with access Tim: control and other security data that you already collect. Tim: Choose one or two of those Tim: questions and agree who can pull Tim: a simple report or export of Tim: that data. Tim: Then meet again and look at the results and decide one small Tim: change to try. Kaz: So keep it light, right?
Kaz: The goal is to prove the data can answer real questions. Tim: Exactly. Clear story. Tim: Small change. Tim: Get a measurable result. Kaz: So that's episode two. Kaz: Security data is not just for incident investigations. Kaz: It can support comfort, safety and a smarter use of your space. Tim: Yeah. Next episode is part Tim: three: Boring Habits that Fix Tim: Scary Risks. Tim: We'll talk about the calm Tim: governance habits that stop Tim: these systems becoming the Tim: forgotten corner of your
Tim: environment. Kaz: Thanks again for listening. Kaz: If you'd like the link to the Kaz: blog post, it's in the show Kaz: notes. Tim: Catch you next time.
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...
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...
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...
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...
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...