<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: What You Want for Wednesday: More Granular Access Control on Remote Vendor Access</title>
	<atom:link href="http://blogs.gartner.com/john_pescatore/2008/10/29/what-you-want-for-wednesday-more-granular-access-control-on-remote-vendor-access/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gartner.com/john_pescatore/2008/10/29/what-you-want-for-wednesday-more-granular-access-control-on-remote-vendor-access/</link>
	<description>A member of the Gartner Blog Network</description>
	<lastBuildDate>Thu, 19 Nov 2009 18:00:12 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob Lewis</title>
		<link>http://blogs.gartner.com/john_pescatore/2008/10/29/what-you-want-for-wednesday-more-granular-access-control-on-remote-vendor-access/comment-page-1/#comment-87</link>
		<dc:creator>Rob Lewis</dc:creator>
		<pubDate>Thu, 30 Oct 2008 13:42:09 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gartner.com/john_pescatore/?p=168#comment-87</guid>
		<description>John,

We solve this problem very easily. Our technology is a security sub-system that turns networks into distributed MLS enclaves in an otherwise discretionary environment. Fine grained access and audit control at the data file level, on a per user basis, is enforced at the kernel level. 

With this technology, all one has to do is create a specific user group that includes only the vendor partner(s) and  your enterprise liaison with a definitive policy about what your staff person can bring into that user group. The policies are based on users, roles and groups, or in the language of the business rules, so they are very intuitive. Rather than ACLs, a couple of rules are usually all that are required. A vendor partner can also be removed, or access privileges changed, in minutes.

Even if the vendor partner&#039;s own systems get owned, no one can ever tunnel past that user group from outside, and if the enterprise provides a laptop with our brand of MAC, MLS security on it to access their information, that laptop will not be owned either.

Sorry if I appear to be crossing  the line into &quot;selling&quot; in any way. I am only trying to respond to your post topic.</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>We solve this problem very easily. Our technology is a security sub-system that turns networks into distributed MLS enclaves in an otherwise discretionary environment. Fine grained access and audit control at the data file level, on a per user basis, is enforced at the kernel level. </p>
<p>With this technology, all one has to do is create a specific user group that includes only the vendor partner(s) and  your enterprise liaison with a definitive policy about what your staff person can bring into that user group. The policies are based on users, roles and groups, or in the language of the business rules, so they are very intuitive. Rather than ACLs, a couple of rules are usually all that are required. A vendor partner can also be removed, or access privileges changed, in minutes.</p>
<p>Even if the vendor partner&#8217;s own systems get owned, no one can ever tunnel past that user group from outside, and if the enterprise provides a laptop with our brand of MAC, MLS security on it to access their information, that laptop will not be owned either.</p>
<p>Sorry if I appear to be crossing  the line into &#8220;selling&#8221; in any way. I am only trying to respond to your post topic.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
