<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The C-I-A Triad – weighed and found wanting</title>
	<link>http://securityrenaissance.com/2007/04/11/the-c-i-a-triad-%e2%80%93-weighed-and-found-wanting/</link>
	<description>Promoting the art and mindset of information security</description>
	<pubDate>Sat, 22 Nov 2008 16:03:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Faith Young</title>
		<link>http://securityrenaissance.com/2007/04/11/the-c-i-a-triad-%e2%80%93-weighed-and-found-wanting/#comment-1491</link>
		<pubDate>Thu, 10 May 2007 08:41:12 +0000</pubDate>
		<guid>http://securityrenaissance.com/2007/04/11/the-c-i-a-triad-%e2%80%93-weighed-and-found-wanting/#comment-1491</guid>
					<description>Thanks.  That was a great explanation.  I agree with you, but there must be a balance in relation to the importance of the assets that are being protected.  Non-repudiation is the inability to deny the integrity and authenticity of a document.  On one end of the balance, encryption and data signatures are needed for important transactions.  On the other end of the balance, IRC chat logs might possibly be considered anonymous.

During my studies, my case study organization is a public Web site that believes in sharing information.  Information is their main asset and it was a challenge communicating to them that classifying their assets is an extremely important step in achieving a balance in Information Assurance.  The result was that they do have processes and information that is not public.   They have to protect that information.</description>
		<content:encoded><![CDATA[<p>Thanks.  That was a great explanation.  I agree with you, but there must be a balance in relation to the importance of the assets that are being protected.  Non-repudiation is the inability to deny the integrity and authenticity of a document.  On one end of the balance, encryption and data signatures are needed for important transactions.  On the other end of the balance, IRC chat logs might possibly be considered anonymous.</p>
<p>During my studies, my case study organization is a public Web site that believes in sharing information.  Information is their main asset and it was a challenge communicating to them that classifying their assets is an extremely important step in achieving a balance in Information Assurance.  The result was that they do have processes and information that is not public.   They have to protect that information.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: www.andrewhay.ca &#187; Suggested Blog Reading - Thursday, April 12th, 2007</title>
		<link>http://securityrenaissance.com/2007/04/11/the-c-i-a-triad-%e2%80%93-weighed-and-found-wanting/#comment-810</link>
		<pubDate>Thu, 12 Apr 2007 19:45:19 +0000</pubDate>
		<guid>http://securityrenaissance.com/2007/04/11/the-c-i-a-triad-%e2%80%93-weighed-and-found-wanting/#comment-810</guid>
					<description>[...] The C-I-A Triad – weighed and found wanting Believe it or not, the field of Information Security has changed! Foundational concepts, such as the traditional C-I-A triad (Confidentiality, Integrity, and Availability) are being challenged and supplanted by a more inclusive model known as the Parkerian Hexad       See Andrew Hay and Daniel Cid's tutorial on Enterprise Log Analysis with Q1 Labs QRadar and OSSEC at the iTrust and PST Conferences on Privacy, Trust Management and Security in Moncton, New Brunswick, Canada. Email andrewsmhay [at] gmail.com for more information. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] The C-I-A Triad – weighed and found wanting Believe it or not, the field of Information Security has changed! Foundational concepts, such as the traditional C-I-A triad (Confidentiality, Integrity, and Availability) are being challenged and supplanted by a more inclusive model known as the Parkerian Hexad       See Andrew Hay and Daniel Cid&#8217;s tutorial on Enterprise Log Analysis with Q1 Labs QRadar and OSSEC at the iTrust and PST Conferences on Privacy, Trust Management and Security in Moncton, New Brunswick, Canada. Email andrewsmhay [at] gmail.com for more information. [&#8230;]
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Rob Lewis</title>
		<link>http://securityrenaissance.com/2007/04/11/the-c-i-a-triad-%e2%80%93-weighed-and-found-wanting/#comment-808</link>
		<pubDate>Thu, 12 Apr 2007 15:38:32 +0000</pubDate>
		<guid>http://securityrenaissance.com/2007/04/11/the-c-i-a-triad-%e2%80%93-weighed-and-found-wanting/#comment-808</guid>
					<description>This adds value to the discussion, except that part of the diagram is cut off on the right hand side. What are the descriptors for integrity and authenticity please?</description>
		<content:encoded><![CDATA[<p>This adds value to the discussion, except that part of the diagram is cut off on the right hand side. What are the descriptors for integrity and authenticity please?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: LonerVamp</title>
		<link>http://securityrenaissance.com/2007/04/11/the-c-i-a-triad-%e2%80%93-weighed-and-found-wanting/#comment-807</link>
		<pubDate>Thu, 12 Apr 2007 15:30:50 +0000</pubDate>
		<guid>http://securityrenaissance.com/2007/04/11/the-c-i-a-triad-%e2%80%93-weighed-and-found-wanting/#comment-807</guid>
					<description>I may have to pick up that book at the bookstore and flip through to this section, as I'm not sure I buy in, yet.

Seems to me that Integrity covers Authenticity and some of Utility just fine. Availability covers the rest of Utility. And Confidentiality covers Possession...</description>
		<content:encoded><![CDATA[<p>I may have to pick up that book at the bookstore and flip through to this section, as I&#8217;m not sure I buy in, yet.</p>
<p>Seems to me that Integrity covers Authenticity and some of Utility just fine. Availability covers the rest of Utility. And Confidentiality covers Possession&#8230;
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
