/
PUC Data Security

PUC Data Security

 

  1. The only way to communicate to a PUC from the Internet is from responses to the PUC’s request via HTTPS. This prevents an outside entity from sending unsolicited traffic to a PUC.

  2. PUC connects to an open port on the customer-provided Internet Switch via Ethernet cable for a secure and reliable communication path. Ethernet provides the best form of local security since it requires a physical connection to an Ethernet network, and thus, the traffic cannot be detected without physically connecting to the network.​

  3. PUC Cloud follows security best practices by using TLS v1.2 and v1.3 for all in transit encryption.

  4. The PUC database and UI assets needed for the PUC tablet software are hosted on Amazon Web Services (AWS), taking advantage of all security and resiliency capabilities offered by AWS. The PUC API and web-based configuration tool are hosted on Heroku, which runs on AWS instances. Personally identifiable information (PII) that may be collected to facilitate order fulfillment include a customer’s name and phone number. PII is deleted once an order is fulfilled. No PII is saved beyond the life cycle of an order.

  1. Communication between the web portal and the API and database are encrypted in transit, using TLS v1.2 and v1.3.

  2. Access keys for the configuration tool can only be generated by an administrator at Powerhouse Dynamics. At rest keys are encrypted using bcrypt and are stored using AES 128-bit encryption.

Related content