Secure System Platform
- Last UpdatedOct 27, 2026
- 4 minute read
AVEVA System Platform comprises a suite of applications including InTouch HMI, Industrial Application Server (IAS), Operations Management Interface (OMI), AVEVA Historian, Communication Drivers, and other supporting components.
This section is designed primarily for process control engineers and IT professionals who are familiar with standard IT practices, Windows domain engineering and administration, and process control or SCADA environment requirements. Content is derived from AVEVA testing documentation.
Topics with security impact are divided into deployment and installation phases.
System Platform deployment references
The following table provides references documented in System Platform deployment guides.
|
Security Area |
Topics |
Summary |
|---|---|---|
|
AVEVA security perspective |
The AVEVA approach to site networks and control system security is driven by the following principles:
|
|
|
Secure System Platform |
System Platform security is directly related to infrastructure (servers, workstations, ethernet cables, fiber optics, switches, routers, firewalls, etc.) as well as hosting software, including operating systems, virus protection, and intrusion protection software. |
|
|
Security considerations |
The number one criterion when securing an industrial control system is defining and understanding the data that needs to be secured. Doing so can help identify potential vulnerabilities. |
|
|
Common security evaluation |
Summary of common security evaluation topics:
|
|
|
General information about security infrastructure |
Summary of security infrastructure topics:
|
|
|
Secure visualization clients |
System Platform includes two visualization clients: InTouch HMI and AVEVA Operations Management Interface (OMI). AVEVA OMI is an advanced visualization client built into Application Server and directly leverages the Application Server security model and settings. |
|
|
Secure the configuration environment |
The System Platform IDE extends the security models of traditional industrial automation applications to incorporate the configuration actions as well as the run-time actions. |
|
|
Secure distributed communication ( DCOM) |
AVEVA has replaced DCOM in Application Server with the more secure option of gRPC beginning with the release of System Platform 2023. Support for DCOM continues for backward compatibility mainly in the aaPIM component in Application Server and by the Communication Drivers Pack (CDP). |
|
|
Summary of security recommendations |
Modern industrial automation requires direct interaction between machines performing specific functionality within an intelligent enterprise. |
System Platform installation references
The following table provides references documented in System Platform installation publications.
|
Security Area |
Topics |
Summary |
|---|---|---|
|
SQL Server |
||
|
Prepare for System Platform Installation |
Before you begin the installation program, you need to prepare your system. |
|
|
SQL Server rights requirements |
When you install a Galaxy Repository or Historian node, the installation process creates or modifies new user groups, SQL Server logins, and a user account (Network Account). |
|
|
Set the SQL Server security mode |
If you are an SQL administrator, you can use the SQL Access Configurator to set user privileges within SQL Server for accessing and using Galaxy databases (the Galaxy Repository) |
|
|
Restore required SQL Server accounts |
If you delete the aaAdministrators group, Network Account, or the aaGalaxyOwner account, restore them by running the SQL Access Configurator. |
|
|
Network |
||
|
Windows network configuration |
If you are installing System Platform products on more than one node, we recommend that you use domain based networking. Domain based (client-server) networks provide better user account security and management than workgroup based (peer to peer) networks. |
|
|
User accounts |
||
|
Network account |
The Network Account is a user name and password combination that enables inter-node communication between all System Platform computers. |
|
|
About network account privileges |
When you install System Platform, you can choose to have the system automatically create the Network account on the local computer. However, a domain account is preferable to a local account. |
|
|
Adjust accounts during System Platform upgrade |
If you are upgrading from an earlier version of System Platform, and the existing Network Account (called ArchestrA User in prior releases) is a system Administrator, you are prompted to either: Remove the Network Account from the Administrators group to enhance security. Keep the Network Account as a system Administrator. You may want to keep the Network Account as a system Administrator, if it is leveraged by other applications and needs elevated privileges. See Upgrading the Wonderware System Platform for more information. |
|
|
Component configuration |
||
|
Install System Platform, AVEVA web client configuration requirements |
For apps that will be used with the OMI web client:
|
|
|
Configure System Platform components |
Configure System Platform components using the Configurator dialog box after installation. Most of the listed items have security impact, either in terms of system topology or security policies and configuration. |
|
|
Security and permissions:
|
Security and permissions can be configured during System Platform installation. |
|
|
User accounts and groups created by System Platform installation (OS groups and accounts):
|
This section of the System Platform Installation Guide describes the user accounts and groups used by System Platform, divided by product. |