
Door access control: the IT checklist before you choose a system
Door access control for small business: the IT checklist on admin accounts, readers, power, failure behaviour, badge lifecycle, logs and handover.
Physical security
Start with your premises, existing equipment and responsibilities before discussing a change or integration with the rest of your IT environment.

Physical security systems protect people, premises and equipment: door access control, cameras, alarms, visitor entry and the rooms where servers and network equipment are kept. Today most of these systems are connected devices. They sit on your network, use accounts and passwords, record information about people and depend on suppliers, which means they belong in your IT plan as well as your facilities plan. BlueNova IT helps small and midsize companies operating across Europe to understand how their physical security systems connect with their IT and to plan changes with the right checks.
We start with what already exists on your premises and with who is responsible for it, rather than with equipment to buy.
Because every country has its own rules on surveillance, access logs and signage, we treat requirements as local questions. What is acceptable in one office may need adjustment in another, and we would rather ask early than assume.
The scope is agreed for each organisation before work begins. A physical security engagement typically covers the following areas.
We list the systems in place at each site, such as access control door readers, CCTV cameras, recorders and alarm panels, and note who installed them, who maintains them and which contracts apply. We also look at the premises themselves, including entrances, shared areas and the rooms holding IT equipment, so the review reflects how the building is really used. Before choosing or replacing a door system, our door access control IT checklist lists what to settle first.
Connected security devices need a network path, power and administrative accounts. We review how each system is connected, who can log in to it, how those accounts are managed when staff or suppliers change and whether device management is separated sensibly from the rest of the network. The connectivity side is closely related to our networks and infrastructure service. For cameras and recorders, our guide to CCTV network requirements for small businesses covers bandwidth, PoE and network separation.
Cameras and access logs record information about people. Who can view it, where it is stored and for how long it is kept are decisions with legal and privacy implications that differ between countries. We help you document the current arrangements and prepare the questions to review with the responsible people or your legal and data-protection advisers. We do not provide legal advice.
Door and camera systems often connect with staff directories, visitor processes or monitoring tools. We map those links, note what depends on what and agree how changes will be planned so that one project does not disrupt another.
Server rooms, communications cabinets and storage areas deserve the same attention as the front door. We look at who can physically reach network and server equipment, how keys, cards or codes are managed and whether visitors or contractors can be left alone near critical equipment. We also check that equipment locations are recorded, so that a fault can be traced to a physical place.
The review described above starts with a list for each site. It is a simple document, and most of its value comes from the questions it raises.
The list is kept per site because sites rarely share the same history. A head office and a small branch often have different installers, different maintainers and different contracts, and a single combined list hides that. Recording who maintains each system answers the first question that arises when something stops working, which is whom to call. Recording the contract shows whether that call is already covered by an agreement.
Illustrative example, not a description of a real client. At a small office, the list might show a door reader at the entrance, a recorder in a storage cupboard and an alarm panel looked after by a different company from the one that installed the cameras. None of this is unusual, and none of it is visible until somebody writes it down. See a sample inventory and connection map (illustrative example).
A list like this is the base for every later decision. A change to the network, a move to new premises or a change of supplier is hard to plan when nobody can say what is installed and who is responsible for it.
Reading the list together with you is also how gaps appear: a system with no known maintainer, a contract that nobody can find or a device that nobody can place on the floor plan. Each gap is a question worth answering before anything is changed.
A central document in this work is a network connection map: a diagram of how each physical security system connects to your network and what it depends on.
Its value shows when something changes. If a switch is replaced, a room is rearranged or a supplier is changed, the map shows which door readers, cameras or recorders are affected, so they can be checked afterwards instead of being found broken. A device that appears on no diagram is typically the one nobody remembers when the network is changed. The map is also the kind of document that a new IT supplier or installer will usually ask for first.
A map is only useful while it is current, so it is worth deciding where it is kept and who updates it when something changes. A diagram that nobody owns goes out of date.
Illustrative example, not a description of a real client. Suppose the entrance cameras are powered through the same network switch as the office phones. The map makes that dependency visible, so replacing the switch is planned as a change that also switches those cameras off for a while, instead of a routine job that quietly stops them recording.
The map fits with the rest of your network documentation. Our guide to planning your business network covers components, risks and supplier questions, and our structured cabling planning guide explains how a cabling installation is planned and documented.
Where a project allows it, BlueNova IT can carry out the installation itself. Whether that applies is confirmed for each project, so we do not describe it as a general rule: it depends on the site, on the technical requirements and on what is agreed in writing.
We explain this carefully because it affects how a project is organised. Who installs, who maintains afterwards and who holds the contract are separate questions, and the inventory is where the answers are written down.
The inventory and the connection map are useful whoever does the work. When we install, they are where the project starts: the inventory shows what is already there and the map shows what a new device would need to connect to. When someone else installs, they describe what exists and what depends on what.
We do not give legal advice. Videosurveillance, access logs and signage are legal questions, and they belong with your legal adviser. What we can do is prepare the questions for that adviser and describe how your systems are set up, so that the conversation starts from facts.
The reason is practical as well as legal. The same camera can raise different questions in different countries, so an answer that suits one office may not suit another. That is why we prepare questions instead of answers.
The accounts that administer these devices need the same discipline as staff accounts when people or suppliers change. Our IT onboarding and offboarding checklist shows that discipline applied to people.
This service suits organisations that have, or are considering, physical security equipment and want it handled as part of their IT rather than as a separate, forgotten system. Typical situations include:
We work in English and Spanish, Monday to Friday, 09:00–18:00 CET/CEST, so teams and local suppliers in different countries can coordinate through one point of contact. Commitments for any engagement are agreed in writing for that scope.
If you would like to review how your physical security connects with your IT, contact us with a short description of your premises and the systems you already have.
You describe your premises, the equipment already installed, the suppliers involved and the problem you want to address.
We examine the systems, their connectivity, the accounts that administer them and the information they record, and write down what we find.
We outline possible changes with their dependencies, and list the points to confirm, including technical compatibility, supplier arrangements and location-specific requirements.
Installation and on-site services depend on the location and are confirmed per project. A first conversation sets out your requirements and the next checks; we do not promise a particular security outcome.
Where work is agreed, we check the result against the plan and leave you with updated documentation.

Door access control for small business: the IT checklist on admin accounts, readers, power, failure behaviour, badge lifecycle, logs and handover.

CCTV network requirements for small businesses: PoE budgets, bandwidth and storage, VLAN separation, accounts, firmware, backup and retention explained.
Tell us what your team needs today and what you would like to improve.