STIGhubSTIGhub
STIGsSearchCompareAbout

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • VPAT
  • DISA STIG Library
STIGs updated 2 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to STIGs

CA API Gateway NDM Security Technical Implementation Guide

Version

V1R2

Release Date

Jun 4, 2024

SCAP Benchmark ID

CA_API_Gateway_NDM_STIG

Total Checks

30

Tags

other
CAT I: 2CAT II: 22CAT III: 6

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.

Export CKLExport CSVExport JSONDownload STIG ZIP

Checks (30)

V-255500HIGHThe CA API Gateway must be installed on Red Hat Enterprise Linux (RHEL) Version 6.7 or higher.V-255501MEDIUMThe CA API Gateway must employ RADIUS + LDAPS or LDAPS to centrally manage authentication settings.V-255502MEDIUMThe CA API Gateway must shut down by default upon audit failure (unless availability is an overriding concern).V-255503LOWThe CA API Gateway must forward all log audit log messages to the central log server.V-255504MEDIUMThe CA API Gateway must not have any default manufacturer passwords when deployed.V-255505MEDIUMIn the event the authentication server is unavailable, there must be one local account of last resort.V-255506MEDIUMThe CA API Gateway must enforce a minimum 15-character password length.V-255507MEDIUMIf 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.V-255508MEDIUMThe CA API Gateway must automatically remove or disable emergency accounts, except the emergency administration account, after 72 hours.V-255509MEDIUMThe CA API Gateway must activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected.V-255510MEDIUMThe CA API Gateway must notify System Administrators (SAs) and Information System Security Officers (ISSMs) when accounts are created, or enabled when previously disabled.V-255511MEDIUMThe 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.V-255512LOWThe 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.V-255513LOWThe CA API Gateway must record time stamps for audit records that can be mapped to Coordinated Universal Time (UTC) or Greenwich Mean Time (GMT).V-255514LOWThe CA API Gateway must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.V-255515MEDIUMThe 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.V-255516LOWThe CA API Gateway must authenticate NTP endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based.V-255517MEDIUMThe CA API Gateway must authenticate SNMP endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based.V-255518MEDIUMThe CA API Gateway must authenticate RADIUS endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based.V-255519MEDIUMThe CA API Gateway must authenticate LDAPS endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based.V-255520MEDIUMThe CA API Gateway must obtain LDAPS server certificates securely to use bidirectional authentication that is cryptographically based.V-255521MEDIUMThe 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.V-255522MEDIUMThe CA API Gateway must generate audit records when successful/unsuccessful logon attempts occur.V-255523MEDIUMThe CA API Gateway must generate audit records showing starting and ending time for administrator access to the system.V-255524MEDIUMThe CA API Gateway must generate audit records when concurrent logons from different workstations occur.V-255525LOWThe CA API Gateway must off-load audit records onto a different system or media than the system being audited.V-255526MEDIUMThe CA API Gateway must generate audit log events for a locally developed list of auditable events.V-255527MEDIUMThe CA API Gateway must employ automated mechanisms to detect the addition of unauthorized components or devices.V-255528MEDIUMThe CA API Gateway must employ automated mechanisms to assist in the tracking of security incidents.V-264435HIGHThe CA API NDM must be using a version supported by the vendor.