Learn about security best practices for PI Connector for UFL

Adhere to the following security guidelines for the individual channels. For an overview of the channels, see Introduction to PI Connector for UFL.

• File channel

  AVEVA recommends setting correct permissions for the Windows directory files that the connector reads. Only data consumers and data producers should have write access to the configured files.

• REST Client channel

  By default, PI Connector for UFL verifies the validity of a certificate provided by the server to which the connector communicates. The option for verifying the certificate validity is configurable. For further information, see Configure purge time/output path/REST channel authentication. AVEVA recommends not disabling the option for verifying the certificate validity, but rather adding the untrusted server's certificate to a trustStore on the connector machine. Microsoft Management Console (MMC) provides the Certificates snap-in for MMC. See the Microsoft TechNet article Using the Certificates MMC Snap-in.

• REST Server channel

  By default, the REST Server channel uses https transport. AVEVA recommends using basic authentication and a strong password to protect it. In order to prevent from denial-of-service attacks (DoS attacks), AVEVA recommends using the connector on an isolated network or behind a firewall.