Artificial Intelligence Risk Scenarios

📢 What are the risks from Artificial Intelligence? We present the AI Risk Repository: a comprehensive living database of 700+ risks extracted, with quotes and page numbers, from 43(!) taxonomies. To categorize the identified risks, we adapt two existing frameworks into taxonomies. Our Causal Taxonomy categorizes risks based on three factors: the Entity involved, the Intent behind the risk, and the Timing of its occurrence. Our Domain Taxonomy categorizes AI risks into 7 broad domains and 23 more specific subdomains. For example, 'Misinformation' is one of the domains, while 'False or misleading information' is one of its subdomains. 💡 Four insights from our analysis: 1️⃣ 51% of the risks extracted were attributed to AI systems, while 34% were attributed to humans. Slightly more risks were presented as being unintentional (37%) than intentional (35%). Six times more risks were presented as occurring after (65%) than before deployment (10%). 2️⃣ Existing risk frameworks vary widely in scope. On average, each framework addresses only 34% of the risk subdomains we identified. The most comprehensive framework covers 70% of these subdomains. However, nearly a quarter of the frameworks cover less than 20% of the subdomains. 3️⃣ Several subdomains, such as *Unfair discrimination and misrepresentation* (mentioned in 63% of documents); *Compromise of privacy* (61%); and *Cyberattacks, weapon development or use, and mass harm* (54%) are frequently discussed. 4️⃣ Others such as *AI welfare and rights* (2%), *Competitive dynamics* (12%), and *Pollution of information ecosystem and loss of consensus reality* (12%) were rarely discussed. 🔗 How can you engage?   Visit our website, explore the repository, read our preprint, offer feedback, or suggest missing resources or risks (see links in comments). 🙏 Please help us spread the word by sharing this with anyone relevant. Thanks to everyone involved: Alexander Saeri, Jess Graham 🔸, Emily Grundy, Michael Noetel 🔸, Risto Uuk, Soroush J. Pour, James Dao, Stephen Casper, and Neil Thompson. #AI #technology

If your team is asking “Can we use this AI tool?” You need governance.   Especially when AI systems can develop discriminatory bias, give incorrect advice, leak customer data, introduce security flaws, and perpetuate outdated assumptions about users.   AI governance programs and assessments are no longer an optional best practice.   They're on the fast track to becoming mandatory as several AI regulations roll out. Most notably for high-risk AI use. I recommend AI assessments beyond high risk use cases to also capture the privacy, security and ethical risks. Here’s how companies can conduct an AI risk assessment: ✔ Start by building an AI data inventory List every AI tool in use, including hidden ones embedded inside vendor software. Capture data inputs, decisions it makes, who has access, and outputs. ✔ Assess the decision impact Identify where wrong AI decisions could cause harm or discriminate, and review AI systems thoroughly to understand if it involves high-risk.   ✔ Examine company data sources Check whether your training data is current, representative, and free from historical bias. Confirm you have disclosures and permissions for use. ✔ Test for bias and fairness Run scenarios through AI systems with different demographic inputs and look for discrepancies in outcomes. ✔ Document everything Maintain detailed records of the assessment process, findings, and changes you make. Regulations like the EU AI Act and the Colorado AI Act have specific requirements for documenting high-risk AI usage.   ✔ Build monitoring checkpoints Set regular reviews and repeat risk assessments when new products or services are introduced or as models, vendors, business needs, or regulations change. AI oversight isn’t coming someday. It’s here.   Companies that start preparing now will be ready when the new regulations come into force. Read our full blog for more tips and to see how to put this into action 👇

AI can generate information that sounds accurate but is completely wrong. AI hallucinations can undermine trust in reporting, introduce compliance exposure, and create financial or operational losses. They can also surface sensitive data or misinform decisions that affect capital allocation, investor communication, and audit readiness. AI hallucinations are not a signal to slow down innovation. They are a signal to strengthen your governance and controls. With a thoughtful risk management approach, leaders can understand uncertainty and build a more confident, resilient AI strategy. Considerations for leaders to reduce AI hallucination risk: 1. Create a validation and review process for AI generated financial outputs. Leaders must ensure that any AI generated forecasts, variance analyses, reconciliations, or narrative summaries have structured validation for source accuracy and logic. 2. Strengthen compliance and regulatory controls within AI workflows. AI hallucinations can create errors that lead to noncompliance and regulatory exposure. Leaders can embed compliance checkpoints into AI driven processes to avoid misstatements, inaccurate filings, or unintended disclosure. 3. Prioritize data governance using high quality, company specific data to reduce the risk of fabricated or inaccurate outputs. This is critical for forecasting, scenario modeling, and automated reporting. 4. Use retrieval augmented generation and automated reasoning for workflows. Pairing these methods anchors AI generated analysis in verified data sources rather than probability-based guesses. 5. Enable filtering and moderation tools to block misleading or irrelevant results. Teams cannot work from flawed or unverified outputs. Filters help prevent misleading content from entering critical workflows or influencing decisions. AI is gaining traction. Now is the time to formalize your AI risk mitigation approach. Start the discussion within your leadership team today. Identify where AI is already influencing decision-making, assess your current controls, and define the safeguards you need next. #RiskManagement #AI #Leaders

A new 145 pages-paper from Google DeepMind outlines a structured approach to technical AGI safety and security, focusing on risks significant enough to cause global harm. Link to blog post & research overview, "Taking a responsible path to AGI" - Google DeepMind, 2 April 2025: https://lnkd.in/gXsV9DKP - by Anca Dragan, Rohin Shah, John "Four" Flynn and Shane Legg * * * The paper assumes for the analysis that: - AI may exceed human-level intelligence - Timelines could be short (by 2030) - AI may accelerate its own development - Progress will be continuous enough to adapt iteratively The paper argues that technical mitigations must be complemented by governance and consensus on safety standards to prevent a “race to the bottom". To tackle the challenge, the present focus needs to be on foreseeable risks in advanced foundation models (like reasoning and agentic behavior) and prioritize practical, scalable mitigations within current ML pipelines. * * * The paper outlines 4 key AGI risk areas: --> Misuse – When a human user intentionally instructs the AI to cause harm (e.g., cyberattacks). --> Misalignment – When an AI system knowingly takes harmful actions against the developer's intent (e.g., deceptive or manipulative behavior). --> Mistakes – Accidental harms caused by the AI due to lack of knowledge or situational awareness. --> Structural Risks – Systemic harms emerging from multi-agent dynamics, culture, or incentives, with no single bad actor. * * * While the paper also addresses Mistakes - accidental harms - and Structural Risks - systemic issues - recommending testing, fallback mechanisms, monitoring, regulation, transparency, and cross-sector collaboration, the focus is on Misuse and Misalignment, which present greater risk of severe harm and are more actionable through technical and procedural mitigations. * * * >> Misuse (pp. 56–70) << Goal: Prevent bad actors from accessing and exploiting dangerous AI capabilities. Mitigations: - Safety post-training and capability suppression – Section 5.3.1–5.3.3 (pp. 60–61) - Monitoring, access restrictions, and red teaming – Sections 5.4–5.5, 5.8 (pp. 62–64, 68–70) - Security controls on model weights – Section 5.6 (pp. 66–67) - Misuse safety cases and stress testing – Section 5.1, 5.8 (pp. 56, 68–70) >> Misalignment (pp. 70–108) << Goal: Ensure AI systems pursue aligned goals—not harmful ones—even if capable of misbehavior. Model-level defenses: - Amplified oversight – Section 6.1 (pp. 71–77) - Guiding model behavior via better feedback – Section 6.2 (p. 78) - Robust oversight to generalize safe behavior, including Robust training and monitoring – Sections 6.3.3–6.3.7 (pp. 82–86) - Safer Design Patterns – Section 6.5 (pp. 87–91) - Interpretability – Section 6.6 (pp. 92–101) - Alignment stress tests – Section 6.7 (pp. 102–104) - Safety cases – Section 6.8 (pp. 104–107) * * * #AGI #safety #AGIrisk #AIsecurity

𝐀𝐈 𝐫𝐢𝐬𝐤 𝐢𝐬𝐧’𝐭 𝐨𝐧𝐞 𝐭𝐡𝐢𝐧𝐠. 𝐈𝐭’𝐬 𝟏,𝟔𝟎𝟎 𝐭𝐡𝐢𝐧𝐠𝐬. That’s not hyperbole. A new meta-review compiled over 1,600 distinct AI risks from 65 frameworks and surfaced a tough truth: most organizations are underestimating both the scope and structure of AI risk. It’s not just about bias, fairness, or hallucination. Risks emerge at different stages, from different actors, with different incentives: • Pre-deployment design decisions • Post-deployment human misuse • Model failure, misalignment, drift • Unclear accountability across teams The taxonomy distinguishes between human and AI causes, intentional and unintentional behaviors, and domain-specific vs. systemic risks. But here’s the real insight: Most AI risks don’t stem from malicious design. They emerge from fragmented ownership and unmanaged complexity. No single team sees the whole picture. Governance lives in compliance. Development lives in product. Monitoring lives in infra. And no one owns the handoffs. → Strategic takeaway: You don’t need another checklist. You need a cross-functional risk architecture. One that maps responsibility, observability, and escalation paths, before the headlines do it for you. AI systems won’t fail in one place. They’ll fail at the intersections. 𝐓𝐫𝐞𝐚𝐭 𝐀𝐈 𝐫𝐢𝐬𝐤 𝐚𝐬 𝐚 𝐜𝐡𝐞𝐜𝐤𝐛𝐨𝐱, 𝐚𝐧𝐝 𝐢𝐭 𝐰𝐢𝐥𝐥 𝐬𝐡𝐨𝐰 𝐮𝐩 𝐥𝐚𝐭𝐞𝐫 𝐚𝐬 𝐚 𝐡𝐞𝐚𝐝𝐥𝐢𝐧𝐞.

Most AI governance frameworks are still based on the assumption that AI is primarily used for answering questions. That world is over. Today’s enterprise AI systems can: • call APIs and tools • access sensitive data • trigger automated workflows • influence real financial and operational decisions Which means the real risk is no longer just model accuracy. The real risk is decision impact. So I built something to visualize the full landscape: The AI Risk Periodic Table™ Instead of treating AI risks as disconnected lists, the framework organizes them the way chemists organize elements — revealing patterns that only appear when you see the whole system. This expanded version maps 80 enterprise AI risks across five layers: Data Risks Training contamination, prompt injection, dataset bias, data leakage. Model Risks Model bias, overfitting, adversarial attacks, model theft. Agent Risks Tool misuse, permission escalation, autonomous loops, unsafe actions. Decision Risks Financial loss, regulatory violations, operational disruption, biased outcomes. Governance Risks Lack of observability, missing audit trails, vendor exposure, security gaps. What becomes clear when you map the system this way: Most organizations are governing models. But the next frontier of AI governance is governing decisions. That requires new capabilities: • runtime observability • agent permissions • decision traceability • human-in-the-loop escalation In other words: An Enterprise AI Control Plane. Curious what others see emerging in this space. What risks do you think are still missing from the table? #AIGovernance #ResponsibleAI #AISecurity #AIRisk #EnterpriseAI

AI risk is no longer a distant theory, and OpenAI founder Sam Altman frames it into three clear categories that show why responsible AI must be addressed at both #technical and #policy levels. The first risk is misuse, where bad actors could leverage powerful AI to design #bioweapons, disrupt financial systems, or attack critical infrastructure, threats that evolve faster than traditional defenses. The second is loss of control, a lower-probability but high-impact scenario in which advanced systems fail to reliably follow #human #intent, making alignment research and safety #engineering essential at the technical level. The third is quiet dominance, where AI becomes so deeply embedded in decision-making that people and even governments over-rely on it, while its reasoning grows harder to understand, raising serious governance and #accountability concerns. Together, these risks show that technical #safeguards alone are not enough; strong policies, global coordination, transparency standards, and clear responsibility #frameworks are equally necessary to ensure AI remains a #tool that serves #humanity rather than one that subtly or suddenly undermines it. #AIRisk #ResponsibleAI #AIGovernance #AISafety #TechPolicy #FutureOfAI

⚠️ Stop these 9 AI threats before it’s too late. Most teams are racing to adopt AI without realizing they’re opening the door to a whole new category of risks. I’ve seen companies get burned by AI hallucinations in customer service. I’ve watched executives fall for deepfake scams. I’ve seen proprietary code accidentally leaked through ChatGPT prompts. Here’s what keeps me up at night: while we’re all excited about AI’s potential, very few organizations have updated their security playbooks to match this new reality. We’re using yesterday’s defenses against tomorrow’s threats. 📌 The 9 AI Security Risks Every Leader Should Know: 1. HALLUCINATIONS Your AI confidently gives wrong answers. Models predict likely words, not facts. They don't say "I don't know." → Fix: Add verification steps. Require citations. Train users not to trust blindly. 2. PILL EXPOSURE Private data (names, emails, IDs) leaks unintentionally from your prompts or responses. → Fix: Mask sensitive data. Audit logs. Use separate environments for testing. 3. DEEPFAKES & SYNTHETIC MEDIA Fake videos/audio impersonating executives. Scams. Misinformation. → Fix: Detection tools. Watermarking. Train employees on verification. 4. PROMPT INJECTION & DATA LEAKS Attackers exploit AI inputs to access data or change commands. → Fix: Sanitize inputs. Limit model access. Monitor unusual queries. 5. SHADOW AI Employees using unauthorized AI tools without IT knowing. → Fix: AI governance policy. Approved tools list. Regular audits. 6. MODEL BIAS AI supports discrimination or unfair decisions trained on biased data. → Fix: Audit training data. Test for bias. Diverse evaluation teams. 7. IP LEAKAGE Internal code or proprietary data leaks via AI systems. → Fix: Don't paste internal data into public AI. Use private deployments. 8. COMPLIANCE & REGULATION Data privacy violations or AI-related legal breaches. → Fix: Know your regulations (GDPR, DPDPA, AI Act). Document decisions. 9. THIRD-PARTY VULNERABILITIES Exposure via vendors, APIs, or model integrations you depend on. → Fix: Vet vendors. Monitor integrations. Have backup providers 📥 Get Free Access to My AI Data Security Guide Here: https://lnkd.in/gtenUagT Save this post. Share it with your team. Because the best defense against AI risks is knowing they exist in the first place. ___________________________________________ 👋 I’m Amit Rawal, an AI practitioner and educator. Outside of work, I’m building SuperchargeLife.ai , a global movement to make AI education accessible and human-centered. ♻️ Repost if you believe AI isn’t about replacing us… It’s about retraining us to think better. Opinions expressed are my own in a personal capacity and do not represent the views, policies, or positions of my employer (currently Google LLC) or its subsidiaries or affiliates.

I've been digging into the latest NIST guidance on generative AI risks—and what I’m finding is both urgent and under-discussed. Most organizations are moving fast with AI adoption, but few are stopping to assess what’s actually at stake. Here’s what NIST is warning about: 🔷 Confabulation: AI systems can generate confident but false information. This isn’t just a glitch—it’s a fundamental design risk that can mislead users in critical settings like healthcare, finance, and law. 🔷 Privacy exposure: Models trained on vast datasets can leak or infer sensitive data—even data they weren’t explicitly given. 🔷 Bias at scale: GAI can replicate and amplify harmful societal biases, affecting everything from hiring systems to public-facing applications. 🔷 Offensive cyber capabilities: These tools can be manipulated to assist with attacks—lowering the barrier for threat actors. 🔷 Disinformation and deepfakes: GAI is making it easier than ever to create and spread misinformation at scale, eroding public trust and information integrity. The big takeaway? These risks aren't theoretical. They're already showing up in real-world use cases. With NIST now laying out a detailed framework for managing generative AI risks, the message is clear: Start researching. Start aligning. Start leading. The people and organizations that understand this guidance early will become the voices of authority in this space. #GenerativeAI #Cybersecurity #AICompliance

☢️Manage Third-Party AI Risks Before They Become Your Problem☢️ AI systems are rarely built in isolation as they rely on pre-trained models, third-party datasets, APIs, and open-source libraries. Each of these dependencies introduces risks: security vulnerabilities, regulatory liabilities, and bias issues that can cascade into business and compliance failures. You must move beyond blind trust in AI vendors and implement practical, enforceable supply chain security controls based on #ISO42001 (#AIMS). ➡️Key Risks in the AI Supply Chain AI supply chains introduce hidden vulnerabilities: 🔸Pre-trained models – Were they trained on biased, copyrighted, or harmful data? 🔸Third-party datasets – Are they legally obtained and free from bias? 🔸API-based AI services – Are they secure, explainable, and auditable? 🔸Open-source dependencies – Are there backdoors or adversarial risks? 💡A flawed vendor AI system could expose organizations to GDPR fines, AI Act nonconformity, security exploits, or biased decision-making lawsuits. ➡️How to Secure Your AI Supply Chain 1. Vendor Due Diligence – Set Clear Requirements 🔹Require a model card – Vendors must document data sources, known biases, and model limitations. 🔹Use an AI risk assessment questionnaire – Evaluate vendors against ISO42001 & #ISO23894 risk criteria. 🔹Ensure regulatory compliance clauses in contracts – Include legal indemnities for compliance failures. 💡Why This Works: Many vendors haven’t certified against ISO42001 yet, but structured risk assessments provide visibility into potential AI liabilities. 2️. Continuous AI Supply Chain Monitoring – Track & Audit 🔹Use version-controlled model registries – Track model updates, dataset changes, and version history. 🔹Conduct quarterly vendor model audits – Monitor for bias drift, adversarial vulnerabilities, and performance degradation. 🔹Partner with AI security firms for adversarial testing – Identify risks before attackers do. (Gemma Galdon Clavell, PhD , Eticas.ai) 💡Why This Works: AI models evolve over time, meaning risks must be continuously reassessed, not just evaluated at procurement. 3️. Contractual Safeguards – Define Accountability 🔹Set AI performance SLAs – Establish measurable benchmarks for accuracy, fairness, and uptime. 🔹Mandate vendor incident response obligations – Ensure vendors are responsible for failures affecting your business. 🔹Require pre-deployment model risk assessments – Vendors must document model risks before integration. 💡Why This Works: AI failures are inevitable. Clear contracts prevent blame-shifting and liability confusion. ➡️ Move from Idealism to Realism AI supply chain risks won’t disappear, but they can be managed. The best approach? 🔸Risk awareness over blind trust 🔸Ongoing monitoring, not just one-time assessments 🔸Strong contracts to distribute liability, not absorb it If you don’t control your AI supply chain risks, you’re inheriting someone else’s. Please don’t forget that.