Difference between revisions of "IIS Security Practices"

From MgmtWiki
Jump to: navigation, search
(Created page with "==Full Title or Meme== Security practices to follow on IIS for good security. ==Context== * Assuming IIS (or any web platform) is running as a front end web server, it should...")
 
Line 5: Line 5:
 
* Assuming IIS (or any web platform) is running as a front end web server, it should never be trusted with high value assets and assumed to be hackable. Still there are ways to make the hacks much less frequent.
 
* Assuming IIS (or any web platform) is running as a front end web server, it should never be trusted with high value assets and assumed to be hackable. Still there are ways to make the hacks much less frequent.
  
 +
==Solutions==
 +
===Application Pool Identities===
 +
Starting with Server 2008 R2 IIS services will not longer run as network services but with virtual [https://docs.microsoft.com/en-us/iis/manage/configuring-security/application-pool-identities Application Pool Identities] that have no entry local or domain accounts, and hence no "Current User" cert store or HKCU registry entries.
 
==References==
 
==References==
  
<Category:Best Practice>
+
[[Category:Best Practice]]
<Category:Web Site>
+
[[Category:Web Site]]
<Category:Security>
+
[[Category:Security]]

Revision as of 22:04, 21 July 2020

Full Title or Meme

Security practices to follow on IIS for good security.

Context

  • Assuming IIS (or any web platform) is running as a front end web server, it should never be trusted with high value assets and assumed to be hackable. Still there are ways to make the hacks much less frequent.

Solutions

Application Pool Identities

Starting with Server 2008 R2 IIS services will not longer run as network services but with virtual Application Pool Identities that have no entry local or domain accounts, and hence no "Current User" cert store or HKCU registry entries.

References