Kantech EntraPass and KT Controllers
Kantech supports small standalone doors and larger EntraPass-managed systems. The system engineering needs to match controller topology, readers, credentials, network ownership and growth to the client’s operations.
Choose controller architecture before counting parts
Door quantity alone does not decide the system. Consider entry and exit readers, offline behavior, network routes, encryption, expansion, integrations and who administers access.
Controller family and topology
KT-1 is useful for one-door IP deployments and supports entry and exit readers. Current KT-2 and KT-4 products address compact two- and four-door applications with their own supported operating modes. Existing sites may also contain KT-300 or KT-400 controllers, so expansions need a compatibility and lifecycle review rather than an automatic like-for-like order.
Map controllers to doors, network closets and power locations. Document what happens if the server, IP network or upstream controller is unavailable. Distributed IP controllers can reduce long field wiring, while centralized panels may simplify power and service; the building layout determines the better balance.
- Doors and readers per opening
- IP, RS-485 and supported controller relationships
- Offline decisions, schedules and event storage
- Existing controller compatibility and lifecycle status
EntraPass software and administration
Select the current EntraPass edition and licenses from site count, workstations, gateways, users, doors, integrations and remote-access requirements. Define operators and permissions by job role. Shared administrator accounts make investigations and changes difficult to attribute.
Build cardholder fields, access levels, schedules, holidays and expiration rules before bulk enrollment. Decide who approves access, who enters changes and how terminations are handled. Reports and alarms are useful only when clients establish ownership and review routines.
- Edition, workstation and gateway licenses
- Cardholder, schedule and access-level standards
- Named operators and audit responsibility
- Approval, termination and periodic review workflow
| Controller | Typical scope | Confirm before selection |
|---|---|---|
| KT-1 | One door with entry/exit readers | PoE, operating mode and expansion topology |
| KT-2 | Compact two-door applications | Standalone and integration requirements |
| KT-4 | Four-door distributed applications | Power, network and EntraPass system engineering |
| Existing KT family | Expansion or migration sites | Current support, firmware and compatibility |
Readers, credentials and door hardware
Coordinate reader technology with credential security, mobile plans and existing populations. Legacy proximity may be convenient for migrations but needs to not be confused with stronger encrypted smart-card technology. Verify the exact reader, credential, key management and controller support as one system.
Each opening needs a hardware and sequence review: lock type, voltage, current, fail mode, door contact, request-to-exit, emergency release, accessibility and mechanical condition. Provide separate or supervised power where required and calculate standby loads.
- Reader protocol and credential technology
- Migration and enrollment approach
- Lock, contact and request-to-exit sequence
- Power, fire interface and egress coordination
Functional Commissioning, backups and support
Test granted, denied, expired, schedule, door held, forced, request-to-exit and network-offline scenarios. Verify event timestamps, alarm routing and reports. When intrusion or video integration is used, include it in the test matrix instead of testing only the access screen.
Back up EntraPass configuration and document the supported restore process. Record controller firmware, addresses, MACs, door assignments and panel power. Obtain software, firmware and documents through Kantech official resources; do not distribute controller files through public download pages.
- Credential and door-state scenarios
- Offline, power and communication tests
- Database backup and restore record
- Controller inventory and official lifecycle sources
How we plan and deliver the work
The final system engineering depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Survey openings
Record doors, hardware, readers, power, pathways and existing controllers.
System Engineering topology
Select controllers, network relationships, software and licenses.
Configure governance
Build operators, cardholders, schedules, access levels and alarms.
Test and close
Validate door, credential, failure and reporting scenarios, then back up.
Information to gather before system engineering
Good decisions are easier when the security engagement team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Opening and hardware schedule
- Controller and network topology
- Reader and credential migration plan
- EntraPass edition, licenses and operator roles
- Testing, backup and lifecycle requirements
Frequently asked questions
These are common engineering assessment questions. A site-specific answer needs to be confirmed during discovery and system engineering.
Is KT-1 limited to one reader?
No. It supports two readers for entry and exit on one controlled door, subject to the supported configuration.
Can Kantech operate without a server connection?
Supported controllers retain defined local functions, but exact offline behavior and event capacity needs to be documented for the selected architecture.
Should an existing KT-300 or KT-400 be reused?
Only after confirming condition, current support, firmware compatibility, capacity and the client’s lifecycle goals.
Are all credentials equally secure?
No. Credential technologies and key management differ. Select readers and credentials as an end-to-end security decision.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Discuss a commercial security security engagement
Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and system engineering conversation.