SharePoint must maintain and support the use of security attributes with stored information.

From MS SharePoint 2013 Security Technical Implementation Guide

Associated with: CCI-000366

SV-74365r1_rule SharePoint must maintain and support the use of security attributes with stored information.

Vulnerability discussion

Security attributes are abstractions representing the basic properties or characteristics of an entity (e.g., subjects and objects) with respect to safeguarding information.These attributes are typically associated with internal data structures (e.g., records, buffers, files) within the information system and are used to enable the implementation of access control and flow control policies, reflect special dissemination, handling or distribution instructions, or support other aspects of the information security policy.One example includes marking data as classified or FOUO. These security attributes may be assigned manually or during data processing, but, either way, it is imperative these assignments are maintained while the data is in storage. If the security attributes are lost when the data is stored, there is the risk of a data compromise.

Check content

Review the SharePoint server to ensure the use of security attributes with stored information is maintained. Click Site Settings. Under the Web Designer Galleries menu, click Site Content Types. Define a set of Content Types that can hold "security attributes", e.g., FOUO, etc. For each required Content Type, under "Change Content Type Column" ensure "Required (Must contain information) is selected. Otherwise, this is a finding.

Fix text

Configure the SharePoint server to maintain and support the use of security attributes with stored information. From the Site Collection Settings menu: Add a column to Content Types that can hold "security attributes", e.g., FOUO, etc., and "prompt the user to enter as metadata or properties to collect when documents of this content type are added to SharePoint."

Pro Tips

Lavender hyperlinks in small type off to the right (of CSS class id, if you view the page source) point to globally unique URIs for each document and item. Copy the link location and paste anywhere you need to talk unambiguously about these things.

You can obtain data about documents and items in other formats. Simply provide an HTTP header Accept: text/turtle or Accept: application/rdf+xml.