From MS SQL Server 2016 Instance Security Technical Implementation Guide
Part of SRG-APP-000133-DB-000199
Associated with: CCI-001499
When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components of the information system and/or application can potentially have significant effects on the overall security of the system.
Determine the directory in which SQL Server has been installed. Using SQL Server Management Studio's Object Explorer: Right-click [SQL Server Instance] >> Facets >> Record value for RootDirectory. Verify that this path does not exist on the same drive as the Operating System. Using Windows Explorer, navigate through all parts of this path verifying that no evidence exists of non-SQL Server or administrative files being stored in the same location. If any non-SQL Server or administrative files are being stored in this location, this is a finding.
Re-install SQL Server application components using dedicated directories that are separate from the operating system. Relocate or reinstall other application software that currently shares directories with SQL Server components. Separate from the operating system and/or temporary storage.
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
.
Powered by sagemincer