Skip to content

Set rotation intervals and handle overdue machine credentials

Rotation for non-human identities (NHIs) is driven by each NHI’s own rotation interval. AtmanID flags an NHI as overdue when its interval has passed, and an administrator decides what happens next. Nothing rotates on a schedule by itself: rotation runs when someone records it, rotates a vaulted secret, or quarantines overdue NHIs.

The pages are under Security & Risk → Machine Identities (tabs All NHIs and Posture).

Who can do what

Task Roles
View NHIs, overdue list, posture Identity Admin, Tenant Owner, PAM Admin, Security Analyst, Compliance Officer, CISO, Super Admin
Change an NHI (interval, overdue action) Identity Admin, Tenant Owner, PAM Admin, Super Admin
Mark Rotated in the detail drawer Identity Admin, Tenant Owner, Super Admin
Bulk mark rotated, Quarantine PAM Admin, Identity Admin, Super Admin (Tenant Owner via the API)
Vault: store and rotate secrets PAM Admin, Super Admin

1. Set the rotation interval

When you register an NHI (Register NHI on All NHIs), fill in Rotation Interval (days), and an Expiry Date for API keys and certificates. Leave the interval empty to use your organisation’s default for the type (see NHI Policy Settings). An NHI without an interval shows No policy and never appears as overdue; the posture score counts the missing policy as a risk factor. An NHI with an interval counts as Never rotated (and so overdue) until a rotation is recorded: if its secret is new, click Mark Rotated after registering it.

To change it later, open the NHI and click Change next to Rotation Policy on the Details tab. Enter 1–3650 days, or leave the field empty and Save to remove the policy. The API equivalent is PATCH /api/nhi/{id} with rotation_interval_days (a number, or null for no policy).

2. Choose what happens when it goes overdue

Open the NHI and, on the Details tab, set Overdue Action:

Option When you quarantine an overdue NHI
Quarantine (default) It is set to inactive and its owner is notified.
Auto-rotate (push to source) AtmanID creates a new credential in the linked application and stores it in the vault. If that fails, the NHI is quarantined.
Auto-rotate, quarantine on fail Same as Auto-rotate.

The change saves immediately. Auto-rotate needs the NHI to be linked to an application whose connector supports rotation (AWS IAM; Entra ID and Google Cloud service-account keys are not yet verified in production).

After the new secret is stored in the vault, AtmanID retires what it replaced: earlier vault versions are marked Rotated, and the previous credential is deactivated (not deleted) in the source system when AtmanID created it in an earlier rotation. The first automatic rotation of an NHI cannot do that, because its original key was made outside AtmanID: disable that one in the source system yourself. The NHI_SECRET_ROTATED event’s old_credential field says which happened (deactivated, not_recorded, unsupported or failed).

3. Work the overdue list

On All NHIs, the banner shows N NHIs overdue for secret rotation. Click Show to open the list. Each row shows Never rotated or {n}d overdue and its risk.

  • Mark Rotated (per row) or Mark {n} Rotated (selected rows): records that the secret was rotated outside AtmanID. Nothing changes in the source system.
  • Quarantine {n}: applies each selected NHI’s Overdue Action after a confirmation. Quarantine is reversible: once the secret has been rotated (or recorded with Mark Rotated), open the NHI and click Reactivate. While it is still overdue the button is disabled and says why, since the next quarantine run would take it straight back out.

The Mark Rotated button in an NHI’s detail drawer does the same as the per-row action and accepts an optional note.

4. Rotate a vaulted secret

If you store the NHI’s secret in AtmanID, open the Vault tab in the detail drawer (PAM Admin and Super Admin only). Click Rotate on the secret, paste the New Secret Value, add Rotation Notes (optional), and click Confirm Rotation. The old version is kept as Rotated under Rotation History and the NHI’s last-rotated date updates. You still have to put the new value into the system that uses it. A secret’s Rotation Due date is shown only; nothing alerts on it.

5. Watch posture

Machine Identities → Posture scores every NHI. Rotation adds Rotation overdue by Nd (weight 30) and No rotation policy (15 for API keys and certificates, 8 otherwise). Expired and soon-expiring credentials add their own factors.

NHI Policy Settings

Platform Config → Governance Settings → NHI policy holds Rotation Interval Defaults by Type, a Secret Rotation Threshold, a rotation reminder and owner auto-escalation. Changes are audited (NHI_SETTINGS_UPDATED).

  • Rotation Interval Defaults by Type: an NHI registered without its own Rotation Interval (from the dashboard, the API or Iris) gets the default for its type; NHI_REGISTER records rotation_interval_from_type_default. NHIs that already exist keep their interval; change those on each NHI. The Impact preview shows how many existing NHIs without an interval would be overdue if they had these defaults.
  • Secret Rotation Threshold, the reminder and owner auto-escalation are saved but not applied yet: they are for scheduled rotation and owner reminders, which are not running. Overdue detection and the posture score use each NHI’s own interval.

Not supported today

  • Scheduled automatic rotation, or reminders to owners before the due date.
  • An overlap window for the old secret after an automatic rotation.

AI agent keys are separate: rotate them with Rotate on AI Governance → Credentials & Delegation → Credentials (or on the agent’s Credentials tab). The new key is shown once, with a Copy button; copy it before you dismiss the dialog. The old key stops working immediately. A revoked key cannot be rotated; issue a new one.

Audit trail

NHI_SECRET_ROTATED (recorded, bulk-marked, vault or automatic rotation), NHI_ROTATION_ENFORCED (quarantined), NHI_QUARANTINED_ROTATION_UNSUPPORTED (automatic rotation failed), NHI_UPDATE (interval or overdue action changed, or reactivated — reactivated: true). See the audit trail.

© AtmanID · Privacy