PowerConnect for SAP Solutions
Auto Light Dark
Auto Light Dark

PowerConnect Cloud Deployment Settings and Security Recommendations

This page lists the settings to review when deploying PowerConnect Cloud. PowerConnect's defaults assume it runs on a trusted internal network. If that does not describe your environment, apply the recommendations below.

Network

Ports

Port

Default

Set with

Used for

Should be reachable from

Web UI and API

3000 (TCP)

PORT or the PowerConnect UI

Browser access, the REST API, HTTP listener inputs

Administrators, API clients, and systems that send to HTTP listener inputs

Cluster

5701 (TCP)


Communication between cluster nodes

The other PowerConnect Cloud nodes only

Syslog listener inputs

Set per input

Input configuration

Receiving syslog

The systems that send syslog to that input only

The web port and syslog listener ports listen on all network interfaces. Use a host or network firewall to limit who can reach them.

Clustering

  • Run cluster nodes on a private network that only they, and the systems they must reach, can access.

  • Allow TCP 5701 inbound on each node from the other nodes only, and block it from everywhere else. No other ports are needed for clustering.

  • Set CIDR_BLOCK to the network the nodes use to reach each other, for example 10.130.0.*. PowerConnect then listens for cluster traffic on that interface only. See Cluster configuration for the accepted formats.

HTTPS for the web UI and API

By default, the web UI and API use HTTP. Use HTTPS whenever the network between users or API clients and PowerConnect is not fully trusted.

You can do this in one of two ways:

  • Terminate TLS in front of PowerConnect with a reverse proxy or load balancer, and restrict the PowerConnect port so that only the proxy can reach it.

  • Enable HTTPS in PowerConnect by enabling SSL on the web sever. PowerConnect then serves HTTPS only, on PORT, using a certificate and private key held in the PowerConnect keystore.

POWERCONNECT_SECRET

POWERCONNECT_SECRET protects PowerConnect's keystore, which holds stored credentials, certificates and keys.

  • Use a long, random value.

  • Use the same value on every node in a cluster.

  • To change it, follow this guide.

PowerConnect will not start without POWERCONNECT_SECRET. If the value does not match the keystore, PowerConnect logs Failed to load keystore at startup, and stored credentials will not work.

Access to PowerConnect

  • Change the default administrator password as soon as PowerConnect is installed.

  • Use single sign-on (SAML) where possible, so that access follows your identity provider's policies.

  • Give users the least access they need. Assign the Inputs Manager or Outputs Manager role to people who only manage inputs or outputs. Give the Administrator role only to people who manage PowerConnect itself.

HTTP and syslog listener inputs

  • HTTP listener inputs receive events at /ingest/http/<input id>/<token> on the web port. The token is part of the URL, so use HTTPS, and keep proxy access logs that record URLs private.

  • Syslog listener inputs accept plain, unencrypted TCP. Limit each listener port to the systems that send to it.

The host

  • Run PowerConnect as a dedicated, non-root user.

  • Restrict the PowerConnect home directory (POWERCONNECT_HOME) to that user.

  • Include the PowerConnect home directory in your backups. Store the backups securely.

Monitoring and updates

  • Configuration changes are recorded in the audit log, logs/audit.log in the PowerConnect home directory. Collect it with your other security logs.

  • Keep PowerConnect, and the Java runtime it runs on, up to date.