| Checked | Name | Title |
|---|
| ☐ | SV-207338r958362_rule | The VMM must provide automated mechanisms for supporting account management functions. |
| ☐ | SV-207339r958364_rule | The VMM must automatically remove or disable local temporary user accounts after 72 hours. |
| ☐ | SV-207340r958366_rule | The VMM must automatically disable local accounts after a 35-day period of account inactivity. |
| ☐ | SV-207341r958368_rule | The VMM must automatically audit account creation. |
| ☐ | SV-207342r958388_rule | The VMM must enforce the limit of three consecutive invalid logon attempts by a user during a 15-minute time period. |
| ☐ | SV-207343r958390_rule | The VMM must display the Standard Mandatory DoD Notice and Consent Banner before granting access to the system. |
| ☐ | SV-207344r958392_rule | The VMM must retain the Standard Mandatory DoD Notice and Consent Banner on the screen until users acknowledge the usage conditions and take explicit actions to log on for further access. |
| ☐ | SV-207345r958398_rule | The VMM must limit the number of concurrent sessions to ten for all accounts and/or account types. |
| ☐ | SV-207346r958400_rule | The VMM must retain the session lock until the user reestablishes access using established identification and authentication procedures. |
| ☐ | SV-207347r958402_rule | The VMM must initiate a session lock after a 15-minute period of inactivity. |
| ☐ | SV-207348r984188_rule | The VMM must provide the capability for users to directly initiate a session lock. |
| ☐ | SV-207349r958404_rule | The VMM must conceal, via the session lock, information previously visible on the display with a publicly viewable image. |
| ☐ | SV-207350r958406_rule | The VMM must monitor remote access methods automatically. |
| ☐ | SV-207351r958408_rule | The VMM must use DoD-approved encryption to protect the confidentiality of remote access sessions. |
| ☐ | SV-207352r958412_rule | The VMM must produce audit records containing information to establish what type of events occurred. |
| ☐ | SV-207353r958414_rule | The VMM must produce audit records containing information to establish when (date and time) the events occurred. |
| ☐ | SV-207354r958416_rule | The VMM must produce audit records containing information to establish where the events occurred. |
| ☐ | SV-207355r958418_rule | The VMM must produce audit records containing information to establish the source of the events. |
| ☐ | SV-207356r958420_rule | The VMM must produce audit records containing information to establish the outcome of the events. |
| ☐ | SV-207357r958422_rule | The VMM must generate audit records containing the full-text recording of privileged commands or the individual identities of group account users. |
| ☐ | SV-207358r958424_rule | The VMM must alert the ISSO and SA (at a minimum) in the event of an audit processing failure. |
| ☐ | SV-207360r958428_rule | The VMM must support the capability to centrally review and analyze audit records from multiple components within the system. |
| ☐ | SV-207361r958430_rule | The VMM must support the capability to filter audit records for events of interest based upon all audit fields within audit records. |
| ☐ | SV-207362r958432_rule | The VMM must use internal system clocks to generate time stamps for audit records. |
| ☐ | SV-207363r958434_rule | The VMM must protect audit information from unauthorized read access. |
| ☐ | SV-207364r958436_rule | The VMM must protect audit information from unauthorized modification. |
| ☐ | SV-207365r958438_rule | The VMM must protect audit information from unauthorized deletion. |
| ☐ | SV-207366r958442_rule | The VMM must provide audit record generation capability for DoD-defined auditable events for all VMM components. |
| ☐ | SV-207367r958444_rule | The VMM must allow only the ISSM (or individuals or roles appointed by the ISSM) to select which auditable events are to be audited. |
| ☐ | SV-207368r958446_rule | The VMM must generate audit records when successful/unsuccessful attempts to access privileges occur. |
| ☐ | SV-207369r958448_rule | The VMM, for PKI-based authentication, must validate certificates by constructing a certification path (which includes status information) to an accepted trust anchor. |
| ☐ | SV-207370r958450_rule | The VMM, for PKI-based authentication, must enforce authorized access to the corresponding private key. |
| ☐ | SV-207371r958452_rule | The VMM must map the authenticated identity to the user or group account for PKI-based authentication. |
| ☐ | SV-207372r984191_rule | The VMM must enforce password complexity by requiring that at least one uppercase character be used. |
| ☐ | SV-207373r984194_rule | The VMM must enforce password complexity by requiring that at least one lowercase character be used. |
| ☐ | SV-207374r984195_rule | The VMM must enforce password complexity by requiring that at least one numeric character be used. |
| ☐ | SV-207375r984198_rule | The VMM must require the change of at least eight of the total number of characters when passwords are changed. |
| ☐ | SV-207376r984199_rule | The VMM must store only encrypted representations of passwords. |
| ☐ | SV-207377r1207724_rule | The VMM must transmit only encrypted representations of passwords. |
| ☐ | SV-207378r984202_rule | The VMM must enforce 24 hours/one day as the minimum password lifetime. |
| ☐ | SV-207379r1038967_rule | The VMM must enforce a 60-day maximum password lifetime restriction. |
| ☐ | SV-207381r984205_rule | The VMM must enforce a minimum 15-character password length. |
| ☐ | SV-207382r958470_rule | The VMM must obscure feedback of authentication information during the authentication process to protect the information from possible exploitation/use by unauthorized individuals. |
| ☐ | SV-207383r1138000_rule | The VMM must enforce approved authorizations for logical access to information and system resources in accordance with applicable access control policies. |
| ☐ | SV-207384r958478_rule | The VMM must be configured to disable non-essential capabilities. |
| ☐ | SV-207385r958480_rule | The VMM must be configured to prohibit or restrict the use of functions, ports, protocols, and/or services, as defined in the PPSM CAL and vulnerability assessments. |
| ☐ | SV-207386r958482_rule | The VMM must uniquely identify and must authenticate organizational users (or processes acting on behalf of organizational users). |
| ☐ | SV-207387r958484_rule | The VMM must use multifactor authentication for network access to privileged accounts. |
| ☐ | SV-207388r958486_rule | The VMM must use multifactor authentication for network access to non-privileged accounts. |
| ☐ | SV-207389r984206_rule | The VMM must use multifactor authentication for local access to privileged accounts. |
| ☐ | SV-207390r984209_rule | The VMM must use multifactor authentication for local access to nonprivileged accounts. |
| ☐ | SV-207391r984210_rule | The VMM must require individuals to be authenticated with an individual authenticator prior to using a group authenticator. |
| ☐ | SV-207392r958494_rule | The VMM must implement replay-resistant authentication mechanisms for network access to privileged accounts. |
| ☐ | SV-207393r984213_rule | The VMM must implement replay-resistant authentication mechanisms for network access to nonprivileged accounts. |
| ☐ | SV-207394r958498_rule | The VMM must uniquely identify peripherals before establishing a connection. |
| ☐ | SV-207395r984214_rule | The VMM must disable local account identifiers (individuals, groups, roles, and devices) after 35 days of inactivity. |
| ☐ | SV-207396r971535_rule | The VMM must use mechanisms meeting the requirements of applicable federal laws, Executive Orders, directives, policies, regulations, standards, and guidance for authentication to a cryptographic module. |
| ☐ | SV-207397r958506_rule | The VMM must support an audit reduction capability that supports on-demand reporting requirements. |
| ☐ | SV-207398r958508_rule | The VMM must automatically remove or disable emergency accounts after the crisis is resolved or 72 hours. |
| ☐ | SV-207399r958510_rule | The VMM must employ strong authenticators in the establishment of nonlocal maintenance and diagnostic sessions. |
| ☐ | SV-207401r1138001_rule | The VMM must separate user functionality (including user interface services) from VMM management functionality. |
| ☐ | SV-207402r958518_rule | The VMM must isolate security functions from non-security functions. |
| ☐ | SV-207403r1138002_rule | The VMM must prevent unauthorized and unintended information transfer via shared system resources. |
| ☐ | SV-207404r958528_rule | The VMM must manage excess capacity, bandwidth, or other redundancy to limit the effects of information-flooding types of Denial of Service (DoS) attacks. |
| ☐ | SV-207405r970703_rule | The VMM 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; and for user sessions (non-privileged session), the session must be terminated after 15 minutes of inactivity, except to fulfill documented and validated mission requirements. |
| ☐ | SV-207406r958550_rule | The VMM must fail to a secure state if system initialization fails, shutdown fails, or aborts fail. |
| ☐ | SV-207407r958552_rule | The VMM must protect the confidentiality and integrity of all information at rest. |
| ☐ | SV-207409r958562_rule | The VMM must check the validity of all data inputs except those specifically identified by the organization. |
| ☐ | SV-207410r958564_rule | The VMM must generate error messages that provide information necessary for corrective actions without revealing information that could be exploited by adversaries. |
| ☐ | SV-207411r958566_rule | The VMM must reveal system error messages only to authorized users. |
| ☐ | SV-207412r1138003_rule | All interactions among guest VMs must be mediated by the VMM or its service VMs to support proper function. |
| ☐ | SV-207413r958590_rule | The VMM must automatically audit account modification. |
| ☐ | SV-207414r958592_rule | The VMM must automatically audit account disabling actions. |
| ☐ | SV-207415r958594_rule | The VMM must automatically audit account removal actions. |
| ☐ | SV-207416r1117269_rule | All guest VM network communications must be implemented through use of virtual network devices provisioned by the VMM. |
| ☐ | SV-207417r1138004_rule | All interactions between guest VMs and external systems, via other interface devices, must be mediated by the VMM or its service VMs. |
| ☐ | SV-207418r958604_rule | The VMM must implement cryptography to protect the integrity of remote access sessions. |
| ☐ | SV-207419r958606_rule | The VMM must initiate session audits at system startup. |
| ☐ | SV-207420r958608_rule | The VMM must produce audit records containing information to establish the identity of any individual or process associated with the event. |
| ☐ | SV-207421r958610_rule | The VMM must protect audit tools from unauthorized access. |
| ☐ | SV-207422r958612_rule | The VMM must protect audit tools from unauthorized modification. |
| ☐ | SV-207423r958614_rule | The VMM must protect audit tools from unauthorized deletion. |
| ☐ | SV-207424r958616_rule | The VMM must limit privileges to change software resident within software libraries. |
| ☐ | SV-207425r984219_rule | The VMM must enforce password complexity by requiring that at least one special character be used. |
| ☐ | SV-207426r958624_rule | In the event of a system failure, the VMM must preserve any information necessary to determine cause of failure and any information necessary to return to operations with least disruption to mission processes. |
| ☐ | SV-207427r984222_rule | The VMM must notify system administrators (SAs) and information system security officers (ISSOs) when accounts are created. |
| ☐ | SV-207428r984225_rule | The VMM must notify the system administrator (SA) and information system security officer (ISSO) when accounts are modified. |
| ☐ | SV-207429r984228_rule | The VMM must notify the system administrator (SA) and information system security officer (ISSO) when accounts are disabled. |
| ☐ | SV-207430r984231_rule | The VMM must notify the system administrator (SA) and information system security officer (ISSO) when accounts are removed. |
| ☐ | SV-207431r958634_rule | The VMM must use cryptographic mechanisms to protect the integrity of audit tools. |
| ☐ | SV-207432r958636_rule | The VMM must automatically terminate a user session after inactivity timeouts have expired or at shutdown. |
| ☐ | SV-207433r958638_rule | VMMs requiring user access authentication must provide a logout capability for user-initiated communications sessions. |
| ☐ | SV-207434r958640_rule | The VMM must display an explicit logout message to users indicating the reliable termination of authenticated communications sessions. |
| ☐ | SV-207435r958672_rule | The VMM must control remote access methods. |
| ☐ | SV-207436r958674_rule | The VMM must provide the capability to immediately disconnect or disable remote access to the information system. |
| ☐ | SV-207437r958676_rule | The VMM must protect wireless access to the system using encryption. |
| ☐ | SV-207438r958678_rule | The VMM must protect wireless access to the system using authentication of users and/or devices. |
| ☐ | SV-207439r958684_rule | The VMM must automatically audit account enabling actions. |
| ☐ | SV-207440r984234_rule | The VMM must notify the system administrator (SA) and information system security officer (ISSO) of account enabling actions. |
| ☐ | SV-207441r958702_rule | The VMM must implement discretionary access controls to allow VMM admins to pass information to any other VMM admin, user, or guest VM. |
| ☐ | SV-207442r958702_rule | The VMM must implement discretionary access controls to allow VMM admins to grant their privileges to other VMM admins. |
| ☐ | SV-207443r958702_rule | The VMM must implement discretionary access controls to allow VMM admins to change security attributes on users, guest VMs, the VMM, or the VMMs components. |
| ☐ | SV-207444r958702_rule | The VMM must implement discretionary access controls to allow VMM admins to choose the security attributes to be associated with newly created or revised guest VMs. |
| ☐ | SV-207445r958726_rule | The VMM must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures. |
| ☐ | SV-207446r958730_rule | The VMM must prevent all software from executing at higher privilege levels than users executing the software. |
| ☐ | SV-207447r958732_rule | The VMM must audit the execution of privileged functions. |
| ☐ | SV-207448r958736_rule | The VMM must automatically lock an account until the locked account is released by an administrator, when three unsuccessful logon attempts in 15 minutes are made. |
| ☐ | SV-207449r971541_rule | The VMM must provide the capability for assigned IMOs/ISSOs or designated SAs to change the auditing to be performed on all VMM components, based on all selectable event criteria in near real time. |
| ☐ | SV-207452r958752_rule | The VMM must allocate audit record storage capacity to store at least one weeks worth of audit records when audit records are not immediately sent to a central audit record storage facility. |
| ☐ | SV-207453r958754_rule | The VMM must off-load audit records onto a different system or media than the system being audited. |
| ☐ | SV-207454r971542_rule | The VMM must provide an immediate warning to the SA and ISSO, at a minimum, when allocated audit record storage volume reaches 75% of repository maximum audit record storage capacity. |
| ☐ | SV-207455r958758_rule | The VMM 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-207456r958766_rule | The VMM must provide an audit reduction capability that supports on-demand audit review and analysis. |
| ☐ | SV-207457r958768_rule | The VMM must provide an audit reduction capability that supports after-the-fact investigations of security incidents. |
| ☐ | SV-207458r958770_rule | The VMM must provide a report generation capability that supports on-demand audit review and analysis. |
| ☐ | SV-207459r958772_rule | The VMM must provide a report generation capability that supports on-demand reporting requirements. |
| ☐ | SV-207460r958774_rule | The VMM must provide a report generation capability that supports after-the-fact investigations of security incidents. |
| ☐ | SV-207461r958776_rule | The VMM that provides an audit reduction capability must not alter original content or time ordering of audit records. |
| ☐ | SV-207462r987795_rule | The VMM that provides a report generation capability must not alter original content or time ordering of audit records. |
| ☐ | SV-207463r1038976_rule | The VMM must, for networked systems, compare internal information system clocks at least every 24 hours with an authoritative time source. |
| ☐ | SV-207464r984238_rule | The VMM must synchronize internal information system clocks to the authoritative time source when the time difference is greater than one second. |
| ☐ | SV-207465r958786_rule | The VMM must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision. |
| ☐ | SV-207466r958788_rule | The VMM must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). |
| ☐ | SV-207467r958790_rule | The VMM must enforce dual authorization for movement and/or deletion of all audit information, when such movement or deletion is not part of an authorized automatic process. |
| ☐ | SV-207468r984239_rule | The VMM must prohibit user installation of software without explicit privileged status. |
| ☐ | SV-207469r958794_rule | The VMM must notify designated personnel if baseline configurations are changed in an unauthorized manner. |
| ☐ | SV-207470r958796_rule | The VMM must enforce access restrictions associated with changes to the system. |
| ☐ | SV-207471r984240_rule | The VMM must audit the enforcement actions used to restrict access associated with changes to the system. |
| ☐ | SV-207472r984242_rule | The VMM must prevent the installation of guest VMs, patches, service packs, device drivers, or VMM components without verification they have been digitally signed using a certificate that is recognized and approved by the organization. |
| ☐ | SV-207473r958804_rule | The VMM must prevent use of service and helper VMs not required to support proper VMM function. |
| ☐ | SV-207474r958804_rule | The VMM must prevent inappropriate use of redundant guest VMs. |
| ☐ | SV-207475r958808_rule | The VMM must employ a deny-all, permit-by-exception policy to allow the execution of authorized software programs and guest VMs. |
| ☐ | SV-207480r984255_rule | The VMM must implement multifactor authentication for remote access to privileged accounts such that one of the factors is provided by a device separate from the system gaining access. |
| ☐ | SV-207481r958816_rule | The VMM must accept Personal Identity Verification (PIV) credentials. |
| ☐ | SV-207482r958818_rule | The VMM must electronically verify Personal Identity Verification (PIV) credentials. |
| ☐ | SV-207483r958820_rule | The VMM must authenticate peripherals before establishing a connection. |
| ☐ | SV-207484r971545_rule | The VMM must authenticate all endpoint devices before establishing a local, remote, and/or network connection using bidirectional authentication that is cryptographically based. |
| ☐ | SV-207486r958828_rule | The VMM must prohibit the use of cached authenticators after one day. |
| ☐ | SV-207487r984257_rule | The VMM, 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-207488r987791_rule | The VMM must implement NSA-approved cryptography to protect classified information in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. |
| ☐ | SV-207489r958860_rule | The VMM must request data origin authentication verification on the name/address resolution responses the system receives from authoritative sources. |
| ☐ | SV-207490r958862_rule | The VMM must request data integrity verification on the name/address resolution responses the system receives from authoritative sources. |
| ☐ | SV-207491r958864_rule | The VMM must perform data integrity verification on the name/address resolution responses the system receives from authoritative sources. |
| ☐ | SV-207492r958866_rule | The VMM must perform data origin verification authentication on the name/address resolution responses the system receives from authoritative sources. |
| ☐ | SV-207493r958868_rule | The VMM must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions. |
| ☐ | SV-207494r1207725_rule | The VMM must implement cryptographic mechanisms to prevent unauthorized modification of all information at rest on all VMM components. |
| ☐ | SV-207495r958872_rule | The VMM must implement cryptographic mechanisms to prevent unauthorized disclosure of all information at rest on all VMM components. |
| ☐ | SV-207496r1117274_rule | The VMM must maintain a separate execution domain for each executing process. |
| ☐ | SV-207497r1138013_rule | The VMM must maintain a separate execution domain for each guest VM. |
| ☐ | SV-207498r958902_rule | The VMM must protect against or limit the effects of Denial of Service (DoS) attacks by ensuring the VMM is implementing rate-limiting measures on impacted network interfaces. |
| ☐ | SV-207499r958908_rule | The VMM must protect the confidentiality and integrity of transmitted information. |
| ☐ | SV-207500r958912_rule | The VMM must maintain the confidentiality and integrity of information during preparation for transmission. |
| ☐ | SV-207501r958914_rule | The VMM must maintain the confidentiality and integrity of information during reception. |
| ☐ | SV-207502r958926_rule | The VMM must behave in a predictable and documented manner that reflects organizational and system objectives when invalid inputs are received. |
| ☐ | SV-207503r958928_rule | The VMM must implement non-executable data to protect its memory from unauthorized code execution. |
| ☐ | SV-207504r958928_rule | The VMM must implement address space layout randomization to protect its memory from unauthorized code execution. |
| ☐ | SV-207505r958936_rule | The VMM must remove all software components after updated versions have been installed. |
| ☐ | SV-207506r958944_rule | The VMM must verify correct operation of all security functions. |
| ☐ | SV-207507r958946_rule | The VMM 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. |
| ☐ | SV-207508r958948_rule | The VMM must shut down, restart, and/or notify the system administrator when anomalies in the operation of any security functions are discovered. |
| ☐ | SV-207509r958968_rule | The VMM must generate audit records when successful/unsuccessful attempts to access security objects occur. |
| ☐ | SV-207510r958970_rule | The VMM must generate audit records when successful/unsuccessful attempts to access security levels occur. |
| ☐ | SV-207511r958972_rule | The VMM must generate audit records when successful/unsuccessful attempts to access categories of information (e.g., classification levels) occur. |
| ☐ | SV-207512r958974_rule | The VMM must generate audit records when successful/unsuccessful attempts to modify privileges occur. |
| ☐ | SV-207513r958976_rule | The VMM must generate audit records when successful/unsuccessful attempts to modify security objects occur. |
| ☐ | SV-207514r958978_rule | The VMM must generate audit records when successful/unsuccessful attempts to modify security levels occur. |
| ☐ | SV-207515r958982_rule | The VMM must generate audit records when successful/unsuccessful attempts to delete privileges occur. |
| ☐ | SV-207516r958984_rule | The VMM must generate audit records when successful/unsuccessful attempts to delete security levels occur. |
| ☐ | SV-207517r958986_rule | The VMM must generate audit records when successful/unsuccessful attempts to delete security objects occur. |
| ☐ | SV-207518r958990_rule | The VMM must generate audit records when successful/unsuccessful logon attempts occur. |
| ☐ | SV-207519r958992_rule | The VMM must generate audit records for privileged activities or other system-level access. |
| ☐ | SV-207520r958994_rule | The VMM must generate audit records showing starting and ending time for user access to the system. |
| ☐ | SV-207521r958996_rule | The VMM must generate audit records when concurrent logons from different workstations occur. |
| ☐ | SV-207522r958998_rule | The VMM must generate audit records when successful/unsuccessful accesses to objects occur. |
| ☐ | SV-207523r959000_rule | The VMM must generate audit records for all direct access to the VMM. |
| ☐ | SV-207524r959002_rule | The VMM must generate audit records for all account creations, modifications, disabling, and termination events. |
| ☐ | SV-207525r959004_rule | The VMM must generate audit records for all module load, unload, and restart actions, and also for all program and guest VM initiations. |
| ☐ | SV-207526r1138009_rule | The VMM must implement NIST FIPS-validated cryptography for the following: to provision digital signatures; to generate cryptographic hashes; and to protect unclassified information requiring confidentiality and cryptographic protection in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. |
| ☐ | SV-207527r959008_rule | The VMM must, at a minimum, off-load interconnected systems in real time and off-load standalone systems weekly. |
| ☐ | SV-207528r959010_rule | The VMM must be configured in accordance with the security configuration settings based on DoD security configuration or implementation guidance, including STIGs, NSA configuration guides, CTOs, and DTMs. |
| ☐ | SV-207529r958358_rule | The VMM must protect the confidentiality and integrity of communications with wireless peripherals. |
| ☐ | SV-264315r984260_rule | The VMM must disable accounts when the accounts are no longer associated to a user. |
| ☐ | SV-264316r984263_rule | The VMM must prohibit the use or connection of unauthorized hardware components. |
| ☐ | SV-264317r984266_rule | The VMM 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-264318r984269_rule | The VMM must for password-based authentication, verify when users create or update passwords the passwords are not found on the list of commonly-used, expected, or compromised passwords in ia-5 (1) (a). |
| ☐ | SV-264319r984272_rule | The VMM must for password-based authentication, require immediate selection of a new password upon account recovery. |
| ☐ | SV-264320r984275_rule | The VMM must for password-based authentication, allow user selection of long passwords and passphrases, including spaces and all printable characters. |
| ☐ | SV-264321r984278_rule | The VMM must for password-based authentication, employ automated tools to assist the user in selecting strong password authenticators. |
| ☐ | SV-264322r984281_rule | The VMM must accept only external credentials that are NIST-compliant. |
| ☐ | SV-264323r984284_rule | The VMM must monitor the use of maintenance tools that execute with increased privilege. |
| ☐ | SV-264324r984287_rule | The VMM must include only approved trust anchors in trust stores or certificate stores managed by the organization. |
| ☐ | SV-264325r984290_rule | The VMM must provide protected storage for cryptographic keys with organization-defined safeguards and/or hardware protected key store. |
| ☐ | SV-264326r984293_rule | The VMM must synchronize system clocks within and between systems or system components. |
| ☐ | SV-279013r1227261_rule | The VMM must enforce a role-based access control (RBAC) policy over defined subjects and objects. |
| ☐ | SV-279014r1138012_rule | The VMM must use a FIPS-validated cryptographic module to provision digital signatures. |
| ☐ | SV-279015r1227262_rule | The VMM must enforce attribute-based access control policy over defined subjects and objects based upon organization-defined attributes to assume access permissions. |
| ☐ | SV-279016r1138019_rule | The VMM must install security-relevant software updates within 30 days unless the time period is directed by an authoritative source (e.g., IAVM, CTOs, DTMs, STIGs). |
| ☐ | SV-279017r1138022_rule | The VMM must be a version supported by the vendor. |
STIGQter: STIG Summary: