<?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: Windows Without Admin Rights</title>
	<atom:link href="http://www.howinthetech.com/windows-without-admin-rights/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.howinthetech.com/windows-without-admin-rights/</link>
	<description>Daily Tech Tips and News</description>
	<lastBuildDate>Wed, 10 Mar 2010 16:07:43 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adam</title>
		<link>http://www.howinthetech.com/windows-without-admin-rights/#comment-22</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Fri, 23 Jun 2006 15:11:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.evileyez.org/windows-without-admin-rights/#comment-22</guid>
		<description>You&#039;re spot on Raemann, and i&#039;ve never really thought of it that way before - I&#039;m referring to the entitlement or ownership that users in the workplace feel towards their PC.

Generally, a mindset change can happen if a psuedo cause &amp; effect situation occurs. User does not comply with procedure or standards put forth by the company, resulting in said problems with the PC - leaving the user without the tool to do his job. The catch22 is, as the person who must support my users, its in my job&#039;s best interest to get them back up and running ASAP - so that they can continue doing their job and in turn, bring money into the company. However, should the users start seeing their tools disappear for longer stints of time - directly by their own mis-doing - then perhaps the attitudes would start to change? It&#039;s a pretty cynical approach (the stalling of problem solving), but you are 100% correct that the change has to occur in carbon.</description>
		<content:encoded><![CDATA[<p>You&#8217;re spot on Raemann, and i&#8217;ve never really thought of it that way before &#8211; I&#8217;m referring to the entitlement or ownership that users in the workplace feel towards their PC.</p>
<p>Generally, a mindset change can happen if a psuedo cause &#038; effect situation occurs. User does not comply with procedure or standards put forth by the company, resulting in said problems with the PC &#8211; leaving the user without the tool to do his job. The catch22 is, as the person who must support my users, its in my job&#8217;s best interest to get them back up and running ASAP &#8211; so that they can continue doing their job and in turn, bring money into the company. However, should the users start seeing their tools disappear for longer stints of time &#8211; directly by their own mis-doing &#8211; then perhaps the attitudes would start to change? It&#8217;s a pretty cynical approach (the stalling of problem solving), but you are 100% correct that the change has to occur in carbon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raemann</title>
		<link>http://www.howinthetech.com/windows-without-admin-rights/#comment-21</link>
		<dc:creator>Raemann</dc:creator>
		<pubDate>Fri, 23 Jun 2006 13:44:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.evileyez.org/windows-without-admin-rights/#comment-21</guid>
		<description>More rant :

  The landscape is changing. We in security and IT oversight have long noted that &quot;home PCs&quot; in the workplace were a security risk. Primarily because of the familiarity to practices which their users had grown accustomed. More specifically the notion that since this is the same OS, look and feel of what people have at home they are not &quot;on their toes&quot; and awake when it comes to business practices. What we found to be a common tendency involved users overlooking physical security practices on their PCs.    
    Among the myriad of additional weakness is the precursor to all failings in the notion that &quot;This is MY computer&quot;. Until we convince users that they are using a tool - much akin to a mechanic going to a tool crib for a wrench - we deal with a mentality that refuses to believe that they must conform to standards, practices or principles involving common use. I fear that the security fix may involve a great deal more work in carbon than silicon.</description>
		<content:encoded><![CDATA[<p>More rant :</p>
<p>  The landscape is changing. We in security and IT oversight have long noted that &#8220;home PCs&#8221; in the workplace were a security risk. Primarily because of the familiarity to practices which their users had grown accustomed. More specifically the notion that since this is the same OS, look and feel of what people have at home they are not &#8220;on their toes&#8221; and awake when it comes to business practices. What we found to be a common tendency involved users overlooking physical security practices on their PCs.<br />
    Among the myriad of additional weakness is the precursor to all failings in the notion that &#8220;This is MY computer&#8221;. Until we convince users that they are using a tool &#8211; much akin to a mechanic going to a tool crib for a wrench &#8211; we deal with a mentality that refuses to believe that they must conform to standards, practices or principles involving common use. I fear that the security fix may involve a great deal more work in carbon than silicon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Raemann</title>
		<link>http://www.howinthetech.com/windows-without-admin-rights/#comment-20</link>
		<dc:creator>Raemann</dc:creator>
		<pubDate>Thu, 22 Jun 2006 21:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.evileyez.org/windows-without-admin-rights/#comment-20</guid>
		<description>I hope to not come off as a &quot;windows flag waver&quot;. Many of the problems can be centered around the familiarity to windows by common users, the tendency of users to own software that they have on home PCs and invariably install at work, and the number of windows PCs in the market compared to other computers make them a &quot;hack target&quot;. None of these are issues noticed in the Unix market. I will admit that there are grave issues with running the PC as a user rather than as an administrator, but the benefits outweigh the challenges in many situations and if they do not - DUMP the application for one that is written to work in a networked environment. 
  Until vendors realize a pinch in the pocket they seem unable to update/configure for non admin operation. We find that vendors we are calling as we add 3000 PCs to a MS Windows 2000 domain are saying, &quot;Well, I don&#039;t know where the registry hack to fix (you choose the problem) is but - if you find out LET US KNOW!&quot; then you hear nervous laughter in the background. We can change this attitude but, it won&#039;t be easy. I just hope that we can do so sooner than later.</description>
		<content:encoded><![CDATA[<p>I hope to not come off as a &#8220;windows flag waver&#8221;. Many of the problems can be centered around the familiarity to windows by common users, the tendency of users to own software that they have on home PCs and invariably install at work, and the number of windows PCs in the market compared to other computers make them a &#8220;hack target&#8221;. None of these are issues noticed in the Unix market. I will admit that there are grave issues with running the PC as a user rather than as an administrator, but the benefits outweigh the challenges in many situations and if they do not &#8211; DUMP the application for one that is written to work in a networked environment.<br />
  Until vendors realize a pinch in the pocket they seem unable to update/configure for non admin operation. We find that vendors we are calling as we add 3000 PCs to a MS Windows 2000 domain are saying, &#8220;Well, I don&#8217;t know where the registry hack to fix (you choose the problem) is but &#8211; if you find out LET US KNOW!&#8221; then you hear nervous laughter in the background. We can change this attitude but, it won&#8217;t be easy. I just hope that we can do so sooner than later.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kirk</title>
		<link>http://www.howinthetech.com/windows-without-admin-rights/#comment-15</link>
		<dc:creator>Kirk</dc:creator>
		<pubDate>Fri, 16 Jun 2006 19:56:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.evileyez.org/windows-without-admin-rights/#comment-15</guid>
		<description>Very interesting article and something I hear all the time from people who eventually purchase our product.  Bit9 provides the logical ability to allow Admin rights to all users, while still transparently creating a locked-down environment, including the ability to create different policies based on user or departmental level. For the enterprise that must be secure yet Open and Available, Parity makes perfect sense. 
How we would work under the situation you illustrated so perfectly above...
1. user needs new software has admin rights but 
   machine is locked down via Bit9 Parity
2. IT receives the request and centrally approves 
   new software via Parity console
3. IT notifies user software is approved
4. User is running new software in minutes with  
   no technicians dispatched. Just a streamlined 
   approach to IT responsiveness and a dramatic 
   increase in both IT and end user productivity

check us out at www.bit9.com</description>
		<content:encoded><![CDATA[<p>Very interesting article and something I hear all the time from people who eventually purchase our product.  Bit9 provides the logical ability to allow Admin rights to all users, while still transparently creating a locked-down environment, including the ability to create different policies based on user or departmental level. For the enterprise that must be secure yet Open and Available, Parity makes perfect sense.<br />
How we would work under the situation you illustrated so perfectly above&#8230;<br />
1. user needs new software has admin rights but<br />
   machine is locked down via Bit9 Parity<br />
2. IT receives the request and centrally approves<br />
   new software via Parity console<br />
3. IT notifies user software is approved<br />
4. User is running new software in minutes with<br />
   no technicians dispatched. Just a streamlined<br />
   approach to IT responsiveness and a dramatic<br />
   increase in both IT and end user productivity</p>
<p>check us out at <a href="http://www.bit9.com" rel="nofollow">http://www.bit9.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
