AvePoint DocAve 6 Security Technical Implementation Guide

Overview

VersionDateFinding Count (9)Downloads
12022-08-24CAT I (High): 3CAT II (Medium): 6CAT III (Low): 0
STIG Description
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: disa.stig_spt@mail.mil.
ClassifiedPublicSensitive
I - Mission Critical ClassifiedI - Mission Critical PublicI - Mission Critical Sensitive
II - Mission Support ClassifiedII - Mission Support PublicII - Mission Support Sensitive
III - Administrative ClassifiedIII - Administrative PublicIII - Administrative Sensitive

Findings - MAC II - Mission Support Public

Finding IDSeverityTitleDescription
V-253510
LOWMEDIUMHIGH
DocAve 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 allow...
V-253511
LOWMEDIUMHIGH
DocAve must initiate a session lock 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 syst...
V-253513
LOWMEDIUMHIGH
DocAve 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) co...
V-253514
LOWMEDIUMHIGH
DocAve 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...
V-253517
LOWMEDIUMHIGH
DocAve must control remote access methods.Remote access applications, such as those providing remote access to network devices and information systems, which lack automated control capabilitie...
V-253518
LOWMEDIUMHIGH
DocAve must only allow the use of DoD PKI-established certificate authorities for verification of the establishment of protected sessions.Untrusted Certificate Authorities (CA) can issue certificates, but they may be issued by organizations or individuals that seek to compromise DoD syst...
V-253512
LOWMEDIUMHIGH
DocAve 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 explo...
V-253515
LOWMEDIUMHIGH
DocAve 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 ...
V-253516
LOWMEDIUMHIGH
The underlying IIS platform must be configured for Smart Card (CAC) Authorization.Without the use of multifactor authentication, the ease of access to privileged functions is greatly increased. Multifactor authentication requires ...