PowerOn Protector System
Manages (and scales) security on devices for your network.
The system contains the following software elements:
- A Windows monitoring agent
- A microcomputer with a Linux operating system customized compiled
- PowerOn Protector ™ System (CualliSyS ™ PowerOn Protector ™ Stack )
The Windows monitoring agent is native to Windows 7 PowerOn Protector has as MySQL Server database which is responsible for receiving the status of the agent, and specialized modules are used for the exploitation and presentation of the final information from the execution Of the PowerOn Protector service. The Final solution includes:
A Windows service, responsible for monitoring (according to the configuration selected by the client) the set of services and Windows interrupts, which denote whether it has been properly restarted or not. The information will be sent via USB and received on the microcomputer via an asynchronous UART (Universal Asynchronous Transmitter / Receiver) connection. It should be noted that this agent does not make any decision, it is only a collector of specific information at the level of hooking Windows 7.
A management and control interface of the PowerOn Service Protector, Web, making use of Apache and developed in PHP and ExtJS. The features of the graphic control interface are as follows:
- Unlocking Locked Device
- Management of the internal database
- Basic user control for device management
- Statistics of HW of PowerOn Protector
- Known status of the secured system.
PowerOn Protector Main Daemon: capable of managing the exchange of information with the MySQL database coming from the Windows agent and in charge of making the decision if the secured system has been attacked or not.
Process of USB control of the native password of the PowerOn Protector. This process is in charge of taking control of the password of the BIOS, making use of libraries written by Cuallisys ™.
The software does not have a site or event license. The software is secured to be installed once only by current ATM (1 for this case), any change of scope of the same, will require a new proposal that will consider a new license of use. The source code is not released.