> 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/products/cc-software/configure/hardening.md).

# Hardening

Find hardening guidance for Command Centre servers, workstations, controllers, and kiosks.

Use the hardening guide that matches your installed Command Centre release. The guides cover software, controllers, and kiosk deployments.

{% hint style="info" %}
Find each guide in the installation files or the Gallagher media library. Confirm the release before applying a control.
{% endhint %}

***

## Available guides

| Guide                                              | What it covers                                                                          |
| -------------------------------------------------- | --------------------------------------------------------------------------------------- |
| **Command Centre Hardening Guide**                 | Server, workstation, and application hardening for the Command Centre software platform |
| **Controller 6000 and 7000 Hardening Guide**       | Hardening the C6000 / C7000 field controllers                                           |
| **Physical Security Levels**                       | Gallagher's guide to physical security levels                                           |
| **Visitor Management Kiosk Hardened Installation** | Hardened installation of the Visitor Management Kiosk                                   |

These guides ship with the Command Centre installation files and are also published in the Gallagher media library.

***

🔗 **Related**

* [Server - Minimum Specification](broken://pages/oV0NQagRsP51dXxb04GU). Server sizing and platform requirements that pair with the Command Centre Hardening Guide.


---

# 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/products/cc-software/configure/hardening.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.