> 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/software.md).

# Software

Configure and maintain Command Centre software, security settings, databases, backups, and integrations.

This section details guidelines for the installation and configuration of Gallagher Security Command Centre software.

## Command Centre

Gallagher is continually testing and improving the security of its software. Specialised penetration testers are used to test the vulnerability of the product. To obtain the highest level of protection, it is recommended that your site use the latest version of Command Centre and update it with each new release.

Our Knowledge Hub has details on how to access our Software Downloads.

See [Download software](https://help.security.gallagher.com/knowledge-hub/deployment-resources/software-resources/downloading-and-uploading-files.md).

## Utilities and Tools

Gallagher Security provides utilities to assist with the use of Command Centre; it is recommended that these are utilised.

### [Upgrade Validation Tool](https://help.security.gallagher.com/knowledge-hub/deployment-resources/support-tools-and-troubleshooting/upgrade-validation-tool.md)

This tool assists sites preparing to upgrade their Gallagher Command Centre and Controllers by evaluating site compatibility with the upgrade. It extracts information about the operating system, SQL Server instance, any configured Controller customizations, and checks for legacy Controllers and devices.

### [Security Health Check](https://help.security.gallagher.com/knowledge-hub/deployment-resources/support-tools-and-troubleshooting/security-health-check.md)

The Gallagher Security Health Check is a free downloadable tool designed to make it quick and easy for you to carry out system checks at any time, as part of regular maintenance and to ensure there are no unintended consequences to Command Centre configuration changes over time.

[Security Health Check - Ensure Optimal System Performance](https://security.gallagher.com/en-NZ/Services/Security-Health-Check)

### [CCFT Service Manager](https://help.security.gallagher.com/knowledge-hub/deployment-resources/support-tools-and-troubleshooting/ccft-service-manager.md)

A powerful tool for any system, this can be used on both the Server and workstations. It is recommended this is used and set up to run on startup.

This utility can easily allow you to:

* Start/Stop your Command Centre (CC) Services
* Enable Trace and/or General (enhanced logging)
* Access CC Configuration and client log files
* Create and access CC application minidump files (for investigating issues)
* Enable memory Diagnostics
* Detach and re-attach the Gallagher databases

### [FT Support Tool](https://help.security.gallagher.com/knowledge-hub/deployment-resources/support-tools-and-troubleshooting/ft-support-tool.md)

A tool used to extract information from a Command Centre system. It is recommended that this is used to provide an overview of the site and provide information to Technical Support when troubleshooting an issue. Note that for this tool to run and get useful data, the Windows user account must have access to the SQL instance – this can require assistance from the local IT team.

## Recovery Code

During installation of Command Centre, a Database Recovery Code will be generated that is unique to each site.

{% hint style="warning" %}
This needs to be exported and securely stored. It is recommended to keep a copy in a secure location separate from the Command Centre server (e.g. elsewhere on the customer’s premises).
{% endhint %}

![Database Recovery Code being generated](https://content.gitbook.com/content/eem9HLOjc53n2VxEz3Cq/blobs/jsGpInLHKbRj8TpE8D05/images%2Fimage6.png)

*Example of a Database Recovery Code being generated*

{% hint style="danger" %}
The loss of this code can mean that restoring a backup is impossible – Gallagher cannot regenerate this code if it cannot be found.
{% endhint %}

If you are unsure if you have the correct recovery code, you can check the code using the Recovery Code tool (CCFTRecoveryCode.exe), located by default in `C:\Program Files (x86)\Gallagher\Command Centre\Bin`.

If you are unable to locate the correct recovery code, and if your Command Centre Service is running, you can generate a new recovery code. Note that any backups made prior to the regeneration of the new Recovery Code will no longer be valid. Take a new backup immediately after generating a new recovery code.

## Naming Conventions

Poor naming conventions increase the likelihood of misconfigurations and human error, while well-structured naming conventions create better navigation, searching and reporting experiences.

{% hint style="info" %}
It is recommended that naming conventions are used when initially setting up a Command Centre system.
{% endhint %}

This would apply to areas within the application such as:

* Hardware
* Access Groups
* Access Zones
* Divisions
* Doors
* Operator Groups
* Site Plans
* Reports

The recommendation is to have a hierarchical data structure. This could start with **Location** or **Site** and then **Building** then **Level** then **Identifier**. Some sites may also choose to add the **Variant of Controller**.

That provides the capability for the system to take a local alarm and add the geographical contexts to it when building alarm messages.

| Location | Building | Level | Identifier             | Controller Type |
| -------- | -------- | ----- | ---------------------- | --------------- |
| HAM      | B01      | L1    | C01 - Data Riser CABXX | C7K 8H          |

Full name: HAM B01 L1 C01 - Data Riser CABXX - C7K 8H

## Divisions

When designing the site, if there are requirements to segregate or split areas to certain operators, then divisions should be implemented. It can be hard to do this at a later stage.

**Example division hierarchy**

```
GLOBAL
├── CARDHOLDERS
│   └── VISITORS
├── OPERATIONS
│   └── SECURITY
│       └── GUARDS
├── COUNTRY 1
│   └── LOCATION 1
│       └── Location 1 Hardware
└── COUNTRY 2
    ├── LOCATION 2
    │   └── Location 2 Hardware
    └── LOCATION 3
```

## Backups and Archives

### Backups

It is recommended that scheduled backups be set up on all sites to a safe and secure location (these should not be on the same server as Command Centre). Ensure you have stored your Recovery Code in a safe location.

{% hint style="warning" %}
If you update the recovery code, all backups made with the previous recovery code are invalid.
{% endhint %}

All configuration, cardholders and other important information is held in the CCFTCentral SQL database, if anything was to happen to the SQL database (E.g. Corruption), physical server (e.g. Hardware failure) or even configuration (e.g. Operator error), then all the information could be lost and non-recoverable.

Recovering a Command Centre Server after a disaster is critically reliant on having as recent as possible copies of the CCFT databases and the appropriate recovery code. If you have access to the CCFT databases, Recovery Code and the system’s licence file, you can recover the server in a relatively short time.

[Backups - An Overview | Knowledge Hub](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/archiving-and-backups/backups-an-overview)

### Disaster Recovery and Business Continuity

A Command Centre server can only be recovered as quickly, and as completely, as its most recent usable backup allows. It is recommended that every site has a documented disaster recovery (DR) plan, agreed with the customer.

#### What a recovery needs

Keep the following available to the people who will carry out a recovery, stored securely:

* Recent backups of the CCFT databases.
* The Database Recovery Code.
* The site's licence file.
* The Site Specific Key (SSK) export, where DESFire cards are used.
* Install media for the Command Centre version in use.
* A record of the server's configuration, such as server name, IP addresses, certificates, integrations and REST Clients.

The Recovery Code and SSK should be protected as carefully as the backups themselves.

#### Recovery objectives

Agree two targets with the customer: how much data they can afford to lose (Recovery Point Objective, RPO), and how long they can operate without the Command Centre server (Recovery Time Objective, RTO). Backup frequency and the recovery approach should be chosen to meet them.

#### Frequency and retention

* Schedule backups at a frequency that meets the agreed RPO.
* In addition, take an interim backup after any significant configuration change, such as adding hardware, restructuring divisions or access groups, or a bulk cardholder import. Otherwise, a restore from the last scheduled backup means that work has to be re-applied, which can be considerable on a site with infrequent backups.
* Keep several generations of backups. If the latest backup is damaged, or was taken after a problem began (such as an operator error found late, or ransomware), an older one can be used.
* Monitor scheduled backups and make sure someone is alerted if a backup fails.

#### Off-site and protected copies

Keep at least one copy away from the Command Centre server and off-site, or offline, so that losing the server, the building or the network does not also lose the backups.

#### Test restores

* Restore backups regularly to an isolated environment (the same one used for testing upgrades) to prove the backups, Recovery Code and licence work together.
* Test at least once a year and after major upgrades, and record how long the restore takes. That time is the site's realistic RTO.

#### Operating during an outage

Gallagher controllers buffer events while they cannot reach Command Centre and send them automatically when communication is restored. Configuration changes, however, cannot be made until the server is back. The business continuity plan should cover how the site will handle tasks such as issuing or cancelling cards and responding to alarms in the meantime.

Sources: [Gallagher – Data Security and Storage](https://products.security.gallagher.com/security/uk/en_UK/products/software/data-security-and-storage/p/INT126)

### Archives

Archiving should be set up on all sites, but especially on sites that will be left unattended and not maintained by a dedicated staff member(s).

Event data is stored in the CCFTEvent database. If the site uses SQL Server Express, the capacity limit depends on the installed version. Check the [Compatibility matrix](https://help.security.gallagher.com/knowledge-hub/deployment-resources/engineering-and-design-reference/compatibility-matrix.md) for the supported SQL Server Express versions and their Microsoft-defined limits.

Once the SQL database reaches maximum capacity, the system will no longer be able to record events, and the event trail will fail to populate. The system will generate alarms well prior to this, but someone must see this and act on it for this to be effective. The options then available are to upgrade to a full edition of SQL Server (e.g. Standard or Enterprise) or lose the events by replacing the database with a blank one.

[Archiving - An Overview | Knowledge Hub](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/archiving-and-backups/archiving-an-overview)

## Calendars

It is important to understand if more than one calendar is needed when setting up a site.

There are two types of Calendars in Command Centre, as described below:

* **Default Calendar** Used for sites that operate in one region.
* **Special Calendar** Special calendars cater for organisations that **span multiple geographic areas** by allowing their local operators to administer the scheduling of special days, (e.g. public holidays), applicable to their region or site.

[Calendars – An Overview| Knowledge Hub](https://help.security.gallagher.com/knowledge-hub/products/cc-software/configure/calendars)

## Day Categories

It is important to understand that most sites will need multiple day categories, and it is harder to implement these later. Day categories allow for greater flexibility for scheduling items in Command Centre. This can vary depending on the site’s requirements and can range from just having a WEEKDAY Day Category and WEEKEND Day Category to having separate day categories for each day of the week.

By default, there is only one Day Category configured. It is recommended to add more Day Categories early in Site configuration as it is more time consuming to do at a later stage.

![Day Category allocation in the Default Calendar](https://content.gitbook.com/content/eem9HLOjc53n2VxEz3Cq/blobs/L1JFe4hCpNMoGfzmBYJl/images%2Fimage7.png)

[Day Categories | Knowledge Hub](https://help.security.gallagher.com/knowledge-hub/products/cc-software/operate/operator-video-library/calendars-day-categories-and-schedules/understanding-day-categories)

## Cards

It is recommended that sites use DESFire EV3 or higher cards as they provide higher levels of security than 125 kHz, MIFARE Classic, Magstripe or other legacy technologies.

When encoding DESFire cards, Site Specific Keys (SSK) are uniquely generated keys that ensure a site’s cards are protected and only work on their site.

The SSK for a site must be exported and securely stored. It is recommended to have this in another location on a customer’s premises.

Gallagher offers a Key Migration Guide for sites that need to change their Site Specific Key, for example if it has been compromised or the site is still using the default key.

![Site-Specific Key being generated on the MIFARE Site Keys tab](https://content.gitbook.com/content/eem9HLOjc53n2VxEz3Cq/blobs/aO9L3eoJEYBzGfVznirF/images%2Fimage8.png)

*Example of a Site-Specific Key being generated*

{% hint style="info" %}
It is recommended that older/unused card technologies are disabled under Permitted Card Technology, on the General tab of Card Security. Note that readers do have the capability to be configured differently than the Server Default.
{% endhint %}

![Permitted Card Technology settings on the General tab of Card Security](https://content.gitbook.com/content/eem9HLOjc53n2VxEz3Cq/blobs/A04tQF2LxWmIfRR14Xna/images%2Fimage9.png)

*Example of the Permitted Card Technology settings*

## Operators

It is recommended that the operator group structure is configured to follow a least-privilege model, ensuring that dedicated groups are configured with the correct privileges to allow operators to perform only the functions that are assigned. It is recommended to have dedicated operator groups such as:

### Cardholder Management

Operators that can modify cardholders and perform functions such as card allocation, personal data field changes, and cardholder lifecycle management.

### Site Management

Operators that can perform configuration of hardware, features, and functionality within Command Centre. This can include viewing, acknowledging, and processing of alarms.

### System Administration

A group that provides full privileged access to all parts of the Command Centre system.

### Alarm Monitoring

Operators, such as guards or control room staff, who view, acknowledge and process alarms but cannot change configuration. Keeping this separate from Site Management means monitoring staff do not need configuration privileges.

These groups are examples. On many sites the same people view and process alarms as well as maintain and configure the system, so each site should decide which privileges to assign based on each person’s role.

### Operator accounts

* Give each operator their own login rather than sharing operator accounts, so the audit trail shows who did what.
* Review operator accounts and group membership periodically, and remove or disable accounts for people who have left or changed roles.
* Limit membership of the System Administration group to the few people who need it.

## Access Groups

It is recommended that Access Group lineage is used. Lineage is a concept concerned with the inheritance of privileges between parents and children.

* Staff Access Group (e.g. Access to primary areas during working hours)
  * Higher Privileged Access Group (e.g. Additional access to more secure areas after hours)
    * Highest Privileged Access Group (e.g. Full access to all areas at all times)

A child Access Group inherits from its parents both their access (access zones and schedules) and their Access Group privileges, such as the ability to escort visitors. Inherited privileges apply only to the parent’s access zones. In the example above, members of the Highest Privileged Access Group therefore also have the access of the Higher Privileged and Staff Access Groups. Lineage is configured on the Lineage tab of each Access Group.

The diagram below, from the Command Centre online help, shows a fuller example. Head Office inherits the Front Door from All Cardholders, and IT Department inherits Head Office’s Levels 1 and 2 along with its privileges for those levels. A visitor going to Levels 3 to 5 therefore needs an IT Department escort.

![Access Group lineage example](https://content.gitbook.com/content/eem9HLOjc53n2VxEz3Cq/blobs/Loxn7KEFJhblQeaJFwmQ/images%2Fimage10.png)

*Example of Access Group lineage*

Lineage works in largely the opposite way for Divisions. See ‘Divisions and Lineage’ in the Command Centre online help.

## Spanning across controllers

Where possible, Gallagher does not recommend spanning configuration across multiple controllers. This applies to alarm zones, door configuration, logic blocks etc. If controller communication is disrupted, then this will affect functionality of any configuration that has been spanned between the controllers.


---

# 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/software.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.
