<?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>Cisco Blog &#187; Jim Fenton</title>
	<atom:link href="http://blogs.cisco.com/author/JimFenton/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.cisco.com</link>
	<description></description>
	<lastBuildDate>Tue, 18 Jun 2013 21:29:28 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Top of Mind: Reexamining Public Key Infrastructure</title>
		<link>http://blogs.cisco.com/security/reexamining-public-key-infrastructure/</link>
		<comments>http://blogs.cisco.com/security/reexamining-public-key-infrastructure/#comments</comments>
		<pubDate>Tue, 15 Nov 2011 02:27:55 +0000</pubDate>
		<dc:creator>Jim Fenton</dc:creator>
				<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=51240</guid>
		<description><![CDATA[Nearly all of us depend on public key infrastructure (PKI) when we engage in secure transactions on the Internet. Digital certificates, most commonly based on ITU standard X.509, are used to prove that one is communicating with an intended website or Internet host. They are also used to establish the ownership of specific email addresses when S/MIME signing and encryption are used.  Having a secure way to determine who you're communicating with is important because an impostor or “man in the middle” site could decrypt the data sent to it, effectively defeating the security of the transaction.]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/reexamining-public-key-infrastructure/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Establishing Trust in the NSTIC</title>
		<link>http://blogs.cisco.com/security/establishing-trust-in-the-nstic/</link>
		<comments>http://blogs.cisco.com/security/establishing-trust-in-the-nstic/#comments</comments>
		<pubDate>Wed, 15 Jun 2011 16:29:15 +0000</pubDate>
		<dc:creator>Jim Fenton</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[identity]]></category>
		<category><![CDATA[NSTIC]]></category>
		<category><![CDATA[NSTIC Series]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=33671</guid>
		<description><![CDATA[The National Strategy for Trusted Identities in Cyberspace (NSTIC) proposes a large ecosystem of identity providers, attribute providers, and relying parties that must establish trust with each other in various ways. NSTIC requires various types of trust within the identity ecosystem. ]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/establishing-trust-in-the-nstic/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Adapting Levels of Assurance for the NSTIC</title>
		<link>http://blogs.cisco.com/security/adapting-levels-of-assurance-for-the-nstic/</link>
		<comments>http://blogs.cisco.com/security/adapting-levels-of-assurance-for-the-nstic/#comments</comments>
		<pubDate>Thu, 19 May 2011 14:16:59 +0000</pubDate>
		<dc:creator>Jim Fenton</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[identity]]></category>
		<category><![CDATA[NSTIC]]></category>
		<category><![CDATA[NSTIC Series]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=30955</guid>
		<description><![CDATA[One of the goals of the National Strategy for Trusted Identities in Cyberspace (NSTIC) is to support a wide range of use cases.  These might include everything from low-value purchases to making adjustments to critical infrastructure, like power systems, where someone might get hurt if an unauthorized action takes place.  The level of confidence in the validity associated with an identity is referred to as Level of Assurance (LOA). ]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/adapting-levels-of-assurance-for-the-nstic/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Credential and Attribute Providers in the NSTIC</title>
		<link>http://blogs.cisco.com/security/credential-and-attribute-providers-in-the-nstic/</link>
		<comments>http://blogs.cisco.com/security/credential-and-attribute-providers-in-the-nstic/#comments</comments>
		<pubDate>Fri, 06 May 2011 15:24:58 +0000</pubDate>
		<dc:creator>Jim Fenton</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[identity]]></category>
		<category><![CDATA[NSTIC]]></category>
		<category><![CDATA[NSTIC Series]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=29769</guid>
		<description><![CDATA[The <a href="http://www.nist.gov/nstic/" target="_blank">National Strategy for Trusted Identities in Cyberspace</a> (NSTIC) <a href="http://www.whitehouse.gov/sites/default/files/rss_viewer/NSTICstrategy_041511.pdf" target="_blank">describes</a> two types of intermediaries between subjects (users) and relying parties: identity providers and attribute providers. This is a separation not frequently found in identity systems.  In order to emphasize this distinction, I often use the term “credential provider” or “authentication provider” rather than identity provider to refer to a service that provides authentication services and makes assertions resulting from authentication but does not directly provide attributes about the subject.]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/credential-and-attribute-providers-in-the-nstic/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Identity Intermediaries and the NSTIC</title>
		<link>http://blogs.cisco.com/security/identity-intermediaries-and-the-nstic/</link>
		<comments>http://blogs.cisco.com/security/identity-intermediaries-and-the-nstic/#comments</comments>
		<pubDate>Thu, 28 Apr 2011 19:40:02 +0000</pubDate>
		<dc:creator>Jim Fenton</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[NSTIC]]></category>
		<category><![CDATA[NSTIC Series]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=28841</guid>
		<description><![CDATA[A couple of months ago, I spoke with a security researcher at a conference about the NSTIC.  He questioned the need for an intermediary to manage users' identity information; he asked why we don't just do this at the user's endpoint, eliminating the need for the user to trust an external party.  This is a good place to begin a discussion about the NSTIC architecture.]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/identity-intermediaries-and-the-nstic/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>NSTIC Strategy Released</title>
		<link>http://blogs.cisco.com/security/nstic-strategy-released/</link>
		<comments>http://blogs.cisco.com/security/nstic-strategy-released/#comments</comments>
		<pubDate>Wed, 20 Apr 2011 21:45:35 +0000</pubDate>
		<dc:creator>Jim Fenton</dc:creator>
				<category><![CDATA[Security]]></category>
		<category><![CDATA[NSTIC]]></category>
		<category><![CDATA[NSTIC Series]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=28146</guid>
		<description><![CDATA[Last June, <a href="http://blogs.cisco.com/security/the_national_strategy_for_trusted_identities_in_cyberspace/" target="_blank">I blogged</a> about a draft of the National Strategy for Trusted Identities in Cyberspace (NSTIC) that had been released for public comment.  This past April 15, the finalized <a href="http://www.whitehouse.gov/sites/default/files/rss_viewer/NSTICstrategy_041511.pdf" target="_blank">NSTIC strategy document</a> was <a href="http://www.nist.gov/public_affairs/releases/whitehouse_nstic.cfm" target="_blank">released</a> at an event at the US Chamber of Commerce.]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/nstic-strategy-released/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Trusted Intermediaries as Privacy Agents</title>
		<link>http://blogs.cisco.com/security/trusted-intermediaries-as-privacy-agents/</link>
		<comments>http://blogs.cisco.com/security/trusted-intermediaries-as-privacy-agents/#comments</comments>
		<pubDate>Tue, 14 Dec 2010 17:10:17 +0000</pubDate>
		<dc:creator>Jim Fenton</dc:creator>
				<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/?p=15789</guid>
		<description><![CDATA[Trusted intermediaries could provide a way for users to manage their personal information, including data managed by third parties (such as their credit score), in a manner they control. The intermediary would provide a way for the user to store their preferences regarding the disclosure of specific information, including the terms under which the information can be reused and repurposed.]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/trusted-intermediaries-as-privacy-agents/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The National Strategy for Trusted Identities in Cyberspace</title>
		<link>http://blogs.cisco.com/security/the_national_strategy_for_trusted_identities_in_cyberspace/</link>
		<comments>http://blogs.cisco.com/security/the_national_strategy_for_trusted_identities_in_cyberspace/#comments</comments>
		<pubDate>Tue, 13 Jul 2010 20:00:00 +0000</pubDate>
		<dc:creator>Jim Fenton</dc:creator>
				<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/online_safety_tips_for_data_privacy</guid>
		<description><![CDATA[On June 25, the US Government <a href="http://www.whitehouse.gov/blog/2010/06/25/national-strategy-trusted-identities-cyberspace" target="_blank">released</a> the National Strategy for Trusted Identities in Cyberspace (NSTIC, pronounced &#8220;N-stick&#8221;) for public review [...]]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/the_national_strategy_for_trusted_identities_in_cyberspace/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Key Lengths for DKIM Signatures</title>
		<link>http://blogs.cisco.com/security/key_lengths_for_dkim_signatures/</link>
		<comments>http://blogs.cisco.com/security/key_lengths_for_dkim_signatures/#comments</comments>
		<pubDate>Wed, 23 Jun 2010 20:00:00 +0000</pubDate>
		<dc:creator>Jim Fenton</dc:creator>
				<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/the_world_cup._watching_at_work._a_massive_wave_of_ways_to_experience_and_v</guid>
		<description><![CDATA[A <a href="http://blog.jgc.org/2010/06/facebooks-dkim-rsa-key-should-be.html" target="_blank">blog post</a> that appeared last Friday, observed that Facebook is signing their mail with <a href="http://www.dkim.org/" target="_blank">DomainKeys Identified Mail</a> (DKIM) using a 512-bit RSA key. The [...]]]></description>
		<wfw:commentRss>http://blogs.cisco.com/security/key_lengths_for_dkim_signatures/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Growth in DKIM Signing Continues</title>
		<link>http://blogs.cisco.com/news/growth_in_dkim_signing_continues/</link>
		<comments>http://blogs.cisco.com/news/growth_in_dkim_signing_continues/#comments</comments>
		<pubDate>Wed, 31 Mar 2010 20:00:00 +0000</pubDate>
		<dc:creator>Jim Fenton</dc:creator>
				<category><![CDATA[The Platform]]></category>

		<guid isPermaLink="false">http://blogs.cisco.com/better_city_better_life_cisco_showcases_smartconnected_communities_at_world</guid>
		<description><![CDATA[Since my <a href="/news/comments/domainkeys_identified_mail_dkim_grows_significantly/" target="_blank">blog post</a> last June on usage of <a href="http://www.dkim.org/">DomainKeys Identified Mail</a> (DKIM), there have been quite a few requests for updated DKIM signing statistics.&#160; [...]]]></description>
		<wfw:commentRss>http://blogs.cisco.com/news/growth_in_dkim_signing_continues/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
	</channel>
</rss>
