# Treat controller door override as a break-glass procedure

> Direct relay control can override normal Secure Entry behavior. Reserve it for vendor-directed troubleshooting with approvals, alternate safeguards, and verified restoration.

- Canonical URL: https://update.dsesecurity.com/updates/treat-controller-door-override-as-a-break-glass-procedure/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-08-25T21:35:34+00:00
- Modified: 2026-08-25T21:36:17+00:00
- Last reviewed by DSE: 2026-08-25
- Resource type: Playbook
- DSE priority: Important
- Topics: Access Control, Business Continuity, Cybersecurity
- Reading time: 2 minutes

## What you need to know

Direct relay control can override normal Secure Entry behavior. Reserve it for vendor-directed troubleshooting with approvals, alternate safeguards, and verified restoration.

## Potentially affected

AXIS A1610 Network Door Controller deployments administered through AXIS Camera Station Secure Entry or related supported workflows.

## DSE recommendation

Restrict direct door-output override to a documented, vendor-supported emergency or diagnostic procedure with two-person control and complete post-action reconciliation.

## Article

Bottom line: a direct relay or door-output command can bypass the access-control application’s expected state. That capability should not become a convenient operator shortcut because monitoring, schedules, credentials, and audit meaning may no longer match the physical lock.

## Source fact: the A1610 manual warns about direct relay control

The [AXIS A1610 Network Door Controller User Manual — Door override](https://help.axis.com/en-us/axis-a1610#door-override) warns that direct control of a relay used for a door can override relay configuration in AXIS Camera Station. The manual directs use only when instructed by Axis support and says to stop Secure Entry before that direct-control procedure.

The warning identifies a support boundary: normal PACS commands and low-level output control are not interchangeable. A physical result achieved outside the normal application can leave operators with an inaccurate or incomplete understanding of door state.

## Source boundary and applicability

The manual applies to the specific controller and documented software context. It does not authorize a general bypass, define an emergency-access policy, or replace fire, egress, accessibility, electrical, or lock requirements. Other products may have different controls and restoration steps. Only qualified authorized personnel should act under current vendor support and site procedures.

## Applicability questions

- Which normal Secure Entry function is unavailable, and what verified condition requires low-level control?

- Has Axis support or the applicable vendor provided current instructions for the exact version?

- What door, lock, alarm, egress, and occupied-area consequences can the action create?

- How will alternate monitoring and access control operate while the application is stopped?

- What proves the relay, door configuration, schedules, events, and permissions are fully restored?

## DSE recommendation: require a controlled break-glass record

The following steps are DSE recommendations based on the cited source.

Restrict the capability to trained administrators and do not publish low-level steps in general operator instructions. Require incident or change identifier, affected door, observed fault, support case and instruction, safety review, approver, two-person confirmation, alternate guard or mechanical control where needed, start time, and maximum duration. Preserve required egress and coordinate with fire/life-safety responsibility before any action.

After vendor-directed work, restore the supported application state and independently test authorized access, denial, relock, door contact, forced and held alarms, schedule, event delivery, and audit logging. Revoke temporary privilege and reconcile every access during the exception window.

## Verification and evidence

Retain the support case, approved procedure, exact model and versions, authorization, personnel record, alternate-control log, start and end times, sanitized configuration evidence, restoration test, access-event reconciliation, privilege review, and incident closure. Never include credentials or exploitable bypass detail in broadly distributed evidence.

## Official references

- [AXIS A1610 Network Door Controller User Manual — Door override](https://help.axis.com/en-us/axis-a1610#door-override) – Axis Communications

## Primary reference

- Name: AXIS A1610 Network Door Controller User Manual — Door override
- Authority: Axis Communications
- URL: https://help.axis.com/en-us/axis-a1610#door-override
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Treat controller door override as a break-glass procedure,” DSE Security, https://update.dsesecurity.com/updates/treat-controller-door-override-as-a-break-glass-procedure/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.