Skip to content
ATO Pathways
  Log In

III - Administrative Sensitive

Rules and Groups employed by this XCCDF Profile

  • SRG-APP-000133

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS software installation account must be restricted to authorized users.

    &lt;VulnDiscussion&gt;When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components...
    Rule High Severity
    Show

  • SRG-APP-000133

    <GroupDescription></GroupDescription>
    Group
    Show

  • Database software, including DBMS configuration files, must be stored in dedicated directories, or DASD pools, separate from the host OS and other applications.

    &lt;VulnDiscussion&gt;When dealing with change control issues, it should be noted any changes to the hardware, software, and/or firmware components...
    Rule Medium Severity
    Show

  • SRG-APP-000133

    <GroupDescription></GroupDescription>
    Group
    Show

  • Database objects (including but not limited to tables, indexes, storage, stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be owned by database/DBMS principals authorized for ownership.

    &lt;VulnDiscussion&gt;Within the database, object ownership implies full privileges to the owned object, including the privilege to assign access t...
    Rule Medium Severity
    Show

  • SRG-APP-000133

    <GroupDescription></GroupDescription>
    Group
    Show

  • The role(s)/group(s) used to modify database structure (including but not necessarily limited to tables, indexes, storage, etc.) and logic modules (stored procedures, functions, triggers, links to software external to the DBMS, etc.) must be restricted to authorized users.

    &lt;VulnDiscussion&gt;If the DBMS were to allow any user to make changes to database structure or logic, then those changes might be implemented wi...
    Rule Medium Severity
    Show

  • SRG-APP-000141

    <GroupDescription></GroupDescription>
    Group
    Show

  • Default demonstration and sample databases, database objects, and applications must be removed.

    &lt;VulnDiscussion&gt;Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, pr...
    Rule Medium Severity
    Show

  • SRG-APP-000141

    <GroupDescription></GroupDescription>
    Group
    Show

  • Unused database components, DBMS software, and database objects must be removed.

    &lt;VulnDiscussion&gt;Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, pr...
    Rule Medium Severity
    Show

  • SRG-APP-000141

    <GroupDescription></GroupDescription>
    Group
    Show

  • Unused database components that are integrated in the DBMS and cannot be uninstalled must be disabled.

    &lt;VulnDiscussion&gt;Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, pr...
    Rule Medium Severity
    Show

  • SRG-APP-000141

    <GroupDescription></GroupDescription>
    Group
    Show

  • Access to external executables must be disabled or restricted.

    &lt;VulnDiscussion&gt;Information systems are capable of providing a wide variety of functions and services. Some of the functions and services, pr...
    Rule Medium Severity
    Show

  • SRG-APP-000142

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must be configured to prohibit or restrict the use of organization-defined functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments.

    &lt;VulnDiscussion&gt;In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e....
    Rule Medium Severity
    Show

  • SRG-APP-000148

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must uniquely identify and authenticate organizational users (or processes acting on behalf of organizational users).

    &lt;VulnDiscussion&gt;To assure accountability and prevent unauthenticated access, organizational users must be identified and authenticated to pre...
    Rule Medium Severity
    Show

  • SRG-APP-000164

    <GroupDescription></GroupDescription>
    Group
    Show

  • If DBMS authentication, using passwords, is employed, the DBMS must enforce the DoD standards for password complexity and lifetime.

    &lt;VulnDiscussion&gt;OS/enterprise authentication and identification must be used (SRG-APP-000023-DB-000001). Native DBMS authentication may be u...
    Rule High Severity
    Show

  • SRG-APP-000171

    <GroupDescription></GroupDescription>
    Group
    Show

  • If passwords are used for authentication, the DBMS must store only hashed, salted representations of passwords.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be us...
    Rule High Severity
    Show

  • SRG-APP-000172

    <GroupDescription></GroupDescription>
    Group
    Show

  • If passwords are used for authentication, the DBMS must transmit only encrypted representations of passwords.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. Authentication based on User ID and Password may be us...
    Rule High Severity
    Show

  • SRG-APP-000175

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS, when utilizing PKI-based authentication, must validate certificates by performing RFC 5280-compliant certification path validation.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. A certificate’s certification path is the path from th...
    Rule Medium Severity
    Show

  • SRG-APP-000176

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must enforce authorized access to all PKI private keys stored/utilized by the DBMS.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. PKI certificate-based authentication is performed by re...
    Rule High Severity
    Show

  • SRG-APP-000177

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must map the PKI-authenticated identity to an associated user account.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. Once a PKI certificate has been validated, it must be m...
    Rule Medium Severity
    Show

  • SRG-APP-000178

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals.

    &lt;VulnDiscussion&gt;The DoD standard for authentication is DoD-approved PKI certificates. Normally, with PKI authentication, the interaction wit...
    Rule High Severity
    Show

  • SRG-APP-000179

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must use NIST FIPS 140-2 or 140-3 validated cryptographic modules for cryptographic operations.

    &lt;VulnDiscussion&gt;Use of weak or not validated cryptographic algorithms undermines the purposes of utilizing encryption and digital signatures ...
    Rule High Severity
    Show

  • SRG-APP-000180

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must uniquely identify and authenticate non-organizational users (or processes acting on behalf of non-organizational users).

    &lt;VulnDiscussion&gt;Non-organizational users include all information system users other than organizational users, which include organizational e...
    Rule Medium Severity
    Show

  • SRG-APP-000211

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must separate user functionality (including user interface services) from database management functionality.

    &lt;VulnDiscussion&gt;Information system management functionality includes functions necessary to administer databases, network components, worksta...
    Rule Medium Severity
    Show

  • SRG-APP-000220

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must invalidate session identifiers upon user logout or other session termination.

    &lt;VulnDiscussion&gt;Captured sessions can be reused in "replay" attacks. This requirement limits the ability of adversaries to capture and contin...
    Rule Medium Severity
    Show

  • SRG-APP-000223

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must recognize only system-generated session identifiers.

    &lt;VulnDiscussion&gt;DBMSs utilize sessions and session identifiers to control application behavior and user access. If an attacker can guess the ...
    Rule Medium Severity
    Show

  • SRG-APP-000224

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must maintain the authenticity of communications sessions by guarding against man-in-the-middle attacks that guess at Session ID values.

    &lt;VulnDiscussion&gt;One class of man-in-the-middle, or session hijacking, attack involves the adversary guessing at valid session identifiers bas...
    Rule Medium Severity
    Show

  • SRG-APP-000225

    <GroupDescription></GroupDescription>
    Group
    Show

  • The DBMS must fail to a secure state if system initialization fails, shutdown fails, or aborts fail.

    &lt;VulnDiscussion&gt;Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. ...
    Rule Medium Severity
    Show

  • SRG-APP-000226

    <GroupDescription></GroupDescription>
    Group
    Show

  • In the event of a system failure, the DBMS must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes.

    &lt;VulnDiscussion&gt;Failure to a known state can address safety or security in accordance with the mission/business needs of the organization. F...
    Rule Medium Severity
    Show

Node 2

siemur/test-space

The content of the drawer really is up to you. It could have form fields, definition lists, text lists, labels, charts, progress bars, etc. Spacing recommendation is 24px margins. You can put tabs in here, and can also make the drawer scrollable.

Capacity
Modules