Where Technology Meet Security
| Status | Checklist item (Professional & plain language + example) | Domain | Priority | ISO mapping (27001 / 42001) | Evidence | Remarks |
|---|---|---|---|---|---|---|
| Governance & Risk Management | ||||||
|
Establish AI governance committee & policy
Professional: Form a cross-functional committee (Security, Compliance, Legal, Product) and publish an AI governance policy.
Description's: Decide who is in charge of AI decisions and put it in writing. Example: Monthly AI steering meetings, formal policy document. |
Governance | High | ISO/IEC 27001 Clauses 4–5; ISO/IEC 42001: 4.3, 5.3 | |||
|
Define AI risk appetite & classification
Professional: Document acceptable risk thresholds and classification for AI use-cases (safety-critical vs non-critical).
Description: Decide how much risk you will accept for each AI use. Example: Customer-facing diagnosis = low risk tolerance; internal reports = moderate tolerance. |
Governance | High | ISO 27001: Clause 6.1, A.5.4; ISO 42001: 6.1 | |||
|
Integrate AI into ISMS & assign controls owner
Professional: Map AI assets to ISMS processes, assign owners, and include in management reviews.
Description: Make AI part of your regular security program and name who owns each control. |
Governance | Medium | ISO 27001: Clauses 4–10, A.5–A.18; ISO 42001: 4.3–10 | |||
| Vendor & Supply Chain Security | ||||||
|
Vendor security assessment & contract clauses
Professional: Validate vendor certifications (SOC2/ISO), require incident SLA, audit rights, and data handling clauses.
Description: Check vendor security, and put protections in contracts. Example: Right-to-audit clause; data deletion on termination. |
Vendor | High | ISO 27001: A.15.1-A.15.2; ISO 42001: 8.4 | |||
|
Software Bill of Materials (SBOM) & component provenance
Professional: Request SBOMs for model artifact components and libraries to track vulnerabilities and licensing.
Description: Ask vendors what components are inside their model so you can patch vulnerabilities. |
Supply Chain | High | ISO 27001: A.8.1, A.14.2; ISO 42001: 8.2.4 | |||
|
Vendor change & patch management
Professional: Require vendors to notify of critical vulnerabilities and patch timelines.
Description: Make sure vendors tell you about security issues and fix them fast. |
Vendor | Medium | ISO 27001: A.12.6; ISO 42001: 8.5 | |||
| Data Protection & Privacy | ||||||
|
Data inventory & classification for AI datasets
Professional: Maintain catalog of training & inference datasets and label sensitivity (PII, PHI, IP).
Description: Know what data you use for AI and how sensitive it is. Example: Customer PII = restricted; public scraped web = public. |
Data | Critical | ISO 27001: A.8.2, A.9.1; ISO 42001: 8.5.1 | |||
|
Encryption & key management
Professional: Encrypt sensitive data at rest & in transit; manage keys with KMS/HSM and rotate keys regularly.
Description: Use locks to protect sensitive data and control who has the keys. |
Data Protection | High | ISO 27001: A.10.1, A.10.3; ISO 42001: 8.5.2 | |||
|
Privacy-by-design & consent management
Professional: Implement minimization, anonymization and consent handling; document retention schedules.
Description: Collect only what you need, and respect user consent. Example: Anonymize PII before training, delete raw logs after X days. |
Privacy | High | ISO 27001: A.18.1; ISO 42001: 6.1.3, 8.6.1 | |||
| Model Security & Lifecycle Management | ||||||
|
Secure SDLC for models (development & CI/CD)
Professional: Enforce secure coding, peer review, automated testing and gated deployments for model changes.
Description: Build models in a controlled pipeline with checks before releasing. Example: Unit tests, adversarial tests, approval gates in CI/CD. |
Model Lifecycle | High | ISO 27001: A.14.2; ISO 42001: 8.1, 8.3 | |||
|
Model provenance, signing & artifact integrity
Professional: Maintain provenance metadata, sign artifacts, and verify integrity before deployment.
Description: Track where models came from and make sure they weren't tampered with. |
Model Security | High | ISO 27001: A.12.7; ISO 42001: 8.2.5 | |||
|
Monitoring, drift detection & rollback controls
Professional: Implement metrics, alerts, and automated rollback for model performance and fairness drift.
Description: Watch model results and revert if things get worse. |
Monitoring | High | ISO 27001: A.12.4, A.12.6; ISO 42001: 9.1, 9.2 | |||
| Vulnerability & Incident Management | ||||||
|
Adversarial & security testing (pen tests + red teaming)
Professional: Schedule periodic adversarial testing including prompt injection, model evasion and API hardening.
Description: Try to break the model to find weaknesses before attackers do. |
Security Testing | High | ISO 27001: A.12.6; ISO 42001: 9.1.2 | |||
|
AI incident response plan & playbooks
Professional: Define playbooks for data leak, model theft, bias incidents and model poisoning.
Description: Have step-by-step instructions when something goes wrong. |
Incident Response | High | ISO 27001: A.16.1; ISO 42001: 10.1 | |||
| Compliance & Training | ||||||
|
AI ethics, privacy & security training
Professional: Regular training for developers, data scientists and business users on secure AI practices.
Description: Teach staff how to use AI safely and responsibly. |
Training | Medium | ISO 27001: A.7.2 | ISO 42001: 7.3 | |||
|
Maintain compliance register & mapping to regulations
Professional: Track legal & regulatory obligations (GDPR, EU AI Act, sector rules) and map controls.
Description: Keep a list of laws and how you meet them. |
Compliance | High | ISO 27001: A.18.1; ISO 42001: 4.2, 9.2 | |||