Jump to: navigation, search
(Update with the copy of version: 9.0.0DRAFT)
(Update with the copy of version: 9.0.0DRAFT)
 
(3 intermediate revisions by 3 users not shown)
Line 4: Line 4:
 
*Cross Site Request Forgery Protection
 
*Cross Site Request Forgery Protection
 
{{NoteFormat|
 
{{NoteFormat|
−
Web Services and Applications is in the final phases of security testing and hardening. Therefore, Genesys does not recommend deploying Web Services and Applications with Internet accessibility without additional security controls such as IP White-listing restrictions, until the security testing and hardening are complete.}}
+
Genesys does not recommend deploying Web Services and Applications with internet accessibility without additional security controls such as IP whitelisting restrictions.}}
  
 
==Transport Layer Security==
 
==Transport Layer Security==
  
−
Transport Layer Security (TLS) is available only in Kubernetes-based deployment. This is not available in Docker Compose-based deployment.  
+
===Docker Compose===
 +
To enable secured endpoint configuration for Web Services and Applications, edit the '''common-env''' file and set '''GWS_HTTPS_ENABLE''' to <tt>true</tt>.
 +
For more details, [[Documentation:HTCC:Dep:SimplifiedLabDeployment|Deployment of Web Services and Applications in Docker Compose]].  
  
−
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 <tt>true</tt> to enable TLS.
+
===Kubernetes===
 +
To enable ingress secured endpoint configuration for Web Services and Applications, edit the '''parameters.yaml''' file and set '''entryPoint.external.ingress.tlsEnable''' to <tt>true</tt>.
  
 
For more details, refer to [[Documentation:HTCC:Dep:InstallingAndDeploying|Deployment of Web Services and Applications in Kubernetes]].
 
For more details, refer to [[Documentation:HTCC:Dep:InstallingAndDeploying|Deployment of Web Services and Applications in Kubernetes]].
  
 
[[Category:V:HTCC:9.0.0]]
 
[[Category:V:HTCC:9.0.0]]

Latest revision as of 20:54, September 28, 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 whitelisting restrictions.

Transport Layer Security

Docker Compose

To enable secured endpoint configuration for Web Services and Applications, edit the common-env file and set GWS_HTTPS_ENABLE to true. For more details, Deployment of Web Services and Applications in Docker Compose.

Kubernetes

To enable ingress secured endpoint configuration for Web Services and Applications, edit the parameters.yaml file and set entryPoint.external.ingress.tlsEnable to true.

For more details, refer to Deployment of Web Services and Applications in Kubernetes.

This page was last edited on September 28, 2020, at 20:54.
Comments or questions about this documentation? Contact us for support!