16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 24: Information Security Policies for SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> 667<br />

■ Required retention period for logs.<br />

■ Information to capture when a compromise is suspected.<br />

■ Logging required before a system can be placed in the production domain.<br />

■ Clock synchronization on all SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> servers<br />

with a master clock of all servers in production domain.<br />

■ Persons authorized to view logs.<br />

■ Logs must be reviewed on a regular basis by authorized personnel.<br />

Authorized Web Parts <strong>and</strong> Applications<br />

Because SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> is designed with a distributed<br />

administrative architecture, it is important to remember that authorized users will be<br />

able to install Web Parts on a site. It would be very easy for authorized users to<br />

download Web Parts that have been created on the Internet <strong>and</strong> then install those<br />

parts on their sites. Remember that site <strong>and</strong> portal administrators delegate the right<br />

to add Web Parts to a Web Parts page, <strong>and</strong> there are protections in place for the<br />

administrator to control how much a Web Part can do. Liberal delegation of this right<br />

might lead to compromised security in your SharePoint implementation. Unsuspecting<br />

users could download an infected or a compromised Web Part, install it, <strong>and</strong><br />

expose your critical information to hackers on the outside.<br />

Because of this potential vulnerability, you should seriously consider restricting<br />

which software can <strong>and</strong> cannot be installed in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong>.<br />

Points to consider when creating policies in this area include the following:<br />

■ Prohibition against downloading third-party software to your corporate systems.<br />

■ Requirement to scan downloaded Web Parts before use in a production system.<br />

■ Testing for viruses must be performed on a non-cabled, st<strong>and</strong>-alone server.<br />

■ Multiple virus screenings must be performed on all downloaded software from<br />

the Internet to corporate systems.<br />

■ Virus scanning software must be employed on all SharePoint <strong>Products</strong> <strong>and</strong><br />

<strong>Technologies</strong> systems.<br />

■ Requirement to run all third-party Web Parts in a test environment prior to<br />

deployment in a production environment.<br />

Change Control<br />

Because SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> will be hosting some of your most<br />

mission-critical <strong>and</strong> sensitive information, it is best to ensure that you have a strong<br />

change control program in place for your servers. By controlling who can make

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!