InformationWhen 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.
If the application were to allow any user to make changes to software libraries, then those changes might be implemented without undergoing the appropriate testing and approvals that are part of a robust change management process.
This requirement is contingent upon the language in which the application is programmed, as many application architectures in use today incorporate their software libraries into, and make them inseparable from, their compiled distributions, rendering them static and version dependant. However, this requirement does apply to applications with software libraries accessible and configurable, as in the case of interpreted languages.
Accordingly, only qualified and authorized individuals shall be allowed to obtain access to information system components for purposes of initiating changes, including upgrades and modifications.
DBA and other privileged administrative or application owner accounts are granted privileges that allow actions that can have a greater impact on SQL Server security and operation. It is especially important to grant access to privileged accounts to only those persons who are qualified and authorized to use them.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
SolutionFrom a Command Prompt, open lusrmgr.msc. Navigate to Users >> right click individual user >> Properties >> Member Of.
Configure SQL Server & OS settings and access controls, to restrict user access to objects and data that the user is authorized to view or interact with.
Develop, document, and implement procedures to restrict use of the DBMS software installation account.