Reading Time: 24 minutes
What are the Database SRG DoD Stigs?
The Database Security Requirements Guide, or SRG, is published as a tool to help you improve the security of your information systems.
They were originally intended for use with the Department of Defense Information Systems, but actually contain some good practices that can be used by all organizations to help secure systems.
Before we start, let’s get some things clear
The requirements are derived from the NIST 800-53 and related documents. The information provided in these posts is based on the publicly available DISA FSO archive of STIG contact (which is public domain information). DISA FSO does not endorse, collaborate or have anything to do with these posts or site. Please do not contact them for support or questions about this site. If you use the information in any of these posts to make changes to your system, we are not responsible for the consequences (unless you use our services to help out).
There is a lot to cover
There are over 300 Findings that are reviewed to make sure your systems are compliant with the Database SRGs.
Of those there are 7 Category I, 306 Category II, and 16 Category III findings. The lower the category number, the higher the priority. Basically Category I means – FIX THIS NOW!
Through a series of blog posts we are going to touch on each of the findings, and make sure you understand if and how it pertains to SQL Server specifically.
Just so you know, a lot of the findings deal with processes outside of the SQL Server environment. In those cases we will do our best to provide basics of what can be done. Those findings that are directly related to SQL Server will be detailed with scripts to be used to determine if a violation has occured and customizable scripts to help take corrective actions.
Let’s get to it! – The List
Here is the list of the Finding IDs under the Database SRG. They are listed in Category level order from critical to low.
We are working constantly to get our interpretations onto each of the posts. If the post states Coming Soon! at the bottom we haven’t quite gotten to it, but we will!
If you come across a STIG that we haven’t commented on and would like us to get to it sooner, let us know!
We hope you find these useful in learning and understanding these requirements.
| Vulnerability ID | Severity | Title | |
|---|---|---|---|
| V-32244 | High | DBA OS accounts must be granted only those host system privileges necessary for the administration of the DBMS. | |
| V-32479 | High | The DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. | |
| V-32476 | High | The DBMS, when using PKI-based authentication, must enforce authorized access to the corresponding private key. | |
| V-32472 | High | DBMS default accounts must be assigned custom passwords. | |
| V-32568 | High | The DBMS must employ cryptographic mechanisms preventing the unauthorized disclosure of information during transmission unless the transmitted data is otherwise protected by alternative physical measures. | |
| V-32410 | High | Vendor supported software must be evaluated and patched against newly found vulnerabilities. | |
| V-32526 | High | The DBMS must recognize only system-generated session identifiers. | |
| V-32242 | Medium | The DBA role must not be assigned excessive or unauthorized privileges. | |
| V-32599 | Medium | The DBMS must notify appropriate individuals when accounts are terminated. | |
| V-32598 | Medium | The DBMS must notify appropriate individuals when account disabling actions are taken. | |
| V-32595 | Medium | The application uses cryptographic mechanisms to protect the integrity of audit tools. | |
| V-32594 | Medium | The application must either implement compensating security controls or the organization explicitly accepts the risk of not performing the verification as required. | |
| V-32597 | Medium | The DBMS must notify appropriate individuals when accounts are modified. | |
| V-32505 | Medium | Software and/or firmware used for collaborative computing devices must prohibit remote activation excluding the organization defined exceptions where remote activation is to be allowed. | |
| V-32591 | Medium | Applications providing notifications regarding suspicious events must include the capability to notify an organization defined list of response personnel who are identified by name and/or by role. | |
| V-32590 | Medium | Applications providing IDS and prevention capabilities must prevent non-privileged users from circumventing intrusion detection and prevention capabilities. | |
| V-32593 | Medium | The application must enforce organizational requirements to protect information obtained from intrusion monitoring tools from unauthorized access, modification, and deletion. | |
| V-32592 | Medium | The DBMS must support taking organization defined list of least disruptive actions to terminate suspicious events. | |
| V-32223 | Medium | Applications providing information flow control must track problems associated with the binding of security attributes to data. | |
| V-32222 | Medium | The application must bind security attributes to information to facilitate information flow policy enforcement. | |
| V-32221 | Medium | Applications must uniquely identify destination domains for information transfer. | |
| V-32220 | Medium | Applications must uniquely authenticate source domains for information transfer. | |
| V-32226 | Medium | Applications must prevent encrypted data from bypassing content-checking mechanisms. | |
| V-32225 | Medium | Applications must enforce information flow using dynamic control based on policy that allows or disallows information flow based on changing conditions or operational considerations. | |
| V-32224 | Medium | Applications must enforce information flow control using protected processing domains (e.g., domain type-enforcement) as a basis for flow control decisions | |
| V-32229 | Medium | Applications must use security policy filters as a basis for making information flow control decisions. | |
| V-32228 | Medium | Applications must enforce information flow control on metadata. | |
| V-32519 | Medium | The application must perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources when requested by client systems. | |
| V-32179 | Medium | The DBMS must display security labels in human-readable form on each object output from the system to system output devices. | |
| V-32454 | Medium | Applications managing devices must authenticate devices before establishing remote network connections using bidirectional authentication between devices that are cryptographically based. | |
| V-32455 | Medium | Applications managing network connections for devices must authenticate devices before establishing wireless network connections by using bidirectional authentication that is cryptographically based. | |
| V-32359 | Medium | The application must provide the capability to compile audit records from multiple components within the system into a system-wide (logical or physical) audit trail that is time-correlated to within organization defined level of tolerance. | |
| V-32450 | Medium | The DBMS must use organization defined replay-resistant authentication mechanisms for network access to privileged accounts. | |
| V-32451 | Medium | The DBMS must use organization defined replay-resistant authentication mechanisms for network access to non-privileged accounts. | |
| V-32452 | Medium | Applications required to identify devices must uniquely identify and authenticate an organization defined list of specific and/or types of devices before establishing a connection. | |
| V-32353 | Medium | The application must validate the binding of the reviewers identity to the information at the transfer/release point prior to release/transfer from one security domain to another security domain. | |
| V-32380 | Medium | The application must reject or delay, as defined by the organization, network traffic generated above configurable traffic volume thresholds. | |
| V-32351 | Medium | The DBMS must maintain reviewer/releaser identity and credentials within the established chain of custody for all information reviewed or released. | |
| V-32245 | Medium | Use of the DBMS software installation account must be restricted to DBMS software installation. | |
| V-32458 | Medium | Web services applications establishing identities at run-time for previously unknown entities must dynamically manage identifiers, attributes, and associated access authorizations. | |
| V-32356 | Medium | Databases utilizing Discretionary Access Control (DAC) must enforce a policy that limits propagation of access rights. | |
| V-32381 | Medium | The DBMS must shutdown immediately in the event of an audit failure, unless an alternative audit capability exists. | |
| V-32524 | Medium | The DBMS must provide a logout functionality to allow the user to manually terminate the session. | |
| V-32588 | Medium | Applications providing malware and/or firewall protection must monitor inbound and outbound communications for unauthorized activities or conditions. | |
| V-32589 | Medium | Applications that detect and alarm on security events such as Intrusion Detection, Firewalls, Anti-Virus, or Malware must provide near real-time alert notification. | |
| V-32460 | Medium | The DBMS must support organizational requirements to enforce minimum password length. | |
| V-32582 | Medium | Applications scanning for malicious code must support organizational requirements to configure malicious code protection mechanisms to perform periodic scans of the information system on an organization defined frequency. | |
| V-32583 | Medium | Applications providing malicious code protection must support organizational requirements to configure malicious code protection mechanisms to perform real-time scans of files from external sources as the files are downloaded, opened, or executed in accordance with organizational security policy. | |
| V-32581 | Medium | Applications providing malicious code protection must support organizational requirements to update malicious code protection mechanisms (including signature definitions) whenever new releases are available in accordance with organizational configuration. | |
| V-32586 | Medium | Intrusion detection software must be able to interconnect using standard protocols to create a system wide intrusion detection system. | |
| V-32587 | Medium | For those instances where the organization requires encrypted traffic to be visible to information system monitoring tools, the application transmitting the encrypted traffic must make provisions to allow that traffic to be visible to specific system monitoring tools. | |
| V-32584 | Medium | Applications providing malicious code protection must support organizational requirements to be configured to perform organization defined action(s) in response to malicious code detection. | |
| V-32585 | Medium | Applications providing malicious code protection must support organizational requirements to address the receipt of false positives during malicious code detection, eradication efforts, and the resulting potential impact on the availability of the information system. | |
| V-32230 | Medium | Applications providing information flow control must uniquely authenticate destination domains when transferring information. | |
| V-32231 | Medium | In support of information flow requirements, applications must track problems associated with information transfer. | |
| V-32232 | Medium | Administrative privileges must be assigned to database accounts via database roles. | |
| V-32501 | Medium | The DBMS must employ NSA-approved cryptography to protect classified information. | |
| V-32234 | Medium | DBMS processes or services must run under custom, dedicated OS accounts. | |
| V-32235 | Medium | The DBMS must restrict grants to sensitive information to authorized user roles. | |
| V-32236 | Medium | A single database connection configuration file must not be used to configure all database clients. | |
| V-32237 | Medium | The DBMS must be protected from unauthorized access by developers. | |
| V-32238 | Medium | The DBMS must be protected from unauthorized access by developers on shared production/development host systems. | |
| V-32239 | Medium | The DBMS must restrict access to system tables and other configuration information or metadata to DBAs or other authorized users. | |
| V-32508 | Medium | Applications must support organizational requirements to issue public key certificates under an appropriate certificate policy or obtain public key certificates under an appropriate certificate policy from an approved service provider. | |
| V-32509 | Medium | Applications designed to address malware issues and/or enforce policy pertaining to organizational use of mobile code must implement detection and inspection mechanisms to identify unauthorized mobile code. | |
| V-32461 | Medium | The DBMS must support organizational requirements to enforce minimum password length. | |
| V-32349 | Medium | The DBMS must validate the binding of the information to the identity of the information producer. | |
| V-32463 | Medium | The DBMS must support organizational requirements to enforce password complexity by the number of upper case characters used. | |
| V-32462 | Medium | The DBMS must support organizational requirements to prohibit password reuse for the organization defined number of generations. | |
| V-32465 | Medium | The DBMS must support organizational requirements to enforce password complexity by the number of numeric characters used. | |
| V-32464 | Medium | The DBMS must support organizational requirements to enforce password complexity by the number of lower case characters used. | |
| V-32467 | Medium | The DBMS must support organizational requirements to enforce the number of characters that get changed when passwords are changed. | |
| V-32466 | Medium | The DBMS must support organizational requirements to enforce password complexity by the number of special characters used. | |
| V-32469 | Medium | The DBMS must support organizational requirements to enforce password encryption for transmission. | |
| V-32468 | Medium | The DBMS must support organizational requirements to enforce password encryption for storage. | |
| V-32346 | Medium | The DBMS must notify users of organization defined security related changes to the users account occurring during the organization defined time period. | |
| V-32516 | Medium | The application must provide additional data origin and integrity artifacts along with the authoritative data the system returns in response to name/address resolution queries. | |
| V-32511 | Medium | Applications utilizing mobile code must meet policy requirements regarding the acquisition, development, and/or use of mobile code. | |
| V-32510 | Medium | Applications designed to address malware issues and/or enforce policy pertaining to organizational use of mobile code must take corrective actions, when unauthorized mobile code is identified. | |
| V-32161 | Medium | Applications must ensure that users can directly initiate session lock mechanisms which prevent further access to the system. | |
| V-32483 | Medium | Applications that are designed and intended to address incident response scenarios must provide a configurable capability to automatically disable an information system if any of the organization defined security violations are detected. | |
| V-32513 | Medium | Applications designed to enforce policy pertaining to the use of mobile code must prevent the automatic execution of mobile code in organization defined software applications and require organization defined actions prior to executing the code. | |
| V-32389 | Medium | The DBMS must provide the capability to automatically process audit records for events of interest based upon selectable event criteria. | |
| V-32449 | Medium | The DBMS, if using multifactor authentication when accessing non-privileged accounts via the network, must provide one of the factors by a device that is separate from the information system gaining access. | |
| V-32512 | Medium | Applications designed to enforce policy pertaining to organizational use of mobile code must prevent the download and execution of prohibited mobile code. | |
| V-32424 | Medium | Unused database components, DBMS software, and database objects must be removed. | |
| V-32375 | Medium | The DBMS must include organization defined additional, more detailed information in the audit records for audit events identified by type, location, or subject. | |
| V-32374 | Medium | The DBMS must produce audit records containing sufficient information to establish the identity of any user/subject or process associated with the event. | |
| V-32377 | Medium | The DBMS itself, or the logging or alerting mechanism the application utilizes, must provide a warning when allocated audit record storage volume reaches an organization defined percentage of maximum audit record storage capacity. | |
| V-32376 | Medium | The DBMS must provide the ability to write specified audit record content to a centralized audit log repository. | |
| V-32209 | Medium | Applications providing information flow control must enforce approved authorizations for controlling the flow of information between interconnected systems in accordance with applicable policy. | |
| V-32208 | Medium | Applications providing information flow control must enforce approved authorizations for controlling the flow of information within the system in accordance with applicable policy. | |
| V-32373 | Medium | The DBMS must produce audit records containing sufficient information to establish the outcome (success or failure) of the events. | |
| V-32205 | Medium | The DBMS must enforce non-discretionary access control policies over users and resources where the policy rule set for each policy specifies access control information (i.e., position, nationality, age, project, time of day). | |
| V-32204 | Medium | The DBMS must enforce dual authorization, based on organizational policies and procedures for organization defined privileged commands. | |
| V-32207 | Medium | The DBMS must prevent access to organization defined security-relevant information except during secure, non-operable system states. | |
| V-32206 | Medium | The DBMS must enforce Discretionary Access Control (DAC) policy allowing users to specify and control sharing by named individuals, groups of individuals, or by both, limiting propagation of access rights and includes or excludes access to the granularity of a single user. | |
| V-32201 | Medium | Service Oriented Architecture (SOA) based applications must dynamically manage user privileges and associated access authorizations. | |
| V-32200 | Medium | The DBMS must support the organizational requirements for automatically monitoring, auditing, and alerting on atypical usage of accounts. | |
| V-32203 | Medium | The DBMS must enforce approved authorizations for logical access to the system in accordance with applicable policy. | |
| V-32202 | Medium | The application must employ automated mechanisms enabling authorized users to make information sharing decisions based on access authorizations of sharing partners and access restrictions on information to be shared. | |
| V-32577 | Medium | The application must prevent non-privileged users from circumventing malicious code protection capabilities. | |
| V-32576 | Medium | The application must automatically update malicious code protection mechanisms, including signature definitions. Examples include anti-virus signatures and malware data files employed to identify and/or block malicious software from executing. | |
| V-32162 | Medium | The application must have the ability to retain a session lock remaining in effect until the user re-authenticates using established identification and authentication procedures. | |
| V-32574 | Medium | Applications serving to determine the state of information system components with regard to flaw remediation (patching) must use automated mechanisms to make that determination. The automation schedule must be determined on an organization defined basis. | |
| V-32573 | Medium | Applications providing patch management capabilities must support the organizational requirements to install software updates automatically. | |
| V-32572 | Medium | The DBMS must support the requirement to activate an alarm and/or automatically shut down the information system if an application component failure is detected. This can include conducting a graceful application shutdown to avoid losing information. | |
| V-32478 | Medium | The DBMS must ensure that PKI-based authentication maps the authenticated identity to the user account. | |
| V-32426 | Medium | Unused database components which are integrated in the DBMS and cannot be uninstalled must be disabled. | |
| V-32474 | Medium | The DBMS must enforce password maximum lifetime restrictions. | |
| V-32475 | Medium | The DBMS, when utilizing PKI-based authentication, must validate certificates by constructing a certification path with status information to an accepted trust anchor. | |
| V-32473 | Medium | DBMS passwords must not be stored in compiled, encoded, or encrypted batch jobs or compiled, encoded, or encrypted application source code. | |
| V-32470 | Medium | The DBMS must enforce password minimum lifetime restrictions. | |
| V-32518 | Medium | The application must perform data origin authentication and data integrity verification on the name/address resolution responses the system receives from authoritative sources when requested by client systems. | |
| V-32406 | Medium | The application must support the employment of automated mechanisms supporting the auditing of the enforcement actions. | |
| V-32246 | Medium | DBMS default account names must be changed. | |
| V-32419 | Medium | Configuration management applications must employ automated mechanisms to centrally verify configuration settings. | |
| V-32378 | Medium | The DBMS must provide a real-time alert when organization defined audit failure events occur. | |
| V-32418 | Medium | Configuration management applications must employ automated mechanisms to centrally apply configuration settings. | |
| V-32481 | Medium | The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users). | |
| V-32480 | Medium | The DBMS must use NIST validated FIPS 140-2 compliant cryptography for authentication mechanisms. | |
| V-32487 | Medium | The DBMS must employ strong identification and authentication techniques when establishing non-local maintenance and diagnostic sessions. | |
| V-32486 | Medium | The DBMS must employ cryptographic mechanisms to protect the integrity and confidentiality of non-local maintenance and diagnostic communications. | |
| V-32485 | Medium | The DBMS, when used for non-local maintenance sessions, must protect those sessions through the use of a strong authenticator tightly bound to the user. | |
| V-32484 | Medium | Applications related to incident tracking must support organizational requirements to employ automated mechanisms to assist in the tracking of security incidents. | |
| V-32489 | Medium | Databases employed to write data to portable digital media must use cryptographic mechanisms to protect and restrict access to information on portable digital media. | |
| V-32488 | Medium | The DBMS must terminate all sessions and network connections when non-local maintenance is completed. | |
| V-32456 | Medium | Applications managing network connectivity must have the capability to authenticate devices before establishing network connections by using bidirectional authentication that is cryptographically based. | |
| V-32255 | Medium | The DBMS must have its auditing configured to reduce the likelihood of storage capacity being exceeded. | |
| V-32362 | Medium | The DBMS must provide audit record generation capability for organization defined auditable events within the database. | |
| V-32363 | Medium | The DBMS must allow designated organizational personnel to select which auditable events are to be audited by the database. | |
| V-32218 | Medium | Applications must provide the ability to enforce security policies regarding information on interconnected systems. | |
| V-32219 | Medium | Applications must uniquely identify source domains for information transfer. | |
| V-32366 | Medium | The DBMS must provide the capability to capture, record, and log all content related to a user session. | |
| V-32367 | Medium | The DBMS must provide the capability to remotely view all content related to an established user session in real time. | |
| V-32364 | Medium | The DBMS must generate audit records for the DoD selected list of auditable events. | |
| V-32365 | Medium | The DBMS must initiate session auditing upon startup of the database. | |
| V-32212 | Medium | Applications providing information flow controls must provide the capability for privileged administrators to configure security policy filters to support different organizational security policies. | |
| V-32213 | Medium | Applications providing flow control must identify data type, specification and usage when transferring information between different security domains so that policy restrictions may be applied. | |
| V-32210 | Medium | Applications providing information flow control must use explicit security attributes on information, source, and destination objects as a basis for flow control decisions. | |
| V-32211 | Medium | Applications providing information flow control must provide the capability for privileged administrators to enable/disable security policy filters. | |
| V-32216 | Medium | Applications designed to control information flow must provide the ability to detect unsanctioned information being transmitted across security domains. | |
| V-32217 | Medium | Applications must provide the ability to prohibit the transfer of unsanctioned information in accordance with security policy. | |
| V-32214 | Medium | Applications, when transferring information between different security domains, must decompose information into policy-relevant subcomponents for submission to policy enforcement mechanisms. | |
| V-32215 | Medium | Applications, when transferring information between different security domains, must implement or incorporate policy filters that constrain data object and structure attributes according to organizational security policy requirements. | |
| V-32564 | Medium | Applications that serve to protect organizations and individuals from SPAM messages must incorporate update mechanisms updating protection mechanisms and signature updates when new application releases are available in accordance with organizational configuration management policy and procedures. | |
| V-32565 | Medium | Applications that are utilized to address the issue of SPAM and provide protection from SPAM must automatically update any and all SPAM protection measures including signature definitions. | |
| V-32409 | Medium | The DBMS must support the enforcement of a two-person rule for changes to organization defined application components and system-level information. | |
| V-32567 | Medium | Applications must provide automated support for the management of distributed security testing. | |
| V-32560 | Medium | Any software application designed to function as a firewall must be capable employing a default deny all configuration. | |
| V-32561 | Medium | Applications providing remote connectivity must prevent remote devices that have established a non-remote connection with the system from communicating outside of the communications path with resources in external networks. | |
| V-32562 | Medium | Proxy applications must support logging individual Transmission Control Protocol (TCP) sessions and blocking specific Uniform Resource Locators (URLs), domain names, and Internet Protocol (IP) addresses. | |
| V-32563 | Medium | Applications performing extrusion detection must be capable of denying network traffic and auditing internal users (or malicious code) posing a threat to external information systems. | |
| V-32403 | Medium | The DBMS must protect the audit records generated, as a result of remote access to privileged accounts, and the execution of privileged functions. | |
| V-32402 | Medium | The DBMS must protect audit data records and integrity by using cryptographic mechanisms. | |
| V-32401 | Medium | The DBMS must support the requirement to back up audit data and records onto a different system or media than the system being audited on an organization defined frequency. | |
| V-32400 | Medium | The DBMS must have the capability to produce audit records on hardware-enforced, write-once media. | |
| V-32407 | Medium | Applications must prevent the installation of organization defined critical software programs not signed with a certificate that has been recognized and approved by the organization. | |
| V-32360 | Medium | A DBMS utilizing Discretionary Access Control (DAC) must enforce a policy that includes or excludes access to the granularity of a single user. | |
| V-32405 | Medium | The DBMS must support the organizational requirement to employ automated mechanisms for enforcing access restrictions. | |
| V-32404 | Medium | The DBMS must support enforcement of logical access restrictions associated with changes to the DBMS configuration and to the database itself. | |
| V-32191 | Medium | Applications must not enable information system functionality providing the capability for automatic execution of code on mobile devices without user direction. | |
| V-32190 | Medium | The application must monitor for unauthorized connections of mobile devices to organizational information systems. | |
| V-32193 | Medium | The DBMS must provide a mechanism to automatically identify accounts designated as temporary or emergency accounts. | |
| V-32192 | Medium | The DBMS must provide automated mechanisms for supporting user account management. | |
| V-32195 | Medium | The DBMS must be capable of automatically disabling accounts after a 35 day period of account inactivity. | |
| V-32194 | Medium | The DBMS must provide a mechanism to automatically terminate accounts designated as temporary or emergency accounts after an organization defined time period. | |
| V-32197 | Medium | The DBMS must support the requirement to automatically audit account modification. | |
| V-32196 | Medium | The DBMS must support the requirement to automatically audit account creation. | |
| V-32199 | Medium | The DBMS must automatically audit account termination. | |
| V-32198 | Medium | The DBMS must automatically audit account disabling actions. | |
| V-32445 | Medium | The DBMS must use multifactor authentication for local access to privileged accounts. | |
| V-32253 | Medium | The DBMS must retain the notification message or banner on the screen until users take explicit actions to log on to the database. | |
| V-32490 | Medium | The DBMS must support organizational requirements to encrypt information stored in the database. | |
| V-32491 | Medium | Application software used to detect the presence of unauthorized software must employ automated detection mechanisms and notify designated organizational officials in accordance with the organization defined frequency. | |
| V-32492 | Medium | The DBMS must terminate the network connection associated with a communications session at the end of the session or after an organization defined time period of inactivity. | |
| V-32493 | Medium | The application must establish a trusted communications path between the user and organization defined security functions within the information system. | |
| V-32494 | Medium | Applications involved in the production, control, and distribution of symmetric cryptographic keys must use NIST-approved or NSA-approved key management technology and processes. | |
| V-32495 | Medium | Applications involved in the production, control, and distribution of symmetric and asymmetric cryptographic keys must use NIST-approved or NSA-approved key management technology and processes. | |
| V-32496 | Medium | Applications involved in the production, control, and distribution of asymmetric cryptographic keys must use must use approved PKI Class 3 certificates or prepositioned keying material. | |
| V-32497 | Medium | Applications involved in the production, control, and distribution of asymmetric cryptographic keys must use approved PKI Class 3 or class 4 certificates and hardware tokens that protect the users private key. | |
| V-32498 | Medium | The DBMS must implement required cryptographic protections using cryptographic modules complying with applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance. | |
| V-32499 | Medium | Database data files containing sensitive information must be encrypted. | |
| V-32459 | Medium | The DBMS must support organizational requirements to disable user accounts after an organization defined time period of inactivity. | |
| V-32361 | Medium | The application must produce a system-wide (logical or physical) audit trail composed of audit records in a standardized format. | |
| V-32399 | Medium | The DBMS must protect audit tools from unauthorized deletion. | |
| V-32398 | Medium | The DBMS must protect audit tools from unauthorized modification. | |
| V-32397 | Medium | The DBMS must protect audit tools from unauthorized access. | |
| V-32395 | Medium | The DBMS must protect audit information from unauthorized deletion. | |
| V-32394 | Medium | The DBMS must protect audit information from unauthorized modification. | |
| V-32393 | Medium | The DBMS must protect audit information from any type of unauthorized access. | |
| V-32392 | Medium | The DBMS must synchronize with internal operating system clocks which in turn, are synchronized on an organization defined frequency with an organization defined authoritative time source. | |
| V-32391 | Medium | The DBMS must use system clocks to generate timestamps for audit records. | |
| V-32390 | Medium | Attempts to bypass access controls must be audited. | |
| V-32553 | Medium | Applications functioning in the capacity of a firewall must check incoming communications to ensure the communications are coming from an authorized source and routed to an authorized destination. | |
| V-32369 | Medium | The DBMS must produce audit records containing sufficient information to establish when (date and time) the events occurred. | |
| V-32555 | Medium | The DBMS must check the validity of data inputs. | |
| V-32554 | Medium | The application must be capable of implementing host-based boundary protection mechanisms for servers, workstations, and mobile devices. | |
| V-32557 | Medium | Applications designed to enforce protocol formats must employ automated mechanisms to enforce strict adherence to protocol format. | |
| V-32556 | Medium | Boundary protection applications must prevent discovery of specific system components (or devices) composing a managed interface. | |
| V-32559 | Medium | Boundary protection applications must be capable of preventing public access into the organizations internal networks except as appropriately mediated by managed interfaces. | |
| V-32558 | Medium | Boundary protection applications must fail securely in the event of an operational failure. | |
| V-32412 | Medium | Database objects must be owned by accounts authorized for ownership. | |
| V-32413 | Medium | Database software directories, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications. | |
| V-32414 | Medium | The DBMS software installation account must be restricted to authorized users. | |
| V-32415 | Medium | Database software, applications and configuration files must be monitored to discover unauthorized changes. | |
| V-32416 | Medium | The DBMS must automatically implement organization defined safeguards and countermeasures if security functions (or mechanisms) are changed inappropriately. | |
| V-32417 | Medium | Configuration management applications must employ automated mechanisms to centrally manage configuration settings. | |
| V-32188 | Medium | The DBMS must ensure remote sessions that access an organization defined list of security functions and security-relevant information are audited. | |
| V-32189 | Medium | The DBMS must support the disabling of network protocols deemed by the organization to be non-secure. | |
| V-32186 | Medium | The DBMS must allow all remote access to be routed through managed access control points. | |
| V-32187 | Medium | The application must monitor for unauthorized remote connections to the information system on an organization defined frequency. | |
| V-32184 | Medium | A DBMS providing remote access capabilities must utilize approved cryptography to protect the integrity of remote access sessions. | |
| V-32185 | Medium | The application must employ automated mechanisms to facilitate the monitoring and control of remote access methods. | |
| V-32182 | Medium | The DBMS must utilize approved cryptography when passing authentication data for remote access sessions. | |
| V-32183 | Medium | A DBMS providing remote access capabilities must utilize organization defined cryptography to protect the confidentiality of data passing over remote access sessions. | |
| V-32181 | Medium | The DBMS must display security labels using organization identified human-readable, standard naming conventions. | |
| V-32448 | Medium | The DBMS, if using multifactor authentication when accessing privileged accounts via the network, must provide one of the factors by a device that is separate from the information system gaining access. | |
| V-32447 | Medium | The DBMS must ensure users are authenticated with an individual authenticator prior to using a group authenticator. | |
| V-32446 | Medium | The DBMS must use multifactor authentication for local access to non-privileged accounts. | |
| V-32566 | Medium | The DBMS must verify there have not been unauthorized changes to the DBMS software and information. | |
| V-32172 | Medium | The DBMS must maintain the binding of security labels to information with sufficient assurance that the information/attribute association can be used as the basis for automated policy actions. | |
| V-32427 | Medium | Access to external executables must be disabled or restricted. | |
| V-32170 | Medium | The DBMS must provide the capability to specify administrative users and grant them the right to change application security labels pertaining to application data. | |
| V-32420 | Medium | Configuration management applications must employ automated mechanisms to centrally respond to unauthorized changes to configuration settings. | |
| V-32423 | Medium | Default demonstration and sample databases, database objects, and applications must be removed. | |
| V-32422 | Medium | The DBMS must enforce requirements for remote connections to the information system. | |
| V-32384 | Medium | To support audit review, analysis and reporting the application must integrate audit review, analysis, and reporting processes to support organizational processes for investigation and response to suspicious activities. | |
| V-32385 | Medium | Applications must provide the capability to centralize the review and analysis of audit records from multiple components within the system. | |
| V-32386 | Medium | The application must prevent the execution of prohibited mobile code. | |
| V-32429 | Medium | To support the requirements and principles of least functionality, the application must support organizational requirements regarding the use of automated mechanisms preventing program execution on the information system in accordance with the organization defined specifications. | |
| V-32428 | Medium | The DBMS must support the organizational requirements to specifically prohibit or restrict the use of unauthorized functions, ports, protocols, and/or services. | |
| V-32382 | Medium | The DBMS must alert designated organizational officials in the event of an audit processing failure. | |
| V-32383 | Medium | The DBMS must be capable of taking organization defined actions upon audit failure (e.g., overwrite oldest audit records, stop generating audit records, cease processing, notify of audit failure). | |
| V-32421 | Medium | Configuration management solutions must track unauthorized, security-relevant configuration changes. | |
| V-32549 | Medium | The DBMS must protect against or limit the effects of the organization defined types of Denial of Service (DoS) attacks. | |
| V-32546 | Medium | Applications must support organization defined requirements to load and execute from hardware-enforced, read-only media. | |
| V-32547 | Medium | The DBMS must prevent unauthorized and unintended information transfer via shared system resources. | |
| V-32544 | Medium | Applications required to be non-modifiable must support organizational requirements to provide components that contain no writeable storage capability. These components must be persistent across restart and/or power on/off. | |
| V-32545 | Medium | Applications must, for organization defined information system components, load and execute the operating environment from hardware-enforced, read-only media. | |
| V-32542 | Medium | Applications must meet organizational requirements to implement security functions as a layered structure minimizing interactions between layers of the design and avoiding any dependence by lower layers on the functionality or correctness of higher layers. | |
| V-32543 | Medium | The application must protect the integrity of information during the processes of data aggregation, packaging, and transformation in preparation for transmission. | |
| V-32540 | Medium | The DBMS must employ automated mechanisms to alert security personnel of inappropriate or unusual activities with security implications. | |
| V-32169 | Medium | The DBMS must dynamically reconfigure security labels in accordance with an identified security policy as information is created and combined. | |
| V-32532 | Medium | Only a Honey Pot information system and/or application must include components that proactively seek to identify web-based malicious code. Honey Pot systems must be not be shared or used for any other purpose other than described. | |
| V-32163 | Medium | The DBMS must maintain and support organization defined security labels on stored information. | |
| V-32500 | Medium | The DBMS must employ NIST validated cryptography to protect unclassified information. | |
| V-32160 | Medium | The DBMS must not interfere or be impacted by an OS level session lock. | |
| V-32371 | Medium | The DBMS must produce audit records containing sufficient information to establish the sources (origins) of the events. | |
| V-32442 | Medium | The DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users). | |
| V-32370 | Medium | The DBMS must produce audit records containing sufficient information to establish where the events occurred. | |
| V-32523 | Medium | The DBMS must terminate user sessions upon user logout or any other organization or policy defined session termination events, such as idle time limit exceeded. | |
| V-32166 | Medium | The DBMS must maintain the binding of security labels to information with sufficient assurance that the information/attribute association can be used as the basis for automated policy actions. | |
| V-32569 | Medium | The DBMS must identify potentially security-relevant error conditions. | |
| V-32432 | Medium | The DBMS must be capable of backing up user-level information per a defined frequency. | |
| V-32433 | Medium | Database backup procedures must be defined, documented, and implemented. | |
| V-32430 | Medium | Recovery procedures and technical system features must exist to ensure recovery is done in a secure and verifiable manner. | |
| V-32431 | Medium | The DBMS must have transaction journaling enabled. | |
| V-32436 | Medium | DBMS must conduct backups of system-level information per organization defined frequency that is consistent with recovery time and recovery point objectives. | |
| V-32437 | Medium | The DBMS software libraries must be periodically backed up. | |
| V-32434 | Medium | Database recovery procedures must be developed, documented, implemented, and periodically tested. | |
| V-32435 | Medium | DBMS backup and restoration files must be protected from unauthorized access. | |
| V-32471 | Medium | Procedures for establishing temporary passwords that meet DoD password requirements for new accounts must be defined, documented, and implemented. | |
| V-32439 | Medium | The application must support and must not impede organizational requirements to conduct backups of information system documentation including security-related documentation per organization defined frequency. | |
| V-32596 | Medium | The DBMS must notify appropriate individuals when accounts are created. | |
| V-32248 | Medium | The DBMS must specify account lockout duration that is greater than or equal to the organization approved minimum. | |
| V-32539 | Medium | Applications must meet organizational requirements to implement an information system isolation boundary that minimizes the number of non-security functions included within the boundary containing security functions. | |
| V-32538 | Medium | The DBMS must isolate security functions enforcing access and information flow control from both non-security functions and from other security functions. | |
| V-32515 | Medium | The DBMS must prevent the presentation of information system management-related functionality at an interface utilized by general (i.e., non-privileged) users. | |
| V-32241 | Medium | Non-privileged accounts must be utilized when accessing non-administrative functions. | |
| V-32379 | Medium | The application must enforce configurable traffic volume thresholds representing auditing capacity for network traffic. | |
| V-32243 | Medium | OS accounts utilized to run external procedures called by the DBMS must have limited privileges. | |
| V-32530 | Medium | Applications must enforce requirements regarding the connection of mobile devices to organizational information systems. | |
| V-32537 | Medium | The DBMS must automatically terminate emergency accounts after an organization defined time period for each type of account. | |
| V-32536 | Medium | The DBMS must isolate security functions from non-security functions by means of separate security domains. | |
| V-32535 | Medium | The DBMS must employ cryptographic mechanisms preventing the unauthorized disclosure of information at rest unless the data is otherwise protected by alternative physical measures. | |
| V-32534 | Medium | The DBMS must take needed steps to protect data at rest and ensure confidentiality and integrity of application data. | |
| V-32579 | Medium | Applications must provide notification of failed automated security tests. | |
| V-32249 | Medium | The DBMS must have the capability to limit the number of failed login attempts based upon an organization defined number of consecutive invalid attempts occurring within an organization defined time period. | |
| V-32514 | Medium | The DBMS must separate user functionality (including user interface services) from database management functionality. | |
| V-32507 | Medium | The application must validate the integrity of security attributes exchanged between systems. | |
| V-32502 | Medium | The DBMS must employ NIST validated FIPS compliant cryptography to protect unclassified information when such information must be separated from individuals who have the necessary clearances yet lack the necessary access approvals. | |
| V-32411 | Medium | The OS must limit privileges to change the DBMS software resident within software libraries (including privileged programs). | |
| V-32164 | Medium | The DBMS must maintain and support organization defined security labels on information in process. | |
| V-32256 | Medium | The DBMS must have allocated audit record storage capacity. | |
| V-32257 | Medium | Applications scanning for malicious code must scan all media used for system maintenance prior to use. | |
| V-32254 | Medium | The DBMS must display the system use information when appropriate, before granting further access. | |
| V-32158 | Medium | The application must ensure the screen display is obfuscated when an application session lock event occurs. | |
| V-32250 | Medium | The DBMS must enforce the organization defined time period during which the limit of consecutive failed login attempts by a user is counted. | |
| V-32251 | Medium | The DBMS, when the maximum numbers of unsuccessful attempts is exceeded, must automatically lock the account/node for an organization defined time period or lock the account/node until released by an administrator IAW organizational policy. | |
| V-32157 | Medium | The DBMS must limit the number of concurrent sessions for each system account to an organization defined number of sessions. | |
| V-32578 | Medium | Malicious code protection applications must update malicious code protection mechanisms only when directed by a privileged user. | |
| V-32258 | Medium | Applications utilizing mobile code must meet DoD-defined mobile code requirements. | |
| V-32528 | Medium | The DBMS must fail to a known safe state for defined types of failures. | |
| V-32529 | Medium | The DBMS must preserve any organization defined system state information in the event of a system failure. | |
| V-32517 | Medium | Applications, when operating as part of a distributed, hierarchical namespace, must provide the means to indicate the security status of child subspaces and (if the child supports secure resolution services) enable verification of a chain of trust among parent and child domains. | |
| V-32444 | Medium | The DBMS must use multifactor authentication for network access to non-privileged accounts. | |
| V-32443 | Medium | The DBMS must use multifactor authentication for network access to privileged accounts. | |
| V-32571 | Medium | The DBMS must restrict error messages, so only authorized personnel may view them. | |
| V-32503 | Medium | Applications must respond to security function anomalies in accordance with organization defined responses and alternative action(s). | |
| V-32520 | Medium | The application must perform data origin authentication and data integrity verification on all resolution responses received whether or not local client systems explicitly request this service. | |
| V-32521 | Medium | Applications that collectively provide name/address resolution service for an organization must implement internal/external role separation. | |
| V-32522 | Medium | The DBMS must ensure authentication of both client and server during the entire session. | |
| V-32570 | Medium | The DBMS must only generate error messages that provide information necessary for corrective actions without revealing organization defined sensitive or potentially harmful information in error logs and administrative messages that could be exploited. | |
| V-32504 | Medium | The DBMS must protect the integrity of publicly available information and applications. | |
| V-32525 | Medium | The DBMS must generate a unique session identifier for each session. | |
| V-32527 | Medium | The DBMS must generate unique session identifiers with organization defined randomness requirements. | |
| V-32533 | Medium | Applications must maintain the confidentiality of information during aggregation, packaging, and transformation in preparation for transmission. When transmitting data, applications need to leverage transmission protection mechanisms such as TLS, SSL VPN | |
| V-32240 | Medium | Administrators must utilize a separate, distinct administrative account when performing administrative activities, accessing database security functions, or accessing security-relevant information. | |
| V-32368 | Medium | The DBMS must produce audit records containing sufficient information to establish what type of events occurred. | |
| V-32506 | Medium | The DBMS must associate and maintain security labels when exchanging information between systems. | |
| V-32531 | Medium | The application must disable network access by unauthorized components/devices or notify designated organizational officials. | |
| V-32176 | Medium | The DBMS must allow authorized users to associate security labels to information in the database. | |
| V-32227 | Low | The DBMS must enforce organization defined limitations on the embedding of data types within other data types. | |
| V-32348 | Low | The DBMS must associate the identity of the information producer with the information. | |
| V-32345 | Low | The DBMS must notify the user of the number of unsuccessful login attempts occurring during an organization defined time period. | |
| V-32347 | Low | The DBMS must protect against an individual using a group account from falsely denying having performed a particular action. | |
| V-32551 | Low | The DBMS must manage excess capacity, bandwidth, or other redundancy to limit the effects of information flooding types of Denial of Service (DoS) attacks. | |
| V-32550 | Low | The DBMS must restrict the ability of users to launch Denial of Service (DoS) attacks against other information systems or networks. | |
| V-32388 | Low | The DBMS must provide a report generation capability for audit reduction data. | |
| V-32387 | Low | The DBMS must provide an audit log reduction capability. | |
| V-32260 | Low | The DBMS must display the number of failed login attempts made with a user account upon successful login of that user account. | |
| V-32548 | Low | The DBMS must not share resources used to interface with systems operating at different security levels. | |
| V-32552 | Low | The DBMS must limit the use of resources by priority and not impede the host from servicing processes designated as a higher-priority. | |
| V-32575 | Low | The DBMS must support organizational requirements to employ automated patch management tools to facilitate flaw remediation to organization defined information system components. | |
| V-32247 | Low | The DBMS must be able to function within separate processing domains (virtualized systems), when specified, to enable finer-grained allocation of user privileges. | |
| V-32252 | Low | The DBMS must display an approved system use notification message or banner before granting access to the database. | |
| V-32259 | Low | The DBMS must, upon successful login, display to the user the date and time of the users last login. | |
| V-32233 | Low | The DBMS must support organizational requirements to implement separation of duties through assigned information access authorizations. |
The post DoD STIGs – Database Security Requirements Guide appeared first on WaterOx Consulting.
