| Checked | Name | Title |
|---|
| ☐ | SV-233015r960759_rule | The container platform must use TLS 1.2 or greater for secure container image transport from trusted sources. |
| ☐ | SV-233016r960759_rule | The container platform must use TLS 1.2 or greater for secure communication. |
| ☐ | SV-233019r1043176_rule | The container platform must use a centralized user management solution to support account management functions. |
| ☐ | SV-233020r960771_rule | The container platform must automatically remove or disable temporary user accounts after 72 hours. |
| ☐ | SV-233021r960774_rule | The container platform must automatically disable accounts after a 35-day period of account inactivity. |
| ☐ | SV-233022r960777_rule | The container platform must automatically audit account creation. |
| ☐ | SV-233023r960780_rule | The container platform must automatically audit account modification. |
| ☐ | SV-233024r960783_rule | The container platform must automatically audit account-disabling actions. |
| ☐ | SV-233025r960786_rule | The container platform must automatically audit account removal actions. |
| ☐ | SV-233026r1137638_rule | Least privilege access and need-to-know must be required to access the container platform registry. |
| ☐ | SV-233027r1137639_rule | Least privilege access and need-to-know must be required to access the container platform runtime. |
| ☐ | SV-233028r1137640_rule | Least privilege access and need-to-know must be required to access the container platform keystore. |
| ☐ | SV-233029r1137641_rule | The container platform must enforce approved authorizations for controlling the flow of information within the container platform based on organization-defined information flow control policies. |
| ☐ | SV-233030r1137642_rule | The container platform must enforce approved authorizations for controlling the flow of information between interconnected systems and services based on organization-defined information flow control policies. |
| ☐ | SV-233031r960840_rule | The container platform must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
| ☐ | SV-233032r960843_rule | The container platform must display the Standard Mandatory DoD Notice and Consent Banner before granting access to platform components. |
| ☐ | SV-233033r960846_rule | The container platform must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage and conditions and take explicit actions to log on for further access. |
| ☐ | SV-233038r960879_rule | The container platform must generate audit records for all DoD-defined auditable events within all components in the platform. |
| ☐ | SV-233039r960882_rule | The container platform must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. |
| ☐ | SV-233040r960885_rule | The container platform must generate audit records when successful/unsuccessful attempts to access privileges occur. |
| ☐ | SV-233041r960888_rule | The container platform must initiate session auditing upon startup. |
| ☐ | SV-233042r960891_rule | All audit records must identify what type of event has occurred within the container platform. |
| ☐ | SV-233043r960894_rule | The container platform audit records must have a date and time association with all events. |
| ☐ | SV-233044r960897_rule | All audit records must identify where in the container platform the event occurred. |
| ☐ | SV-233045r960900_rule | All audit records must identify the source of the event within the container platform. |
| ☐ | SV-233046r960903_rule | All audit records must generate the event results within the container platform. |
| ☐ | SV-233047r960906_rule | All audit records must identify any users associated with the event within the container platform. |
| ☐ | SV-233048r960906_rule | All audit records must identify any containers associated with the event within the container platform. |
| ☐ | SV-233049r960909_rule | The container platform must generate audit records containing the full-text recording of privileged commands or the individual identities of group account users. |
| ☐ | SV-233052r960918_rule | The container platform components must provide the ability to send audit logs to a central enterprise repository for review and analysis. |
| ☐ | SV-233055r960927_rule | The container platform must use internal system clocks to generate audit record time stamps. |
| ☐ | SV-233056r960930_rule | The container platform must protect audit information from any type of unauthorized read access. |
| ☐ | SV-233057r960933_rule | The container platform must protect audit information from unauthorized modification. |
| ☐ | SV-233058r960936_rule | The container platform must protect audit information from unauthorized deletion. |
| ☐ | SV-233059r960939_rule | The container platform must protect audit tools from unauthorized access. |
| ☐ | SV-233060r960942_rule | The container platform must protect audit tools from unauthorized modification. |
| ☐ | SV-233061r960945_rule | The container platform must protect audit tools from unauthorized deletion. |
| ☐ | SV-233063r960951_rule | The container platform must use FIPS validated cryptographic mechanisms to protect the integrity of log information. |
| ☐ | SV-233064r981843_rule | The container platform must be built from verified packages. |
| ☐ | SV-233065r981844_rule | The container platform must verify container images. |
| ☐ | SV-233066r960960_rule | The container platform must limit privileges to the container platform registry. |
| ☐ | SV-233067r960960_rule | The container platform must limit privileges to the container platform runtime. |
| ☐ | SV-233068r960960_rule | The container platform must limit privileges to the container platform keystore. |
| ☐ | SV-233069r960960_rule | Configuration files for the container platform must be protected. |
| ☐ | SV-233070r960960_rule | Authentication files for the container platform must be protected. |
| ☐ | SV-233071r960963_rule | The container platform must be configured with only essential configurations. |
| ☐ | SV-233072r960963_rule | The container platform registry must contain only container images for those capabilities being offered by the container platform. |
| ☐ | SV-233073r1043177_rule | The container platform runtime must enforce ports, protocols, and services that adhere to the PPSM CAL. |
| ☐ | SV-233074r1043177_rule | The container platform runtime must enforce the use of ports that are non-privileged. |
| ☐ | SV-233075r1051115_rule | The container platform must uniquely identify and authenticate users. |
| ☐ | SV-233076r1051115_rule | The container platform application program interface (API) must uniquely identify and authenticate users. |
| ☐ | SV-233077r1051115_rule | The container platform must uniquely identify and authenticate processes acting on behalf of the users. |
| ☐ | SV-233078r1051115_rule | The container platform application program interface (API) must uniquely identify and authenticate processes acting on behalf of the users. |
| ☐ | SV-233079r960972_rule | The container platform must use multifactor authentication for network access to privileged accounts. |
| ☐ | SV-233080r960975_rule | The container platform must use multifactor authentication for network access to non-privileged accounts. |
| ☐ | SV-233081r981845_rule | The container platform must use multifactor authentication for local access to privileged accounts. |
| ☐ | SV-233082r981848_rule | The container platform must use multifactor authentication for local access to nonprivileged accounts. |
| ☐ | SV-233083r981849_rule | The container platform must ensure users are authenticated with an individual authenticator prior to using a group authenticator. |
| ☐ | SV-233084r960993_rule | The container platform must use FIPS-validated SHA-1 or higher hash function to provide replay-resistant authentication mechanisms for network access to privileged accounts. |
| ☐ | SV-233085r981852_rule | The container platform must implement replay-resistant authentication mechanisms for network access to nonprivileged accounts. |
| ☐ | SV-233086r960999_rule | The container platform must uniquely identify all network-connected nodes before establishing any connection. |
| ☐ | SV-233087r981853_rule | The container platform must disable identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. |
| ☐ | SV-233088r981854_rule | The container platform must enforce a minimum 15-character password length. |
| ☐ | SV-233090r981856_rule | The container platform must enforce password complexity by requiring that at least one uppercase character be used. |
| ☐ | SV-233091r981857_rule | The container platform must enforce password complexity by requiring that at least one lowercase character be used. |
| ☐ | SV-233092r981858_rule | The container platform must enforce password complexity by requiring that at least one numeric character be used. |
| ☐ | SV-233093r981859_rule | The container platform must enforce password complexity by requiring that at least one special character be used. |
| ☐ | SV-233094r1107119_rule | The container platform must require the change of at least eight of the total number of characters when passwords are changed. |
| ☐ | SV-233095r981861_rule | For container platform using password authentication, the application must store only cryptographic representations of passwords. |
| ☐ | SV-233096r961029_rule | For accounts using password authentication, the container platform must use FIPS-validated SHA-2 or later protocol to protect the integrity of the password authentication process. |
| ☐ | SV-233097r981862_rule | The container platform must enforce 24 hours (one day) as the minimum password lifetime. |
| ☐ | SV-233098r1043190_rule | The container platform must enforce a 60-day maximum password lifetime restriction. |
| ☐ | SV-233101r961044_rule | The container platform must map the authenticated identity to the individual user or group account for PKI-based authentication. |
| ☐ | SV-233102r961047_rule | The container platform must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
| ☐ | SV-233105r961056_rule | The container platform must provide an audit reduction capability that supports on-demand reporting requirements. |
| ☐ | SV-233106r961062_rule | The container platform must employ strong authenticators in the establishment of non-local maintenance and diagnostic sessions. |
| ☐ | SV-233108r961068_rule | The application must terminate all network connections associated with a communications session at the end of the session, or as follows: for in-band management sessions (privileged sessions), the session must be terminated after 10 minutes of inactivity. |
| ☐ | SV-233114r1137643_rule | The container platform must separate user functionality (including user interface services) from information system management functionality. |
| ☐ | SV-233118r1043178_rule | The container platform must protect authenticity of communications sessions with the use of FIPS-validated 140-2 or 140-3 security requirements for cryptographic modules. |
| ☐ | SV-233122r961122_rule | The container platform runtime must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. |
| ☐ | SV-233123r961125_rule | The container platform must preserve any information necessary to determine the cause of the disruption or failure. |
| ☐ | SV-233125r961131_rule | The container platform runtime must isolate security functions from non-security functions. |
| ☐ | SV-233126r971528_rule | The container platform must never automatically remove or disable emergency accounts. |
| ☐ | SV-233127r1137644_rule | The container platform must prohibit containers from accessing privileged resources. |
| ☐ | SV-233128r1137645_rule | The container platform must prevent unauthorized and unintended information transfer via shared system resources. |
| ☐ | SV-233129r961152_rule | The container platform must restrict individuals' ability to launch organizationally defined denial-of-service (DoS) attacks against other information systems. |
| ☐ | SV-233133r961167_rule | The container platform must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. |
| ☐ | SV-233142r961206_rule | The container platform must use cryptographic mechanisms to protect the integrity of audit tools. |
| ☐ | SV-233143r981871_rule | The container platform must notify system administrators (SAs) and the information system security officer (ISSO) when accounts are created. |
| ☐ | SV-233144r981872_rule | The container platform must notify system administrators (SAs) and the information system security officer (ISSO) when accounts are modified. |
| ☐ | SV-233145r981873_rule | The container platform must notify system administrators and ISSO for account disabling actions. |
| ☐ | SV-233146r981874_rule | The container platform must notify system administrators and ISSO for account removal actions. |
| ☐ | SV-233149r961227_rule | Access to the container platform must display an explicit logout message to user indicating the reliable termination of authenticated communication sessions. |
| ☐ | SV-233155r981875_rule | The container platform must terminate shared/group account credentials when members leave the group. |
| ☐ | SV-233157r961290_rule | The container platform must automatically audit account-enabling actions. |
| ☐ | SV-233158r981878_rule | The container platform must notify the system administrator (SA) and information system security officer (ISSO) of account enabling actions. |
| ☐ | SV-233162r961353_rule | The container platform must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
| ☐ | SV-233163r961359_rule | Container images instantiated by the container platform must execute using least privileges. |
| ☐ | SV-233164r961362_rule | The container platform must audit the execution of privileged functions. |
| ☐ | SV-233165r961368_rule | The container platform must automatically lock an account until the locked account is released by an administrator when three unsuccessful login attempts in 15 minutes are exceeded. |
| ☐ | SV-233166r961863_rule | The container platform must provide the configuration for organization-identified individuals or roles to change the auditing to be performed on all components, based on all selectable event criteria within organization-defined time thresholds. |
| ☐ | SV-233168r961392_rule | The container platform must allocate audit record storage capacity in accordance with organization-defined audit record storage requirements. |
| ☐ | SV-233169r961395_rule | Audit records must be stored at a secondary location. |
| ☐ | SV-233170r961398_rule | The container platform must provide an immediate warning to the SA and ISSO (at a minimum) when allocated audit record storage volume reaches 75 percent of repository maximum audit record storage capacity. |
| ☐ | SV-233171r961401_rule | The container platform must provide an immediate real-time alert to the SA and ISSO, at a minimum, of all audit failure events requiring real-time alerts. |
| ☐ | SV-233181r961443_rule | All audit records must use UTC or GMT time stamps. |
| ☐ | SV-233182r961446_rule | The container platform must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision. |
| ☐ | SV-233184r981884_rule | The container platform must prohibit the installation of patches and updates without explicit privileged status. |
| ☐ | SV-233185r981885_rule | The container platform runtime must prohibit the instantiation of container images without explicit privileged status. |
| ☐ | SV-233186r981888_rule | The container platform registry must prohibit installation or modification of container images without explicit privileged status. |
| ☐ | SV-233188r961461_rule | The container platform must enforce access restrictions for container platform configuration changes. |
| ☐ | SV-233189r981889_rule | The container platform must enforce access restrictions and support auditing of the enforcement actions. |
| ☐ | SV-233190r961470_rule | All non-essential, unnecessary, and unsecure DoD ports, protocols, and services must be disabled in the container platform. |
| ☐ | SV-233191r961473_rule | The container platform must prevent component execution in accordance with organization-defined policies regarding software program usage and restrictions, and/or rules authorizing the terms and conditions of software program usage. |
| ☐ | SV-233192r961479_rule | The container platform registry must employ a deny-all, permit-by-exception (whitelist) policy to allow only authorized container images in the container platform. |
| ☐ | SV-233193r1050787_rule | The container platform must require users to reauthenticate when organization-defined circumstances or situations require reauthentication. |
| ☐ | SV-233195r961494_rule | The container platform must be configured to use multi-factor authentication for user authentication. |
| ☐ | SV-233200r961521_rule | The container platform must prohibit the use of cached authenticators after an organization-defined time period. |
| ☐ | SV-233201r981893_rule | The container platform, for PKI-based authentication, must implement a local cache of revocation data to support path discovery and validation in case of the inability to access revocation information via the network. |
| ☐ | SV-233202r961527_rule | The container platform must accept Personal Identity Verification (PIV) credentials from other federal agencies. |
| ☐ | SV-233206r961548_rule | The container platform must audit non-local maintenance and diagnostic sessions' organization-defined audit events associated with non-local maintenance. |
| ☐ | SV-233207r961554_rule | Container platform applications and Application Program Interfaces (API) used for nonlocal maintenance sessions must use FIPS-validated keyed-hash message authentication code (HMAC) to protect the integrity of nonlocal maintenance and diagnostic communications. |
| ☐ | SV-233208r961557_rule | The container platform must configure web management tools and Application Program Interfaces (API) with FIPS-validated Advanced Encryption Standard (AES) cipher block algorithm to protect the confidentiality of maintenance and diagnostic communications for nonlocal maintenance sessions. |
| ☐ | SV-233210r961563_rule | Vulnerability scanning applications must implement privileged access authorization to all container platform components, containers, and container images for selected organization-defined vulnerability scanning activities. |
| ☐ | SV-233211r961863_rule | The container platform must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. |
| ☐ | SV-233220r1050650_rule | The container platform keystore must implement encryption to prevent unauthorized disclosure of information at rest within the container platform. |
| ☐ | SV-233221r1137646_rule | The container platform runtime must maintain separate execution domains for each container by assigning each container a separate address space. |
| ☐ | SV-233222r961620_rule | The container platform must protect against or limit the effects of all types of denial-of-service (DoS) attacks by employing organization-defined security safeguards. |
| ☐ | SV-233224r961632_rule | The application must protect the confidentiality and integrity of transmitted information. |
| ☐ | SV-233226r961638_rule | The container platform must maintain the confidentiality and integrity of information during preparation for transmission. |
| ☐ | SV-233227r961641_rule | The container platform must maintain the confidentiality and integrity of information during reception. |
| ☐ | SV-233228r961656_rule | The container platform must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. |
| ☐ | SV-233229r961665_rule | The container platform must implement organization-defined security safeguards to protect system CPU and memory from resource depletion and unauthorized code execution. |
| ☐ | SV-233230r961677_rule | The container platform must remove old components after updated versions have been installed. |
| ☐ | SV-233231r961677_rule | The container platform registry must remove old container images after updating versions have been made available. |
| ☐ | SV-233233r1137649_rule | The container platform registry must contain the latest images with most recent security-relevant software updates within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, STIGs). |
| ☐ | SV-233234r1137650_rule | The container platform runtime must have security-relevant software updates installed within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, and STIGs). |
| ☐ | SV-233242r961731_rule | The organization-defined role must verify correct operation of security functions in the container platform. |
| ☐ | SV-233243r961734_rule | The container platform must perform verification of the correct operation of security functions: upon system startup and/or restart; upon command by a user with privileged access; and/or every 30 days. Security functionality includes, but is not limited to, establishing system accounts, configuring access authorizations (i.e., permissions, privileges), setting events to be audited, and setting intrusion detection parameters. |
| ☐ | SV-233244r961737_rule | The container platform must provide system notifications to the system administrator and operational staff when anomalies in the operation of the organization-defined security functions are discovered. |
| ☐ | SV-233252r961791_rule | The container platform must generate audit records when successful/unsuccessful attempts to access security objects occur. |
| ☐ | SV-233253r961794_rule | The container platform must generate audit records when successful/unsuccessful attempts to access security levels occur. |
| ☐ | SV-233254r961797_rule | The container platform must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
| ☐ | SV-233255r961800_rule | The container platform must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
| ☐ | SV-233256r961803_rule | The container platform must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
| ☐ | SV-233257r961806_rule | The container platform must generate audit records when successful/unsuccessful attempts to modify security levels occur. |
| ☐ | SV-233258r961809_rule | The container platform must generate audit records when successful/unsuccessful attempts to modify categories of information (e.g., classification levels) occur. |
| ☐ | SV-233259r961812_rule | The container platform must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
| ☐ | SV-233260r961815_rule | The container platform must generate audit records when successful/unsuccessful attempts to delete security levels occur. |
| ☐ | SV-233261r961818_rule | The container platform must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
| ☐ | SV-233262r961821_rule | The container platform must generate audit records when successful/unsuccessful attempts to delete categories of information (e.g., classification levels) occur. |
| ☐ | SV-233263r961824_rule | The container platform must generate audit records when successful/unsuccessful logon attempts occur. |
| ☐ | SV-233264r961827_rule | The container platform must generate audit record for privileged activities. |
| ☐ | SV-233265r961830_rule | The container platform audit records must record user access start and end times. |
| ☐ | SV-233266r961833_rule | The container platform must generate audit records when concurrent logons from different workstations and systems occur. |
| ☐ | SV-233267r961836_rule | The container platform runtime must generate audit records when successful/unsuccessful attempts to access objects occur. |
| ☐ | SV-233268r961839_rule | Direct access to the container platform must generate audit records. |
| ☐ | SV-233269r961842_rule | The container platform must generate audit records for all account creations, modifications, disabling, and termination events. |
| ☐ | SV-233270r961845_rule | The container runtime must generate audit records for all container execution, shutdown, restart events, and program initiations. |
| ☐ | SV-233271r1137647_rule | The container platform must use a valid FIPS 140-2 or FIPS 140-3 approved cryptographic module to generate hashes. |
| ☐ | SV-233273r961863_rule | Container platform components must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including SRGs, STIGs, NSA configuration guides, CTOs, and DTMs. |
| ☐ | SV-233274r961863_rule | The container platform must be able to store and instantiate industry standard container images. |
| ☐ | SV-233275r961863_rule | The container platform must continuously scan components, containers, and images for vulnerabilities. |
| ☐ | SV-233276r961869_rule | The container platform must prohibit communication using TLS versions 1.0 and 1.1, and SSL 2.0 and 3.0. |
| ☐ | SV-233284r961893_rule | The container platform must validate certificates used for Transport Layer Security (TLS) functions by performing an RFC 5280-compliant certification path validation. |
| ☐ | SV-233285r961896_rule | The container platform must use FIPS-validated SHA-2 or higher hash function for digital signature generation and verification (non-legacy use). |
| ☐ | SV-233289r1137648_rule | The container platform must use a FIPS-validated cryptographic module to implement encryption services for unclassified information requiring confidentiality. |
| ☐ | SV-233290r961911_rule | The container platform must prohibit or restrict the use of protocols that transmit unencrypted authentication information or use flawed cryptographic algorithms for transmission. |
| ☐ | SV-257291r961287_rule | The container platform must enforce organization-defined circumstances and/or usage conditions for organization-defined accounts. |
| ☐ | SV-263586r982453_rule | The container platform must disable accounts when the accounts are no longer associated to a user. |
| ☐ | SV-263587r982455_rule | The container platform must implement the capability to centrally review and analyze audit records from multiple components within the system. |
| ☐ | SV-263588r982457_rule | The container platform must alert organization-defined personnel or roles upon detection of unauthorized access, modification, or deletion of audit information. |
| ☐ | SV-263589r981907_rule | The container platform must implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that one of the factors is provided by a device separate from the system gaining access. |
| ☐ | SV-263590r981910_rule | The container platform must implement multifactor authentication for local; network; and/or remote access to privileged accounts; and/or nonprivileged accounts such that the device meets organization-defined strength of mechanism requirements. |
| ☐ | SV-263591r981913_rule | The container platform must for password-based authentication, maintain a list of commonly used, expected, or compromised passwords on an organization-defined frequency. |
| ☐ | SV-263592r982459_rule | The container platform must for password-based authentication, update the list of passwords on an organization-defined frequency. |
| ☐ | SV-263593r982461_rule | The container platform must for password-based authentication, update the list of passwords when organizational passwords are suspected to have been compromised directly or indirectly. |
| ☐ | SV-263594r982463_rule | The container platform must for password-based authentication, verify when users create or update passwords, that the passwords are not found on the list of commonly-used, expected, or compromised passwords in IA-5 (1) (a). |
| ☐ | SV-263595r982465_rule | The container platform must for password-based authentication, require immediate selection of a new password upon account recovery. |
| ☐ | SV-263596r982467_rule | The container platform must for password-based authentication, allow user selection of long passwords and passphrases, including spaces and all printable characters. |
| ☐ | SV-263597r982469_rule | The container platform must for password-based authentication, employ automated tools to assist the user in selecting strong password authenticators. |
| ☐ | SV-263598r982471_rule | The container platform must protect nonlocal maintenance sessions by separating the maintenance session from other network sessions with the system by logically separated communications paths. |
| ☐ | SV-263599r982473_rule | The container platform must include only approved trust anchors in trust stores or certificate stores managed by the organization. |
| ☐ | SV-263600r982475_rule | The container platform must provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store. |
| ☐ | SV-263601r982477_rule | The container platform must synchronize system clocks within and between systems or system components. |
| ☐ | SV-270875r1050646_rule | The container must have resource request limits set. |
| ☐ | SV-270876r1050649_rule | The container root filesystem must be mounted as read-only. |
| ☐ | SV-278968r1137653_rule | The container platform must be a version supported by the vendor. |
STIGQter: STIG Summary: