(Update with the copy of version: 9.0.0DRAFT) |
|||
Line 4: | Line 4: | ||
*Cross Site Request Forgery Protection | *Cross Site Request Forgery Protection | ||
{{NoteFormat| | {{NoteFormat| | ||
− | + | Genesys does not recommend deploying Web Services and Applications with Internet accessibility without additional security controls such as IP White-listing restrictions.}} | |
==Transport Layer Security== | ==Transport Layer Security== |
Revision as of 04:38, March 12, 2020
Configuring Security
Genesys Web Services and Applications follows security guidelines to minimize risks as outlined in the Open Web Application Security Project (OWASP) Top 10. It has adopted several methods of ensuring security, for example:
- User sessions have a timeout option.
- Cross Site Request Forgery Protection
Important
Genesys does not recommend deploying Web Services and Applications with Internet accessibility without additional security controls such as IP White-listing restrictions.Transport Layer Security
Transport Layer Security (TLS) is available only in Kubernetes-based deployment. This is not available in Docker Compose-based deployment.
To enable Ingress secured endpoint configuration for Web Service and Applications, the customer perform changes in the Environment File during the deployment. While editing the parameters.yaml file, the ingressTlsEnable variable is set as true to enable TLS.
For more details, refer to Deployment of Web Services and Applications in Kubernetes.
Comments or questions about this documentation? Contact us for support!