<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Security &amp; Encryption — Deep Dive on 🏠</title><link>https://tofl.github.io/docs/9-security-encryption-deep-dive/</link><description>Recent content in Security &amp; Encryption — Deep Dive on 🏠</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://tofl.github.io/docs/9-security-encryption-deep-dive/index.xml" rel="self" type="application/rss+xml"/><item><title>28. KMS</title><link>https://tofl.github.io/docs/9-security-encryption-deep-dive/kms-deep-dive/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/9-security-encryption-deep-dive/kms-deep-dive/</guid><description>&lt;h1 id="kms-key-management-service--deep-dive"&gt;KMS (Key Management Service) — Deep Dive&lt;a class="anchor" href="#kms-key-management-service--deep-dive"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;AWS Key Management Service (KMS) is a managed service that lets you create, control, and use cryptographic keys to protect your data. Its core purpose is simple: rather than managing raw encryption keys yourself — which is error-prone and operationally burdensome — KMS centralises key management, enforces access control via IAM and key policies, and maintains an audit trail through CloudTrail. Every call to KMS is logged, which makes it the default choice for encryption across nearly every AWS service.&lt;/p&gt;</description></item><item><title>29. Secrets Manager &amp; SSM Parameter Store</title><link>https://tofl.github.io/docs/9-security-encryption-deep-dive/secrets-manager-ssm-parameter-store/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/9-security-encryption-deep-dive/secrets-manager-ssm-parameter-store/</guid><description>&lt;h2 id="secrets-manager--ssm-parameter-store"&gt;Secrets Manager &amp;amp; SSM Parameter Store&lt;a class="anchor" href="#secrets-manager--ssm-parameter-store"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Applications constantly need access to sensitive configuration: database passwords, API keys, OAuth tokens, and feature flags. Hardcoding these into source code or environment variables is a well-known security risk. AWS provides two services to solve this: &lt;strong&gt;Secrets Manager&lt;/strong&gt; for sensitive credentials that need lifecycle management (rotation, auditing, cross-account sharing), and &lt;strong&gt;SSM Parameter Store&lt;/strong&gt; for general-purpose configuration storage, including secrets. Knowing which to reach for — and when — is a frequently tested decision on the DVA-C02 exam.&lt;/p&gt;</description></item><item><title>30. ACM / ACM Private CA</title><link>https://tofl.github.io/docs/9-security-encryption-deep-dive/acm-private-ca/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/9-security-encryption-deep-dive/acm-private-ca/</guid><description>&lt;h2 id="acm--acm-private-ca"&gt;ACM / ACM Private CA&lt;a class="anchor" href="#acm--acm-private-ca"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;TLS certificates are what enable HTTPS — they authenticate your server&amp;rsquo;s identity and encrypt traffic between clients and your application. Without them, browsers display security warnings and connections are unencrypted. The problem they solve sounds simple, but managing certificates manually is error-prone: you have to generate them, validate domain ownership, deploy them to the right services, and renew them before they expire (typically every 13 months). A missed renewal causes an outage. &lt;strong&gt;AWS Certificate Manager (ACM)&lt;/strong&gt; &lt;a href="https://docs.aws.amazon.com/acm/latest/userguide/acm-overview.html"&gt;🔗&lt;/a&gt; automates all of this — provisioning, validation, deployment, and renewal — at no cost for certificates used with supported AWS services.&lt;/p&gt;</description></item><item><title>31. Macie</title><link>https://tofl.github.io/docs/9-security-encryption-deep-dive/macie/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/9-security-encryption-deep-dive/macie/</guid><description>&lt;h2 id="macie"&gt;Macie&lt;a class="anchor" href="#macie"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;As applications grow, so does the amount of data they store in S3 — user uploads, logs, exports, backups. It becomes increasingly difficult to track whether any of that data contains sensitive information like names, email addresses, credit card numbers, or API keys. Amazon Macie exists to solve exactly this problem: it automatically scans S3 buckets using machine learning to detect sensitive and personally identifiable information (PII), and alerts you when it finds something — or when your bucket configurations expose data in risky ways.&lt;/p&gt;</description></item></channel></rss>