Security, Compliance and Redundancy
The security module provides various security measures to protect the system and its data, including access control, user authentication, and data encryption. It enables users to define and manage user roles and permissions, limiting access to specific areas of the system based on user roles and privileges.
The module also supports multi-factor authentication and includes features such as audit trails and activity logs, which track user activity within the system, providing a detailed record of who accessed what data and when. This helps detect and investigate security breaches and identify potential security threats.
The security module also supports various industry-standard security protocols, including Secure Sockets Layer (SSL) and Transport Layer Security (TLS), which provide secure data transmission between the system and other devices or applications.
On this page:
Table of Contents | ||
---|---|---|
|
Key Functionalities
Security
FDA 21 CFR Part 11 and NERC
The software platform has a range of security and compliance features that can be used to help organizations meet the requirements of FDA 21 CFR Part 11. It is important to note that compliance is an ongoing process, and therefore, organizations should regularly monitor and update their systems and policies to ensure adherence to the standards established by the FDA.
Built-in .NET Security
The FrameworX development is based on .NET, using managed code, following security guidelines, where the development with .NET managed code must follow the .NET rules. There are specific guidelines followed for specific modules. For example, the Alarms adherence to the FDA guidelines are followed, for Electrical device communications with the IEC61850, or the other IEC are followed. Below are the main FS-Security topics and some basic information about them.
Group and User Permissions
The platform offers Total flexibility to define privileges based on groups or specific users. Permissions can be global or tied to a specified specific display, object , or input action.
Runtime Users
Dynamically create users and store credentials in SQL databases. Get users from Active-Directory or third - party system for integrated security or unified login.
User Policies
Identification policies, session duration, control, automated logoff, e-sign, audit-trail , and a bundle complete set of user management features is are available.
FDA and NERC Regulated Applications
Our platform allows delivering applications in compliance with Title 21 CFR Part 11, and it was designed following the applicable recommendations from NERC, such as the CIP- 007-1-Cyber Security-System Management.
Core-Level Security
Security must be implemented at the core, not applied externally. Our modules have built-in security-related components designed from the core.
Tip |
---|
Redundancy switch time and high-volume data were tested to meet rigorous offshore requirements. |
Redundancy
Hot-standby Fault-tolerant Servers
Reliable, easily configurable redundancy, for seamless failover; FrameworX The platform automatically initializes and continues to synchronize the primary and secondary serversserver. The Device communication channels are also easily set up setup for redundant physical networks and redundant PLC nodes.
Database Redundancy
The Alarm and Historian databases database can be assigned to a third-party external cluster or replicated automatically when running on the platform's FrameworX servers.
Project Configuration Synchronization
Engineering tools provide features to simplify configuration and updates in redundant scenarios.
Hot-swapping
Redundant or stand-alone servers allow dynamic switching of project versions, without interrupting service for connected clients and keeping the real-time database loaded.
Redundancy at the Core
LevelLevel
All modules (Real-Time tags, Devices, Alarms, HistoriansHistorian, Scripts, Clients, and others) all modules were designed from the ground up to meet redundancy and hot-swapping requirements.
Redundancy can be set for each Execution Profile (Development, Testing and Production) individually!
Info |
---|
Learn more at Security, Users and Roles. |
In this section...
Page Tree | ||||
---|---|---|---|---|
|