Skip to main content
Matrix42 Self-Service Help Center

Installation Guide I: Components and Architecture

  1. Last updated
  2. Save as PDF

Overview

This section provides a brief overview of the components used and the system architecture. Here, you'll find key details about the architecture's structure, as well as insights into how the components interact within the system. To review the system requirements, please refer to Installation Guide II: System Requirements

Components

Component Description
EgoSecure Server
  • Installed on any computer in your network.
  • Handles the central management of your EgoSecure clients.
  • Synchronizes with your existing Microsoft Active Directory, Novell eDirectory, LDAP (Lightweight Directory Access Protocol) or Azure Active Directory, and stores it in its own database.
  • Manages all data in an SQL database.
  • Transmits any changes to the clients immediately, and saves them in the database.
EgoSecure Console
  • Controls the functionality of EgoSecure Data Protection.
  • Functions irrespective of the location, i.e. can be installed and launched on any workstation.
EgoSecure Admin Tool
  • Used to adjust EgoSecure Server settings.
  • For details about Admin Tool, please refer to Admin Tool
EgoSecure Agent (Client)
  • Uses a push/pull process to get any changes from the server.
  • Transmits all communication between the console, server, kernel driver, and user.
  • Offline management: rights changes for a system or a use outside a corporate are applied via the unblocking code.
Kernel filter driver:
  • Installed on the Windows system with EgoSecure client component.
  • Controls access rights to external devices and applications.
  • Applies the assigned permissions.
  • Enforces permissions set for offline clients.
  • Provides a high degree of security.

System Architecture

clipboard_ec2113a6d2fa4383e3d5049db35871aef.png

Communication scheme

  • The administrator controls and manages the EgoSecure Agents via the EgoSecure Data Protection Console. The Console sends defined policies to the Server.
  • The Agent refreshes rights and settings if needed:
    •  If Agent is online (connection to Server is established), it receives a server notification that an update is required. Agent takes the settings and applies them immediately. In the Polling mode, the Server saves a notification to the database. The Agent checks on a regular basis whether changes are necessary and then takes and applies them.
    • If Agent is offline (connection to Server can NOT be established), the notification is not saved to the database. Once the connection with the Sever is established, Agent takes all rights and settings and applies all of them. In the Polling mode, the Server saves the notification to the database. Agent makes a connection attempt automatically at regular intervals.
  • For details, see: Polling
  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
  2. Tags
    This page has no tags.