Study guide

9.2 Encryption, Secrets, Networking, and Data Privacy

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.2 Encryption, Secrets, Networking, and Data Privacy

Key Takeaways Explain This Topic AI

AI data should be protected at rest and in transit, including prompts, source documents, model artifacts, logs, embeddings, and generated outputs where they are stored.

AWS KMS, TLS, IAM, Secrets Manager, VPC design, private connectivity, and storage policies help reduce exposure, but they must be matched to the data risk.

Secrets such as API keys, database passwords, and service credentials should not be placed in prompts, code, notebooks, source files, or plain environment variables without controls.

Data privacy for AI depends on minimization, classification, retention, residency, logging decisions, masking, and user consent or policy basis where required.

Practitioners should ask whether sensitive data is actually needed for the model task before approving its use.

Last updated: May 2026

Protecting the AI data path

AI security discussions often focus on the model, but the data path is usually wider. A generative AI application may read documents from Amazon S3, create embeddings, store vectors, send prompts to Amazon Bedrock, call Lambda functions, write logs to CloudWatch Logs, store transcripts, and return outputs to users. Each step can contain sensitive data. Encryption, secrets management, network controls, and privacy rules should be considered before the pilot becomes production.

Encryption at rest protects stored data. S3 objects, databases, logs, model artifacts, vector indexes, and backups should use encryption settings appropriate to the sensitivity of the data. AWS Key Management Service, or AWS KMS, lets organizations manage cryptographic keys and key policies for many AWS services. A practitioner does not need to design key rotation logic, but should know that key ownership, access to keys, and logging destinations matter.

Encryption in transit protects data moving between clients, applications, and services. TLS is the normal expectation for service APIs and web applications. If users upload documents to an AI assistant, those uploads should be protected in transit. If an application calls Bedrock, SageMaker AI, S3, OpenSearch Service, or an API action, the network path should use secure protocols and avoid unnecessary public exposure.

Control area What it protects Practitioner question

Encryption at rest Stored prompts, logs, documents, embeddings, outputs, and artifacts Are storage locations encrypted with keys that match data sensitivity?

Encryption in transit Requests and responses between users, apps, and AWS services Are secure protocols used for uploads, model calls, and APIs?

Secrets management Passwords, API keys, database credentials, and tokens Are secrets stored in AWS Secrets Manager or another approved system instead of prompts or code?

Network boundaries Traffic paths to services and data stores Can private connectivity or VPC endpoints reduce public network exposure?

Privacy controls Personal, regulated, customer, or confidential information Is the data necessary, minimized, masked, retained properly, and logged intentionally?

Secrets are a common failure point. A developer may paste a database password into a notebook, put a third-party API key in application code, or ask a model to remember a token during troubleshooting. That is not acceptable governance. Secrets should be stored in a managed system such as AWS Secrets Manager and retrieved by authorized applications at runtime. IAM should decide which role can read a secret, and logs should not expose secret values.

Network design depends on the workload. Some AI tools are internal and should not be reachable from the public internet. A web application may run in a VPC, use private subnets for backend services, and access AWS services through controlled paths. For some AWS services, VPC endpoints and AWS PrivateLink can keep traffic on the AWS network path instead of sending it over the public internet. The exam-level judgment is to recognize when private connectivity and network segmentation reduce exposure.

Data privacy starts with minimization. If the model only needs a product description, do not include customer account numbers. If a summarizer only needs a transcript excerpt, do not include unrelated case history. If a RAG assistant needs approved policy documents, do not index personal employee records by default. The safest sensitive data is the data that never enters the AI workflow.

Logging decisions can create privacy risk. Model invocation logs, application logs, traces, and error messages may contain prompts, responses, retrieved passages, or user identifiers. Those logs are useful for troubleshooting and safety review, but they need access control, encryption, retention limits, and redaction where appropriate. A team should not enable verbose logging in production without knowing who can read the logs and how long they are kept.

Data residency and retention are business requirements, not only technical settings. Some organizations restrict where regulated or customer data may be processed or stored. Others have rules for deleting chat transcripts, removing documents from search indexes, or keeping audit evidence. A practitioner should ask which Region is approved, which records must be retained, which records must be deleted, and whether downstream copies such as embeddings or logs follow the same rule.

Privacy review workflow:

Classify the data that will enter the AI workflow.

Decide whether each data element is necessary for the task.

Remove, mask, tokenize, or aggregate sensitive fields where possible.

Confirm encryption at rest and in transit for each storage and service boundary.

Store secrets in an approved secrets manager and grant access only to runtime roles that need them.

Decide whether logs will contain prompts, responses, or retrieved context.

Define retention, deletion, Region, and access-review requirements before launch.

Scenario: a financial services team wants to summarize customer calls. The model may need the call transcript, but it probably does not need full payment card details or authentication secrets. The design should redact or avoid sensitive fields, protect the transcript store, limit who can view summaries, and control logs. A human review step may also be required if summaries affect customer decisions.

Scenario: an engineering team wants a code assistant that can query internal systems. Secrets Manager can store API credentials, but the assistant should not reveal those credentials to users or include them in model prompts. The backend can call approved APIs using a role, while the model receives only the minimum result needed to answer the user. That separation is a basic privacy and security pattern.

In AWS Skill Builder practice, pay attention to where data lands. A lab might show S3 encryption, KMS keys, Secrets Manager, VPC settings, or CloudWatch Logs. Do not memorize them as isolated services. Map them onto the AI path: source data, prompt, model call, retrieved context, output, logs, and action systems.