<?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>least privilege &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/tag/least-privilege/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Mon, 24 Mar 2025 16:03: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>Use AWS service reference information to automate policy management workflows</title>
		<link>https://noise.getoto.net/2025/03/24/use-aws-service-reference-information-to-automate-policy-management-workflows/</link>
		
		<dc:creator><![CDATA[Ramesh Rajan]]></dc:creator>
		<pubDate>Mon, 24 Mar 2025 16:03:17 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS IAM Access Analyzer]]></category>
		<category><![CDATA[AWS IAM policies]]></category>
		<category><![CDATA[AWS Identity and Access Management]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[Best practices]]></category>
		<category><![CDATA[IAM]]></category>
		<category><![CDATA[IAM Access Analyzer]]></category>
		<category><![CDATA[IAM policies]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=5b8657de13178c1445a7c667f74b5b75</guid>

					<description><![CDATA[Amazon Web Services (AWS) provides service reference information in JSON format to help you automate policy management workflows. With the service reference information, you can access available actions across AWS services from machine-readable files. The service reference information helps to address a key customer need: keeping up with the ever-growing list of services and actions […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Four ways to grant cross-account access in AWS</title>
		<link>https://noise.getoto.net/2025/02/24/four-ways-to-grant-cross-account-access-in-aws/</link>
		
		<dc:creator><![CDATA[Anshu Bathla]]></dc:creator>
		<pubDate>Mon, 24 Feb 2025 20:01:05 +0000</pubDate>
				<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS IAM policies]]></category>
		<category><![CDATA[AWS Identity and Access Management]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[Best practices]]></category>
		<category><![CDATA[IAM]]></category>
		<category><![CDATA[IAM policies]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=d82532a151928554776de736af601f0f</guid>

					<description><![CDATA[As your Amazon Web Services (AWS) environment grows, you might develop a need to grant cross-account access to resources. This could be for various reasons, such as enabling centralized operations across multiple AWS accounts, sharing resources across teams or projects within your organization, or integrating with third-party services. However, granting cross-account access requires careful consideration […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>How to implement IAM policy checks with Visual Studio Code and IAM Access Analyzer</title>
		<link>https://noise.getoto.net/2025/01/14/how-to-implement-iam-policy-checks-with-visual-studio-code-and-iam-access-analyzer/</link>
		
		<dc:creator><![CDATA[Anshu Bathla]]></dc:creator>
		<pubDate>Tue, 14 Jan 2025 17:02:04 +0000</pubDate>
				<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS IAM Access Analyzer]]></category>
		<category><![CDATA[AWS IAM policies]]></category>
		<category><![CDATA[AWS Identity and Access Management]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[IAM]]></category>
		<category><![CDATA[IAM Access Analyzer]]></category>
		<category><![CDATA[IAM policies]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=e65bb63588f35d018d106aeaff490e5c</guid>

					<description><![CDATA[In a previous blog post, we introduced the IAM Access Analyzer custom policy check feature, which allows you to validate your policies against custom rules. Now we’re taking a step further and bringing these policy checks directly into your development environment with the AWS Toolkit for Visual Studio Code (VS Code). In this blog post, […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Customize the scope of IAM Access Analyzer unused access analysis</title>
		<link>https://noise.getoto.net/2025/01/08/customize-the-scope-of-iam-access-analyzer-unused-access-analysis/</link>
		
		<dc:creator><![CDATA[Stéphanie Mbappe]]></dc:creator>
		<pubDate>Wed, 08 Jan 2025 17:35:14 +0000</pubDate>
				<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS IAM Access Analyzer]]></category>
		<category><![CDATA[AWS IAM policies]]></category>
		<category><![CDATA[AWS Identity and Access Management]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[IAM]]></category>
		<category><![CDATA[IAM Access Analyzer]]></category>
		<category><![CDATA[IAM policies]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=48e65569ea7a4ab0d9f412e9d81950b1</guid>

					<description><![CDATA[AWS Identity and Access Management Access Analyzer simplifies inspecting unused access to guide you towards least privilege. You can use unused access findings to identify over-permissive access granted to AWS Identity and Access Management (IAM) roles and users in your accounts or organization. From a delegated administrator account for IAM Access Analyzer, you can use the dashboard […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Refine unused access using IAM Access Analyzer recommendations</title>
		<link>https://noise.getoto.net/2024/09/18/refine-unused-access-using-iam-access-analyzer-recommendations/</link>
		
		<dc:creator><![CDATA[Stéphanie Mbappe]]></dc:creator>
		<pubDate>Wed, 18 Sep 2024 19:09:34 +0000</pubDate>
				<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS IAM Access Analyzer]]></category>
		<category><![CDATA[AWS IAM policies]]></category>
		<category><![CDATA[AWS Identity and Access Management]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[IAM Access Analyzer]]></category>
		<category><![CDATA[IAM policies]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=4648a7ca3a0b47cddf98049ce4b7af27</guid>

					<description><![CDATA[As a security team lead, your goal is to manage security for your organization at scale and ensure that your team follows AWS Identity and Access Management (IAM) security best practices, such as the principle of least privilege. As your developers build on AWS, you need visibility across your organization to make sure that teams […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Refine permissions for externally accessible roles using IAM Access Analyzer and IAM action last accessed</title>
		<link>https://noise.getoto.net/2023/11/01/refine-permissions-for-externally-accessible-roles-using-iam-access-analyzer-and-iam-action-last-accessed/</link>
		
		<dc:creator><![CDATA[Nini Ren]]></dc:creator>
		<pubDate>Wed, 01 Nov 2023 18:51:27 +0000</pubDate>
				<category><![CDATA[Access management]]></category>
		<category><![CDATA[Amazon DynamoDB]]></category>
		<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS IAM Access Analyzer]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[IAM roles]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[policies]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[Security Blog]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=4185671b8c05efc692a62d9e54459559</guid>

					<description><![CDATA[When you build on Amazon Web Services (AWS) across accounts, you might use an AWS Identity and Access Management (IAM) role to allow an authenticated identity from outside your account—such as an IAM entity or a user from an external identity provider—to access the resources in your account. IAM roles have two types of policies […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Two real-life examples of why limiting permissions works: Lessons from AWS CIRT</title>
		<link>https://noise.getoto.net/2023/08/31/two-real-life-examples-of-why-limiting-permissions-works-lessons-from-aws-cirt/</link>
		
		<dc:creator><![CDATA[Richard Billington]]></dc:creator>
		<pubDate>Thu, 31 Aug 2023 14:03:48 +0000</pubDate>
				<category><![CDATA[AWS Incident Response]]></category>
		<category><![CDATA[Best practices]]></category>
		<category><![CDATA[incident response]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[Threat Detection & Incident Response]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=58e6de58c53330a6eb11161a8161ed7a</guid>

					<description><![CDATA[Welcome to another blog post from the AWS Customer Incident Response Team (CIRT)! For this post, we’re looking at two events that the team was involved in from the viewpoint of a regularly discussed but sometimes misunderstood subject, least privilege. Specifically, we consider the idea that the benefit of reducing permissions in real-life use cases […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Use IAM Access Analyzer policy generation to grant fine-grained permissions for your AWS CloudFormation service roles</title>
		<link>https://noise.getoto.net/2022/10/07/use-iam-access-analyzer-policy-generation-to-grant-fine-grained-permissions-for-your-aws-cloudformation-service-roles/</link>
		
		<dc:creator><![CDATA[Joel Knight]]></dc:creator>
		<pubDate>Fri, 07 Oct 2022 19:19:32 +0000</pubDate>
				<category><![CDATA[Access management]]></category>
		<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[AWS CloudTrail]]></category>
		<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[policies]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=66af7307dc311d91b394cfd379abf6fe</guid>

					<description><![CDATA[AWS Identity and Access Management (IAM) Access Analyzer provides tools to simplify permissions management by making it simpler for you to set, verify, and refine permissions. One such tool is IAM Access Analyzer policy generation, which creates fine-grained policies based on your AWS CloudTrail access activity—for example, the actions you use with Amazon Elastic Compute […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>IAM Access Analyzer makes it simpler to author and validate role trust policies</title>
		<link>https://noise.getoto.net/2022/10/04/iam-access-analyzer-makes-it-simpler-to-author-and-validate-role-trust-policies/</link>
		
		<dc:creator><![CDATA[Mathangi Ramesh]]></dc:creator>
		<pubDate>Mon, 03 Oct 2022 22:43:21 +0000</pubDate>
				<category><![CDATA[Access management]]></category>
		<category><![CDATA[AWS CloudTrail]]></category>
		<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS IAM Access Analyzer]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[policies]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[Technical How-to]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=56e945541f595b15cdb506d6651b96e5</guid>

					<description><![CDATA[AWS Identity and Access Management (IAM) Access Analyzer provides many tools to help you set, verify, and refine permissions. One part of IAM Access Analyzer—policy validation—helps you author secure and functional policies that grant the intended permissions. Now, I’m excited to announce that AWS has updated the IAM console experience for role trust policies to […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Use IAM Access Analyzer to generate IAM policies based on access activity found in your organization trail</title>
		<link>https://noise.getoto.net/2021/08/26/use-iam-access-analyzer-to-generate-iam-policies-based-on-access-activity-found-in-your-organization-trail/</link>
		
		<dc:creator><![CDATA[Mathangi Ramesh]]></dc:creator>
		<pubDate>Thu, 26 Aug 2021 20:33:49 +0000</pubDate>
				<category><![CDATA[Access management]]></category>
		<category><![CDATA[Amazon CloudTrail]]></category>
		<category><![CDATA[Amazon DynamoDB]]></category>
		<category><![CDATA[Amazon EC2]]></category>
		<category><![CDATA[Amazon S3]]></category>
		<category><![CDATA[Amazon Simple Storage Services (S3)]]></category>
		<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS IAM Access Analyzer]]></category>
		<category><![CDATA[AWS Lambda]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[policies]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=2cdfd0f94867b7aa06ac9e9ec198b00d</guid>

					<description><![CDATA[In April 2021, AWS Identity and Access Management (IAM) Access Analyzer added policy generation to help you create fine-grained policies based on AWS CloudTrail activity stored within your account. Now, we’re extending policy generation to enable you to generate policies based on access activity stored in a designated account. For example, you can use AWS […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Techniques for writing least privilege IAM policies</title>
		<link>https://noise.getoto.net/2020/12/02/techniques-for-writing-least-privilege-iam-policies/</link>
		
		<dc:creator><![CDATA[Ben Potter]]></dc:creator>
		<pubDate>Wed, 02 Dec 2020 18:01:31 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[AWS Well-Architected]]></category>
		<category><![CDATA[Best practices]]></category>
		<category><![CDATA[IAM policies]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[well architected]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=bbc6ca1ca98e2a6f1ff59ce7f228443e</guid>

					<description><![CDATA[In this post, I&#8217;m going to share two techniques I&#8217;ve used to write least privilege AWS Identity and Access Management (IAM) policies. If you&#8217;re not familiar with IAM policy structure, I highly recommend you read understanding how IAM works and policies and permissions. Least privilege is a principle of granting only the permissions required to [&#8230;]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>New! Streamline existing IAM Access Analyzer findings using archive rules</title>
		<link>https://noise.getoto.net/2020/10/28/new-streamline-existing-iam-access-analyzer-findings-using-archive-rules/</link>
		
		<dc:creator><![CDATA[Andrea Nedic]]></dc:creator>
		<pubDate>Wed, 28 Oct 2020 18:13:32 +0000</pubDate>
				<category><![CDATA[Access management]]></category>
		<category><![CDATA[Automated reasoning]]></category>
		<category><![CDATA[AWS IAM]]></category>
		<category><![CDATA[AWS IAM Access Analyzer]]></category>
		<category><![CDATA[AWS Identity and Access Management (IAM)]]></category>
		<category><![CDATA[IAM Access Analyzer]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=6c57cc8004d5ce04fc93d03d69005019</guid>

					<description><![CDATA[AWS Identity and Access Management (IAM) Access Analyzer generates comprehensive findings to help you identify resources that grant public and cross-account access. Now, you can also apply archive rules to existing findings, so you can better manage findings and focus on the findings that need your attention most. You can think of archive rules as [&#8230;]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>How to get read-only visibility into the AWS Control Tower console</title>
		<link>https://noise.getoto.net/2020/10/01/how-to-get-read-only-visibility-into-the-aws-control-tower-console/</link>
		
		<dc:creator><![CDATA[Bruno Mendez]]></dc:creator>
		<pubDate>Thu, 01 Oct 2020 19:30:38 +0000</pubDate>
				<category><![CDATA[AWS Control Tower]]></category>
		<category><![CDATA[Foundational (100)]]></category>
		<category><![CDATA[IAM policy]]></category>
		<category><![CDATA[least privilege]]></category>
		<category><![CDATA[Readonly]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=26250f99ed03b7bf85da18b2556f6110</guid>

					<description><![CDATA[When you audit an environment governed by AWS Control Tower, having visibility into the AWS Control Tower console allows you to collect important configuration information, but currently there isn&#8217;t a read-only role installed by AWS Control Tower. In this post, I will show you how to create a custom permission set by using both a [&#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 40/286 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2025-12-09 13:09:01 by W3 Total Cache
-->