> 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/engineering-and-design-reference/deployment-guidelines/infrastructure-and-it.md).

# Infrastructure and IT

Plan the network, servers, SQL Server, workstations, and integrations that support Command Centre.

### Network

Configure the network so Gallagher Command Centre can communicate through the site's routers and firewalls. Provide these requirements to the site's IT department.

If the site has a large number of controllers, Gallagher recommends a dedicated VLAN for the controllers, both to separate security traffic from corporate traffic and to prevent interference from other systems (such as broadcast events from cameras).

{% hint style="warning" %}
Wireless networking should be used as a last resort or as a backup network path as Wireless networking can be susceptible to packet loss.
{% endhint %}

#### Remote sites and WAN connections

* Controllers need a permanent Ethernet connection to the Command Centre server.
* The Command Centre BootP Service gives controllers their IP address using broadcast packets, which normally only reach the server’s own subnet and are often blocked by routers and switches. For controllers on other subnets or at remote sites, assign addresses by DHCP or manually, as described in the [Controllers install notes](https://help.security.gallagher.com/knowledge-hub/deployment-resources/install-and-commission/hardware-install-notes/controllers-install-notes.md).
* From 9.30, a Controller 7000 can connect to Command Centre over the internet using OneLink. See ‘OneLink Configuration’ in the Configuration Client online help.
* Controllers can keep operating if the link to the server drops, but only with the cardholder information they already hold. After a system upgrade, Command Centre rebuilds each controller’s configuration automatically once the controller reports that its upgrade is complete, and sends it to the controller. A Push Configuration or Resync Databases is occasionally needed, for example when a new controller is installed, but not typically after an upgrade. Where a resync is needed on a large site, resync one controller at a time.

See [Ports by component](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/network-ports-and-protocols/ports-by-component.md) for firewall requirements.

### Computer specifications

Gallagher provides recommendations for servers, workstations, and visitor management specifications on the Knowledge Hub. It is important that these meet the requirements of the site now and in the future.

Keep sustained CPU, memory, and disk utilization below 75%. If use remains above this level, increase the server’s resources.

[Minimum Computer Spec | Knowledge Hub](https://help.security.gallagher.com/knowledge-hub/products/cc-software/reference/minimum-specifications)

It is recommended that the supported operating system is kept up to date and updated as per the site’s policies.

Gallagher recommends separate Windows accounts for installing Command Centre and for running its services. The account used to install and upgrade Command Centre needs sysadmin rights on the SQL instance during installation (see SQL Server Database). This user account should be under strict control. It should be used only for installs and upgrades.

The Command Centre services should run under a dedicated service account. It needs only db\_owner access to the CCFT databases, and should not be used to log on to the server interactively. Avoid running the services under built-in accounts such as Network Service.

Neither account should be used for normal everyday housekeeping functions on the server; create a separate, more limited account for that purpose.

If the site has a monitoring system in place, monitoring the Command Centre Services is recommended.

Command Centre has the facility to create Minidumps and logs of its systems. The minidump type is set in the CCFT Service Manager (Diagnostic > Set Minidump Type) and has four levels: 0 – Stack only, 1 – Stack & Memory, 2 – Everything Except Code, and 3 – Everything. For normal day-to-day operation, level 1 (Stack & Memory) is recommended. Level 3 (Everything) is advised when investigating a problem on site, but it can produce exceptionally large files; return to level 1 afterwards, and delete minidumps once they are no longer needed. Command Centre logging (Trace) should also be turned off once troubleshooting is complete, so that log files do not grow unnecessarily. Trace Performance is used mainly to trace performance in the Command Centre Client, and should likewise only be enabled while investigating an issue.

It is recommended that old install files and unused licenses are removed from the Command Centre Server.

#### Virtual machines

Gallagher recommends that when using Virtual Machines to host Command Centre, the VM is set up as follows:

* **No long-lived snapshots.** Do not leave Command Centre running on VM snapshots. Reverting a snapshot rolls the Command Centre databases back to that point, and snapshots are not a substitute for SQL database backups. A snapshot may be taken before an upgrade as a rollback option should the upgrade be unsuccessful, provided it is deleted as soon as possible once the upgrade is confirmed.
* **Fixed memory.** Allocate a fixed amount of memory; do not use dynamic memory.
* **Fixed disks.** Use thick-provisioned (fixed-size) disks rather than thin-provisioned or dynamically expanding disks.
* **Reserved CPU.** Reserve the CPU allocated to the VM rather than relying on shared or over-committed CPU.
* **Same specifications as physical.** Size the VM to the same minimum specifications as a physical server (see Minimum Computer Specifications).

### SQL Server database

Sites have full access to the Command Centre databases. This means administrators can grant local and/or domain Windows users access to edit, manage and maintain the SQL Instance and attached Gallagher (CCFT) databases.

When Command Centre is installed, the Windows User account performing the install requires sysadmin rights to the SQL instance. The Windows User account that runs the Command Centre services for normal use only requires db\_owner level access.

It is recommended that the supported SQL Server is kept up to date and updated as per the site’s policies.

{% hint style="warning" %}
Gallagher does not recommend that the SQL instance used by Command Centre be shared with any other databases as this could significantly impact system performance.
{% endhint %}

Gallagher recommends that the network latency between Command Centre and the SQL instance be less than 1ms. This is a recommendation rather than a hard limit. Latency of up to 5ms is workable, but it can lead to serious performance issues on larger systems.

#### SQL Express limitations

Command Centre can run on Microsoft SQL Server Express, the free edition of SQL Server. It suits small sites, but Microsoft caps what it can use, regardless of the server's hardware.

| Limit                                              | SQL Server Express                                                         | SQL Server Standard (2025)      |
| -------------------------------------------------- | -------------------------------------------------------------------------- | ------------------------------- |
| Maximum size per database                          | 10 GB (supported versions before SQL Server 2025); 50 GB (SQL Server 2025) | 524 PB                          |
| CPU used per instance                              | Lesser of 1 socket or 4 cores                                              | Lesser of 4 sockets or 32 cores |
| Memory for buffer pool                             | 1,410 MB                                                                   | 256 GB                          |
| SQL Server Agent (scheduled jobs)                  | Not available                                                              | Available                       |
| High availability (Always On, failover clustering) | Not available                                                              | Available                       |

What this means for Command Centre:

* The size limit applies to each database separately, so on a large site CCFTCentral can reach it, not only CCFTEvent.
* When a database reaches the limit it cannot grow, and Command Centre stops recording events. Set up archiving from the start. See [Software](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/deployment-guidelines/software.md).
* Adding CPU or memory to the server will not speed up SQL Express beyond its caps.
* Database maintenance cannot be scheduled with SQL Server Agent, so it needs another method.
* Check the [Compatibility matrix](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/compatibility-matrix.md) for the SQL Server versions supported by the Command Centre version in use.

It is recommended that a full edition of SQL Server (Standard or Enterprise) is used where the site has large or growing cardholder and event volumes, several integrations or REST clients, many operators, or a need for high availability, or where an Express database is approaching its limit.

Sources: [Microsoft – Editions and supported features of SQL Server 2025](https://learn.microsoft.com/en-us/sql/sql-server/editions-and-components-of-sql-server-2025)

#### Customer responsibilities

As per the Software License and Maintenance Terms and Conditions accepted upon installation of Command Centre, Gallagher will not be liable in any circumstances for the loss or corruption of data.

It is the responsibility of the customer to:

* Not modify any Data, Metadata or Schemas in the Gallagher Command Centre databases by any method other than via the Gallagher Command Centre Application.
* Not share the database instance with other services.
* Not upgrade the databases while in Availability groups.
* Implement appropriate measures to ensure adequate levels of data security.
* Manage, monitor and maintain their Gallagher Command Centre databases, including backups (scheduled and manual), archiving and database transaction log files.
* Accept full responsibility for any data loss or corruption associated with the unauthorized modification of data or schemas within the Gallagher system.
* Accept that if the event data is required for legal purposes, Gallagher will be unable to verify that the data has not been altered by an unauthorized method, or software outside the Gallagher Command Centre application.
* Communicate promptly and completely in response to all issues and requests for information from Gallagher.

#### Support approach

Support requests resulting from tampering, corruption, failure to maintain transaction log files or unauthorized modification of any Gallagher system Data or Schema will be at the Customer’s full cost where possible.

### Hardening

Gallagher provides Command Centre, Controller and Visitor Management hardening guides for customers to help protect your Gallagher Command Centre software from attack, increasing the overall security of your system. Review and apply them where possible.

The guides are available with the Command Centre install files.

### Workstation deployment

Different deployment options are available depending on the requirements of the customer:

* File Server as a Deployment (ClickOnce)
* MSI Installation
* XCOPY Deployment
* Installing using Command Prompt (intended for silent deployment by Sysadmins)

Gallagher recommends ClickOnce because it can be set up on the server and automatically upgrades the workstation after a server upgrade. One downside of this deployment is that each user account on the PC that deploys by this method creates an install under their user account.

If multiple users are using one PC, then the MSI deployment method is recommended. This allows for only one shared install of Command Centre for all users.

Detailed information on each option is available in the *New Installations release note* located with the installation software.

#### Command Centre certificate

By default, Command Centre secures communication between the server and its clients with an internally generated certificate. Its private key stays within the server and database, and no other copies are made. This is the recommended configuration.

Where a site needs the trust chain to extend to its own certificate authority, the default certificate can be replaced using the CCFTCustomCertificate utility. Because of the impact it can have on the system, the utility is not openly available; customers need to request access to it through Gallagher Technical Support. Changing the certificate has a significant impact and a lot can go wrong, so the warnings in the utility's release note must be read and followed before starting.

Changing the certificate affects:

* Command Centre Client
* Visitor Management Client
* Visitor Management Kiosk
* Multiserver communication

Before making the change:

* Test the change on an offline test system first.
* Plan an outage. The server must be offline while the certificate is installed, so make sure operators and stakeholders know.
* Prefer Windows certificate enrolment on the server, which keeps the private key on that machine. A .pfx or .p12 file contains a copy of the private key and must be handled and disposed of securely; if the key is compromised, Command Centre traffic could be read and altered.
* Generating a secure certificate chain needs the right expertise. Expired certificates, weak keys and single self-signed certificates are rejected by the utility.

After the change:

* **ClickOnce deployments:** the workstations must be rebuilt and redeployed.
* **Manual (MSI) deployments:** the certificate must be deployed to each workstation manually. Until then, existing clients will not trust the server.
* **Multiserver:** install the certificate chain on each connected server, and apply the 'Accept Certificate' override on each multiserver connection.

The current utility is for Command Centre 8.50 MR1 and later; a separate version covers 8.10 to 8.40. Refer to the CCFTCustomCertificate Utility Release Note for the full procedure.

#### Least-privilege access on workstations

* Operators should log on to workstations with standard Windows user accounts, not local administrator accounts.
* Use a separate administrator account to install and upgrade the Command Centre Client where the deployment method needs one (e.g. MSI installations).
* Give each operator their own Command Centre login rather than sharing operator accounts, so the audit trail shows who did what. Operator privileges are covered under Operators.
* Keep the workstation operating system patched as per the site's policies, and upgrade the Command Centre Client along with the server.

### Integrations with other systems

Gallagher Security creates integrations with different systems; these can be found on our public website [Security Integration Solutions - Seamless Connectivity.](https://products.security.gallagher.com/security/global/en/products/integrations/c/integrations)

Our Tech Partner Program allows integrators to develop their own integrations with Command Centre; more information can be found on this webpage [Our Technology Partners - Innovating Security Together](https://security.gallagher.com/en/Our-Partners/Our-Technology-Partners)

These are typically tied to the version of Command Centre, so it is recommended to ensure that the correct version of the integration is available prior to upgrading the server.

#### REST API

The Command Centre REST API lets third-party systems read and update Command Centre data over HTTPS. Each area of the API is licensed separately (RESTEvents, RESTCardholders, RESTStatus, RESTOverrides and RESTCreateEvents), and the server only exposes the calls it is licensed for. Developer documentation is published online, and sample code ships on the install media in the Utilities/REST API folder.

It is recommended that every REST integration is designed and reviewed against the guidance below before it is connected to a production server.

**Access and security**

* Create a dedicated REST Client item for each integration, so each has its own API key. Treat the API key as a secret.
* Link each REST Client to a dedicated REST operator with the fewest privileges it needs, limited to the divisions it works with. Never give a REST operator 'advanced user'.
* After changing the REST operator's privileges, use 'Refresh operator privileges' on the REST Client item.
* Keep pinned client certificates required, and enter the client's certificate thumbprint on the REST Client item. This is how Command Centre ships and is the recommended production setting.
* Enable source IP filtering on the REST Client item where the client's address is fixed.
* For remote or cloud-hosted clients, consider the Gallagher Cloud API Gateway. It uses an outbound-only connection from the local Command Centre server to the cloud, so no inbound firewall rule should be required.
* Command Centre returns strings exactly as they were stored and does not sanitise them, so integrations should guard against injection.

**Throughput management**

* When retrieving many items, sort by ID and set the page size (top) explicitly. From 8.70 the default is 1,000 items per page, around where throughput levels off.
* Avoid sorting large result sets by name: it is slower and can skip or duplicate items if someone edits the database mid-download.
* Use the fields parameter to request only the fields the integration needs.
* Combine changes into a single POST or PATCH rather than creating an item and then refining it with several calls.
* Expect a 409 response when an operator has a cardholder open with unsaved changes; log it and retry later.

**Query management**

* Avoid large numbers of individual searches, such as one Personal Data Field lookup per cardholder. Retrieving in bulk and filtering in the integration is faster.
* Use exact-match (quoted) searches on names and Personal Data Fields where possible; substring searches are much slower.
* Start every session from /api and follow the links it returns, rather than hard-coding URLs. This keeps integrations working across Command Centre upgrades.

**Frequency of session connections**

* For alarms, events and item status, use the long-poll updates and next links instead of repeated polling. The call waits for a change and returns empty after a short timeout if nothing happens.
* On busy servers, pause between alarm update calls; no alarms are missed. If a batch returns the maximum of 100 updates, call again straight away to catch up.
* To monitor many items, use a status subscription rather than one updates link per item.
* Make sure authentication is correct before going live. More than ten failed attempts in a minute raises a flood alarm on the server.
* From 9.30, Command Centre can raise an alarm if an API client has not made a call within a set period. Enable this for integrations the site depends on.

**Intermediary repository for large queries**

Where several systems need large volumes of Command Centre data, consider synchronising it to a separate repository rather than having each system query Command Centre directly.

For further advice on managing large volumes of REST API queries to Command Centre, and on designing queries that give the customer the best experience, please reach out to your local Gallagher representative.

**Upgrades**

REST integrations should be tested in the isolated upgrade environment. See [Upgrade and migrate](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/migrate-and-upgrade.md), and check the API change notes for the target version before upgrading production.

Sources: [Command Centre REST API reference](https://gallaghersecurity.github.io/cc-rest-docs/ref/index.html) · [Command Centre REST API specification](https://gallaghersecurity.github.io/cc-rest-docs/oas3/redoc-static.html)


---

# 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/engineering-and-design-reference/deployment-guidelines/infrastructure-and-it.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.
