<?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>FIPS 140-2 &#8211; Noise</title>
	<atom:link href="https://noise.getoto.net/tag/fips-140-2/feed/" rel="self" type="application/rss+xml" />
	<link>https://noise.getoto.net</link>
	<description>The collective thoughts of the interwebz</description>
	<lastBuildDate>Fri, 09 May 2025 15:25:42 +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>How to manage migration of hsm1.medium CloudHSM clusters to hsm2m.medium</title>
		<link>https://noise.getoto.net/2025/05/09/how-to-manage-migration-of-hsm1-medium-cloudhsm-clusters-to-hsm2m-medium/</link>
		
		<dc:creator><![CDATA[Roshith Alankandy]]></dc:creator>
		<pubDate>Fri, 09 May 2025 15:25:42 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[announcements]]></category>
		<category><![CDATA[AWS CloudHSM]]></category>
		<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[deprecation]]></category>
		<category><![CDATA[FIPS 140-2]]></category>
		<category><![CDATA[Migration]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=2f1a63007c55f77a296d10bd173b98ec</guid>

					<description><![CDATA[On August 20, 2024, we announced the general availability of the new AWS CloudHSM instance type hsm2m.medium (hsm2). This new type comes with additional features compared to the previous AWS CloudHSM instance type, hsm1.medium (hsm1), such as support for Federal Information Processing Standard (FIPS) 140-3 Level 3, the ability to run clusters in non-FIPS mode, […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>AWS-LC FIPS 3.0: First cryptographic library to include ML-KEM in FIPS 140-3 validation</title>
		<link>https://noise.getoto.net/2024/12/10/aws-lc-fips-3-0-first-cryptographic-library-to-include-ml-kem-in-fips-140-3-validation/</link>
		
		<dc:creator><![CDATA[Jake Massimo]]></dc:creator>
		<pubDate>Tue, 10 Dec 2024 16:28:08 +0000</pubDate>
				<category><![CDATA[announcements]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[Federal Information Processing Standard]]></category>
		<category><![CDATA[FIPS]]></category>
		<category><![CDATA[FIPS 140]]></category>
		<category><![CDATA[FIPS 140-2]]></category>
		<category><![CDATA[Foundational (100)]]></category>
		<category><![CDATA[nist]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[post quantum]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=586e82f740e1016d0c0f98ad279650f6</guid>

					<description><![CDATA[We’re excited to announce that AWS-LC FIPS 3.0 has been added to the National Institute of Standards and Technology (NIST) Cryptographic Module Validation Program (CMVP) modules in process list. This latest validation of AWS-LC introduces support for Module Lattice-Based Key Encapsulation Mechanisms (ML-KEM), the new FIPS standardized post-quantum cryptographic algorithm. This is a significant step towards enhancing the […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>How to migrate 3DES keys from a FIPS to a non-FIPS AWS CloudHSM cluster</title>
		<link>https://noise.getoto.net/2024/09/26/how-to-migrate-3des-keys-from-a-fips-to-a-non-fips-aws-cloudhsm-cluster/</link>
		
		<dc:creator><![CDATA[Roshith Alankandy]]></dc:creator>
		<pubDate>Thu, 26 Sep 2024 13:23:36 +0000</pubDate>
				<category><![CDATA[Advanced (300)]]></category>
		<category><![CDATA[AWS CloudHSM]]></category>
		<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[FIPS 140-2]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=ed4667c3fcf385931efce34a39282519</guid>

					<description><![CDATA[On August 20, 2024, we announced the general availability of the new AWS CloudHSM hardware security module (HSM) instance type hsm2m.medium, referred to in this post as hsm2. This new type comes with additional features compared to the previous CloudHSM instance type hsm1.medium (hsm1). The new features include the following: Support for Federal Information Processing […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>AWS KMS is now FIPS 140-2 Security Level 3. What does this mean for you?</title>
		<link>https://noise.getoto.net/2023/11/07/aws-kms-is-now-fips-140-2-security-level-3-what-does-this-mean-for-you/</link>
		
		<dc:creator><![CDATA[Rushir Patel]]></dc:creator>
		<pubDate>Tue, 07 Nov 2023 18:31:15 +0000</pubDate>
				<category><![CDATA[announcements]]></category>
		<category><![CDATA[AWS Key Management Service*]]></category>
		<category><![CDATA[AWS KMS]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[FIPS 140-2]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=a96bb9137f83505a6705cfb86371e4f8</guid>

					<description><![CDATA[AWS Key Management Service (AWS KMS) recently announced that its hardware security modules (HSMs) were given Federal Information Processing Standards (FIPS) 140-2 Security Level 3 certification from the U.S. National Institute of Standards and Technology (NIST). For organizations that rely on AWS cryptographic services, this higher security level validation has several benefits, including simpler set up and operation. In […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>AWS-LC is now FIPS 140-3 certified</title>
		<link>https://noise.getoto.net/2023/10/06/aws-lc-is-now-fips-140-3-certified/</link>
		
		<dc:creator><![CDATA[Nevine Ebeid]]></dc:creator>
		<pubDate>Fri, 06 Oct 2023 17:55:44 +0000</pubDate>
				<category><![CDATA[announcements]]></category>
		<category><![CDATA[Compliance]]></category>
		<category><![CDATA[Cryptography]]></category>
		<category><![CDATA[Federal Information Processing Standard]]></category>
		<category><![CDATA[FIPS]]></category>
		<category><![CDATA[FIPS 140]]></category>
		<category><![CDATA[FIPS 140-2]]></category>
		<category><![CDATA[Foundational (100)]]></category>
		<category><![CDATA[nist]]></category>
		<category><![CDATA[open source]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=56c4a959be229dd89c54114867bc60f9</guid>

					<description><![CDATA[AWS Cryptography is pleased to announce that today, the National Institute for Standards and Technology (NIST) awarded AWS-LC its validation certificate as a Federal Information Processing Standards (FIPS) 140-3, level 1, cryptographic module. This important milestone enables AWS customers that require FIPS-validated cryptography to leverage AWS-LC as a fully owned AWS implementation. AWS-LC is an […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>TLS 1.2 will be required for all AWS FIPS endpoints beginning March 31, 2021</title>
		<link>https://noise.getoto.net/2021/03/01/tls-1-2-will-be-required-for-all-aws-fips-endpoints-beginning-march-31-2021/</link>
		
		<dc:creator><![CDATA[Janelle Hopper]]></dc:creator>
		<pubDate>Mon, 01 Mar 2021 18:04:09 +0000</pubDate>
				<category><![CDATA[announcements]]></category>
		<category><![CDATA[AWS service FIPS endpoints]]></category>
		<category><![CDATA[Federal Information Processing Standard]]></category>
		<category><![CDATA[FedRAMP]]></category>
		<category><![CDATA[FIPS]]></category>
		<category><![CDATA[FIPS 140-2]]></category>
		<category><![CDATA[FIPS endpoints]]></category>
		<category><![CDATA[Intermediate (200)]]></category>
		<category><![CDATA[nist]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[TLS]]></category>
		<category><![CDATA[Transport Layer Security]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=b7595d3a117aaaece8a3199844baeba4</guid>

					<description><![CDATA[To help you meet your compliance needs, we’re updating all AWS Federal Information Processing Standard (FIPS) endpoints to a minimum of Transport Layer Security (TLS) 1.2. We have already updated over 40 services to require TLS 1.2, removing support for TLS 1.0 and TLS 1.1. Beginning March 31, 2021, if your client application cannot support […]]]></description>
		
		
		<enclosure url="" length="0" type="" />

			</item>
		<item>
		<title>Over 40 services require TLS 1.2 minimum for AWS FIPS endpoints</title>
		<link>https://noise.getoto.net/2021/02/02/over-40-services-require-tls-1-2-minimum-for-aws-fips-endpoints/</link>
		
		<dc:creator><![CDATA[Janelle Hopper]]></dc:creator>
		<pubDate>Tue, 02 Feb 2021 17:47:30 +0000</pubDate>
				<category><![CDATA[announcements]]></category>
		<category><![CDATA[AWS service FIPS endpoints]]></category>
		<category><![CDATA[Federal Information Processing Standard]]></category>
		<category><![CDATA[FedRAMP]]></category>
		<category><![CDATA[FIPS]]></category>
		<category><![CDATA[FIPS 140-2]]></category>
		<category><![CDATA[FIPS endpoints]]></category>
		<category><![CDATA[Foundational (100)]]></category>
		<category><![CDATA[nist]]></category>
		<category><![CDATA[Security Blog]]></category>
		<category><![CDATA[Security, Identity & Compliance]]></category>
		<category><![CDATA[TLS]]></category>
		<category><![CDATA[Transport Layer Security]]></category>
		<guid isPermaLink="false">http://noise.getoto.net/?guid=a84c315c500d025d43c7cb43bb4f8910</guid>

					<description><![CDATA[In a March 2020 blog post, we told you about work Amazon Web Services (AWS) was undertaking to update all of our AWS Federal Information Processing Standard (FIPS) endpoints to a minimum of Transport Layer Security (TLS) 1.2 across all AWS Regions. Today, we’re happy to announce that over 40 services have been updated and […]]]></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 36/175 objects using Memcached
Page Caching using Disk: Enhanced 
Lazy Loading (feed)
Database Caching using Memcached

Served from: noise.getoto.net @ 2025-12-05 21:09:26 by W3 Total Cache
-->