CA API Gateway NDM 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]

Details

Version / Release: V1R1

Published: 2016-09-20

Updated At: 2018-09-23 19:12:37

Actions

Download

Filter


Findings
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-86143r1_rule CAGW-DM-000100 CCI-000366 HIGH The CA API Gateway must be installed on Red Hat Enterprise Linux (RHEL) Version 6.7 or higher. The API Gateway (Appliance version) depends on specific RHEL capabilities for the security, logging, and auditing subsystems. Installation on alternative or older RHEL versions may create vulnerabilities.
    SV-86145r1_rule CAGW-DM-000110 CCI-000366 MEDIUM The CA API Gateway must employ RADIUS + LDAPS or LDAPS to centrally manage authentication settings. The use of authentication servers or other centralized management servers for providing centralized authentication services is required for network device management. Maintaining local administrator accounts for daily usage on each network device without
    SV-86147r1_rule CAGW-DM-000120 CCI-000140 MEDIUM The CA API Gateway must shut down by default upon audit failure (unless availability is an overriding concern). It is critical that when the network device is at risk of failing to process audit logs as required, it take action to mitigate the failure. Audit processing failures include: software/hardware errors; failures in the audit capturing mechanisms; and audit
    SV-86149r1_rule CAGW-DM-000130 CCI-001348 LOW The CA API Gateway must forward all log audit log messages to the central log server. Protection of log data includes assuring log data is not accidentally lost or deleted. Regularly backing up audit records to a different system or onto separate media than the system being audited helps to assure, in the event of a catastrophic system fai
    SV-86151r1_rule CAGW-DM-000140 CCI-002041 MEDIUM The CA API Gateway must not have any default manufacturer passwords when deployed. Network devices not protected with strong password schemes provide the opportunity for anyone to crack the password and gain access to the device, which can result in loss of availability, confidentiality, or integrity of network traffic. Many default v
    SV-86153r1_rule CAGW-DM-000150 CCI-001358 MEDIUM In the event the authentication server is unavailable, there must be one local account of last resort. Authentication for administrative (privileged-level) access to the device is required at all times. An account can be created on the device's local database for use in an emergency, such as when the authentication server is down or connectivity between th
    SV-86155r1_rule CAGW-DM-000160 CCI-000205 MEDIUM The CA API Gateway must enforce a minimum 15-character password length. Password complexity, or strength, is a measure of the effectiveness of a password in resisting attempts at guessing and brute-force attacks. Password length is one factor of several that helps to determine strength and how long it takes to crack a passwor
    SV-86157r1_rule CAGW-DM-000170 CCI-000195 MEDIUM If multifactor authentication is not supported and passwords must be used, the CA API Gateway must require that when a password is changed, the characters are changed in at least 8 of the positions within the password. If the application allows the user to consecutively reuse extensive portions of passwords, this increases the chances of password compromise by increasing the window of opportunity for attempts at guessing and brute-force attacks. The number of changed c
    SV-86159r1_rule CAGW-DM-000180 CCI-001682 MEDIUM The CA API Gateway must automatically remove or disable emergency accounts, except the emergency administration account, after 72 hours. Emergency accounts are administrator accounts which are established in response to crisis situations where the need for rapid account activation is required. Therefore, emergency account activation may bypass normal account authorization processes. If e
    SV-86161r1_rule CAGW-DM-000190 CCI-000366 MEDIUM The CA API Gateway must activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected. Predictable failure prevention requires organizational planning to address device failure issues. If components key to maintaining the device's security fail to function, the device could continue operating in an insecure state. If appropriate actions are
    SV-86163r1_rule CAGW-DM-000200 CCI-002132 MEDIUM The CA API Gateway must notify System Administrators (SAs) and Information System Security Officers (ISSMs) when accounts are created, or enabled when previously disabled. Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of reestablishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of account
    SV-86165r1_rule CAGW-DM-000210 CCI-000366 MEDIUM The CA API Gateway must transmit organization-defined access authorization information using organization-defined security safeguards to organization-defined information systems which enforce access control decisions. Protecting access authorization information (i.e., access control decisions) ensures that authorization information cannot be altered, spoofed, or otherwise compromised during transmission. In distributed information systems, authorization processes and
    SV-86167r1_rule CAGW-DM-000220 CCI-000366 LOW The CA API Gateway must be configured to synchronize internal information system clocks with the primary and secondary time sources located in different geographic regions using redundant authoritative time sources. The loss of connectivity to a particular authoritative time source will result in the loss of time synchronization (free-run mode) and increasingly inaccurate time stamps on audit events and other functions. Multiple time sources provide redundancy by i
    SV-86169r1_rule CAGW-DM-000230 CCI-001890 LOW The CA API Gateway must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT). If time stamps are not consistently applied and there is no common time reference, it is difficult to perform forensic analysis. Time stamps generated by the application include date and time. Time is commonly expressed in Coordinated Universal Time (UTC
    SV-86171r1_rule CAGW-DM-000240 CCI-001889 LOW The CA API Gateway must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision. Without sufficient granularity of time stamps, it is not possible to adequately determine the chronological order of records. Time stamps generated by the application include date and time. Granularity of time measurements refers to the degree of synchron
    SV-86173r1_rule CAGW-DM-000250 CCI-001811 MEDIUM The CA API Gateway must generate an alert that will then be sent to the ISSO, ISSM, and other designated personnel (deemed appropriate by the local organization) when the unauthorized installation of software is detected. Unauthorized software not only increases risk by increasing the number of potential vulnerabilities, it also can contain malicious code. Sending an alert (in real time) when unauthorized software is detected allows designated personnel to take action on t
    SV-86175r1_rule CAGW-DM-000260 CCI-001967 LOW The CA API Gateway must authenticate NTP endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based. Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of gre
    SV-86177r1_rule CAGW-DM-000270 CCI-001967 MEDIUM The CA API Gateway must authenticate SNMP endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based. Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of gre
    SV-86179r1_rule CAGW-DM-000280 CCI-001967 MEDIUM The CA API Gateway must authenticate RADIUS endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based. Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of gre
    SV-86181r1_rule CAGW-DM-000290 CCI-001967 MEDIUM The CA API Gateway must authenticate LDAPS endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based. Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of gre
    SV-86183r1_rule CAGW-DM-000300 CCI-001967 MEDIUM The CA API Gateway must obtain LDAPS server certificates securely to use bidirectional authentication that is cryptographically based. Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of gre
    SV-86185r1_rule CAGW-DM-000310 CCI-002385 MEDIUM The CA API Gateway must protect against or limit the effects of all known types of Denial of Service (DoS) attacks on the CA API Gateway management network by employing organization-defined security safeguards. DoS is a condition when a resource is not available for legitimate users. When this occurs, the organization either cannot accomplish its mission or must operate at degraded capacity. This requirement addresses the configuration of network devices to mit
    SV-86187r1_rule CAGW-DM-000320 CCI-000172 MEDIUM The CA API Gateway must generate audit records when successful/unsuccessful logon attempts occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor
    SV-86189r1_rule CAGW-DM-000330 CCI-000172 MEDIUM The CA API Gateway must generate audit records showing starting and ending time for administrator access to the system. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit reco
    SV-86191r1_rule CAGW-DM-000340 CCI-000172 MEDIUM The CA API Gateway must generate audit records when concurrent logons from different workstations occur. Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit recor
    SV-86193r1_rule CAGW-DM-000350 CCI-001851 LOW The CA API Gateway must off-load audit records onto a different system or media than the system being audited. Information stored in one location is vulnerable to accidental or incidental deletion or alteration. Off-loading is a common process in information systems with limited audit storage capacity.
    SV-86195r1_rule CAGW-DM-000360 CCI-000366 MEDIUM The CA API Gateway must generate audit log events for a locally developed list of auditable events. Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack; to recognize resource utilization or capacity thresholds; or to identify an improperly configured netwo
    SV-86197r1_rule CAGW-DM-000400 CCI-000366 MEDIUM The CA API Gateway must employ automated mechanisms to assist in the tracking of security incidents. Despite the investment in perimeter defense technologies, enclaves are still faced with detecting, analyzing, and remediating network breaches and exploits that have made it past the network device. An automated incident response infrastructure allows net
    SV-86199r1_rule CAGW-DM-000370 CCI-000366 MEDIUM The CA API Gateway must employ automated mechanisms to detect the addition of unauthorized components or devices. This requirement addresses configuration management of the network device. The network device must automatically detect the installation of unauthorized software or hardware onto the device itself. Monitoring may be accomplished on an ongoing basis or by