> 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/licensable-features/ciphertoken-card-support/rolling-configuration-on-a-ciphertoken-card.md).

# Rolling configuration on a CipherToken card

### Introduction

If CipherToken keys have been compromised they can be rolled by creating a new configuration card which is then reimported to Command Centre.

**Note:** Configuration on CipherToken cards can be rolled a maximum of six times. After that, all cards would need reissuing.

This procedure describes how to update/modify the Configuration Key on a CipherToken Card Type.

### Configuration

Click **FIle** from the menu bar, then **Server Properties**.

The **Command Centre Server Properties** List Window opens.

1. Click the **Standards** tab.
2. Click the **CipherToken** sub-tab.
3. Present the correct card at the reader and click the **Read Card** button.

   ![](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)

### Result

The system successfully reads the new configuration data, and once the **Apply** button is clicked the configuration is sent to the Controller(s).

**Important:** The user muist apply the changes.


---

# 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/licensable-features/ciphertoken-card-support/rolling-configuration-on-a-ciphertoken-card.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.
