SharePoint portal service sites are fast becoming a common web-based collaboration tool. Along with publishing SharePoint sites come the same types of risks that are faced by web servers. It is therefore recommended to secure SharePoint Portal Sites under the protective umbrella of ISA.
Understanding SharePoint 2003
SharePoint Portal Server 2003, illustrated in Figure 14.12, is an advanced document management and collaboration portal utility released by Microsoft. It allows for custom lists, document libraries, discussion groups, and other collaboration features right out of the box, and it is fast becoming a critical port of many organization's environments.
Figure 14.12. Viewing SharePoint Portal Server 2003.
Publishing a SharePoint Site with ISA Server Publishing Rules
Publishing a SharePoint portal site involves exactly the same procedure that was outlined in the previous section, with a few small exceptions as follows:
Using Link Translation to Hide Internal SharePoint Links
One of the most useful features of ISA Server for SharePoint Sites is its capability to perform link translation of the site. Link translation, as previously defined, effectively looks through all the web traffic and replaces specific hypertext links with administrator-defined ones. Where this comes in handy is with SharePoint, which too often exposes a bug in the code that allows internal SharePoint Portal identities to be exposed to the Internet. For example, if SERVER15 is a SharePoint Server, but the SharePoint Site is http://portal.companyabc.com, the pages in SharePoint sometimes appear with links to //server15, which cannot be resolved from the Internet.
To enable link translation on a SharePoint site, do the following:
In addition to replacing text links with link translation, in the Link Translation tab it is also possible to restrict by content type, by clicking on the Content Types button. The following types of content are available for restriction: