Best practices to Setup and Configure the SharePoint 2007 / 2010 Internet Web Application
I find some key points to setup the MOSS Internet Web Applications properly and safely in Web hosting applications environment.
1. When created the MOSS Web applications using "home" folder as the Web site folder. It contains MOSS default sub folders like "bin" and Web.config file.
2. Turn on anonymous access in entire site contents except the backend area such as "_layouts" pages using Windows authentication or Form authentication. Using IIS 7 URL rewrite rules to block the public access to "_layouts" page as mentioned in my last post "Using IIS 7 URL rewrite rules to block the public access to SharePoint "_layouts" pages".
3. Turn on anonymous access in IIS 7 site.
4. Remove any custom (non-system) users' access in local Web site folders.
5. Created file folders "styles" and "controls" outside Web site "home" folder and also create virtual folders "styles" and "controls" which related to these folders. They are used for custom style, images and control files. Give the Application Pool account to access to these virtual folders but NOT the "home" folder.
6. Create and use a SQL server alternative name ("Alias" ) for the Content Database SQL server.
7. Using Imperva firework to prevent the illegal Internet access if it's possible.
1. When created the MOSS Web applications using "home" folder as the Web site folder. It contains MOSS default sub folders like "bin" and Web.config file.
2. Turn on anonymous access in entire site contents except the backend area such as "_layouts" pages using Windows authentication or Form authentication. Using IIS 7 URL rewrite rules to block the public access to "_layouts" page as mentioned in my last post "Using IIS 7 URL rewrite rules to block the public access to SharePoint "_layouts" pages".
3. Turn on anonymous access in IIS 7 site.
4. Remove any custom (non-system) users' access in local Web site folders.
5. Created file folders "styles" and "controls" outside Web site "home" folder and also create virtual folders "styles" and "controls" which related to these folders. They are used for custom style, images and control files. Give the Application Pool account to access to these virtual folders but NOT the "home" folder.
6. Create and use a SQL server alternative name ("Alias" ) for the Content Database SQL server.
7. Using Imperva firework to prevent the illegal Internet access if it's possible.
Comments
Post a Comment