PHY-09 · EXPERIENCE
Physical Security and Surveillance, Where Access Control Meets Cyber
I administer Software House C-CURE 9000 access control and stand up Axis IP cameras, then keep both running as part of your security program, not a side system nobody owns. Door controllers, badge readers, and cameras are endpoints on your network, so I treat them like endpoints: segmented, hardened, patched, and logged. You get one person who speaks both the physical access language and the cyber language, instead of two vendors pointing at each other.
01 · What I do
The actual work
- Administer C-CURE 9000: clearances, time schedules, badge holders, door and reader configuration, and access levels mapped to real roles.
- Install and commission Axis IP cameras, from mounting and addressing to firmware, recording, and view layouts.
- Segment access panels, controllers, and cameras onto their own VLANs so a camera compromise does not become a network compromise.
- Harden the devices and servers: change defaults, disable unused services, enforce strong auth, and apply firmware updates on a schedule.
- Tune retention, storage, and recording so footage is there when an investigation needs it and not a surprise storage bill.
- Build access and door-event reporting plus alarm handling so the right people see forced doors, held-open events, and offline readers.
- Document the badge lifecycle: issue, modify, revoke, and audit, so terminations actually remove access the same day.
02 · What you get
What you are left with
- A working C-CURE 9000 deployment with access levels that match real job roles, not a tangle of one-off exceptions.
- Axis cameras that are addressed, hardened, recording reliably, and documented so the next person can support them.
- Access devices and cameras isolated on their own network segments, so a weak camera cannot reach the rest of your environment.
- A documented badge and access lifecycle, including same-day revocation when someone leaves.
- Clear ownership: written configuration, retention settings, and reporting handed over so the system does not depend on me to keep running.
03 · Tools and knowledge
What I work with here
04 · How I approach it
Planned, scoped, and owned
I start with a 30-minute scoping call and send a same-day written fit assessment, so we both know what we are dealing with before any work. Because cameras and access panels touch live doors and live networks, every production change gets a documented change plan with a defined rollback before I touch anything. I cut over inside an agreed window, validate against the gates we set (doors lock and unlock correctly, readers report, cameras record, segmentation holds), and I own the rollback if a gate fails. Nothing goes to production on a guess.
05 · Questions
Good questions, straight answers
Can you take over an existing C-CURE 9000 system, or only new installs?
Both. I can come into an existing deployment, document the current access levels and door configuration, clean up stale clearances, and harden it. I can also stand up new doors, readers, and badge holders from scratch.
Do you handle the network side of the cameras and access panels too?
Yes. That is the point of having one person on it. I put cameras, controllers, and panels on segmented VLANs, lock down the switch ports, and make sure the devices are patched and authenticated, so physical and cyber are handled together.
What happens if a cutover goes wrong on a live door?
It does not get that far without a plan. Every production change has a written, ordered change plan and a defined rollback before I start, I validate against agreed gates inside the window, and I own reverting if a gate fails. Doors stay in a known good state.
06 · Related experience
Adjacent work I do
Need this handled?
Tell me what you are trying to move and where it is stuck. A few sentences is plenty to start, and it goes straight to my inbox.