Home › Technical articles

Đọc bằng tiếng Việt

AVEVA System Platform security: System Management Server, certificates, encrypted SuiteLink and Galaxy roles

TDL Industrial Automation · Last updated:

From AVEVA's System Platform 2026 documentation: what the System Management Server does, generated or IT-provided certificates, encrypted SuiteLink and mixed mode, NMX, gRPC, trust boundaries, Galaxy security modes, roles and classifications, the Network Account, SQL Server, ports and anti-virus exclusions.

AVEVA System Platform 2026 secures the traffic between its nodes through one System Management Server (SMS): every node connects to it and gets a certificate it signs, and the same Configurator settings decide whether SuiteLink and NMX accept unsecured connections. Galaxy security in the IDE decides who may change which attribute. This article follows AVEVA's 2026 documentation for System Platform, Application Server, InTouch HMI, Historian and the Communication Drivers Pack. Network Account basics and fault finding are in System Platform troubleshooting; zones and conduits are in IEC 62443.

System Platform 2026: one SMS, secured links between nodesAt the top, the System Management Server, only one for the whole topology, on an AVEVA node or a separate machine; it signs node certificates and sets the SuiteLink mode, NMX access and ports. Each node connects to it in the Configurator, downloads the root certificate and gets its own certificate signed by the SMS. In the middle, five node types: Galaxy Repository, redundant AppEngine pair, Historian, driver node and InTouch or OMI clients. Below, five links: SuiteLink is TLS-encrypted when both nodes use the SMS, with mixed mode off on new installations; GR operations run over gRPC instead of DCOM; NMX is DCOM-based and on new installations open only to some groups and accounts; HCAP between redundant AppEngines needs secure communication, so redundant nodes do not work without the SMS; Historian Client Web and the REST API use HTTPS with an X.509 certificate. Based on AVEVA System Platform 2026 documentation.System Platform 2026: one SMS, secured links between nodesSystem Management Serverone per topology, on an AVEVA node or a separate machinesigns node certificates · SuiteLink mode · NMX access · portsEach node connects to the SMS in the Configurator, downloads the root certificate and gets itsown certificate signed by the SMSGalaxyRepositoryIDE, deployAppEngine pairredundant, HCAPHistoriansecure web accessDriver nodeSuiteLink serverInTouch, OMIclientsSuiteLink client,web clientSecured linksSuiteLinkInTouch, driversTLS-encrypted when both nodes use the SMSnew installation: mixed mode off, unencryptedconnections refusedupgrade: mixed mode on, reset after the node-by-node upgradeGR operationsdeploy, undeploy, start, stoprun over gRPC instead of DCOMreconfigure gRPC after any change to the SMSNMXbetween platformsDCOM-basednew installation: only aaRuntimeUsers, Administrators,Network Account, local systemHCAPredundant AppEngine pairneeds secure communicationredundant nodes do not work without the SMSHistorianClient Web, REST APIHTTPS with an X.509 certificateself-signed: trust it on every clientBased on AVEVA, System Platform 2026, Application Server 2026 and Communication Drivers Pack 2026documentation: System Management Server node, Communications tab, Certificates tab, Configure SecureCommunication, the Historian HTTPS page (read 17 November 2026). Figure: drawn by TDL.
Figure 1: System Platform 2026: one SMS, secured links between nodes. On a phone, swipe sideways to see the whole figure.

1. The System Management Server

The SMS belongs to the Platform Common Services and is set up in the Configurator under Common Platform. Its jobs, per AVEVA: secure communication between nodes, data synchronisation between redundant AppEngines, installation type and licence mode, inter-node ports, the SuiteLink security mode and NMX user access, certificate management, and single sign-on through OpenID Connect with an external identity provider.

There should be only one SMS in the topology; a second one can disrupt communication. It runs on a node with an AVEVA application or on a separate machine. When a system older than 2017 Update 3 is upgraded, the installer puts it on the Galaxy Repository (GR) node; in a multi-Galaxy system only one GR node is the SMS.

AVEVA calls the SMS highly recommended, and it is required for:

  • Redundant AppEngines. Their HCAP instance synchronises tags and store-and-forward data over secure communication, so redundant nodes do not work without the SMS, and AVEVA warns of data loss.
  • Multi-Galaxy communication.
  • The OMI web client and the connected experience, Azure AD or CONNECT federation.

To connect a node, choose Connect to an existing System Management Server in its Configurator; the user must be in aaAdministrators or Administrators on the SMS machine. The SMS shows a security code when configured, and AVEVA asks to check that it matches on each connecting node, because trusted machines pass traffic freely. Name the SMS by its fully qualified domain name, as AVEVA recommends; an IP address may cause errors.

AVEVA warns not to change the SMS configuration after deployment: nodes can lose connectivity, and each change means re-registering Identity Manager for Application Server and InTouch and reconfiguring Application Server gRPC. The No System Management Server configured option is meant only for temporary troubleshooting and lets SuiteLink fall back to unencrypted connections. A Redundant SSO server backs up single sign-on only; clients still register with the SMS.

2. Certificates

On the Certificates tab of the Advanced settings the source is Automatically Generated (default) or Provided by IT, imported into the Root, Intermediate or Personal store. Generated certificates renew automatically on the SMS and the remote nodes, and every product should be able to reach the SMS for renewal; certificates from IT must be renewed by IT. A connecting node downloads the root certificate from the SMS (automatic option only), and its own certificate is generated locally and signed by the SMS. Certificates sit in the Windows Certificate Store; SuiteLink uses the same SMS certificate, visible in certlm.msc.

AVEVA's general guidance: a self-signed certificate is secure only if you control both server and client; certificates from a public CA, or domain-issued ones from Active Directory Certificate Services, must be renewed at regular intervals.

Under CIS Level 2 or DISA STIG, the browser policy RequireOnlineRevocationChecksForLocalAnchors makes Edge and Chrome check revocation online. Certificates generated by System Platform carry no revocation data, so License Manager and the AVEVA Web Client may not open. AVEVA prefers an Enterprise CA certificate with a CRL distribution point or OCSP address the clients can reach; the alternative is to disable that policy.

The pages do not say what happens when a certificate expires or a node is renamed.

3. Encrypted links between nodes

Link What the 2026 documentation says
SuiteLink (InTouch, drivers) mixed mode disabled is the default for new installations: a connection succeeds only if it is encrypted and both nodes use the SMS; mixed mode enabled is the default after an upgrade
NMX between platforms DCOM-based; a new installation allows it only for aaRuntimeUsers, Administrators, the Network Account and the local system account; an upgrade allows all users
GR operations deploy, undeploy, start and stop run over gRPC instead of DCOM, enabled under Secure Communication; gRPC should always stay enabled
IDE to GR, clients to services secure gRPC in Application Server 2026, replacing DCOM and WCF
OPC UA service with Galaxy security enabled, encrypted communication to the OPC UA clients must also be enabled
Historian Client Web, REST API HTTPS with an X.509 certificate; a self-signed one is installed in Trusted Root Certification Authorities on each client to avoid browser warnings
SQL Server Force Encryption in SQL Server Configuration Manager; Application Server supports Encrypt=true with trust server certificate

AVEVA recommends mixed mode and open NMX access only during a node-by-node upgrade or for legacy applications, reset afterwards; each change needs a restart. slsping <machine name> <driver name> from an administrator prompt shows SL V3 SUCCESS for a secure link, SL V2 SUCCESS for an unsecure one. A secure SuiteLink server runs as SYSTEM or as a member of ArchestrAWebHosting, and the TLS handshake times out after 20 seconds by default (registry value TLS_Timeout). Standard-user cases where WindowViewer connections fail are in InTouch troubleshooting.

DCOM remains for aaPIM (ports 49152 to 65535, not configurable) and the Communication Drivers Pack (port 135).

Trust boundaries, new in 2026, are set on the SMS node. In Universal Mode the SMS holds the boundary: every AVEVA application connected to it is inside and Galaxies pair automatically. Classic Mode keeps the boundary in the GR with explicit Galaxy pairing, as up to System Platform 2023 R2 SP1 P04. After an upgrade from such a version, the SMS plugin shows Warning and must be reconfigured.

On the TLS version AVEVA's pages differ: the data protection page says traffic between SMS-enabled nodes uses TLS 1.2, while the client-server page says System Platform 2026 supports TLS 1.3, enabled by default on compatible Windows versions.

4. Galaxy security: modes, roles and classifications

A new Galaxy has no security. The IDE offers four authentication modes: Galaxy, OS User Based, OS Group Based, and Authentication Providers (AVEVA Identity Manager with Azure AD or CONNECT). Galaxy mode is not supported for multi-Galaxy systems, ViewApp credentials or the OMI web client. For a domain, the deployment guide recommends OS Group based security for Application Server and ArchestrA security in InTouch WindowMaker (InTouch application types: InTouch HMI or System Platform). In every mode, connecting from the IDE needs the aaConfigTools group or Run as administrator.

By default the users DefaultUser and Administrator and the roles Default and Administrator have full access, with one security group, Default. AVEVA asks to change both passwords once security is on, to cut the Default role to what every user needs (every user gets it), and not to log in as Administrator, a reserved name. Device integration objects (DI and RDI) belong in a separate group only administrators can reach.

Each writable attribute has one of seven security classifications (value names as AVEVA lists them):

Classification Who can write it at run time
FreeAccess anyone, even without permissions on the object, for time-critical actions
Operate users with Operate permission, for setpoints and commands
SecuredWrite Operate permission, plus user name and password at each write
VerifiedWrite as SecuredWrite, plus a second user with Can Verify Writes
Tune users with Tune permission, for alarm setpoints and PID sensitivity
Configure users with Configure permission, with the object off scan first
ViewOnly nobody

Roles grant operational permissions per security group: acknowledge and shelve alarms, modify alarm modes and plant states, verify writes, and modify Operate, Tune or Configure attributes. Secured and verified writes are logged with signer, verifier, comment and reason, and work only when both Galaxy and InTouch security are enabled.

5. Accounts, SQL Server and Windows

Since 2017 Update 3 the Network Account is no longer in the Windows Administrators group; an upgrade from 2017 Update 2 or earlier asks whether to remove it, which AVEVA recommends for security. An existing account used for it joins aaAdministrators, which has no system admin rights. AVEVA recommends denying it RDP and interactive logon by group policy; the Diagnostic Manager flags an existing account missing from Deny log on locally and Deny log on through Remote Desktop Services. Change it only with the Change Network Account utility (aaAdminUser.exe), followed by a restart.

Enhanced Security mode in the SQL Access Configurator, the default, removes sysadmin from the NT AUTHORITY\SYSTEM and aaAdministrators logins; Legacy mode gives authenticated users sysadmin, and changing modes restarts the computer. On the Historian, give default SQL logins such as aaUser and aaAdminUser new passwords or delete them. Application Server does not support the Windows FIPS policy, which must be disabled. AVEVA recommends a domain, does not support mixed workgroup and domain nodes, and says not to put the GR on a domain controller.

6. Ports, firewall and anti-virus

AVEVA's 2026 ports page says every destination port must allow inbound connections. The ones tied to security:

Port Used for
TCP 80, 443 Platform Common Services; SMS HTTP and HTTPS by default, the same numbers on remote nodes
TCP 443 Bootstrap gRPC
TCP 7084, 7085 system authentication during node registration
TCP 5026 NMX service
TCP 5413 SuiteLink
TCP 32565 Historian Client Access Point NG
TCP 135 RPC (Bootstrap), DCOM for the drivers
TCP 49152–65535 Application Server components, only when no SMS is configured
TCP 1433 SQL Server

AVEVA's guidance is to open only the ports in use and close the rest, as in our firewall article for Rockwell systems. The Application Server security chapter adds: install with an administrator account and run with a non-administrator one, keep Windows on mainstream support with updates in planned shutdowns, enable Windows Firewall, disable Remote Desktop and file sharing, use BitLocker on mobile computers or those outside a secure facility (at some performance cost), and never expose the control network directly to the internet.

For anti-virus, exclude the Historian's history block folders. The 2026 release notes add two Microsoft Defender exclusions: C:\Program Files (x86)\Common Files\ArchestrA\Services when the IDE's Configure Services window is slow, and C:\Windows\Installer temporarily during an air-gapped installation. AVEVA's Cybersecurity Deployment Guide (full edition November 2025, focused on HMI environments) gathers many of these topics, and the Application Server chapter recommends NIST SP 800-82 Revision 3.

What we check first

This is TDL's practice, not an AVEVA requirement.

  • How many SMS nodes the Configurator lists, and whether all nodes point to one by FQDN.
  • SuiteLink mode and NMX access per node, with slsping; mixed mode left on after an upgrade.
  • The certificate source; for IT certificates, expiry dates and who renews them.
  • The Galaxy security mode, the Default role's permissions, and the members of aaConfigTools and aaAdministrators.
  • The Network Account's groups and logon rights.
  • Firewall rules against the ports list, and anti-virus exclusions.
  • A current Galaxy backup before any change to the SMS or to Galaxy security.

How TDL approaches it

TDL Industrial Automation is a System Integrator member of the AVEVA Partner Ecosystem. At SEHC, TDL maintains and upgrades the facility and power monitoring systems, built on ControlLogix and AVEVA System Platform, under a yearly maintenance contract. VLAN segmentation, firewalls and secure remote access following IEC 62443 zone and conduit principles: Industrial networks and OT security. More: AVEVA system integrator in Vietnam.

Frequently asked questions

What does the System Management Server do in System Platform?

It secures communication between System Platform nodes: each node connects to the one SMS and gets a certificate it signs. AVEVA also lists synchronising data between redundant AppEngines, the SuiteLink security mode, NMX user access, inter-node ports and single sign-on through an external identity provider.

Can System Platform run without a System Management Server?

AVEVA intends the No System Management Server configured option only for temporary troubleshooting. Redundant AppEngines, multi-Galaxy communication and the OMI web client need the SMS, and without it SuiteLink is set to allow unencrypted connections.

Why does a SuiteLink connection fail on a new 2026 installation?

Mixed mode is disabled by default on new installations, so a SuiteLink connection succeeds only if it is encrypted and both nodes use the System Management Server. AVEVA advises mixed mode only during a node-by-node upgrade or for legacy applications; slsping shows SL V3 for a secure link.

Should the SMS use its own certificate or one from IT?

Automatically generated certificates are the default and renew automatically; certificates from IT must be renewed by IT. Under CIS Level 2 or DISA STIG browser policies, AVEVA prefers an Enterprise CA certificate with a reachable CRL distribution point or OCSP address.

Which Galaxy security mode suits a domain?

The deployment guide recommends OS Group based security for Application Server in a domain, with ArchestrA security in InTouch. Galaxy mode is not supported for multi-Galaxy systems or the OMI web client.

Sources

Read 17 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
Industrial networks & OT security AVEVA (Wonderware)