> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/getting-started/technical-overview/product-security.md). # Product security The Patchworks platform is designed with robust security controls at every level of our [tech stack](/product-documentation/getting-started/technical-overview/tech-stack.md), ensuring peace of mind for your organisation. ## Security by design Our core product is built using industry-standard frameworks, which are certified as part of our I[SO 27001](/product-documentation/getting-started/technical-overview/iso-certification.md) and [SOC](/product-documentation/getting-started/technical-overview/data-security-soc-2.md) compliance. Our Information Security Management System is continuously updated and improved to meet the ever-changing threat landscape. From inception through deployment, security is a fundamental part of our development lifecycle. ## Secure coding practices Our development team adheres to secure coding standards and best practices. Secure coding training is mandatory for all engineers (security awareness training is mandatory for everyone), and regular code reviews are an integral part of our release pipeline. ## Security testing All code repositories are tested with static and dynamic code analysis to ensure clean code, a secure product and the use of appropriate code library licensing. ## Separation of customer data Each customer is provisioned with a dedicated, tenanted database. This ensures strict data segregation. ## Strong authentication measures All passwords are hashed and salted using secure AES cryptographic algorithms. We never store plain-text passwords. Federated SSO FIDO2 Google authentication implementation is in place for all internal and privileged access roles. ## Vaulted sensitive data Sensitive application data (such as API keys and access tokens) is encrypted and securely stored in a protected vault. ## Single sign-on (SSO) Organisations can manage user authentication using their preferred single sign-on (SSO) method, choosing from a range of identity providers. SSO can be assigned at both the company and user levels. ## Role-based access control (RBAC) Role-Based Access Control (RBAC) is strictly enforced throughout the platform - both in the front-end user interface (i.e. the dashboard) and the back-end API layer. Access to features and data is granted according to user roles and permissions, ensuring the principle of least privilege is maintained. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://doc.wearepatchworks.com/product-documentation/getting-started/technical-overview/product-security.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.