<?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> &#187; Regulatory Issues</title>
	<atom:link href="http://www.embeddedmarketintelligence.com/category/regulatory-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.embeddedmarketintelligence.com</link>
	<description>Embedded Topics and Best Practices</description>
	<lastBuildDate>Wed, 07 Sep 2011 21:50:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>FIPS 140-3: What Embedded Vendors Need to Know About the New NSA and NIST Mandated Communication Security Standard</title>
		<link>http://www.embeddedmarketintelligence.com/2010/02/28/fips-140-3-what-embedded-vendors-need-to-know-about-the-new-nsa-and-nist-mandated-communication-security-standard/</link>
		<comments>http://www.embeddedmarketintelligence.com/2010/02/28/fips-140-3-what-embedded-vendors-need-to-know-about-the-new-nsa-and-nist-mandated-communication-security-standard/#comments</comments>
		<pubDate>Sun, 28 Feb 2010 22:24:04 +0000</pubDate>
		<dc:creator>Jerry Krasner</dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Development Tools]]></category>
		<category><![CDATA[Market Intelligence]]></category>
		<category><![CDATA[Regulatory Issues]]></category>

		<guid isPermaLink="false">http://www.embeddedmarketintelligence.com/?p=435</guid>
		<description><![CDATA[     FIPS 140 (acronym for “Federal Information Processing Standard number 140”) is a US government standard, established by the National Institute of Standards and Technology (NIST), which specifies a series of requirements that must be met by an encryption module before it can be used in a Federal government system.  These requirements cover a [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-thumbnail wp-image-438" title="Cool dog" src="http://www.embeddedmarketintelligence.com/wp-content/uploads/2010/02/Cool-dog-150x150.jpg" alt="Cool dog" width="150" height="150" /> </p>
<p> </p>
<p> FIPS 140 (acronym for “Federal Information Processing Standard number 140”) is a US government standard, established by the National Institute of Standards and Technology (NIST), which specifies a series of requirements that must be met by an encryption module before it can be used in a Federal government system.  These requirements cover a range of subjects, from proper key management, to secure generation of random numbers, and from which encryption algorithms may be used, to module self-tests and error detection.</p>
<p> </p>
<p>Put more simply, if a product performs encryption, the portion of that product which actually implements the encryption is the focus of FIPS 140. FIPS 140 is of interest to the embedded systems industry for several reasons:</p>
<p> </p>
<p>First, under Section 5-131 of the Information Technology Reform Act of 1996 (Public Law 104-106), and the Computer Security Act of 1987 (Public Law 100-235), FIPS from NIST may be approved by the Secretary of Commerce and made binding to all Federal agencies.  FIPS 140 has been granted such approval, and therefore all Federal agencies are required to use FIPS 140-certified encryption to protect all sensitive information processed by all data processing systems, from embedded systems to mainframes.</p>
<p> </p>
<p>This means that vendors cannot sell systems which use encryption to any Federal agency unless that system incorporates FIPS 140-certified encryption.</p>
<p> <span id="more-435"></span></p>
<p>Why is there now a FIPS 140-3?</p>
<p> </p>
<p>By mandate, NIST must review all Federal Information Processing Standards Publications every five years. Reviews determine if the standards should be modified, kept as-is, or deprecated as technology and government needs change. FIPS 140-2 was released in 2001 and came due for review in 2006. However, the CMVP had already begun planning for an update for FIPS 140-2 to reflect the ever-changing security technology industry. Although the existing FIPS 140-2 standard does a good job of addressing many validation needs, FIPS 140-3 will be designed to strengthen requirements, and update requirements in the face of new technologies, attacks, and techniques.</p>
<p> </p>
<p>What will happen to FIPS 140-2?</p>
<p> </p>
<p>Once FIPS 140-3 has been released, we will expect to see much of same transition rules as we say from FIPS 140-1 to FIPS 140-2. The new FIPS 140-3 will eventually completely replace FIPS 140-2. As with the prior transition we can expect to see a one year rollover and previous FIPS 140-2 validations most likely will not expire.</p>
<p>Due to the more stringent, revised requirements of the new release, <em>it will likely be much harder to obtain FIPS 140-3 validation</em>. For this reason, consulting companies expect to see a rush of vendors trying to achieve FIPS 140-2 certification before the end of the 1 year rollover period.</p>
<p> </p>
<p>Revalidation will be possible under FIPS 140-2 still, but practically new versions will have to undergo a FIPS 140-3 validation after some time. Technically, a FIPS 140-3 revalidation might be called a new validation. However, FIPS 140-3 is just an evolution of FIPS 140-2, meaning that most of the technical points and work done for the prior validation can be reused. This will expedite certification under FIPS 140-3 and EMF believes this to be a good and timely investment.</p>
<p> </p>
<p>Due to past experiences with the transition from FIPS 140-1 to FIPS 140-2, vendors looking to pursue a certification should consult with companies that assist in the certification process as early as possible in order to avoid common obstacles.</p>
<p> </p>
<p>FIPS 140-2, like all Federal Information Processing Standards, is periodically reviewed, and changes and revisions are expected to be published in the form of the new FIPS 140-3. However, the draft FIPS 140-3 has not yet been finalized let alone signed into law. Although NIST is moving quickly towards this, it still takes significant time to publish and sign a FIPS into law. In addition, we expect NIST to provide transition time between the two standards, including roughly a one year rollover. FIPS 140-2 was signed into law in March 2001, but FIPS 140-1 validations could still be issued until March 2002. Thus, although plans for FIPS 140-3 are under way, vendors may still comfortably pursue FIPS 140-2 for some time.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.embeddedmarketintelligence.com/2010/02/28/fips-140-3-what-embedded-vendors-need-to-know-about-the-new-nsa-and-nist-mandated-communication-security-standard/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

