AONA · SYNTHETIC WORKED EXAMPLE
Employee AI security review
Fictional example. This 30-day review uses invented records from two teams. It is not a customer report, an Aona export or evidence of compliance.
1. Review scope
A fictional review of two teams and twenty policy outcomes. The question: which examples should the security owner inspect before changing policy scope?
20Sample outcomes
2Teams
30Day window
2. Outcome summary
| Outcome | Finance | Operations | Total |
|---|---|---|---|
| Compliant | 6 | 6 | 12 |
| Redacted | 2 | 2 | 4 |
| Blocked | 1 | 2 | 3 |
| Warned | 1 | 0 | 1 |
| Total | 10 | 10 | 20 |
These 20 outcomes include compliant activity. The public events API excludes compliant records and would not provide the same report scope.
3. An accountable follow-up
| Observation | Three synthetic actions were classified as blocked. |
|---|---|
| Owner | Security lead |
| Question | Is the selected workflow correctly scoped? |
| Next decision | Inspect the synthetic cases and control requirements before tuning policy. |
| Unresolved | Real collection coverage, policy behavior and product export fidelity have not been demonstrated by this example. |
Return to the reporting page · Use your browser's Print command for this illustrative layout.