When planning to secure the K2 platform, you should establish a methodology using models first, such as STRIDE or VAST. This article describes options and approaches for securing your K2 environment, with links to supporting documentation based on the feature and object you want to secure.
Once you have secured your K2 environment, you may want to review the article KB003338: Securing K2 Solutions for information on solution-specific security considerations.
If you are looking for compliance information, see the following articles:
This article is divided into three main sections including tools and features, data contained within or accessed by the platform, and objects you can create with the tools provided. There is also a fourth area that describes additional security measures you can perform that affect the platform but are not features of it, such as IP restrictions and IIS request filtering. Lastly, K2 Five customers can use the Appendix for information about securing on-premises K2 servers.
Use the following information to restrict access or rights to K2 sites, design tools, administration tools, and K2 Mobile.
Finally, see Permissions needed for common tasks for a summary of the permissions needed for various tasks.
You may want to restrict access to data stored in, or accessed through, K2 SmartObjects.
In addition to common security approaches like encrypting backups and network communication, there is some additional configuration that you may consider doing.
When installing K2 Five, take into consideration network and infrastructure-related security, such as: