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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

■ Permissible information to collect on employees when creating a contacts list.<br />

■ Permissible information to disclose on self in the My Site area.<br />

■ Expressions of personal views in My Site.<br />

■ Information about children of employees may not be collected.<br />

■ Requirement of disclaimer when collecting information.<br />

■ Existence of personnel records in SharePoint <strong>Products</strong> <strong>and</strong> <strong>Technologies</strong> prohibited<br />

without proper security.<br />

■ Disclosure of worker change of status notification.<br />

■ Marketing or promotion of employee-owned businesses prohibited on company<br />

systems.<br />

Data Classification Schemes<br />

Different firms have different levels of confidentiality, but it is certainly worth assigning<br />

a security level to every document in your organization so that workers know<br />

how to h<strong>and</strong>le the data. As the document is developed in SharePoint <strong>Products</strong> <strong>and</strong><br />

<strong>Technologies</strong>, the security level of the document can become a defining (<strong>and</strong> indexable)<br />

piece of metadata. Most classification schemes use one or more of the following<br />

document categories: public, confidential, secret, <strong>and</strong> private. Each organization<br />

will have its own scheme, <strong>and</strong> our point is not that you should copy what we have<br />

written here, but instead that you implement a classification scheme <strong>and</strong> then use<br />

that scheme as new information is developed. Because most content that is developed<br />

is automatically considered confidential, it might be important in your organization<br />

to spell that out to those content developers. Doing so will ensure that they<br />

do not disseminate confidential information.<br />

Items to consider when developing this policy include the following:<br />

■ Data classification scheme is required for all company data.<br />

■ Labeling requirements for all company data.<br />

■ Information is treated as confidential whenever the classification is unknown.<br />

■ Departments may create additional classifications if authorized.<br />

■ Content developers are responsible to assign data classification to all documents<br />

during development.<br />

■ Owner of content must meet classification requirements.<br />

■ Declassification of content must follow prescribed procedures.

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

Saved successfully!

Ooh no, something went wrong!