SECURA® SOFTWARE consists of:
1) SECURA® Control Server Stack
2) SECURA® Supervisor
3) SECURA® Switching
4) SECURA® Maintenance & Admin Tools
5) SECURA® 3rd Party API for Switching
6) SECURA® DVR (Digital Video Record)

1) SECURA® Control Server Stack: The Control Server Stack is a group of micro-services applications using mTLS (mutual Transport Layer Security), a cryptographic protocol. The stack can be loaded on to RHEL or Ubuntu FIPS certified OS.  It supplies the system with the means to control all of the transmit and receive nodes as well as authorized users, areas, and workstations. The Secura Control Server Stack can use AD (active domain) and LDAP (directory access protocol) or can run as a standalone.  All security levels are defined and enforced by the Secura Control Server Stack whose chief aim is to maintain compliance of current security policies.

2) SECURA® Supervisor: The Supervisor software application is used to configure the Secura System and sets up each node device such as transmitters, receivers, touch panels, and other nodes necessary to fulfill an encrypted audio, video, and HID USB matrix.  Each node can be tagged and filtered in such a manner as to fulfill current security policies of a particular enclave.  The Supervisor is intended for use by Secura System Administrators, and as such can add and delete devices.

3) SECURA® Switching:  The Secura Switching Application manages the switching of video, audio and HID USB devices from sources to destinations.  It works by allowing each user, according to their specific security level, to view, listen, or manipulate (using keyboard and mouse), the signals that they are authorized to use.  Prior to any switch, a mutual TLS connection is established ensuring security for both endpoints.  Once authenticated and verified, the switch is made.  This insures a properly secured connection based on the signal, user, room, and work seat, as configured with Secura Supervisor.

4) SECURA® Maintenance: The Maintenance software application is used for updates and changes to the micro services platform as well as the placement of customer Certificates of Authority (CA), FIPS keys and AES keys as well as assignment of IP addresses and multicast addresses.  The Secura System does not use mDNS, DHCP or SSH to make changes and it’s this module that insures proper administration of each and every node of the Secura System.

5) SECURA® 3rd Party API: The 3rd Party API allows 3rd party (non-PESA) devices, which are generally unsecured, to attach to a Secura System. This API is typically used for 3^rd party panels, but also allows many non-secured devices to be used within the environment.  Use of the 3rd Party API requires PESA training to properly integrate to the Secura System.

6) SECURA® DVR: The DVR software runs as a Digital Video Recording and Playback device using standard, commercial-off-the-shelf (COTS) hardware. Any or all video flows can be recorded for storage or instant playback anywhere on the network.