> 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/configuration-client/site-installation/server-properties/standards.md).

# Standards

### Introduction

This tab enables operators with the "Edit Site" (or higher) operator privilege to:

* configure specific system-wide behaviour with respect to alarm system standards. All fields in the **Support for alarm system standards** section will be 'read-only' for operators with the "View Site" operator privilege.
* configure **NPSA and CAPSS compliance** settings for extra security, if required.

  **Note:** To be able to configure these settings on sites licensed for NPSA, (i.e. `NPSA=1` appears in the licence file), operators need to log into Command Centre using FIDO2 Authentication.
* configure the system so that when controllers are being upgraded, any readers connected to those controller will display a unique flash pattern.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Standards** tab.

   The **British Standard** sub-tab displays by default.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9ec53ff05eb741627d96afca90dc7b964973469c%2Fstandardstab_britishstandard.png?alt=media)
3. Ticking the **Enable confirmed alarms** checkbox has the following effects throughout the system:
   * enables the transmission of se.quentially confirmed alarms.
   * maintains a confirmation state for all Alarm Zones, such that entry delay will be prevented if confirmed alarms are not inhibited in the zone.
   * causes inputs in an Alarm Zone to be automatically isolated if they are still active when the confirmation time expires. An additional Contact ID restoral message is also transmitted on expiry of the confirmation time.
4. Click each of the other sub-tabs in turn and configure as required:

<details>

<summary>NPSA tab</summary>

1. Click the **NPSA** sub-tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8d5d6b6b423c312339db934a0c496d8d161b03b3%2F44865.png?alt=media)
2. Configure the **CAPSS Compliance** settings if required.

   **Note:** These checkboxes will all be checked by default if your site is licensed for CAPSS.

   <table><thead><tr><th width="202">Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Disable Controller web overrides</td><td>With this option checked, the <strong>Enable WWW Connections</strong> and <strong>Cancel WWW Override</strong> overrides for Controllers will be removed from the workstation menu. Uncheck this option if you want these overrides to be available.<br><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-31ef07d6bfbc6f00294dfa054350dcb6711fc9ea%2Fcontrollerwwwoverrides.png?alt=media" alt="SP_CompetencyMessages"></td></tr><tr><td>Disable Contrtoller web services</td><td>With this option checked, the <strong>Dip Switch 1 controls the diagnostic web interface</strong> checkbox (on the <strong>Setup</strong> tab of Controller properties) will be greyed out so it cannot be enabled. Uncheck this option if you want this to be available.</td></tr><tr><td>Disable command line macros</td><td>With this option checked, the Macro command lines cannot be inserted. Uncheck this option if you want to be able to insert Macro command lines.</td></tr><tr><td>Hide version numbers on HBUS Terminals</td><td>With this option checked, the Firmware version numbers will not appear on an HBUS Terminal screen. Uncheck this option if you want Firmware version numbers to appear on an HBUS Terminal screen when the <strong>#</strong> button is pressed several times.</td></tr></tbody></table>
3. Check the **AACS Compliance** checkbox if your site needs to comply with AACS standards.

   When the **AACS compliance** option is enabled:

   * the **Enable PIN validation** checkbox is selected automatically and is 'read-only',
   * a "Class" option becomes available to choose from, and based on the selected "Class" the following options will either be enforced or available to modify:

     ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-09cb773db6da6ff8e8fa7ba330092e2da6cb8147%2F44870.png?alt=media)

     **Note:** If your site is licensed for CAPSS all the options will be ticked and enforced by default, with **Class 3** option selected.

   When AACS Compliance option is unchecked, the below options will still be available to select/deselect.

   <table><thead><tr><th width="229">Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Enable PIN validation</td><td><ul><li>is enabled by default</li><li>when selected, the <strong>Enable PIN validation for REST card imports</strong> checkbox is selected and can be configured.</li></ul><p>Standard PIN pattern validation is enforced for manual PIN assignments in Command Centre and Configuration Client.</p><ul><li>when deselected, the <strong>Enable PIN validation for REST card imports</strong> checkbox is deselected and 'read-only'.</li><li>enforced or Class 1, Class 2 and Class 3 AACS</li></ul></td></tr><tr><td>Enable PIN validation for REST card imports</td><td><ul><li>is enabled by default</li><li>when unticked it will disable the PIN validation (sequences and repeating characters) for REST card imports</li><li>enforced for Class 1, Class 2 and Class 3 AACS</li></ul></td></tr><tr><td>PINs must be System Generated</td><td><ul><li>is disabled by default and the user is allowed to Assign PIN manually</li><li>when ticked the user cannot Assign PIN manually through <strong>Cardholder</strong>><strong>Print/Encode</strong> in Configuration Client OR <strong>Cardholder Viewer</strong>><strong>Cardholder Cards tile</strong>><strong>Assign PIN</strong> in Command Centre Client</li><li>enforced for Class 1, Class 2 and Class 3 AACS</li></ul></td></tr><tr><td>Password must be System Generated</td><td><ul><li>is disabled by default and the user is allowed to change the password manually</li><li>when checked the Password textbox becomes "read-only" and cannot be typed manually through <strong>Cardholder</strong>><strong>Operator configuration</strong>><strong>New Password</strong> option and <strong>Manage</strong>><strong>Change Password</strong>><strong>New Password</strong> option in Configuration Client OR <strong>Burger Menu</strong>><strong>Change Password</strong> and <strong>Cardholder Viewer</strong>><strong>Logon details</strong> option in Command Centre Client</li><li>enforced for Class 2 and Class 3 AACS but enabled and available to modify for Class 1 AACS</li></ul></td></tr><tr><td>View new PIN on first use at configured HBUS Terminals</td><td><ul><li>is disabled by default</li><li>when checked the <strong>Allow assigning of system generated PIN</strong> checkbox (in the 'PIN Handling' section on the <strong>Advanced</strong> tab of the HBUS terminal properties) becomes available to select. When selected the system generated PIN can be viewed on the configured HBUS terminal when a card is badged for the first time.</li><li>when checked 'View PIN’ functionality is disabled, (i.e. the <strong>View PIN</strong> button is disabled, and a <em>"View PIN at configured HBUS Terminals"</em> message displays when the <strong>Generate PIN</strong> button is clicked</li></ul><p><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a716925f8d86c7c861544f44978bc61aadcee2bd%2Fstandardstab_npsa_pinselection.png?alt=media" alt="SP_Icons" data-size="original"></p><ul><li>enforced for Class 3, eanbled and available to modify for Class 2 and unchecked for Class 1 AACS</li></ul></td></tr></tbody></table>
4. Check the **Comply with NPSA Readers and Tokens** checkbox if your site needs to comply with NPSA Readers and Tokens.

   If you enable this option, the following changes also occur for other properties:

   * **Card Security t** ab (Server Properties):

     The "Enable Fast CSN Mode" and "Allow Admin card update at readers" checkboxes, and the **Generate Admin Card** button all become disabled/un-editable.
   * **PINs** tab (Card Type properties):

     The "Use PINs" checkbox becomes ticked by default, as new card types should be created to use PINs with a minimum of 4 digits.
   * **Mobile Access Settings** tab (Server Properties and Reader properties):

     Mobile Connect settings become disabled/un-editable.
   * **Advanced** tab (Reader properties):

     "Require MIFARE Enhanced Security encoded cards" checkbox is ticked and becomes disabled/un-editable.

     "Use MIFARE Serial Number as Card Data" checkbox becomes disabled/un-editable.

     The Permitted Card Technology is forced to only allow the "Mifare Desfire EV1 to EV3" option.

</details>

<details>

<summary>EN50131 tab</summary>

1. Click the **EN50131** sub-tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b1084f1366f58a999657f580ba66ed53e626ba74%2Fstandardstab_en50131.png?alt=media)
2. Check the **EN50131 Compliance** or **SSP1014 Compliance** checkbox depending on which standard your site needs to comply with.

   These options are only applicable to sites wanting to comply with UK standards (EN50131), or Swedish standards (SSF1014), and makes it easier to configure a site for compliance.

   In its simplest form it would be checked by the installer before any other site configuration, would auto-select most of the other options on the **EN50131** tab and otherwise would simply change the defaults for various other settings.

   When checked, most of the EN50131 and SSF1014-required configuration is applied at once.

   **Note:** Installers will still need to configure Divisions, Operator Groups, etc. appropriately.
3. Configure the fields as required:

   <table><thead><tr><th width="202">Checkbox</th><th>Description</th></tr></thead><tbody><tr><td>Restrict indications of alarms on terminal while Armed</td><td>Checking this option removes all visual and audio indicators on the 'Welcome' screen of a terminal (i.e. any active alarms while the Alarm Zone is armed).</td></tr><tr><td>Delay alarm dialling for alarms during entry delay</td><td>With this option checked, any alarm activations that occur during entry delay will have immediate local indications, (i.e. relays, etc.), according to their Action Plan setup. However, remote notification via alarm dialling will be delayed until the end of entry delay, or 30 seconds, whichever is greater. The alarm activations will not be remotely notified if unsetting occurs successfully before the expiry of entry delay.</td></tr><tr><td>Tamper alarm on Controller upgrade</td><td>With this option checked, an alarm will be created whenever Controller firmware is upgraded. When enabled, an active tamper condition is created when a download starts. This alarm is made inactive by any event that indicates the end of a download. This includes both successful and unsuccessful completion.</td></tr></tbody></table>

</details>

<details>

<summary>GovPass tab (This sub-tab will only display if your site is licensed for GovPass, (i.e. the license file contains <code>UKGovPass=1</code>))</summary>

1. Click the **GovPass** sub-tab.

   **Note:** There is no limit to the number GovPass card flows and card types a site can have.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-87fdf0a35a924f819ad617a4ec74053a0f11fee9%2Fstandardstab_govpass.png?alt=media)
2. The **Reader** drop-down list displays all the readers connected to Command Centre.

   Select the appropriate reader from the Reader drop-down list.
3. Manually type in the **Configuration Key**, or copy and paste it in.
4. Present a GovPass configuration card to the USB MIFARE reader connected to the Command Centre Server PC with the key to be used to read the Cardholders cards.

   Once the card is read successfully, a green bar displays and a completed message displays asking you to click the **Apply** button to save the changes.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7464e52d9e74d7741d7272267c1bddd7ea4fe25c%2Fstandardstab_govpass_successfulcardread.png?alt=media)

   **Note:** The following table describes the errors that can occur:

   <table><thead><tr><th width="229">Error message</th><th>Problem</th></tr></thead><tbody><tr><td><em>Authentication failed with supplied key(s).</em></td><td>The key entered (or read from previous Configuration card) does not match this Configuration card.</td></tr><tr><td><em>The Configuration Key must be exactly 32 characters long.</em></td><td>The key entered for the first Configuration card read is not the correct size.</td></tr><tr><td><em>Timeout waiting for card read. No Card detected.</em></td><td>The encoder/reader did not detect a valid card to read.</td></tr><tr><td><em>Detected card does not appear to be a valid GovPass Configuration card.</em></td><td>The card is a non-GovPass card (Classic, Plus, PIV).</td></tr><tr><td><em>Card application not found.</em></td><td>The card is not a <strong>*valid*</strong> GovPass Configuration card. This is a different error to the above as it is a valid DESFire card but is lacking one or more GovPass applications.</td></tr><tr><td><em>The data necessary to complete this operation is not yet available.</em></td><td>Something went wrong talking to the encoder/reader. If you try to read the card again it should work on the second or subsequent attempt(s).</td></tr></tbody></table>
5. Tick the **Online Validation** checkbox if your site intends using the GovPass REST API.

   All fields become enabled, allowing you to set up all the values required to communicate with the GovPass REST API.

   **Note:** If this box is unticked, any cards subsequently enrolled will have Status = Active, and cards with Unverified status will be changed to Active. The following warning will display if unticked:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6499d54d44c959ea7ecee62d5a9885744900d6b0%2Fonlinevalidationscreen.png?alt=media)
6. Configure the fields as required:

   <table><thead><tr><th width="229">Field / Button</th><th>Description</th></tr></thead><tbody><tr><td>Base URL *</td><td>This is the address of the endpoint we need to connect to. This field accepts alpha-numeric and special characters. (Maximum limit = 100 characters)<br><br><strong>Note:</strong> Operators require the "Manage Keys" privilege to edit this field, otherwise it will be "read-only".</td></tr><tr><td>Site ID *</td><td>Also known as the Building ID, this is the identifier for the site. If there is more than one Access Control System per site, a Site ID will be issued per system. This field accepts alpha-numeric and special characters. (Maximum limit = 50 characters)<br><br><strong>Note:</strong> Operators require the "Manage Keys" privilege to edit this field, otherwise it will be "read-only".</td></tr><tr><td>API Key *</td><td>This is the key required to authenticate with the GovPass REST API to enable usage. This is an alpha numeric value, with no special characters, and must be exactly 40 characters.<br><br><strong>Note:</strong> Operators require the "Manage Keys" privilege to edit this field, otherwise it will be masked and "read-only".</td></tr><tr><td>Restricted Enrolment Period</td><td>When Restricted Enrolment Period is selected and a time period specified (from 1 to 999 hours), if the GovPass Check Service was unable to be contacted at the time of enrolment and this condition lasts for longer than the specified time the card becomes disabled with card state "Suspended (Not Verified)". Command Centre will continue to attempt to contact the GovPass Check service and once successful will update the card state to the correct value (which may result in the card becoming Active).<br>When Restricted Enrolment Period is not selected, cards may be enrolled with the service offline and may remain in the "Unverified" state indefinitely. (Default = 24 hours)<br><br><strong>Note:</strong> Operators require the "Configure Site" privilege to edit this field.</td></tr><tr><td>Revocation Check Period</td><td>When selected, Command Centre will contact the GovPass Check Service with the specified period (from 1 to 24 hours), starting at the specified Initial Check time.<br>Any cards found to be revoked will be disabled Revoked (GovPass), Inactive, Expired (GovPass) or Lost (GovPass).<br>It depends on what the revocation status is. (Default = 12 hours)<br><br><strong>Note:</strong> Operators require the "Configure Site" privilege to edit this field.</td></tr><tr><td>Initial Check</td><td>This is only enabled when the Revocation Check Period is ticked, and specifies the starting time for the Revocation Check. (Default = 2 hours. Range = 0 - 23:59)</td></tr><tr><td>Check Revocation Now</td><td>When this button is clicked a revocation check is carried out immediately.</td></tr><tr><td>Enable Occupancy Monitoring</td><td><p>Occupancy Monitoring can be turned off by unchecking this option. When turned off:</p><ul><li>the Occupancy Count will no longer be updated to the GovPass API, and</li><li>the reset occupancy count, department and exit zones will be disabled as these are all related to occupancy counting.<br>(Default = Checked)</li></ul></td></tr><tr><td>Reset Occupancy Count Daily</td><td>When this checkbox is ticked, the occupancy count for each department is reset every midnight (12:00am) and is passed on to the GovPass Check Service.<br><br><strong>Note:</strong> Although occupancy is based on Cardholder location in Command Centre, locations will not automatically update at midnight because this might interfere with other functionality in Command Centre, (e.g. Evacuation Reports). Cardholders are only marked as outside for the purpose of occupancy counting at midnight and their location according to their status will not be changed.</td></tr><tr><td>Department (PDF)</td><td>This is the Personal Data Field (PDF) that will be used to identify which GovPass Department a cardholder belongs to. It is used to report the number of cardholders belonging to each department who are currently on-site, known as Building Occupancy.<br><br><strong>Note:</strong> Only "Text" or "Text - List" PDF types can be selected.</td></tr><tr><td>Exit Zones</td><td>Access Zone(s) can be dragged in this grid to be used as Exit Zones. When a cardholder’s location changes to one of these zones or to the special "Outside the system" zone, the occupancy count for the cardholder’s department (or Unconfigured) is decremented.</td></tr></tbody></table>

   \* Mandatory fields.

   **Note:** A site can untick the **Online Validation** checkbox at any point, should they choose to opt out of the validation. All 'Unverified' cards will automatically be set to 'Verified', and any queued messages to the GovPass REST API will be cleared.

</details>

<details>

<summary>CipherToken tab (This sub-tab will only display if your site is licensed for CipherToken, (i.e. the license file contains <code>CipherToken=1</code>))</summary>

1. Click the **CipherToken** sub-tab.

   **Note:** There is no limit to the number of CipherToken card flows and card types a site can have.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f75fa5d3bb11a35663ba3131a6e5bf6ccf95a44d%2Fstandardstab_ciphertoken.png?alt=media)
2. The **Reader** drop-down list displays all the readers connected to Command Centre.

   Select the appropriate reader from the Reader drop-down list.
3. Manually type in the **Configuration Key**, or copy and paste it in.
4. Present a CipherToken configuration card to the USB MIFARE reader connected to the Command Centre Server PC with the key to be used to read the Cardholders cards.

   Once the card is read successfully, a green bar displays and a completed message displays asking you to click the **Apply** button to save the changes.

   **Note:** The following table describes the errors that can occur:

   <table><thead><tr><th width="229">Error message</th><th>Problem</th></tr></thead><tbody><tr><td><em>Authentication failed with supplied key(s).</em></td><td>The key entered (or read from previous Configuration card) does not match this Configuration card.</td></tr><tr><td><em>The Configuration Key must be exactly 32 characters long.</em></td><td>The key entered for the first Configuration card read is not the correct size.</td></tr><tr><td><em>Timeout waiting for card read. No Card detected.</em></td><td>The encoder/reader did not detect a valid card to read.</td></tr><tr><td><em>Detected card does not appear to be a valid CipherToken Configuration card.</em></td><td>The card is a non-CipherToken card (Classic, Plus, PIV).</td></tr><tr><td><em>Card application not found.</em></td><td>The card is not a <strong>*valid*</strong> CipherToken Configuration card. This is a different error to the above as it is a valid DESFire card but is lacking one or more CipherToken applications.</td></tr><tr><td><em>The data necessary to complete this operation is not yet available.</em></td><td>Something went wrong talking to the encoder/reader. If you try to read the card again it should work on the second or subsequent attempt(s).</td></tr></tbody></table>

</details>

<details>

<summary>UL2610 Intruder Alarms</summary>

1. Click the **UL2610 Intruder Alarms** sub-tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-e89ee6fcf44d977884ab8b5c1a0b23def0b5e8c8%2Fstandardstab_ul2610intruderalarms.png?alt=media)
2. Check the **Enable indication of controller upgrade on connected readers/terminals** checkbox if you want users to be made aware when controllers are upgrading by way of a unique flash pattern on the readers connected to the controller.

</details>

5. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/configuration-client/site-installation/server-properties/standards.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.
