Magnesium

Magnesium is a high reliability and secure system that provides for messaging, file transfer and conferencing over insecure IP-based network, typically the Internet. 

The system is designed to facilitate the secure exchange of information between pre-authorized parties without the high capital and operational (administrative) costs of traditional high security methods.  The features include:

• Centralized/automated management and policy generation, distributed enforcement;
• Very scalable with support for regionalization (groups);
• Very low administrative overhead;
• Strong chain of evidence, logging and traceability;
• High reliability (system robustness);
• Highly flexible and scalable.
• High security (CMVP FIPS-140-2 pending)

An Mg deployment consists of many geographically distributed Mg-RU (remote unit) devices, reporting to one (or more) Mg-GW devices. 

The Mg-RUs implement the subscriber access equipment and are available in a number of different configurations, including:

Mg-Fe

The Mg-Fe implements the “subscriber” access to the Mg messaging system over an un-secure IP network.  Subscribers access the Mg-Fe via Ethernet (1000BaseT) or USB 3.0 (MSD) using their own device.  The Mg-Fe implements the access control, security, policy, queuing and reliable message transfer both generating and receiving messages and/or files from other members of the Mg community. 

Mg-Fe-PC

The Mg-Fe-PC implements the functionality provided by the Mg-Fe with an internal, physically secured PC running captive applications in kiosk mode.  This offers a more secure package compared to employing external subscriber devices (PCs).

This interface allows the operator to:

• Execute pre-defined, authentification procedures (who are you)
• Log onto the system
• Be notified of, and view/export any outbound messages
• Address and generate inbound messages
• Manage their local inventory of messages
• Attach (upload) digital files to these messages.
• Exit the system (logging off)

This approach implements a hard security boundary between the source equipment and the Mg secure zone.  The user employs native COTS software on his/her system (ie their browser of choice) to generate messages and/or send files either on their system or connected devices (cameras, DVRs, smart phones etc) without having to (attempt to) include these devices within or allow access to the security envelope.  Files submitted across the security boundary are tagged, never executed and maintained in their native format c/w the file name and extension. 

This approach is substantially more secure, reliable and easier to use than a PC and/or traditional VPN solution.