> ## Documentation Index
> Fetch the complete documentation index at: https://syteca.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Syteca secret rotation

> Rotate the shared secret used to establish a trusted connection between the Syteca and ESPM, ensuring uninterrupted communication and secure authentication between them.

## Overview

A shared secret is used to establish and maintain a trusted connection between Syteca and the ESPM module.

To maintain security and ensure uninterrupted operation, the secret should be rotated before it expires. During the rotation process, ESPM supports both the old and the new secret until the previous secret reaches its expiration date, allowing administrators to update ESPM without disrupting service.

<Note>
  Secret rotation requires the [Tenant Management and System Configuration administrative permission](/docs/administration/users/administrative-permissions).
</Note>

## Procedure

1. Rotate the secret in **Syteca** before the current secret expires.
2. Copy the newly generated secret.
3. Open the **ESPM Portal**.
4. Navigate to **Configuration**.
5. Locate the secret configuration field.
6. Paste the newly generated secret into the masked secret field.
7. Click **Save**.
8. Confirm the action when prompted.
9. ESPM updates the stored secret and begins using it for communication with the Main Application.
10. The rotation event is recorded in the internal audit log.
11. Verify the **Last Updated** date displayed in the configuration page.

## What Happens After Rotation?

Once the new secret is saved:

* ESPM begins using the new secret for authentication.
* The old secret remains valid until it expires.
* Both secrets can be used during the transition period.
* Communication between the Syteca and ESPM continues without interruption.
* The rotation event is recorded for auditing purposes.

## If the Secret Is Not Updated

If the secret expires before it is updated in ESPM:

* Authentication between the Syteca and ESPM will fail.
* Users will no longer be able to access ESPM through Syteca.
* Administrative intervention will be required to restore connectivity.

In this situation, follow the troubleshooting procedures to restore the trusted connection.

## Key Considerations

* Rotate secrets before their expiration date to avoid service interruptions.
* Always verify that the new secret has been successfully saved in ESPM.
* The **Last Updated** field can be used to confirm when the current secret was configured.
* Secret rotation events are automatically recorded in the internal audit log for traceability and compliance purposes.
* During the grace period, both the previous and current secrets remain valid until the older secret expires.