Respond to a security alert

Purpose

Assess an unfamiliar sign-in, factor, session or account change and take the narrow protective action needed.

Obedience Cloud is the shared identity and tenant-control surface. It does not turn a platform role into a customer workspace role or a corporate owner, and it never exposes readable passwords or authentication-factor secrets.

Checks before action

• The event time, device and location are recognised.
• The alert came from an approved domain.
• Compromise risk and active work are considered.

Safe process

1. Use the canonical hostStart on cloud.obedience.global or the approved obedience.cloud entry and confirm the secure browser origin before entering account information.
2. Verify scope and authorityFor respond to a security alert, confirm the account, organisation, role and customer case or contract reference before continuing.
3. Complete the bounded actionUse the narrow control provided. Elevated operations require personal 2FA, exact-origin requests, unique request identifiers and durable audit availability.
4. Review the resultConfirm provider-authoritative state, record the outcome and route any inconsistency to support without repeating a high-impact request blindly.

Expected records

• User acknowledgement or report.
• Session or account action.
• Support or security case reference.

Security boundary

• Administrators can lock an account, revoke sessions or start a bounded support flow; they cannot read or choose the user’s password.
• A support actor session is time-limited, labelled, auditable and blocked from non-read HTTP methods.
• Tenant metadata is validated server-side and cannot contain executable JavaScript, secret credentials or hidden role elevation.