 




<?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>Enterprise IT Watch Blog &#187; Wikipedia</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/IT-watch-blog/tag/wikipedia/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/IT-watch-blog</link>
	<description>What's new and what matters in IT news, opinion and analysis.</description>
	<lastBuildDate>Wed, 15 May 2013 14:37:26 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Can your IT security take a page from Wikipedia?</title>
		<link>http://itknowledgeexchange.techtarget.com/IT-watch-blog/can-your-it-security-take-a-page-from-wikipedia/</link>
		<comments>http://itknowledgeexchange.techtarget.com/IT-watch-blog/can-your-it-security-take-a-page-from-wikipedia/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 21:11:55 +0000</pubDate>
		<dc:creator>Michael Morisy</dc:creator>
				<category><![CDATA[Bruce Schneier]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Wikipedia]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/IT-watch-blog/?p=241</guid>
		<description><![CDATA[Security guru Bruce Schneier recently noted some Columbia University research on &#8220;Laissez-Faire File Sharing,&#8221; which advocates allowing users to set their own sharing permissions, with a focus on access auditing rather than access control (administrator policies don&#8217;t stop users from receiving or sharing a file, but all the viewers and editors of that file are [...]]]></description>
				<content:encoded><![CDATA[<p><a href="http://en.wikipedia.org/wiki/Wikipedia:Barnstars"><img class="size-medium wp-image-242 alignright" src="http://cdn.ttgtmedia.com/ITKE/uploads/blogs.dir/141/files/2009/11/wikipedia_good_security.png" alt="" width="115" height="115" /></a>Security guru Bruce Schneier recently noted some <a href="http://www.schneier.com/blog/archives/2009/11/laissez-faire_a.html">Columbia University research on &#8220;</a><a href="http://www.schneier.com/blog/archives/2009/11/laissez-faire_a.html">Laissez-Faire File Sharing,&#8221;</a> which advocates allowing users to set their own sharing permissions, with a focus on access auditing rather than access control (administrator policies don&#8217;t <em>stop </em>users from receiving or sharing a file, but all the viewers and editors of that file are then logged for later review and flagging).</p>
<p><a href="http://www.schneier.com/blog/archives/2009/11/laissez-faire_a.html" target="_blank">Schneier simplifies it</a> as a Wikipedian ideal (&#8220;Everybody has access to everything, but there are audit mechanisms in place to prevent abuse&#8221;), but that shortchanges the idea. Not all users can access files, for example: They must be granted access by a current user. The paper&#8217;s authors argue that this is already happening in an underground IT economy through e-mail attachments, USB thumbdrives and other workarounds, and that by working with the system, rather than against it, the new paradigm has the potential the &#8220;potential to increase both productivity and security.&#8221;</p>
<p>The paper outlines 5 cornerstones of <em>Laissez-Faire File Sharing</em>:<span id="more-241"></span></p>
<blockquote><p><strong> Ownership</strong><br />
The owner of a document, initially the individual who creates it or first introduces it into a sharing system, must not be required to sacrifice rights in order to add the file into the system.<br />
<strong> Freedom of delegation</strong><br />
The owners of a document may grant (delegate) or deny any or all rights – including the right\to further delegation or even full ownership – to whomever they so choose, regardless of organizational or administrative boundaries.<br />
<strong> Transparency</strong><br />
The owners of (and ideally all contributors to) a document must be able to quickly and easily find and comprehend the rights associated with it, including such meta-rights as delegation. All changes to the document or its rights must be attributable to the individual who made the change.<br />
<strong> Dependability</strong><br />
Users must be able to rely on the sharing system to both store and transmit their information both reliably and securely, enforcing their chosen sharing (access control) policies.<br />
<strong>Minimal friction</strong><br />
A sharing system should be free of barriers that [/asp]unnecessarily or excessively inhibit sharing.</p></blockquote>
<p>There&#8217;s some great discussion on Schneier&#8217;s blog in the comments, ranging from the political ramifications (&#8220;The reason it&#8217;s not used more often <a href="http://www.schneier.com/blog/archives/2009/11/laissez-faire_a.html#c398472">isn&#8217;t rational, but political</a> &#8212; folks want power, and auditing methods diffuse power.&#8221;) to concerns that auditing turns <a href="http://www.schneier.com/blog/archives/2009/11/laissez-faire_a.html#c398472">security into a cost center</a> doomed for failure.</p>
<p>What do you think? Can users be trusted to set their own permissions, or are these academics too far up the Ivory Tower? I&#8217;d love to hear your thoughts, whether <a href="#comments">in the comments</a>, at <a href="mailto:Michael@ITKnowledgeExchange.com">Michael@ITKnowledgeExchange.com</a>, or on Twitter at <a href="twitter.com/morisy">@Morisy</a> and <a href="http://twitter.com/ITKE">@ITKE</a>.</p>
<p class="regularBox_titleBar">More on security:</p>
<ul>
<li><a href="http://www.cs.columbia.edu/~smb/papers/nspw-use.pdf">&#8220;Laissez-faire file sharing&#8221;:</a> The original Columbia University paper in PDF</li>
<li><a href="http://itknowledgeexchange.techtarget.com/IT-watch-blog/everyone-hates-your-insecure-password-rules/">Everyone hates your insecure password rules</a></li>
<li><a href="http://itknowledgeexchange.techtarget.com/IT-watch-blog/time-warners-smc8014-security-hole-could-make-for-a-spooky-halloween/">Time Warner’s SMC8014 security hole could make for a spooky Halloween</a></li>
<li><a href="http://itknowledgeexchange.techtarget.com/IT-watch-blog/new-ssl-security-hole-allows-man-in-the-middle-attacks/">New SSL security hole allows man-in-the-middle attacks</a></li>
</ul>
<p class="regularBox_titleBar">
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/IT-watch-blog/can-your-it-security-take-a-page-from-wikipedia/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
