Navigation is quick and simple in the EagleEyeOS™ Professional Control Center using the home page. It is a collection page of frequently used links and general statistical data.

Wizards enable the setup the properties of the different objects.

It serves as a display for continuous, real-time monitoring of Events occurring throughout the network. Its significance increases at it inspects real-time incidents; in addition, it helps to perform the operational work on the required level. (E.g. immediate follow-up of rule modification).

Reports query and analyze user events. When creating reports, any kind of stored information can be searched, grouped and ranged in order to find them at the earliest possible moment. Beyond file operations, some special information can be attained e.g. leaving the protected network, enters, Copy and Paste etc.

Who did what and when with the file? Where and under what name can the file be found? The File Lifecycle Tracking (FLT) is a specially developed feature to trace what operations the file went under since its creation. The File Lifecycle Tracking function marks the parallel life-tracks of the file with branches; it is also possible to search the file's Lifecycle directly from the queried Reports.

It shows that what hosts were connected with the certain storage independently from that the storage is a pen-drive or a photo camera. Based on its hardware identification ability it shows exactly who did connect it, when and on which hosts, or rather what kind of file operations were executed on it.

Auto Reports can be scheduled to analyze certain activities and report File Lifecycle. Large, count-intensive reports can be scheduled to avoid overloading the network.

Alerts notify of an optional event and get generated at the moment an event occurres. Alerts can be queried in both Report and File Lifecycle format. It has great significance at the immediate detection of the abuses, since it notifies of the root cause of any blocking simultaneously.

It provides complete network management. With just one click the installation to multiple, remote hosts becomes possible, while also able to update the Agents running on the Hosts.

Servers store the incoming event logs and defined rules, as well as instruct the Agents to manage the network properly. Several Servers can be overseen with a single Control Center, or several Control Centers can be connected to a single Server. Furthermore, the relevant statistical information on the Server can be queried from here.

The incoming event logs are located in a data storage structure specially developed for this purpose. Event logs are archived automatically based on the determined size and time. This function increases in significance with ongoing operations. Constant personal control is not necessary to keep the performance of the Server at an appropriate level despite of continuously increasing logs. The information can be queried directly in the archived data.

The different process- and security level related activities can be separated from each other. Different rights can be assigned to certain operators, and it is possible to separate e.g. the operation tasks of the information technology area from the report reading rights of the people responsible for the security.

Server Logs provide continuous status information on Server operations; displaying informal messages on the procedures performed by the Server is real-time. Error messages are marked with support identification in order to make troubleshooting easier.

Install Logs supply information on remote installation to a pre-selected workstation. Install Logs provide additional data on events occurred during the installation, beyond the logs containing successor failure information. It is an efficient aid during the troubleshooting process.

It presents all managed hosts and created host group lists in hierarchy order here. Operation of the Agents can be controlled, the Silent mode can be switched on, and in addition it is possible to control the connected storages containing a file system.

Rule Groups help group the predefined rules and makes assigning them to hosts and host groups quick and easy.

With the help of the Log Filter, unnecessary logs containing information irrelevant to user activities and don't provide important information can be filtered. These events can be the temporary, processes internal operations made by several applications. The network flow and the quantity of unnecessary logs stored on Servers can be decreased with the right setup.

Filters are rules that enforce security, and determine who, when, with what kind of device, and how is enabled to access files.

A Device provides the possibility to establish the access policy of a general purpose communication media. Such Devices can be Floppy drives, CD-, DVD drives, Infrared, COM, LPT, USB, Bluetooth, Wireless ports etc. The most important feature of it is to block the devices irrespectively of whether at the moment there is a Device connected to the host or not.

The Quarantine function is a special document area protection, which provides the possibility to create separate territories. Data movement can be controlled within this area as well as beyond. It has the important ability to define approved users, applications, printers in the area, and specify the path to where the data can be exported to. It has the ability to separate the information both from the Local and Domain Administrator, and the separation of the same application - running in the Quarantine and outside of it -, e.g. copy content between two Word document.

With the help of this function rules can be created, and if those are realized, then a record will be made about the certain workstation. The importance of it is in the approval of the circumstances. With the Snapshot can be showed if the behavior caused any forbidden activity happened accidentally or on purpose. The Snapshot can be freely combined with other protection functions (e.g.: Filter, Quarantine).

Printer rules can also be predefined. With their help it can be determined which printers can be used or blocked on a certain host. This feature is very important during creating Quarantines too.

The program’s rule enforcement technology works in the kernel of the operating system, between the levels of the access control and the file system. It enables protection processes that cannot be found anywhere else.

It monitors and controls the processes at kernel level, so it is completely independent from applications running at user levels.

It builds in the kernel above the file system, therefore, it is completely independent from file system driver programs and the physical discs under the drivers.

It supports Novell Netware sharing equal to Microsoft Windows sharing, providing all logging protection features on both platforms. The technology can be used without restrictions on both Microsoft Netware Client or Novell Netware Client.

Copy recognition is independent from the initiating application. E.g. Explorer, Drag and Drop, Copy and Paste, Print Screen, Command Prompt.

It builds an additional protection line in the kernel under the level of access control. It can block document from the Local and/or the Domain Administrator. Furthermore it opens up the possibility to create separate document territories securely.

Communication channels can be controlled irrespective of their actual availability. We can block e.g. the Bluetooth communication on a certain host even if the host is not connected to a Bluetooth device at that moment. The Bluetooth device connected later on will not be able to operate.

Beyond the communication channels, there is a possibility to recognize and control storages connected to the computer in runtime. This makes the management of devices, independent of producer and type (e.g. Pen-Drive, camera, etc.), possible. A major feature is that events made on storages, will be logged; also it is possible to use the Read-Only rule.

With its help the own database technology can be redeemed to an existing and centrally managed SQL database, which some operational processes had been developed already (e.g.: secured storage, backup, etc.) Through the SQL support the resources and costs of the operation can be reduced more. Supported databases: Microsoft SQL Server.

With a single setup, this makes it possible to restrict access to the files stored on a given Computer only for those Computers on the network, which have Clients. Using this technology, the files stored on a Computers inside an EagleEyeOS™ Zone®, are unavailable for Computers connected illegally to the network.

With its help the generated information can be forwarded to an existing and centrally managed SYSLOG logging system, which some operational processes had been developed already (e.g.: secured storage, backup, etc.) Through the SYSLOG support the resources and costs of the operation can be reduced more, furthermore the simpler integration to the third party’s central remote administration, error handling or alert systems. The SYSLOG contains the full path of the objects, therefore for example by the use of the HP OpenView Operations without developing a separate Smart Plug-In the occurrence of the event can be presented in the Service Grid. (Third parties’ products without a completeness demands: HP OpenView, IBM Tivoli, Cisco MARS, Novell Nsure Audit, etc.)

Running on kernel level offers the possibility to keep the defined rules after losing network connection, and to make these rules impossible to by-pass. It is possible to disable the Bluetooth devices and pen-drives on a notebook removed from the network. Furthermore, user activities will be logged locally together with the date and time of the disconnection and reconnection. At the next network connection, the rules and the logs will be synchronized.

Local storage procedure prevents data loss. If the Host loses the connection with the server because of maintenance work or network cut, the latest defined rules remain valid and logging will be continued locally. Synchronization will take place at the next connection to the Server.