The request
{
"name": "wever_cyber-access-check",
"arguments": {
"policy": {
"review_days": 90,
"dormant_days": 60,
"revoke_days": 2
},
"accounts": [
{
"id": "U-ANA",
"kind": "person",
"owner": "Ana Ruiz",
"owner_status": "active",
"level": "owner",
"needed": "admin",
"last_used_on": "2026-11-14",
"last_reviewed_on": "2026-10-01"
},
{
"id": "SVC-CI",
"kind": "service",
"owner": "Cam Lee",
"owner_status": "departed",
"level": "write",
"needed": "write",
"last_used_on": "2026-11-15"
}
],
"as_of": "2026-11-15"
}
}What the report returns
Verdict: cyber_access_overbroad.
| Finding, privilege above need | 1 account holds admin or owner access above the need: U-ANA (owner where admin is needed). |
|---|
| Finding, orphaned access | 1 account has standing access and no current owner: SVC-CI. |
|---|
| Fix, privilege above need | Lower admin or owner access to the level the work requires. |
|---|
| Fix, orphaned access | Assign a current owner to the account or key, or revoke it. |
|---|
The standing access is overbroad: privilege above need and orphaned access.
A person holds owner access where the work needs admin, and a deploy service still runs under an owner who has left. Both were used this week, so neither is dormant, and the privileged account was reviewed inside its cycle. The report states that lowering the owner access to admin and assigning the service a current owner, or revoking it, moves the verdict to cyber_access_scoped.