<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Your Complete Source for GSA Approved Identity Products: Paragon KVM receives FIPS 201 approval</title>
    <link>http://www.fips201.com/articles/2008/01/10/paragon-kvm-receives-fips-201-approval</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description></description>
    <item>
      <title>Paragon KVM receives FIPS 201 approval</title>
      <description>&lt;p&gt;Raritan recently announced that its Paragon II enterprise-class KVM solution, said to be the industry&amp;#8217;s first to be offered with an optional integrated smart-card-reader, has achieved approval under FIPS 201 &amp;#8211; the U.S. Federal government&amp;#8217;s important standard that specifies Personal Identity Verification (PIV) requirements for Federal employees and contractors. The FIPS 201 approval has been granted under the category of &amp;#8220;Transparent Card Reader.&amp;#8221; Only FIPS 201-compliant card readers can be used in identity management systems for complying with the U.S. Homeland Security Presidential Directive (HSPD-12). The directive outlines a common identification standard for authenticating federal employee and contractor access, both physically and logically, to federal information systems.&lt;/p&gt;

&lt;p&gt;Read the full article at &lt;a href="http://www.secureidnews.com/news/2008/01/10/paragon-kvm-receives-fips-201-approval"&gt;SecureIDNews.com&lt;/a&gt;.&lt;/p&gt;</description>
      <pubDate>Thu, 10 Jan 2008 08:58:00 -0500</pubDate>
      <guid isPermaLink="false">urn:uuid:2e751ae9-ed86-4f6f-bde2-729f0b821cc8</guid>
      <author>FIPS 201 Administrator</author>
      <link>http://www.fips201.com/articles/2008/01/10/paragon-kvm-receives-fips-201-approval</link>
      <category>New Additions</category>
      <category>News</category>
    </item>
  </channel>
</rss>
