← Back to the chapter · Previous detail
Technical detail · Edge Acquisition: Power and Gateway Functions
Fail-Closed Gateway Admission Control
Read the Fail-Closed Gateway Admission Control material as a decision path rather than as isolated entries. First identify the operating condition in each entry and keep its units, timing, source, and assumed system state attached to it. Next compare the entries at the point where responsibility changes between device, gateway, network, analytic service, and operator; that hand-off is where apparently similar choices often produce different outcomes. Then follow the failure case: ask what becomes stale, delayed, unavailable, or unsafe, who detects it, and what evidence permits recovery. Finally connect the result to the chapter’s running design record by naming the selected behavior, the rejected alternative, the measurement that justifies the choice, and the condition that forces a recheck. That order turns the examples or comparison into an auditable engineering argument.
For industrial or safety-critical gateways, security should start before the protocol bridge accepts a device. A fail-closed gateway uses a default-deny policy:
- Check approved provisioning records against identifiers available before the session, such as a MAC address or serial number. These identifiers are not cryptographic proof of identity.
- Reject and log unknown devices before TLS begins when the provisioning identifier is available at that stage.
- For an admitted connection, start TLS or mTLS and check the relevant certificate credentials during the handshake. Deny forwarding until the configured device authentication succeeds.
- Apply command filtering and payload validation before forwarding data to the cloud or issuing actuator commands.
| Choice | Use when | Risk if chosen poorly |
|---|---|---|
| Fail-closed whitelist | Critical infrastructure, industrial gateways, small controlled fleets | Stale allow-lists can block legitimate replacements until provisioning is updated. |
| Fail-open blacklist | Consumer or rapidly changing fleets where onboarding speed dominates | Unknown or cloned devices may connect before they are explicitly blocked. |
Encryption protects data confidentiality, but it does not prove device identity by itself. A gateway that validates identity, encrypts transport, and rejects unknown devices before forwarding traffic has a smaller attack surface than a gateway that only wraps every connection in TLS.