AvePoint Compliance Guardian Security Technical Implementation Guide


This Security Technical Implementation Guide is published as a tool to improve the security of Department of Defense (DOD) information systems. The requirements are derived from the National Institute of Standards and Technology (NIST) 800-53 and related documents. Comments or proposed revisions to this document should be sent via email to the following address: [email protected].


Version / Release: V1R1

Published: 2023-02-21

Updated At: 2023-05-04 00:32:51




Severity Open Not Reviewed Not Applicable Not a Finding
Overall 0 0 0 0
Low 0 0 0 0
Medium 0 0 0 0
High 0 0 0 0
Drop CKL or SCAP (XCCDF) results here.

    Vuln Rule Version CCI Severity Title Description Status Finding Details Comments
    SV-256839r890127_rule APCG-00-000001 CCI-000054 MEDIUM Compliance Guardian must limit the number of concurrent sessions to an organization-defined number for all accounts and/or account types. Application management includes the ability to control the number of users and user sessions that utilize an application. Limiting the number of allowed users and sessions per user is helpful in limiting risks related to DoS attacks. This requirement may
    SV-256840r890130_rule APCG-00-000005 CCI-000057 MEDIUM Compliance Guardian must initiate a session timeout after a 15-minute period of inactivity. A session time-out lock is a temporary action taken when a user stops work and moves away from the immediate physical vicinity of the information system but does not log out because of the temporary nature of the absence. Rather than relying on the user t
    SV-256841r890133_rule APCG-00-000010 CCI-000068 HIGH Compliance Guardian must use TLS 1.2, at a minimum, to protect the confidentiality of sensitive data during electronic dissemination using remote access. Using older unauthorized versions or incorrectly configuring protocol negotiation makes the gateway vulnerable to known and unknown attacks that exploit vulnerabilities in this protocol. This requirement applies to Transport Layer Security (TLS) gateways
    SV-256842r890136_rule APCG-00-000015 CCI-000015 MEDIUM Compliance Guardian must provide automated mechanisms for supporting account management functions. Remote access (e.g., Remote Desktop Protocol [RDP]) is access to DOD nonpublic information systems by an authorized user (or an information system) communicating through an external, nonorganization-controlled network. Remote access methods include dial-u
    SV-256843r890139_rule APCG-00-000020 CCI-000382 MEDIUM Compliance Guardian 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. In order to prevent unauthorized connection of devices, unauthorized transfer of information, or unauthorized tunneling (i.e., embedding of data types within data types), organizations must disable or restrict unused or unnecessary physical and logical po
    SV-256844r890142_rule APCG-00-000025 CCI-000187 HIGH Compliance Guardian must use multifactor authentication for network access to privileged accounts. Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires using two or more factors to achieve authentication. Factors include: (i) Something a user knows (e.g.,
    SV-256845r890145_rule APCG-00-000030 CCI-002314 MEDIUM Compliance Guardian must control remote access methods. Remote access applications (such as those providing remote access to network devices and information systems) which lack automated control capabilities, increase risk, and make remote user access management difficult at best. Remote access is access to D
    SV-256846r890148_rule APCG-00-000035 CCI-002011 MEDIUM Compliance Guardian must accept FICAM-approved third-party credentials. Access may be denied to legitimate users if FICAM-approved third-party credentials are not accepted. This requirement typically applies to organizational information systems that are accessible to nonfederal government agencies and other partners. This
    SV-256847r890151_rule APCG-00-000040 CCI-002014 MEDIUM Compliance Guardian must conform to FICAM-issued profiles. Without conforming to FICAM-issued profiles, the information system may not be interoperable with FICAM-authentication protocols, such as SAML 2.0 and OpenID 2.0. This requirement addresses open identity management standards.
    SV-256848r890154_rule APCG-00-000045 CCI-002470 MEDIUM Compliance Guardian must only allow the use of DOD PKI established certificate authorities for verification of the establishment of protected sessions. Untrusted Certificate Authorities (CAs) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DOD systems or by organizations with insufficient security controls. If the CA used for verifying the certificat