Agentic Risk Analyst

What could go wrong with this AI use case, and what should we do about it?

Chirag Dani · ARA v3.2.1
LLM: huggingface · meta-llama/Llama-3.3-70B-Instruct · Secure-RAG: connected

Library / ARA-261031-2D523F / governance

Worked example: Generative AI chatbot for internal HR policy

Versions of this assessment, reviewer sign-off, suggested framework mapping, and every linked deliverable.

Sign-off

Sign off version 1 (the latest run). 15 of 15 items are not yet reviewed; the sign-off will record this.

Versions (1)

VersionSaved (UTC)ModelSHA-256
12026-10-31 06:37:15Worked example: prepared in advance, not generated livef73afa28ce4bdd86

Client

Item-by-item review

Confirm each AI-drafted risk, threat, regulatory finding and control. 0 of 15 reviewed (0 changed, 0 rejected). "Accepted with changes" needs a note describing the change. The counts are sealed into the sign-off.

TypeIDItemReviewNoteLast reviewed
riskR-01Employees see colleagues' salary or medical data (Critical)
riskR-02Wrong policy answers (Medium)
riskR-03External LLM retains HR data (High)
riskR-04Translation errors change policy meaning (Medium)
threatT-01Permission bypass through retrieval (Critical)
threatT-02Indirect prompt injection in a policy document (Medium)
regulationREG-01Privacy Act 1988: potentially_applicable
regulationREG-02General Data Protection Regulation (EU) 2016/679: potentially_applicable
regulationREG-03Regulation (EU) 2024/1689 (AI Act), Article 50 transparency: potentially_applicable
regulationREG-04Personal Information Protection Law (China); LGPD (Brazil): not_enough_information
controlC-01Permission-aware retrieval
controlC-02Exclude personal records from the index
controlC-03Provider terms: no training, limited retention
controlC-04Grounded answers with citations and version control
controlC-05Leakage testing before go-live

Deliverables

Failure simulationsnone
Operating envelopesnone
ADM inventory entriesnone (add)
Vendor reviewsnone (start)

Framework mapping (suggested)

Suggested by keyword rules at heading level; verify each mapping against the licensed standard before using it in a statement of applicability or audit.

ControlISO/IEC 42001 Annex ANIST AI RMFISO/IEC 27001:2022OWASP LLM 2025
C-01 Permission-aware retrieval---LLM06 Excessive Agency; LLM08 Vector and Embedding Weaknesses
C-02 Exclude personal records from the indexA.2 Policies related to AI---
C-03 Provider terms: no training, limited retentionA.10 Third-party and customer relationships---
C-04 Grounded answers with citations and version controlA.2 Policies related to AI; A.6 AI system life cycleGOVERN5 OrganizationalLLM09 Misinformation
C-05 Leakage testing before go-liveA.6 AI system life cycleMEASURE-LLM08 Vector and Embedding Weaknesses

Headings with no mapped control

ISO/IEC 42001 Annex A: A.3 Internal organization; A.4 Resources for AI systems; A.5 Assessing impacts of AI systems; A.7 Data for AI systems; A.8 Information for interested parties of AI systems; A.9 Use of AI systems

NIST AI RMF: MAP; MANAGE

An uncovered heading is a prompt to check whether a control is needed, not proof of a gap.

Decision support only, not legal or regulatory advice. AI-generated ratings and citations must be reviewed by a qualified person before they are relied on.