> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-hermes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm-hermes/readme/asm-security-and-compliance/security-penetration-test-reports.md). # Security Penetration Test Reports ### Independent Security Assessments #### Regular Third-Party Penetration Testing Our web applications undergo independent penetration testing by qualified external security specialists. These assessments are designed to evaluate real-world attack scenarios and identify potential vulnerabilities from both unauthenticated and authenticated perspectives. Our external security specialists hold up to date [CREST ](https://www.crest-approved.org/)Accreditations. *** ### Continuous Improvement Security is not a one-time exercise. We operate a **continuous improvement approach** that includes: * Periodic independent penetration testing * Secure development and change management processes * Risk-based remediation and validation of findings * Ongoing review of emerging threats and attack techniques Where appropriate, findings from independent assessments are incorporated into our development and operational roadmaps to further strengthen our security posture. *** ### Transparency and Customer Assurance We believe transparency is an important part of building trust. Summary information from independent security assessments is made available to customers and prospective customers to support their own risk and compliance evaluations. For customers requiring additional assurance or specific security documentation, further details may be provided under appropriate confidentiality arrangements. *** ### Learn More If you would like more information about our product security practices or independent assurance activities, please contact your account representative or our security team. --- # 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://docs.alemba.com/asm-hermes/readme/asm-security-and-compliance/security-penetration-test-reports.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.