Security and compliance

Last published : Oct 20, 2026
This section is written for security reviewers, whether you are assessing SecurSpaces before adoption or answering questions about a deployment you already run.
SecurSpaces is customer-hosted, so responsibility is shared. The platform provides controls; your cluster, ingress, and infrastructure encryption are yours. Trust boundaries states where the line falls.
Related information
Security control catalogueTrust boundariesHow the SecurSpaces proxy service worksLayered controls with the Citrix platformSecurity data flowsNetwork policiesTechnical security overview for SecurSpaces Flex

Assessing the platform

Question Page
What controls exist, and how do I cite one? Control catalogue
Where does the deployment separate trust, and who owns each side? Trust boundaries
How does data move between components? Data flows
What ports must be open, and what encrypts what? Ports and protocols, Cryptography

Controlling workspace traffic

Task Page
Understand the policy model and the defaults Network policies
Create a policy Create a network policy
Apply one across projects Assign and enforce a policy
Work out why traffic was blocked Monitor and troubleshoot

SecurSpaces Flex

Flex is the managed offering, with a different responsibility split. See SecurSpaces Flex security.