Skip to content

feat: dry-run a policy change against recent sign-ins #403

Description

@Bccorb

Why

Before tightening policy, admins need to know who it would block.

What

  • Evaluate a draft policy against the last N days of auth events
  • Report the users and sign-ins that would have failed and why
  • Shown in the console before publish

Done when

Admins see the impact of a policy before publishing it.

Activity

  1. added this to the v0.20 milestone on Oct 13, 2026
  2. added theissue type on Oct 13, 2026
  3. added
    P2GovRAMP readiness track
    safeServes the safe promise: no lockout, no lock-in, honest
    on Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2GovRAMP readiness tracksafeServes the safe promise: no lockout, no lock-in, honestv0.20Targets the v0.20 release

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions