Yes. Time-based port scheduling is a supported operational mode and is useful for DevOps segregation, timed third-party access windows, or out-of-hours isolation of non-critical systems.

No. By design. Disconnection and reconnection require explicit authorized commands. This prevents accidental reconnection but also means operational procedures must be defined for returning to a connected state after an isolation event.

Two primary operational models exist:

1. Normally connected — the FireBreak™ sits inline and is triggered to disconnect in response to a threat, alert, schedule, or procedural event
2. Normally disconnected — assets are isolated by default and only connected when service is actively required, such as during scheduled maintenance windows or authorized third-party access

Many deployments use a combination of both models across different segments.

‍

This is a common concern and, in practice, a manageable one. FireBreak™ is designed to be operated by the same staff who already control critical systems — network, security, and processing teams. Standard operating procedures define when and how ports are opened or closed. Accidental disconnection carries a similar risk profile to accidentally removing a patch cable, which trained operations staff already manage routinely.

‍

Via the rear Management Console Port. Connect it to a dedicated management network and access the device’s IP address through a browser. Security aligns with NIST 800-63 requirements, including two-factor authentication, brute-force protection, and full audit logging.

The SMS interface rejects all messages by default. To authorize a user:

1. Whitelist their mobile number
2. Assign specific port permissions
3. Generate a unique OTP seed key compatible with Google Authenticator, Microsoft Authenticator, or Cisco Duo

Every command must include a valid OTP. Failure to meet any of the three criteria results in rejection.

Enable port [1–12], Disable port [1–12], and Status port [1–12]. All commands require challenge/response authentication and are case-sensitive. The full command set is documented in the Administration Guide.

There are two roles. Administrators configure the appliance, provision users, set port permissions, and manage OTP seed keys — exclusively via the rear Management Port (ensuring physical separation of duties). Users are authorized to send connect/disconnect commands to assigned ports via the secure messaging stack. Users have no access to the Management Port.