Fictional training scenario. This prototype uses generated records only. It does not connect to a bank, collect real data, change accounts, or provide an audit opinion.
Access review, step by step
A reviewer controls each stage: approve the evidence request, inspect test results, disposition findings, approve a draft report, then record a follow-up plan.
Case ITAR-2026-014 · Fictional Northstar Sample Bank
1. Evidence request
Define the test and request only the synthetic evidence needed for this sample review.
Awaiting reviewer
Control under review
Access to technology accounts is authorized, protected with MFA where required, and periodically reviewed.
Reference framework
NIST Cybersecurity Framework 2.0 · Identity Management, Authentication and Access Control (PR.AA).
Evidence requested
Fictional user/account list, role and privilege, employment status, MFA flag, last sign-in, last access review.
Review boundary
One synthetic snapshot only. No live monitoring, system access or account actions.
Reviewer check: Is this scope limited to the sample snapshot and relevant fields? Evidence source: generated CSV in this package. Data owner and approval for any real environment: Undecided · out of scope
Approval here is an in-demo reviewer choice only. No request is sent.
2. Accounts test
Run transparent rules against the fictional snapshot. Missing fields stay undecided.
Scope approved in demo
Test rules: flag an enabled account with explicit Former status; flag an admin role with MFA set to No; flag a missing review date as an evidence gap, not a confirmed failure. These are demo rules, not a bank policy.
Account
Employment
Role
Enabled
MFA
Last review
SYN-204
Former · synthetic HR snapshot
Platform Admin
Yes
No
2026-07-02
SYN-217
Active
Read Only
Yes
Yes
2026-10-15
SYN-231
Active
Operations Admin
Yes
Yes
Undecided · no date supplied
SYN-248
Active
Service Account
Yes
N/A
Undecided · owner not supplied
Before running: reviewer confirms the rule set and the supplied fields are sufficient for this synthetic test. Any live-system authority, policy thresholds and evidence provenance remain Undecided.
3. Review findings
Rule-generated proposals are not conclusions until a human reviews them.
Human disposition required
A reviewer can approve a proposal, reject it, or leave it Undecided. No account change, incident ticket, or notification is created.
4. Draft report
The report includes the evidence, rules and reviewer decisions, including unresolved items.
Awaiting reviewer approval
3Proposed observations
0Still undecided
0Changes executed
Reviewer confirms the draft faithfully reflects the sample evidence and keeps all open points marked undecided. This is not a compliance certification or an audit opinion.
5. Follow-up
Record a proposed next step without assigning a real owner or deadline.
Details undecided
Owner, deadline, remediation authority and any connection to a real work tracker are Undecided. Leave blank to preserve that status. No ticket or reminder is sent.
Reviewer may approve this as a sample follow-up record only. Any real-world owner, due date or implementation decision requires separate approval and verified policy.
No follow-up has been assigned.
Prototype v0.1 · local browser interaction · no AI model, network calls, credentials, real bank data, or system writes