Study guide
9.3 Prompt Injection, Data Exfiltration, and GenAI Threat Modeling
AWS AI Practitioner Study Guide Exam
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: AIF-C01 Orientation and Official Source Control
1.1 Credential Scope, Code, and Search Language 1.2 Exam Format, Cost, Score, and Delivery 1.3 Official Exam Guide, Skill Builder, and Practice Workflow 1.4 Target Candidate Boundaries and Out-of-Scope Tasks 1.5 Domain Weights and Study Prioritization 1.6 Exam Policy, Retake, Results, and Recertification
2 Chapter 2: AI/ML Foundations and Use-Case Fit
2.1 AI, ML, Deep Learning, and Core Terminology 2.2 Supervised, Unsupervised, and Reinforcement Learning 2.3 Data Types, Labels, Structure, and Quality 2.4 Inference Patterns: Batch, Real-Time, and Embedded AI 2.5 AI Use-Case Fit and No-AI Decisions 2.6 Classification, Regression, Clustering, Forecasting, and Recommendation 2.7 AI/ML Foundations Case Lab
3 Chapter 3: ML Lifecycle, Metrics, and Practitioner MLOps
3.1 Data Collection, EDA, Preprocessing, and Feature Concepts 3.2 Training, Evaluation, Deployment, and Monitoring Lifecycle 3.3 Model Sources: Managed APIs, Open Source, and Custom Models 3.4 Evaluation Metrics and Business Metrics 3.5 Practitioner MLOps: Repeatability, Monitoring, and Retraining 3.6 SageMaker Lifecycle Service Map 3.7 ML Lifecycle Case Lab
4 Chapter 4: Generative AI Foundations and Inference Concepts
4.1 Foundation Models, LLMs, Transformers, and Modalities 4.2 Tokens, Context Windows, Embeddings, and Vector Search 4.3 Inference Parameters: Temperature, Top-p, and Output Controls 4.4 Hallucination, Grounding, and Context Quality 4.5 GenAI Use-Case Fit and Risk Triage 4.6 Prompt Injection, Data Leakage, and User Input Risk 4.7 Generative AI Foundations Case Lab
5 Chapter 5: Prompting, Model Selection, Customization, and Evaluation
5.1 Prompt Engineering Patterns and Business Quality 5.2 Zero-Shot, Few-Shot, Templates, and Instruction Design 5.3 Model Selection: Capability, Latency, Cost, and Risk 5.4 RAG vs Fine-Tuning vs Prompting vs Custom Models 5.5 Model Evaluation, Human Review, and Red-Team Feedback 5.6 Cost, Performance, and Throughput Decision-Making 5.7 Prompting and Model Selection Case Lab
6 Chapter 6: Amazon Bedrock, RAG, Agents, and Guardrails
6.1 Bedrock Core Concepts, Model Access, and Managed FM Choice 6.2 Knowledge Bases, RAG, Data Sources, and Grounding 6.3 AI Agents, Tools, Orchestration, and Business Workflows 6.4 Guardrails, Content Filters, Denied Topics, and Sensitive Data 6.5 Bedrock Model Evaluation, Monitoring, and Human Feedback 6.6 Bedrock Cost, Latency, Throughput, and Operational Fit 6.7 Bedrock, RAG, and Agents Case Lab
7 Chapter 7: AWS Managed AI/ML Services and SageMaker Map
7.1 Managed AI Services vs Foundation Model Apps vs Custom ML 7.2 Text, Language, Search, and Document AI Services 7.3 Vision, Speech, Contact Center, and Personalization Services 7.4 Amazon Quick, Amazon Q Developer, Kiro, and Practitioner Fit 7.5 SageMaker Canvas, Studio, Clarify, Autopilot, and Data Wrangler 7.6 Data Foundation Services: S3, Glue, OpenSearch, and Quick Sight 7.7 AWS AI Service Selection Case Lab
8 Chapter 8: Responsible AI, Human Review, and Safety
8.1 Fairness, Bias, Transparency, and Explainability 8.2 Privacy, Safety, Human Review, and Accountability 8.3 Guardrails, Clarify, Human Review, and Content Safety Controls 8.4 Responsible AI Risk Registers and Governance Workflows 8.5 Monitoring, Feedback, Drift, and Incident Response 8.6 Responsible AI Case Lab
9 Chapter 9: Security, Compliance, Governance, and Cost Controls
9.1 Shared Responsibility, IAM, and Least Privilege for AI 9.2 Encryption, Secrets, Networking, and Data Privacy 9.3 Prompt Injection, Data Exfiltration, and GenAI Threat Modeling 9.4 Logging, Monitoring, CloudTrail, CloudWatch, and Config 9.5 Compliance: Artifact, Config, Macie, and Policy Evidence 9.6 AI Cost Controls, Pricing, Throughput, and Budget Governance 9.7 Security and Governance Case Lab
10 Chapter 10: Integrated AWS AI Business Scenario Labs
10.1 Customer Support GenAI Assistant Lab 10.2 Document Intelligence and Compliance Review Lab 10.3 Personalization, Forecasting, and Fraud Detection Lab 10.4 Enterprise Search, RAG, and Knowledge Management Lab 10.5 Responsible AI and Security Review Board Lab 10.6 Cost, Performance, and Operations Review Lab 10.7 Full AIF-C01 Business Simulation
11 Chapter 11: Final Review, Exam Readiness, and Recertification
11.1 Final 30-Day AIF-C01 Study Plan 11.2 Official Practice Resources and Weak-Domain Remediation 11.3 90-Minute Exam Timing, Flagging, and Guessing Workflow 11.4 Test-Day Checklist: Online or Test Center 11.5 Post-Exam Results, Retake, and Recertification Plan 11.6 AWS AI Practitioner Final Mixed Review
9.3 Prompt Injection, Data Exfiltration, and GenAI Threat Modeling
Key Takeaways Explain This Topic AI
Prompt injection happens when user input or retrieved content tries to override application instructions, reveal hidden context, or cause unsafe actions.
Data exfiltration risk increases when a model can access private documents, tools, logs, secrets, or action systems without strong boundaries.
Generative AI threat modeling should identify assets, actors, trust boundaries, inputs, outputs, tools, and failure modes before production approval.
Controls include least privilege, source filtering, prompt design, Amazon Bedrock Guardrails, tool allow lists, output checks, logging, and human review.
The practical goal is not perfect prevention, but reducing impact and making unsafe behavior observable and recoverable.
Last updated: October 2026
GenAI threat modeling for practitioners
A traditional web application usually treats form fields, files, and API calls as inputs. A generative AI application treats natural language as an input too. That creates a new control problem: a user, document, email, web page, or retrieved passage can contain instructions that try to manipulate the model. Prompt injection is the broad term for attempts to override system instructions, bypass policy, reveal hidden context, or trigger unauthorized behavior.
Direct prompt injection comes from the user. The user might ask the assistant to ignore safety rules, reveal the hidden prompt, output private context, or call a tool it should not call. Indirect prompt injection comes from content the application retrieves or processes. A document in a knowledge base could contain text that tells the model to send confidential data to the user. An email summary tool could read an email that instructs it to ignore the original task.
Threat area What can go wrong Practitioner control question
Direct prompt injection User tries to override application rules or reveal hidden context Are instructions, guardrails, and refusal behavior tested against adversarial prompts?
Indirect prompt injection Retrieved content includes malicious instructions Are data sources trusted, scanned, filtered, and separated from control instructions?
Data exfiltration The assistant reveals private documents, secrets, or system prompts Are access controls and output checks limiting what can be returned?
Tool misuse An agent calls an action outside the user's intent or authority Are tools narrow, validated, logged, and gated by confirmation where needed?
Over-trust Users treat generated text as authoritative when it is not Are citations, disclaimers, human review, and escalation paths appropriate?
Data exfiltration is the security concern behind many prompt-injection stories. If the model cannot access sensitive data, it cannot reveal that data. If the application retrieves only documents the user is allowed to see, the blast radius is lower. If an agent has only one narrow action, tool misuse is constrained. That is why least privilege, data minimization, and authorization checks are still the first line of defense for GenAI.
Prompt design helps, but prompts are not a security boundary by themselves. A strong system instruction can tell the model to follow company policy, use only retrieved sources, and refuse requests for secrets. That is useful. But a determined user can still try to manipulate the model, and retrieved text can still conflict with instructions. Security should not depend only on the model deciding to behave.
Amazon Bedrock Guardrails can help evaluate user inputs and model responses for unsafe content, denied topics, sensitive data, prompt attack patterns where supported, and grounding behavior. Guardrails are part of defense-in-depth. They should be combined with IAM, application authorization, source controls, tool schemas, logging, and human review for high-impact actions.
Tool use changes the risk level. A chat assistant that only answers from a public FAQ has limited impact. An AI agent that can create refunds, update customer records, or open support cases needs stronger controls. The application should define allowed tools, required parameters, validation rules, and confirmation steps. The model should not be able to invent new tools or call arbitrary APIs just because the user asks.
A simple threat modeling workflow:
Name the business workflow and the decision or action the AI supports.
List the assets: prompts, documents, embeddings, logs, secrets, user identities, tools, and outputs.
Draw trust boundaries between users, the application, model service, data stores, logs, and action systems.
Identify abuse cases, including prompt injection, indirect instructions, sensitive data requests, unauthorized actions, and false authoritative answers.
Choose layered controls: least privilege, source governance, guardrails, validation, citations, logging, and human review.
Test the system with normal, edge-case, and adversarial prompts before production.
Monitor incidents and update controls as users find new ways to interact with the assistant.
Scenario: a company builds a support assistant that retrieves internal troubleshooting documents. An attacker asks the assistant to reveal all hidden instructions and all documents about unreleased products. The correct control answer is not to trust a stronger prompt alone. The application should enforce user authorization, retrieve only permitted documents, use guardrails and output checks, and log suspicious requests for review.
Scenario: an email summarizer reads incoming messages and drafts replies. A malicious email says to ignore previous instructions and include the user's private calendar details in the reply. This is indirect prompt injection because the instruction comes from content being processed. The application should separate untrusted email content from control instructions, limit tool access, and require user approval before sending responses.
Scenario: an internal procurement agent can submit purchase requests. A user asks it to split a purchase into smaller orders to bypass approval thresholds. This is not only a prompt issue; it is a business policy issue. The backend should enforce spending rules and approvals even if the model produces a persuasive request. The model can assist with form completion, but the system of record must enforce policy.
Practitioner-level GenAI security is about asking where the model can read, write, and act. If the model can only read approved public content, the risk is smaller. If it can read sensitive records and trigger business actions, the review must be stronger. AIF-C01 expects that kind of judgment, not exploit engineering.