Answer

Planview Hub is secured on various levels. At the highest level, virtually all the servers, traffic and data are contained within a customer firewall. Hub is an on-premise tool and the hardware where it is installed is maintained by our customers. This provides a very secure environment provided the customer's environment and tools are properly secured as well. 

The web application runs on Tomcat web servers and is configured to use SSL. To learn more about this, please see the HTTPS Configuration section of the User Guide. All calls made to Hub from a Hub Administrator are checked against a separate User Management server to verify the user is authenticated. Additionally, the customer is able to set various password rules such as minimum length, special characters, re-set interval, etc. Hub can also be configured to connect to a customer's LDAP server. To read more about the User Management, please go to User Management.

Hub connects to customer repositories via publicly available APIs. Hub relies on repository credentials supplied by the customer for access. These repository credentials are stored in an encrypted form in the Operational Database and are not visible to the Hub Administrator. Customers must provide a Master Password upon install which is used to encrypt the repository passwords. This is covered in more detail in the Master Password Configuration section of the User Guide.

The Gateway add-on allows for inbound webhooks and listens via HTTPS. Customers are able to create unique UUIDs to listen for specifically formatted inbound information. For more details about Gateway integration styles, see the Create via Gateway and the Modify via Gateway sections in the User Guide.

Planview Hub communicates with the Operational Database via a customer-supplied JDBC driver and customer-provided credentials. The Operational Database is installed within a customer's environment and should participate in the customer's backup plan. 

The Enterprise Data Stream add-on allows a user to flow artifact information to a central database for reporting. Hub communicates with the Enterprise Data Stream database via a customer-supplied JDBC driver and customer-provided credentials.The Enterprise Data Stream database is installed within a customer's environment and should participate in the customer's backup plan. For more details on Enterprise Data Stream, see the Enterprise Data Stream section in the User Guide.