Menu AuthGuardHelp centre
Portuguêsauthguard.pt

End users · Privileged access (PAM)

Request break-glass (emergency) access

  • 1 min read
  • SaaS · Self-hosted · Edge
  • Video
Tutorial 14Privileged access: request and approve2:02 · Narrated in Portuguese, with English captions.Transcript and details

Break-glass access is for incidents where there is no time for the normal approval path. Only members of your organization's break-glass group can request it, and another member must confirm.

How do I request it?

  1. Open «Access» › «Break-glass».
  2. Fill in:
    • «Account»: the privileged account you need.
    • «Duration (minutes, at most 60)».
    • «Incident reference»: the incident's identifier (up to 128 characters).
    • «Justification (at least 20 characters)».
  3. Choose «Request break-glass access».
  4. «Break-glass access requested. Another officer must confirm within 15 minutes; then activate it under My access.» appears.
  5. Call another officer and ask them to confirm.
  6. After the confirmation, activate the access under «My access» with your passkey, also within 15 minutes.

How do I confirm a colleague's request?

  1. Under «Access» › «Break-glass», the request appears as «Waiting for your confirmation».
  2. Check the situation with your colleague and choose «Confirm with passkey».
  3. «Confirmed. The requester may now activate the access.» appears.

What happens during and after?

«Break-glass access is active: every action is recorded, the credential is rotated when it ends and administrators review it.»

  • Officers and administrators are emailed about the request and the confirmation.
  • At the end, the account's credential is rotated.
  • An administrator who is not an officer reviews the access within 72 hours and marks it justified or not.

The option does not appear

Only members of the break-glass group see the request form. If you are not in the group, use the normal request under «My access». Break-glass requests do not go through the normal approvers or the phone.

Error codes in this article

Article referenceeu-pam-breakglassquote it to support to identify this article. Checked against the product at commit 5f6607a8.