Study guide

Conduct Security, Safety, and Ethics Risk Assessments

PMI Certified Professional in Managing AI PMI-CPMAI

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: PMI-CPMAI Exam Foundations & the CPMAI Methodology

The PMI-CPMAI Exam: Format, Eligibility, Fees & Scoring The CPMAI Methodology: Six Phases and Data-Centric Iteration CPMAI vs Waterfall, Agile, and CRISP-DM

2 Chapter 2: AI and Machine Learning Fundamentals for CPMAI

The Seven Patterns of AI Supervised, Unsupervised & Reinforcement Learning Why AI Projects Fail: Value, Data Readiness & Right-Sizing

3 Chapter 3: Domain I — Support Responsible and Trustworthy AI Efforts (15%)

Oversee the Privacy and Security Plan Manage AI/ML Transparency in Data and Algorithm Selection Conduct Bias Checks on Model, Data, and Algorithm Monitor Regulatory and Policy Compliance Manage Accountability Documentation and the Audit Trail

4 Chapter 4: Domain II — Identify Business Needs and Solutions, Part 1 (26%)

Identify the Problem to Be Solved Evaluate Initial AI Feasibility Conduct Security, Safety, and Ethics Risk Assessments Develop the AI Project Scope Statement Determine Return on Investment

5 Chapter 5: Domain II — Identify Business Needs and Solutions, Part 2

Manage Adoption and Integration Risks Draft the AI Solution Define Success Criteria and KPIs Support Business Case Creation Identify Project Resources: People, Hardware, and Contractors

6 Chapter 6: Domain III — Identify Data Needs, Part 1 (26%)

Define the Required Data Identify Data Subject-Matter Experts Identify Data Sources and Locations Coordinate the AI Workspace and Infrastructure Gather the Required Data

7 Chapter 7: Domain III — Identify Data Needs, Part 2

Check Data Privacy, Compliance, and Access Oversee Data Evaluation Determine If the Data Meets Solution Needs: The Phase 2 Go/No-Go Convey Data Understanding to Leadership

8 Chapter 8: Domain IV — Manage AI Model Development and Evaluation (16%)

Oversee AI/ML Model Technique and Algorithm Selection Oversee Model QA/QC and Configuration Management Manage AI/ML Model Training Manage Data Transformation and Data Preparation Verify Data Quality for the Data Preparation Go/No-Go Verify the Model Is Ready for Operationalization

9 Chapter 9: Domain V — Operationalize AI Solution, Part 1 (17%)

Manage Creation of the AI Solution Deployment Plan Manage the AI Solution Deployment Oversee Model Governance in Production Oversee AI Solution Metrics and Performance Monitoring

10 Chapter 10: Domain V — Operationalize AI Solution, Part 2

Prepare the Final Report and Lessons Learned Manage the AI Solution Transition Plan Oversee the AI Solution Contingency Plan

Conduct Security, Safety, and Ethics Risk Assessments

Key Takeaways Explain This Topic AI

Risk assessment is a Phase 1 Business Understanding task revisited at every phase gate, not a check performed after a model exists.

Analyze false positives and false negatives separately: they cost different amounts and are borne by different parties.

A CPMAI manager must be able to name six AI-specific exposures: data poisoning, model evasion, model inversion and membership inference, model theft, prompt injection, and pre-trained model supply-chain risk.

Every risk register entry needs an owner, an early control, an observable trigger, and a contingency action.

Severity of potential harm drives how much human oversight is designed into the solution, which is why risk must be settled before scope and ROI are fixed.

Last updated: August 2026

Risk Work Belongs at the Front of the Project

Domain II Task 3 is conduct risk assessment(s) (e.g., security, safety, ethics) , and its placement matters as much as its content. It sits in Phase 1, Business Understanding , beside problem identification and feasibility — not after a model exists. The reason is structural. In deterministic software, risk is largely about defects, integration, and schedule. An AI system is probabilistic : it will be wrong a knowable percentage of the time, it can be attacked through its data as well as its code, and its errors do not distribute evenly across the people it acts on. Those properties change what the solution has to look like, so they must be known before the solution is drafted. Assess in Phase 1, then revisit the register at every phase gate as data and model behavior become known.

Identify Potential Failure Modes and Safety Implications

Start with the question deterministic projects never ask: what does being wrong cost, and who pays? Analyze false positives and false negatives separately, because they land on different parties.

Fraud model, false positive : a legitimate customer's card is declined at checkout. The customer bears it; the business sees churn and complaint volume.

Fraud model, false negative : the fraudulent payment clears. The business bears it as loss and possible regulatory reporting.

Predictive maintenance, false negative : the asset fails in service. On a conveyor that is downtime; on a brake assembly or an infusion pump it is human harm.

Safety escalates the entire assessment whenever the model touches physical systems (vehicles, plant equipment, robotics) or human welfare (clinical, benefits, hiring, credit, safeguarding). For those cases, define hard operating limits, a fail-safe default state , and a route by which a person can override or stop the system — and record them as requirements now, because retrofitting them after Phase 4 is expensive and often architecturally impossible.

Assess Cybersecurity Vulnerabilities in AI Systems

A CPMAI project manager is not expected to implement defenses, but must be able to name the AI-specific attack surfaces and require that security review covers them, because a conventional application security review will not. Published threat catalogs such as MITRE ATLAS enumerate these in depth; you need the vocabulary and the judgment, not the implementation.

Data poisoning — corrupted or crafted records injected into training or retraining data so the model learns wrong behavior or a hidden trigger. Highest where data is scraped, crowdsourced, or continuously retrained on user input.

Model evasion (adversarial input) — inputs perturbed at inference time so a working model misclassifies them. The attacker never touches your model or your data.

Model inversion and membership inference — repeated querying used to reconstruct sensitive training records, or to confirm that a named individual was in the training set. This makes a model itself a privacy exposure even though the underlying data never left.

Model theft (extraction) — systematic querying of an exposed prediction interface to reproduce a proprietary model's behavior, losing the asset you paid to build.

Prompt injection — instructions hidden in user input or in retrieved content (a document, a web page, an email) that override a generative system's rules, exfiltrate data, or trigger unauthorized actions.

Supply-chain risk — pre-trained models, open weights, third-party datasets, and vendor application programming interfaces (APIs) inherit whatever was in them. Require provenance, licensing terms, and update and deprecation terms for anything you did not build.

Evaluate Ethical Implications of AI Decision-Making

Ask three questions of every automated decision: who is affected , do they know , and what recourse do they have ? Then ask whether error rates differ across groups — a strong aggregate accuracy figure can conceal a model that performs materially worse for one population. Domain I covers bias checks and transparency in depth; your Phase 1 job is to locate the ethical exposure and record it, so that explainability, appeal routes, and oversight enter the scope statement rather than arriving as a late and unbudgeted surprise.

Analyze Reputational and Business Continuity Risks

Reputational risk asks what a single bad output looks like when it is screenshotted, published, or quoted in a regulator's letter. For generative systems, one confidently wrong answer given to a customer is a publishable event, and the volume of outputs makes such an event a near-certainty over time. Continuity risk asks what happens when the system is unavailable or degraded: does the manual process still exist, do staff still have the skill to run it, and what breaks if a third-party API suffers an outage, reprices, or retires the model version you built on? Vendor model deprecation runs on the vendor's schedule, not yours, and belongs in the register from day one.

Develop Risk Mitigation Strategies and Contingency Plans

Convert all of the above into a risk register in which each entry carries a description, a category, likelihood and impact, an owner with authority to act, an early control, a trigger — the observable condition saying the risk is materializing — and a contingency. Triggers are what make an AI risk register operational rather than decorative: "accuracy for the over-65 segment falls below the agreed floor," "manual override rate exceeds 20%," "vendor announces deprecation of the model version in use."

Risk category Concrete AI example Early control Contingency

Failure mode / accuracy Claims triage model wrongly routes complex claims to fast-track Separate false-positive and false-negative cost analysis; confidence thresholds Route low-confidence cases to manual queue; revert to prior routing rules

Safety Predictive maintenance misses an impending pump failure Hard operating limits and a fail-safe default; human confirmation before service action Retain scheduled preventive maintenance in parallel until performance is proven

Security Chatbot retrained monthly on customer messages is poisoned by crafted input Provenance checks and anomaly screening on retraining data; approval gate before promotion Roll back to the last known-good model version; freeze retraining

Privacy Repeated queries reconstruct records or reveal training-set membership Rate limiting, access control, and scrubbing of identifiers before training Withdraw the interface; run a disclosure assessment with legal and privacy owners

Ethical Hiring screen shows materially lower accuracy for one applicant group Per-segment performance review before go-live; documented appeal route Suspend automated screening; revert to human review while the gap is investigated

Reputational Generative assistant gives a confidently wrong answer to a customer Output guardrails; grounded responses; visible uncertainty and escalation path Pre-agreed communications plan; disable the feature pending review

Continuity Vendor deprecates the hosted model version the solution is built on Contractual notice and version-support terms; monitored dependency list Tested fallback to an alternative model or to the manual process

Severity Drives the Level of Human Oversight

The judgment the exam most wants from you is this: the severity and reversibility of harm determine how much human oversight is designed into the solution. A low-severity, easily reversed decision — which article to recommend next — can run fully automated. A high-severity, hard-to-reverse decision — deny a claim, take a medical device out of service, halt a production line — requires human-in-the-loop approval, decision logging, and an appeal or override route. That choice changes latency, staffing, and cost, which is precisely why it is settled here in Phase 1, before scope and return on investment are fixed, and why a risk register that is written once and never reopened is a defect rather than a deliverable.