<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Compliance on Daman Arora</title>
    <link>https://damanarora.netlify.app/tags/compliance/</link>
    <description>Recent content in Compliance on Daman Arora</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Mon, 18 May 2026 16:00:00 +0000</lastBuildDate><atom:link href="https://damanarora.netlify.app/tags/compliance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AWS Security &amp; Compliance: A Tour of the Services</title>
      <link>https://damanarora.netlify.app/posts/aws-security-and-compliance/</link>
      <pubDate>Mon, 18 May 2026 16:00:00 +0000</pubDate>
      
      <guid>https://damanarora.netlify.app/posts/aws-security-and-compliance/</guid>
      <description>Security on AWS is a layered set of responsibilities and a long catalogue of services. AWS handles the security of the cloud; you handle security in the cloud. This post walks through that split, then through the services that protect networks, manage keys, detect threats, and prove compliance.
The shared responsibility model The foundation: AWS and the customer have clearly divided jobs.
AWS is responsible for security of the cloud — the hardware, software, facilities, and networking that run every AWS service, plus the operations of fully managed services like S3, DynamoDB, and RDS.</description>
    </item>
    
  </channel>
</rss>
