Practice area
Security systems
Video surveillance, access control, and intrusion detection — installed on network infrastructure that is segmented, monitored, and encrypted, because a camera on your office VLAN is a way into your office network.
What we do
Physical security, engineered like the network it runs on
Most security-system installers are electricians with a laptop. Most IT providers treat cameras as somebody else's problem. The gap between those two positions is exactly where physical security deployments go wrong — and it is the gap we work in.
Video surveillance
Camera design, placement, and recording — on-premises or cloud-retained — sized around what you actually need to see, not the maximum a sales sheet offers.
Access control
Badge, fob, PIN, or mobile credentials at the doors that matter, with schedules, audit trails, and a revocation process that runs the day someone leaves.
Intrusion detection
Perimeter and interior detection with proper zoning and alert routing, so a notification means something is happening rather than that a tree moved.
Structured cabling and PoE
Power budgeting, cable runs, and switching designed so the camera system does not brown out the network closet or exceed the switch's budget.
Intercom and entry
Door stations, visitor entry, and after-hours access with the same credential model as your interior doors — one system to administer, not five.
Environmental monitoring
Temperature, humidity, water, and door-position sensors for closets, server rooms, and racks, wired into the same alerting the NOC already watches.
Design decisions that matter
The parts a camera quote usually leaves out
A functioning camera system is not difficult. A camera system that does not become the weakest point in your network takes deliberate design, and these are the decisions we make explicitly rather than by default.
| Decision | What we do | Why it matters |
|---|---|---|
| Network placement | Cameras and controllers live on their own VLAN with no route to user networks | A compromised camera becomes a dead end instead of a foothold |
| Credentials | Default passwords removed, unique credentials per device, firmware kept current | Default-credential cameras are among the most exploited devices in existence |
| Transport | Encrypted where the platform supports it, including remote viewing paths | Video of your site is sensitive; it should not cross the internet in the clear |
| Retention | Retention set from your policy and any legal requirement, then monitored | Retention that silently stopped working is discovered at the worst moment |
| Access to footage | Individual accounts with roles and an access log | Who watched what, and when, is itself an audit question |
| Remote access | Through your identity provider where possible, not shared vendor logins | One offboarding action removes access everywhere |
Where it connects
Physical and logical security are one problem
One network, one standard
Because we run the network, the camera system is designed into segmentation, monitoring, and patching from the start rather than added to whatever ports were free.
Physical access is in scope
Badge records, visitor logs, and camera retention frequently appear in audit evidence requests. Built with an access trail, those requests take minutes to answer.
Same discipline in the cage
Facility access control, cabinet locks, and environmental monitoring are the same design patterns we use in our own colocation space.
Questions
Security systems, answered
Can you take over a system someone else installed?
Usually, yes — provided the platform is still supported by its manufacturer and we can get administrative access. We audit what is there, document the device inventory and firmware state, fix default or shared credentials, and correct network placement. If the platform is end-of-life or administratively locked, we will tell you before you spend anything on trying to save it.
How long should we keep footage?
That is a policy question before it is a storage question. Retention is driven by what you need the footage for, any regulatory or contractual requirement, and privacy considerations about recording staff and visitors. We will help you set a period you can defend, size the storage to match, and then monitor that recording is actually working for that whole window.
Do you monitor the cameras for us?
We monitor system health — whether cameras are online, recording, and storing footage as expected — and alert when something fails. We are not a staffed video-monitoring or dispatch center and we will not present ourselves as one. If you need live human monitoring, we will tell you that plainly and point at who genuinely provides it.
What about privacy and legal requirements?
We design so that access to footage is individually attributable and logged, retention is deliberate, and recording is confined to areas where it belongs — which is both good practice and what a privacy review will ask about. We are not your legal counsel: where signage, notice, or jurisdiction-specific rules apply, we will flag it and you should confirm with your attorney.
Can we keep remote viewing on phones?
Yes, and we will set it up so it does not undermine the rest of the design: individual accounts rather than a shared login, through your identity provider where the platform supports it, with encrypted transport and multi-factor authentication on the account itself.
Site survey first, equipment list second
Tell us what you need to see and control. We will design to that, and put the coverage plan and cost in writing.