SQL6-D0-001500 - In the event of a system failure, hardware loss or disk failure, SQL Server must be able to restore necessary databases with least disruption to mission processes.


Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. Failure to a known secure state helps prevent a loss of confidentiality, integrity, or availability in the event of a failure of the information system or a component of the system. In the event of a system failure, SQL Server must be able to bring the database back to a consistent state.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.


Modify the system security plan, to include whether the database is static, the correct recovery model to be used, the backup schedule, and the plan for testing database restoration.

In SQL Server Management Studio, Object Explorer, right-click on the name of the database; select Properties. Select the Options page. Set the Recovery Model field, near the top of the page, to the correct value.

In Object Explorer, expand >> SQL Server Agent >> Jobs. Create, modify, and delete jobs to implement the backup schedule. (Alternatively, this may done using T-SQL code or Third-party Backup software.)

Correct any issues that have been causing backups to fail.

Test the restoration of the database at least once a year; correct any issues that cause it to fail. Maintain a record of these tests.

See Also


Item Details

References: CAT|II, CCI|CCI-001665, Rule-ID|SV-213910r879641_rule, STIG-ID|SQL6-D0-001500, STIG-Legacy|SV-93789, STIG-Legacy|V-79083, Vuln-ID|V-213910

Plugin: MS_SQLDB

Control ID: b52a2c3a7ae834442c37ebb01606cb9537234089f66d9ffb581429e0771c92a7