jabrena/plinth / skills/813-regulations-iso-42001
813-regulations-iso-42001
VerifiedUse when reviewing, designing, or modifying Java enterprise systems that use GenAI, LLMs, AI-assisted coding, RAG, AI agents, generated code, generated dependencies, prompt workflows, external model providers, or AI-enabled business logic and need ISO/IEC 42001 AI management system-aware engineering guidance. Part of Plinth Toolkit
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.6 KB |
| assets/questions/813-iso-42001-engineering-review-questionnaire.md | markdown | 9.2 KB |
| assets/reports/813-iso-42001-engineering-review-report-template.md | markdown | 9.1 KB |
| references/813-regulations-iso-42001-chapters-summary.md | markdown | 11.4 KB |
| references/813-regulations-iso-42001-engineering-examples.md | markdown | 14.3 KB |
assets/reports/813-iso-42001-engineering-review-report-template.md
View on GitHub# ISO/IEC 42001 Engineering Review Report
Use this template after reviewing `references/813-regulations-iso-42001-chapters-summary.md`, asking the needed questions from `assets/questions/813-iso-42001-engineering-review-questionnaire.md`, and matching the relevant examples from `references/813-regulations-iso-42001-engineering-examples.md` for AI inventory, generated-code review, dependency provenance, prompt and data boundaries, AI-enabled business logic, monitoring, incident handling, corrective action, and owner handoffs.
This report is not legal advice, certification advice, audit advice, an audit conclusion, or a final conformity decision. Use it as engineering evidence for AI governance, legal, compliance, privacy, security, risk, platform, product, procurement, model-provider, architecture, release, and business-owner review.
The purpose of this report is to increase awareness of potential GenAI Java delivery gaps and create engineering evidence for qualified review. The response produced from this template does not represent ISO/IEC 42001 certification readiness, legal compliance, audit pass/fail status, compliance approval, final risk acceptance, or final conformity with ISO/IEC 42001.
Official public source references:
- ISO 42001 explained: `https://www.iso.org/home/insights-news/resources/iso-42001-explained-what-it-is.html`
- ISO/IEC 42001 standard page: `https://www.iso.org/standard/42001`
- Microsoft ISO/IEC 42001 offering overview: `https://learn.microsoft.com/en-us/compliance/regulatory/offering-iso-42001`
## 1. Review Context
- Java system, service, repository, module, delivery pipeline, or AI-enabled capability:
- Repository or implementation path:
- Review date:
- Reviewers:
- System owner:
- Product or business owner:
- AI governance owner:
- Technical owner or architect:
- Security owner:
- Privacy or data owner:
- Legal/compliance owner:
- Risk owner:
- Platform or release owner:
- Procurement or model-provider owner:
- Source materials reviewed:
## 2. AI Management System Scope
- GenAI capability or AI-assisted delivery path:
- Lifecycle stage:
- Model provider or AI tool:
- Prompt workflow:
- RAG sources or retrieval workflow:
- AI-agent tools or actions:
- Generated Java code, SQL, tests, migrations, configuration, API contracts, dependencies, or business rules:
- Data classes in prompts, retrieval, logs, model calls, or reports:
- Environments in scope:
- Users, affected groups, operators, or business processes:
- AI inventory or capability register evidence:
- Open scope questions:
## 3. Engineering Evidence Reviewed
- Java applications, libraries, APIs, jobs, agents, or generated code:
- Build files, Maven dependencies, plugins, SBOM, vulnerability scans, and license/provenance evidence:
- Prompts, prompt versions, model versions, model-provider approvals, and provider-boundary records:
- RAG retrieval sources, source approval, grounding checks, and source freshness evidence:
- AI-agent tool policies, tool action audit logs, preconditions, approvals, and rollback:
- Generated outputs, generated business logic, fairness or impact tests, and domain-owner approvals:
- CI/CD workflows, pull requests, tests, static analysis, security checks, and release approvals:
- Monitoring, incident, corrective-action, rollback, disablement, and continual-improvement records:
- Owner handoffs and qualified review records:
## 4. Potential Management-System Nonconformity Mapping
This section is not a certification or audit finding. Use it to list concrete potential ISO/IEC 42001 AI management system nonconformity signals from the reviewed evidence and route each item to qualified AI governance, audit, legal, compliance, privacy, security, risk, platform, product, procurement, model-provider, architecture, release, or business-owner review. When no concern is confirmed, say so explicitly and keep open items as potential evidence gaps.
| Potential nonconformity or risk signal | ISO/IEC 42001 management-system reference area | Associated public source link | Evidence from reviewed system | Current status | Required owner review | Engineering action |
| -------------------------------------- | ---------------------------------------------- | ----------------------------- | ----------------------------- | -------------- | --------------------- | ------------------ |
| AI capability, AI-assisted delivery path, model provider, prompt flow, generated artifact, or owner is not inventoried | AI management system scope and documented information | https://www.iso.org/home/insights-news/resources/iso-42001-explained-what-it-is.html | TBD | None identified / Potential gap / Confirmed concern | AI governance / platform / product owner | TBD |
| GenAI risks are not assessed or treated before merge, release, or operation | Planning, risk treatment, and operational control | https://www.iso.org/standard/42001 | TBD | None identified / Potential gap / Confirmed concern | Risk / AI governance / release owner | TBD |
| Generated code, SQL, migrations, configuration, tests, dependencies, or business rules bypass engineering review | Operation and lifecycle controls | https://www.iso.org/home/insights-news/resources/iso-42001-explained-what-it-is.html | TBD | None identified / Potential gap / Confirmed concern | Architecture / platform / security owner | TBD |
| Proprietary source, personal data, regulated data, logs, secrets, or trade secrets may enter prompts, model calls, or evidence stores without controls | Support, documented information, data governance, and provider boundary | https://learn.microsoft.com/en-us/compliance/regulatory/offering-iso-42001 | TBD | None identified / Potential gap / Confirmed concern | Privacy / security / legal / model-provider owner | TBD |
| Generated dependency suggestions lack SBOM, vulnerability, license, provenance, or malicious-package review | Operational control and supply-chain governance | https://www.iso.org/standard/42001 | TBD | None identified / Potential gap / Confirmed concern | Platform / security / open-source program owner | TBD |
| AI-enabled business logic lacks bias, impact, domain-owner, override, complaint, or monitoring evidence | Responsible AI objectives, risk treatment, monitoring, and improvement | https://www.iso.org/home/insights-news/resources/iso-42001-explained-what-it-is.html | TBD | None identified / Potential gap / Confirmed concern | Business / legal / compliance / risk owner | TBD |
| Monitoring, incident response, corrective action, rollback, disablement, or continual-improvement evidence is missing | Performance evaluation, improvement, nonconformity, and corrective action | https://www.iso.org/standard/42001 | TBD | None identified / Potential gap / Confirmed concern | AI governance / operations / risk owner | TBD |
## 5. Engineering Controls
- AI inventory and lifecycle scope:
- Owner accountability and review handoffs:
- Generated-code review gate:
- Trusted-source verification for model claims:
- Secure generated implementation review:
- Prompt minimization and redaction:
- Approved model/provider route:
- RAG source governance:
- AI-agent tool policy, approvals, and rollback:
- Generated dependency provenance:
- SBOM, vulnerability, license, and malicious-package checks:
- Bias, fairness, and impact review:
- Monitoring and measurement:
- Incident response and corrective action:
- Rollback, disablement, and recovery:
- Release readiness and owner approvals:
## 6. Evidence Inventory
- AI inventory or capability register:
- Risk assessment and risk treatment record:
- Prompt catalog and prompt versions:
- Model/provider approval and version evidence:
- RAG source registry and source approval evidence:
- Generated artifact provenance:
- Pull request, review, test, static analysis, and security evidence:
- Dependency decision, SBOM, vulnerability, license, and provenance evidence:
- Data classification, minimization, redaction, and retention evidence:
- Bias or impact testing evidence:
- Monitoring dashboards or alerts:
- Incident and corrective-action records:
- Release decision:
## 7. Residual Risks
- Residual risk:
- Impact:
- Likelihood:
- Mitigation:
- Owner:
- Acceptance decision:
- Review date:
## 8. Release Decision
- Decision:
- Conditions:
- Blockers:
- Required approvals:
- Expiry or review date:
- Environments or versions approved:
- Rollback path:
- Disablement or kill-switch path:
- Next monitoring checkpoint:
## 9. Action Plan
| Priority | Action | Owner | Due date | Evidence expected | Status |
| -------- | ------ | ----- | -------- | ----------------- | ------ |
| High | | | | | Open |
| Medium | | | | | Open |
| Low | | | | | Open |
## 10. Final Notes
- Items requiring legal interpretation:
- Items requiring certification scope or conformity review:
- Items requiring audit evidence or internal audit review:
- Items requiring privacy or data protection review:
- Items requiring security or AppSec review:
- Items requiring AI governance or risk acceptance:
- Items requiring procurement or model-provider review:
- Items requiring architecture decision:
- Items requiring product or business acceptance:
- Next review trigger:
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |