<?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>s3 on logsec</title>
    <link>https://www.logsec.cloud/tags/s3/</link>
    <description>Recent content in s3 on logsec</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Sat, 20 Jun 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://www.logsec.cloud/tags/s3/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Detect Public S3 Bucket using Splunk</title>
      <link>https://www.logsec.cloud/posts/detect-public-s3-bucket-using-splunk/</link>
      <pubDate>Sat, 20 Jun 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.logsec.cloud/posts/detect-public-s3-bucket-using-splunk/</guid>
      <description>Splunk searches over CloudTrail logs that catch S3 buckets made public through the console, canned ACLs or grant flags, plus how to respond and prevent it.</description>
    </item>
    
    <item>
      <title>Investigating S3 Scanning Activities on AWS</title>
      <link>https://www.logsec.cloud/posts/investigating-on-aws/</link>
      <pubDate>Thu, 04 Jun 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.logsec.cloud/posts/investigating-on-aws/</guid>
      <description>Investigating unknown AWSConfig requests against S3 buckets, reproducing them in a lab, and how AWS Config could be used to check whether a bucket exists.</description>
    </item>
    
  </channel>
</rss>
