<?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: IIS Security</title>
	<atom:link href="http://www.msdigest.net/2009/04/iis-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.msdigest.net/2009/04/iis-security/</link>
	<description>Technical blog about Exchange, Lync &#38; Office 365 by Peter Schmidt [MVP and MCM: Exchange]</description>
	<lastBuildDate>Mon, 02 Jan 2012 07:55:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Peter Schmidt</title>
		<link>http://www.msdigest.net/2009/04/iis-security/comment-page-1/#comment-26918</link>
		<dc:creator>Peter Schmidt</dc:creator>
		<pubDate>Tue, 09 Jun 2009 20:35:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.iis-digest.com/index.php/2009/04/iis-security/#comment-26918</guid>
		<description>Cool, thanks for replying back with your solution.</description>
		<content:encoded><![CDATA[<p>Cool, thanks for replying back with your solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://www.msdigest.net/2009/04/iis-security/comment-page-1/#comment-26916</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Tue, 09 Jun 2009 08:43:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.iis-digest.com/index.php/2009/04/iis-security/#comment-26916</guid>
		<description>Hi, figured it out, posting for whoever ponders this question as well - it&#039;s very straightforward really, just got confused by the best practice we typically use for shares, where we leave the share permissions wide open, and handle security on the Security tab -- in this situation however, that&#039;s a bad idea: 
when a website uses Integrated Windows Security, these rules apply:

+ the access to the website is determined by the Security tab
+ if necessary, you can share the folder, and the access to the share should then be managed by configuring the Share Permissions (so only give the administrators of the website access to the share)</description>
		<content:encoded><![CDATA[<p>Hi, figured it out, posting for whoever ponders this question as well &#8211; it&#8217;s very straightforward really, just got confused by the best practice we typically use for shares, where we leave the share permissions wide open, and handle security on the Security tab &#8212; in this situation however, that&#8217;s a bad idea:<br />
when a website uses Integrated Windows Security, these rules apply:</p>
<p>+ the access to the website is determined by the Security tab<br />
+ if necessary, you can share the folder, and the access to the share should then be managed by configuring the Share Permissions (so only give the administrators of the website access to the share)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://www.msdigest.net/2009/04/iis-security/comment-page-1/#comment-26892</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Fri, 29 May 2009 15:14:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.iis-digest.com/index.php/2009/04/iis-security/#comment-26892</guid>
		<description>Hi, I have one question there doesn&#039;t seem to be much info on - I&#039;m hoping you can help.
We have an IIS website using Integrated Windows Authentication which has to be accessible to everyone in the company - all working fine, but we noticed that with the current settings (share permissions: everyone full access -- Security: authenticated users Read access), everybody can also access the windows file share, and thus open the .asp, .config, ... etc files which sometimes contain passwords! - How can we grant them access to the website, without also granting access to the actual file share?

Thanks in advance!
Fred</description>
		<content:encoded><![CDATA[<p>Hi, I have one question there doesn&#8217;t seem to be much info on &#8211; I&#8217;m hoping you can help.<br />
We have an IIS website using Integrated Windows Authentication which has to be accessible to everyone in the company &#8211; all working fine, but we noticed that with the current settings (share permissions: everyone full access &#8212; Security: authenticated users Read access), everybody can also access the windows file share, and thus open the .asp, .config, &#8230; etc files which sometimes contain passwords! &#8211; How can we grant them access to the website, without also granting access to the actual file share?</p>
<p>Thanks in advance!<br />
Fred</p>
]]></content:encoded>
	</item>
</channel>
</rss>

