<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on Syafiy Rahman</title>
    <link>https://syafiy.dev/tags/security/</link>
    <description>Recent content in Security on Syafiy Rahman</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://syafiy.dev/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Guarding the Cloud: Security Services &amp; Auditing</title>
      <link>https://syafiy.dev/posts/aws-saa-c03-domain1-security/</link>
      <pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate>
      <guid>https://syafiy.dev/posts/aws-saa-c03-domain1-security/</guid>
      <description>&lt;p&gt;In &lt;a href=&#34;https://syafiy.dev/posts/aws-saa-c03-domain1-identity/&#34;&gt;Part 1&lt;/a&gt;, I covered the identity side of Domain 1 — IAM, STS, Cognito, Organizations, and all the services that control who gets in and what they&amp;rsquo;re allowed to do. Now comes the next layer: how do you protect what&amp;rsquo;s inside, detect threats, and audit everything?&lt;/p&gt;&#xA;&lt;p&gt;AWS has a surprisingly deep set of security tools. Some are for prevention, some for detection, some for compliance. Knowing which one does what — and when to use each — is a big part of Domain 1.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
