Pega Cloud services maintains policies to implement data-in-transit encryption for all Pega Cloud services sandbox and production environments.
Using data-in-transit encryption Pega Cloud services ensures the following network connections meet the highest industry standards and helps your application comply with your enterprise security requirements:
- Internal connections within the service, such as service-to-service and node-to-node connections.
- External connections to the service, such as Pega environment-to-client data connections.
Required client reviews following infrastructure updates
As Pega evolves your service, Pega updates this page to show the most recent protocol and cipher support changes and protocols or ciphers that your service no longer supports. After any Pega security-policy or infrastructure-update communications that include security protocol or cipher support changes, the Pega Cloud servers will negotiate from this list of ciphers in order of preference. To support this change, you should review and make certain that any of your clients (such as a Web browser) that interact with Pega services fully support the updated list.
Pega will provide this information as soon as possible so your environment security administrators and network administrators have time to prepare for upcoming changes.
Latest supported protocols and cipher suites for data-in-transit
The following table lists the ciphers that clients can and cannot use for their data-in-transit connections.
Supported Transport Layer Security (TLS) encryption settings following your next Pega Cloud services infrastructure update
|Supported TLS encryption protocols and cipher suites effective September 2021|
TLS encryption settings no longer supported following your next Pega Cloud services infrastructure update
|Unsupported TLS encryption cipher suites effective September 2021|