Understanding the Security Module

What the Security Module Enables

User roles management

Managing user roles involves assigning a role to each user that defines their level of access to various components of the solution. Each role has its permissions, which can be customized to meet the security requirements of your organization.

Managing External Users (Runtime Users)

External Users in this context refers to users who are not part of the organization but need access to specific components of the project. This can include contractors, clients, or third-party vendors. These users are typically managed via RuntimeUsers or integration with Active Directory and LDAP.

Securing Solution Configuration

The platform provides several tools to secure the solution configuration itself.  By assigning Permissions and Policies, administrators can control which users have access to specific modules, editors and documents. This ensures that only authorized users can make changes on each part the solution configuration.

Securing Runtime Execution

Securing runtime involves managing user sessions in client displays by setting password requirements, session restrictions, and e-signature settings. The platform allows administrators to monitor client connections and manage active sessions.

Users, Permissions and Policies Summary

For a summary of the Security Configuration, go to Security Module (How-to Guide), which presents the basic configuration steps and properties for Users, Permission and Policies. 

The next section presents the configuration of those elements in further details.

Working with the Security Module

Customizing Login Procedures

Modify the login page, fine-tune user validation, and incorporate custom logic into the client startup ScriptTask process for a tailored login experience.

Further User management can also be execute on Scripts.

→ Read more on Scripts, Handling Security

Applying Security to Displays

Regulate user access and interactions within displays, either by protecting the entire display, or specific commands or elements within each display.

Display Edit or Run Security

The configuration table Displays / List, has the columns EditSecurity and RunSecurity that allow to define the PermissionGroups allowed to configure, or open in runtime, each displays. 

Security within the Display

When drawing the solution User Interface, there is a Dynamic Property specifically to apply security to any Input the operator may do at the display.

→ Read more on Drawing User Interfaces / Dynamics and UI Elements, the Security Dynamic configuration. 

Configuration Interfaces

Module Components

Users

Local users defined within the solution configuration. Includes three pre-defined accounts:

• Administrator - Full system access (set password immediately)
• Guest - Anonymous/default access
• User - Generic login account

→ [Security Users (Reference)] for detailed configuration

Permissions

Role-based access control groups defining what users can access in Designer and Runtime.

Pre-defined groups: Administrator, Engineering, Supervisor, Operator, Maintenance, Guest

→ [Security Permissions (Reference)] for detailed configuration

Policies

Security requirements for passwords, sessions, and electronic signatures.

Pre-defined policies: Default, Enhanced, Critical

→ [Security Policies (Reference)] for detailed configuration

RuntimeUsers

Dynamic users from external sources:

• External SQL databases
• Active Directory integration
• LDAP server authentication
• Script-created users

→ [Security RuntimeUsers (Reference)] for detailed configuration

Monitor

Real-time view of connected users and active sessions during runtime.

→ [Security Monitor (Reference)] for detailed configuration

External Authentication

Integration with enterprise authentication systems:

• Windows Active Directory
• LDAP servers
• Custom authentication providers

→ [Windows AD / LDAP Server (Reference)] for detailed configuration

Runtime Behavior

Authentication Flow

1. Check for local Engineering User
2. If not found, check RuntimeUsers database
3. If not found, check AD/LDAP (if configured)
4. If no valid user, default to Guest

Permission Evaluation

Permissions are evaluated at multiple levels:

• Solution Level - Overall access to the solution
• Module Level - Access to specific modules (Tags, Alarms, etc.)
• Display Level - Access to specific displays
• Object Level - Access to individual controls/elements

Session Management

• Automatic session timeout based on policy
• Concurrent login restrictions
• Session monitoring via Security → Monitor
• Programmatic access via @Server.GetAllConnections()

Security Namespaces

Client Namespace

Runtime information about current user:

• @Client.UserName - Current logged user
• @Client.CurrentUser - User object with all properties
• @Client.LogOn(username, password) - Login method
• @Client.LogOff() - Logout method

Security Namespace

Security management methods:

• @Security.CreateUser() - Create RuntimeUser dynamically
• @Security.ValidateUser() - Verify credentials
• @Security.ChangePassword() - Update user password

Configuration Storage

Solution Database

Local users, permissions, and policies are stored in the solution database (.dbsln file).

RuntimeUsers Database

External users stored in:

• Default: SQLite database (Dataset.DB.RuntimeUsers)
• Optional: SQL Server, PostgreSQL, or other databases
• Encrypted storage for credentials

Security Features

Compliance Support

• FDA 21 CFR Part 11 - Electronic signatures, audit trail, password policies
• NERC CIP - Account monitoring, session management, audit logging
• ISA-99/IEC 62443 - Zone security, role-based access

Advanced Features

• Multi-factor authentication support
• Certificate-based authentication
• Single Sign-On (SSO) via AD
• Encrypted credential storage
• Session replay protection

Best Practices

Initial Setup

1. Change default passwords immediately
2. Configure policies before creating users
3. Define permission groups based on roles
4. Test authentication before deployment

Maintenance

• Review user accounts quarterly
• Monitor failed login attempts
• Update passwords regularly
• Audit permission changes
• Document security model

Troubleshooting

Related Information

• [Security Module (Concept)] - Overview and architecture
• [Security Module (How-to Guide)] - Step-by-step configuration
• [FDA 21 CFR 11 Compliance Design] - Regulatory compliance
• [High Availability (Reference)] - Redundant security servers

In This Section

• [Security Users (Reference)]
• [Security Permissions (Reference)]
• [Security Policies (Reference)]
• [Security RuntimeUsers (Reference)]
• [Security Monitor (Reference)]
• [Windows AD / LDAP Server (Reference)]

.

In this section:

Diagnostic Architecture

Logging Infrastructure

Image Removed

Scalability Factors

Security Highlights

Security and Reliability

We prioritize stability and security throughout our platform's design, from technology selection to module architecture.

Easy Configuration and Maintenance

Our platform offers secure, straightforward configuration and maintenance for various scenarios, ensuring scalability and consistency.

Operational Stability

Operational stability is guaranteed with our platform's 100% managed code implementation, featuring robust exception handling and seamless failure recovery.

Redundancy and Availability

For high availability, our platform offers redundancy with a proven hot-standby system for real-time databases, alarms, and historians, catering to diverse network setups.

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.

The platform was also designed following the applicable recommendations from NERC CIP, such as the CIP-007-1 - Cyber Security-System Management.

Title 21 CFR Part 11 is the part of Title 21 of the Code of Federal Regulations that establishes the United States Food and Drug Administration (FDA) regulations on electronic records and electronic signatures (ERES).

Part 11, as it is commonly called, defines the criteria under which electronic records and electronic signatures are considered trustworthy, reliable, and equivalent to paper records.

Listed below and described are some security-related features available in the product:

• Access Control: Security technique that regulates who or what can view or use resources in a computing environment.

• Password Encryption: System administrator does not possess access to the user password. They are encrypted before being stored.

• Maximum and Minimum Age for Password: A feature that imposes a minimum password age before allowing its change, and a maximum age before expiring.

• Required Password changing: Forces the user to alter his password after the first login has been made.

• User Name and Password Minimum Length: Establishes minimum requirements for passwords.

• Block on Invalid Login Attempt: Blocks User after reaching maximum number of invalid logins attempted.

• Store Password History: A range of the last 0-5 passwords can be stored to make sure User does not repeat an already used one.

• Auto Log Off: User is logged off the system for inactivity or expiration date.

• Audit Trail Data: Security-relevant chronological record, set of records, that provide documentary evidence of the sequence of activities that have affected at any time a specific operation.

For detailed Explanation on how to add security management in project consist with these rules, go to the page FDA 21 CRT Compliance page.

For addition information on NERC CIP-007-1 - Cyber Security-System Management, go to the page NERC CIP Overview.

Built-in .NET Security

FrameworX development is built on the .NET framework, following strict security protocols. Each module adheres to specific guidelines aligned with its function, such as FDA compliance for the Alarms module and adherence to standards like IEC61850 for modules handling electrical device communications.

Below are the main security topics along with essential details about each.

Security at the Core Level

Security implementation is ingrained at the core level rather than being applied externally. The platform's modules incorporate built-in security components designed from their very core.

For more detailed insights into security in .NET, refer to Microsoft's documentation available at: Microsoft .NET Security Information

Web Client Communication Security

HTML5 provides flexibility in choosing between "http" or "https/ssl" protocols.

The production servers will use HTTPS, but the allowing http connection on development, simplifies the early state of the projects.

The HTTPS uses TLS security. 

The TSecureGateway is a crucial part of our platform, enabling smooth data transfer across different security network zones. It serves as a bridge, moving data from lower levels, like the factory floor (Level 2), to higher levels such as the enterprise (Level 4).

Acting as a protective barrier, the TSecureGateway shields internal networks from insecure traffic. Enterprises rely on it to guard employees and users against potential threats from malicious web traffic, websites, viruses, and malware.

Files and Execution Protection

License/Softkey

The "License/Softkey" feature employs the .NET class System.Security.Cryptography.Rijndael, utilizing symmetric encryption with a key size of 256 bits.

Digital signature

All assemblies created by Tatsoft are signed digitally.

Project format (Configuration protection) 

All project settings, including security measures like cryptography, power recovery, and user/password protections, are stored in a relational database (.dbsln file). The source code and compiled binaries for Scripts and Displays are also stored in this file. This centralized storage method streamlines project management and deployment, making access and maintenance easier.

User Authentication and Permissions

User Authentication

Our platform offers integration with various systems for user authentication:

• Microsoft Active Directory and Windows Authentication
• LDAP server connection
• Built-in Users Database
• External databases or user authentication servers

Active-Directory / Windows Authentication

Enabling Windows Authentication bypasses the project's configured user list, relying on Windows policies instead. Windows manages user authentication directly, utilizing the currently logged-in Windows user for system access.

LDAP

When LDAP is used, the project ignores its configured user list and relies on policies managed by Windows and the LDAP Server. Authentication is handled by both Windows and the LDAP Server, with the external user logged into the LDAP Server being utilized within the system.

Runtime Users

The system dynamically generates users and stores their credentials in SQL databases. It seamlessly integrates with Active Directory or third-party systems to retrieve users, enabling integrated security and unified login capabilities.

Roles, Permission and Policies

Group and User Permissions

Our users have complete flexibility to define privileges based on groups or specific individuals. Permissions can be set globally or linked to particular displays, objects, or input actions, offering granular control over access levels.

User Policies

Our platform offers a comprehensive array of user management features, including identification policies, session duration control, automated logoff mechanisms, electronic signature capabilities, and robust audit-trail functionality.

Database Injection Protection

In database operations involving stored procedures, there is a significant concern about SQL injection. SQL injection can occur if parameters are passed as plain text within SQL statements, which could allow malicious code to be executed. To prevent this, we use the .NET API, where parameters are added to a command object’s parameter list. This approach makes SQL injection impossible by safely handling user input.

Security External Validation

Regularly the platform is accessed by Veracode, or third-party companies, on penetration testing report, gap analysis, and various other topics.

Any issues that would prevent a 100% approval are corrected.

Security & Users

Overview

Security & Users management in FrameworX 10.1 provides comprehensive access control, authentication, authorization, and audit capabilities to protect your industrial systems. This guide covers user management, role-based security, integration with enterprise authentication systems, and cybersecurity best practices following industry standards including ISA-99/IEC 62443.

Security Architecture

Defense in DepthSecurity Zones (ISA-99/IEC 62443)

Image Removed

User Management

User Account Types

SecureGateway module simplifies connecting Level 3 and Level 4 opeartoins 

Creating Users

Manual User Creation

1. Navigate to Security → Users
2. Click New User
3. Configure user properties:

User Configuration:
??? Identity
?   ??? Username: john.smith
?   ??? Full Name: John Smith
?   ??? Email: jsmith@company.com
?   ??? Employee ID: EMP001
??? Authentication
?   ??? Type: Forms / Windows / Certificate
?   ??? Password: (if Forms)
?   ??? Domain: COMPANY (if Windows)
??? Authorization
?   ??? Role: Operator
?   ??? Groups: [Production, Maintenance]
?   ??? Areas: [Line1, Line2]
??? Settings
    ??? Account Enabled: Yes
    ??? Password Expires: 90 days
    ??? Session Timeout: 20 minutes
    ??? Concurrent Sessions: 1

Bulk User Import

csv

# Users.csv format
Username,FullName,Email,Role,Groups,Password
jsmith,John Smith,jsmith@company.com,Operator,"Production,Line1",TempPass123!
mjones,Mary Jones,mjones@company.com,Supervisor,"All",TempPass456!
bwilson,Bob Wilson,bwilson@company.com,Engineer,"Engineering",TempPass789!

Import process:

1. Prepare CSV file
2. Security → Users → Import
3. Map columns
4. Validate and import
5. Force password change on first login

Password Policies

Password Requirements Configuration

Password Complexity Rules

Requirements (3 of 4):
? Uppercase letters (A-Z)
? Lowercase letters (a-z)
? Numbers (0-9)
? Special characters (!@#$%^&*)

Additional Rules:
? Cannot contain username
? Cannot contain common words
? No sequential characters (123, abc)
? No repeated characters (aaa)

Role-Based Access Control (RBAC)

Predefined Roles