> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/deployment-resources/security-and-compliance/cyber-security-and-penetration-testing.md).

# Cybersecurity and penetration testing

Find Gallagher security assessment, responsible disclosure, and CVE guidance.

Gallagher runs an in-house cybersecurity and penetration-testing team and engages CyberCX to review software and hardware before every major Command Centre release. Security Assessment statement letters are available to share with customers.

The full penetration report is never shared as it contains highly sensitive product detail.

Gallagher publishes CVEs and runs a Responsible Disclosure Policy for security researchers.

### Assessment and disclosure process

* **Independent review:** CyberCX conducts cybersecurity reviews of software and hardware products before the major release of every Command Centre product and service. Gallagher also has dedicated in-house cybersecurity and penetration-testing personnel.
* **Vulnerability handling:** A formal triage and prioritization process fixes critical and high vulnerabilities within defined service-level response times.
* **Responsible Disclosure Policy:** This lets security researchers work with Gallagher and disclose vulnerabilities safely. It minimizes harm to users. If Gallagher assesses a vulnerability as unlikely to be actively exploited at customer sites, it fixes the issue. It then releases version updates and informs Gallagher teams and Channel Partners.
* **CVE location:** [Gallagher Security Advisories](https://security.gallagher.com/en-NZ/Security-Advisories)

### Security assessment statement letters

Customer-shareable summary letters confirming the independent assessment for each release.

#### Command Centre software and subsidiary applications

{% file src="/files/eWS5J0tIZ3BdbTet4bzD" %}
Command Centre Release 9.40, 19 March 2026
{% endfile %}

{% file src="/files/fh0Mz1G8lJ4D6FabwNSo" %}
Command Centre Release 9.30, 25 September 2025
{% endfile %}

{% file src="/files/RHqqlBaOMYNH6zkqZ4KW" %}
Command Centre Release 9.20
{% endfile %}

#### Command Centre Cloud security testing

{% file src="/files/IHU0H5BSD1MlxxGB4cE0" %}
CC Cloud Security Assessment, September 2024. Covers the Mobile Wallet Service Review (12 August 2024) and CC Cloud Penetration Testing (21 February 2024).
{% endfile %}

#### Command Centre products

{% file src="/files/7l8iOaxVttNMw7yv1UNi" %}
Controller 7000 Security Testing, 4 April 2025. Covers Controller 7000 Standard, Enhanced, High Security, and Single Door.
{% endfile %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/deployment-resources/security-and-compliance/cyber-security-and-penetration-testing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.