Security Overview

GENESIS64 uses a security model that is both granular and additive. You can set individual rights and access based on users and groups, create named policy settings that can be applied to users and groups, and control access to individual applications, features, systems, and more based on time settings if you wish. The Security Server offers a powerful means for configuring access to your applications. The security model evaluates the membership of users and groups and will deny access to a user when that feature is denied to them regardless of the group's access rights. However, if a user's access isn't specified as denied or allowed then the group membership sets the access policy.

The security system contains two components:

The Security Server which manages user logins (for more information, refer to Logins and Passwords), and

Security system clients contained within the applications in the GENESIS64 family (e.g., GraphWorX64 , TrendWorX64 , AlarmWorX64 , etc.). Any information that causes a change in security status (e.g., a user login or logout) will be immediately posted to the affected clients.

Security settings are configured in the Security node in Workbench. Here is your road map to defining security:

Learn the basics what of Security Server can do; refer to Security to learn how to open Security Server and define an initial Administrator account.
Define your global settings; refer to Global Settings.
Define a default account policy, and optionally override the default with more specific or tailored account policies; refer to Account Policies. You may also want to read more about passwords by referring to Logins and Passwords.
Define user groups and user accounts; refer to Users and Groups. Supplemental information is provided in Security Privileges for Users and Groups and Wildcards and Performance Optimization.