Join our Newsletter — 33% off our NHI Course
Home› Guides› Tridium Niagara Framework Hardening Guide: accounts, TLS, roles…
Guide OT & IoT Security

Tridium Niagara Framework Hardening Guide: accounts, TLS, roles and audit logging for stations

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 14 November 2026 13 min read
On this page

A Niagara 4 station brings HVAC, lighting, access, metering and dozens of field protocols under one web-reachable supervisor, so its accounts, certificates and services decide the security of the whole building. Tridium publishes a detailed Niagara 4 Hardening Guide covering passwords and lockout, the system passphrase, platform and station accounts, roles and categories, authentication schemes, TLS for Fox, web and platform connections, module and program signing, service settings and Syslog audit forwarding. This guide turns that material into a working baseline for owners, facilities teams, OT security leads and systems integrators who run Niagara 4 on JACE-8000 and Edge controllers and on Supervisor servers. It covers how identity works across platform and station, who should hold Super User rights, how station-to-station links, databases and other integrations should authenticate, what to log and the misconfigurations seen most often. For the wider building systems picture, read the Building Management System Security Guide first; this page goes deeper on Niagara settings.

This is an independent guide from NHI Mgmt Group, based on Tridium's public documentation as of November 2026. It is not sponsored or reviewed by Tridium. Product features change, so confirm settings against Tridium's current documentation.

Key takeaways

  • Separate platform and station identity. Platform accounts manage the host and its software; station accounts in the UserService use the station. Each needs its own named accounts, unique per project, with credentials held by the owner as well as the integrator.
  • Change the system passphrase on day one. New JACEs ship with a default passphrase that protects encrypted data and backups; set a strong one over a TLS connection and give it to the platform owner.
  • Turn on FoxS Only, Https Only and platform TLS Only. Encrypted Fox, web and platform connections with CA-signed certificates and a TLS 1.2 or higher minimum are the core of a Niagara baseline.
  • Keep Super Users rare and use two-factor for administrators. Tridium recommends the Google Authentication Scheme for admin accounts, the minimum number of Super Users, and roles and categories that match each job.
  • Forward audit logs off the box. From Niagara 4.13, Syslog in PlatformServices can send audit records over UDP, TCP or TLS to a remote server for non-repudiation, and the Security Dashboard shows the security state of each station.

How identity and access work in Niagara 4

Niagara has two identity planes, and hardening needs both.

  • Platform: the platform daemon runs the host, installs software, manages certificates and starts stations. Platform user accounts authenticate administrators who connect from Workbench. The system passphrase encrypts sensitive data and station backups on the host.
  • Station: the running station enforces its own identity through the UserService (accounts, lockout, auto logoff), the AuthenticationService (schemes such as the default Digest scheme, LdapAuthenticationScheme, the Google Authentication Scheme and ClientCertAuthScheme), the RoleService (permissions) and the CategoryService (which components a role reaches). Each user is assigned a scheme through its Authentication Scheme Name property.
  • Federation: Tridium's cybersecurity brochure lists LDAP, Kerberos, PKI and SAML 2 single sign-on, and Niagara itself can act as a SAML identity provider from Niagara 4.9. Central identity makes leaver removal reliable across a large estate. See the LDAP Security Deep Dive Guide and the SAML Security Guide.
ControlWhere it livesKey settingsWhat it stops
Password strengthAuthentication scheme, Global Password ConfigurationDefault minimum 10 characters with a digit, an uppercase and a lowercase letter; raise, never lowerGuessable station passwords
Account lockoutUserServiceLock Out Enabled (on by default), Lock Out Period, Max Bad Logins Before Lock Out, Lock Out WindowOnline password guessing
Password lifecycleAuthentication scheme and userExpiration Level (default 365 days), Warning Period, Password History Length (default 2, maximum 10), Force Reset at Next LoginLong-lived and reused passwords
Session controlUserService and userDefault Auto Logoff Period, Absolute Logoff Enabled (4.15 and later, default 7 days), Allow Concurrent SessionsAbandoned and shared sessions
Temporary accessUserExpiration propertyContractor accounts that outlive the job
AuthorisationRoleService, CategoryServiceLeast-privilege roles, categories per area or systemUsers reaching services and points they do not need
Workbench cachingWorkbench Tools, OptionsAllow User Credential Caching set to falseSaved credentials on shared laptops

Admin roles and privileged access

In Niagara the privileged identities are the platform administrator, the station Super User, and anyone holding the system passphrase.

  • Disable the default admin account: create named Super User accounts, then disable the default admin station account. Tridium also advises separate normal and emergency accounts for administrators.
  • Minimum Super Users: keep the number of Super Users as small as possible and give everyone else roles built for their job. Tridium's examples: keep file system write access to administrators, and keep users who only acknowledge alarms away from the UserService and WebService.
  • Two-factor for administrators: assign admin accounts to the Google Authentication Scheme, which pairs a password with a single-use token. See the MFA Guide.
  • One account per person: never share platform or station accounts, and make platform credentials unique per project so one integrator laptop does not unlock every site.
  • Owner custody: Tridium is explicit that the platform owner, not only the integrator, should hold and be able to change the platform credentials and the system passphrase. Hand them over at commissioning, store them in a vault and rotate them when the integrator relationship changes. The OT Third-Party and Integrator Access Guide covers the contract side.
  • Set the passphrase properly: at least 10 characters with a digit, a lowercase and an uppercase letter, set over a TLS connection in Platform Administration.

Integrations, API tokens and service accounts

Niagara stations talk to other stations, databases, mail servers, cloud services and field devices. Each connection is a non-human identity that needs its own credential, an owner and a rotation plan.

  • Station-to-station accounts: Supervisors and JACEs connect to each other with accounts. Tridium advises keeping these separate from human accounts, unique per project, and preferably authenticated with the ClientCertAuthScheme rather than passwords. Where passwords are used, rotate them when staff change. The Service Account Security Guide covers ownership and rotation.
  • Database connections: for an RdbmsNetwork with a SqlServerDatabase or similar, give the database account only the rights it needs on the external server, never a database administrator login.
  • Email and other outbound services: enable TLS on the EmailService outgoing and incoming accounts and on any other service that supports it, so service credentials are not sent in clear text.
  • LDAP binds: use TLS for LDAP so the bind credentials used by LdapAuthenticationScheme are protected, and give the bind account read-only directory rights.
  • Program objects and robots: set program.requireSigning=true in system.properties so only program objects and robots signed by trusted certificates run. Tridium's brochure also states that code modules must be digitally signed and are checked at run time; review each module's requested permissions and Purpose under Securityinfo, Policy information on the spy page.
  • Signing keys and certificates: Niagara 4.13 added a private key password option, a global certificate password option and the Niagara Signing Service. Treat signing keys and TLS private keys as machine credentials with recorded owners and expiry dates; see the Device and IoT Identity Guide.
  • Field protocols: BACnet, Modbus and other drivers usually carry no user authentication of their own; isolate them on field networks and, where devices support it, use BACnet Secure Connect. See the BACnet and BACnet Secure Connect Guide.

Logging and detection

Niagara keeps audit and security records on the station; the work is to forward them, review them and alarm on the right events.

  • Syslog forwarding: from Niagara 4.13, configure Syslog in PlatformServices, choosing UDP, TCP or TLS. Use TLS to a remote collector; Tridium recommends remote storage so records cannot be altered on the station.
  • Audit log management: back up and forward audit logs as Tridium describes, so history survives a station rebuild.
  • Security Dashboard: review the Security Dashboard under Services, Security Service regularly. Tridium describes it as a snapshot of the security configuration of your station.
  • Custom controls: As of November 2026 Tridium's guide describes implementing dual approval and alarms on audit failure with the Niagara API. Decide whether your risk needs them and document the decision.
EventSourceATT&CK for ICSResponse
Repeated failed logins and lockoutsStation audit records via SyslogT0859 Valid Accounts (attempts)Find the source; block it at the firewall or VPN
New user, role or permission changeAudit recordsT0859 Valid AccountsMatch to an approved request; review Super User changes daily
Login from an unexpected network or outside hoursAudit records, VPN and firewall logsT0822 External Remote ServicesConfirm with the account owner; disable if unexplained
Software install or module change on the platformPlatform audit and SyslogT0889 Modify ProgramCheck against the change record and signed module list
Security Dashboard state worsensSecurity DashboardNot a technique; a configuration drift signalRestore the baseline and find who changed it
New connection to Fox, web or platform portsFirewall logs and passive monitoringT0886 Remote ServicesOnly Supervisors, Workbench hosts and approved clients should connect

Send these events to the SIEM used for OT; the OT Network Security Monitoring Guide explains baselining.

Hardening baseline

Apply the baseline in this order. Test on a lab station or a single JACE first, take an encrypted backup before each change, and keep the backup and passphrase so you can roll back.

  1. Update: keep Niagara 4 on a current supported release and apply vendor security updates promptly. Tridium publishes security bulletins on product pages and through targeted communications; its product security page explains the process.
  2. Passphrase and platform accounts: change the default system passphrase, create named platform accounts unique to the project, and hand credentials to the owner.
  3. Platform TLS: in Change TLS Settings set State to TLS Only (default port 5011), choose a certificate and a protocol of TLSv1.2 or higher.
  4. Fox and web TLS: in the FoxService set FoxS Enabled and FoxS Only to true (Foxs port 4911 by default), with Foxs Min Protocol and Foxs Cert. In the WebService set Https Enabled and Https Only to true (port 443 by default), with TLS Min Protocol and Https Cert.
  5. Certificates: replace the default self-signed certificates, which encrypt but do not prove identity, with CA-signed certificates; use the Recommended cipher suite group and, from 4.11, cipherSuite.exclude.patterns to drop more suites. The TLS Server Configuration Baseline Guide covers protocol choices.
  6. Station accounts and authentication: named accounts, admin disabled, Google Authentication Scheme for administrators, lockout and password history set, and unused schemes deleted (remove AXDigestScheme if no NiagaraAX stations connect).
  7. Roles and categories: build roles per job and categories per area, and assign each user only what they need.
  8. Web service settings: set X Frame Options to Deny, Show Stack Traces to false and Require Https for Passwords to true; configure auto logoff and Absolute Logoff.
  9. Reduce services: delete or disable unused services, keep SFTP/SSH disabled on JACE-8000 (off by default) unless needed, and use niagara.remoteBlacklist.fileNamePatterns and niagara.remoteBlacklist.filePaths to block remote access to sensitive files.
  10. Signing and logging: set program.requireSigning, forward Syslog over TLS and start a regular Security Dashboard review.
  11. Network and physical: place stations behind a properly configured VPN, never directly on the internet, restrict physical access to JACEs, Edge controllers and fieldbus devices, and sanitise media before disposal. See the OT Remote Access Guide and the OT Network Segmentation, Purdue Model and IEC 62443 Zones and Conduits Guide.

Small site versus enterprise: a single building with one JACE can apply every step with local accounts, the Google Authentication Scheme and a Syslog collector. A portfolio with a Supervisor and many stations should add LDAP or SAML for people, client certificates for station-to-station links, a private CA for station certificates and Security Dashboard review at the Supervisor. In both cases, the owner should hold the passphrase and platform credentials.

Framework mapping

Baseline areaNIST SP 800-53 Rev. 5NIST CSF 2.0ISA/IEC 62443-3-3
Named accounts, lockout, expiryAC-2, IA-5PR.AAFR1 Identification and authentication control
Two-factor and federationIA-2PR.AAFR1
Roles, categories, Super User limitsAC-3, AC-6PR.AAFR2 Use control
FoxS, HTTPS and platform TLSSC-8, SC-23PR.DSFR3 System integrity, FR4 Data confidentiality
Module and program signingSI-7, CM-5PR.PSFR3
Disabling servicesCM-7PR.PSFR7 Resource availability
VPN and segmentationSC-7PR.IRFR5 Restricted data flow
Syslog and Security DashboardAU-6, AU-9, SI-4DE.CMFR6 Timely response to events

Tridium's cybersecurity brochure states that Niagara 4 is certified to ISA 62443-3-3 Security Level 4, which describes the product's capability; the security level a site achieves still depends on the settings above.

Detection and measurement

  • TLS-only coverage: percentage of stations with FoxS Only, Https Only and platform TLS Only all set.
  • CA-signed certificates: percentage of stations not using default self-signed certificates, and certificates expiring within 60 days.
  • Super User count: Super Users per station, trending down, with zero enabled default admin accounts.
  • Administrator two-factor: percentage of admin accounts on the Google Authentication Scheme or federated MFA.
  • Log forwarding: percentage of stations sending Syslog over TLS to a remote collector.
  • Owner custody: percentage of sites where the owner holds the current passphrase and platform credentials.

Common misconfigurations

  • Default passphrase kept: the factory passphrase left on a JACE, so encrypted backups and sensitive data rely on a known value.
  • Station reachable from the internet: a station published for remote convenience instead of placed behind a VPN, as Tridium's guide and CISA's OT mitigations advise.
  • One integrator credential for every site: the same platform and station passwords across a whole portfolio, held only by the integrator.
  • Station-to-station links on human accounts: a Supervisor connecting with an engineer's account, which breaks when the person leaves or is reused for logins.
  • Self-signed certificates accepted forever: TLS turned on but default certificates kept, so clients cannot verify which station they reached.
  • Audit logs only on the station: no Syslog forwarding, so evidence is lost when a station is rebuilt or altered.

Practitioner checklist

  • Change the system passphrase and give it, with platform credentials, to the owner.
  • Create named platform and station accounts, unique per project; disable the default admin account.
  • Set lockout, password history, expiry and absolute logoff; turn off Workbench credential caching.
  • Use the Google Authentication Scheme or federated MFA for administrators; delete unused schemes.
  • Build least-privilege roles and categories and keep Super Users to a minimum.
  • Set FoxS Only, Https Only and platform TLS Only with CA-signed certificates and TLS 1.2 or higher.
  • Use client certificates for station-to-station links and least-privilege database accounts.
  • Set program.requireSigning and review module permissions.
  • Forward Syslog over TLS and review the Security Dashboard on a schedule.
  • Keep stations behind a VPN, disable SFTP/SSH unless needed, and restrict physical access.

Standards and references

Related NHI Mgmt Group resources: Building Management System Security Guide · BACnet and BACnet Secure Connect Guide · OT Remote Access Guide · OT Third-Party and Integrator Access Guide · OT Security Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 14 November 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.