SQL Server user-level information must be backed up based on a defined frequency.

From Microsoft SQL Server 2012 Database Instance Security Technical Implementation Guide

Associated with: CCI-000535

SV-53284r2_rule SQL Server user-level information must be backed up based on a defined frequency.

Vulnerability discussion

SQL Server backups are a critical step in maintaining data assurance and availability.User-level information is data generated by information system and/or application users. In order to assure availability of this data in the event of a system failure, DoD organizations are required to ensure user generated data is backed up at a defined frequency. This includes data stored on file systems, within SQL Server or within any other storage media.Applications performing backups must be capable of backing up user-level information per the DoD defined frequency.Databases that do not backup information regularly risk the loss of that information in the event of a system failure.

Check content

Windows Server Backup, or a 3rd Party Backup Tool, can be utilized to perform this function. Determine how SQL Server is being backed up. If there is no scheduled backup or if organizationally defined backup policy and procedures does not exist, this is finding. Check evidence of inclusion user-level information into current backup records, if the organizationally defined backup policy, procedures, and backup configurations is not including user-level information backups, this is a finding.

Fix text

Deploy a backup solution to perform backups as per organizationally defined Backup Policy.

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.