<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Fola Bolodeoku &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/author/fola-bolodeoku/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Thu, 08 Jul 2021 18:00:17 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.2</generator>
	<item>
		<title>Automatically update AWS WAF IP sets with AWS IP ranges</title>
		<link>https://noise.getoto.net/2021/07/08/automatically-update-aws-waf-ip-sets-with-aws-ip-ranges/</link>
		
		<dc:creator><![CDATA[Fola Bolodeoku]]></dc:creator>
		<pubDate>Thu, 08 Jul 2021 18:00:17 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[AWS Shield]]></category>
		<category><![CDATA[AWS Threat Research Team]]></category>
		<category><![CDATA[AWS WAF]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[Web application]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=8e64700ac3eabe3c9f272f7f199c5fd7</guid>

					<description><![CDATA[Note: This blog post describes how to automatically update AWS WAF IP sets with the most recent AWS IP ranges for AWS services. This related blog post describes how to perform a similar update for Amazon CloudFront IP ranges that are used in VPC Security Groups. You can use AWS Managed Rules for AWS WAF […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Set up centralized monitoring for DDoS events and auto-remediate noncompliant resources</title>
		<link>https://noise.getoto.net/2020/11/19/set-up-centralized-monitoring-for-ddos-events-and-auto-remediate-noncompliant-resources/</link>
		
		<dc:creator><![CDATA[Fola Bolodeoku]]></dc:creator>
		<pubDate>Thu, 19 Nov 2020 19:21:33 +0000</pubDate>
				<category><![CDATA[AWS Firewall Manager]]></category>
		<category><![CDATA[AWS Shield]]></category>
		<category><![CDATA[AWS Threat Research Team]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[ddos]]></category>
		<category><![CDATA[Detection]]></category>
		<category><![CDATA[Governance]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=8a4b1091b5b206e2161f6dd75c49b33a</guid>

					<description><![CDATA[When you build applications on Amazon Web Services (AWS), it&#8217;s a common security practice to isolate production resources from non-production resources by logically grouping them into functional units or organizational units. There are many benefits to this approach, such as making it easier to implement the principal of least privilege, or reducing the scope of [&#8230;]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
	</channel>
</rss>

<!--
Performance optimized by W3 Total Cache. Learn more: https://www.boldgrid.com/w3-total-cache/

Object Caching 26/80 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2026-03-11 09:27:18 by W3 Total Cache
-->