What changed in CA API Gateway NDM STIG V1R2V1R2 changes

CA API Gateway NDM STIG V1R2 (2024-07-24) replaced V1R1 (2016-09-19): 30 checks added, 29 removed. It has 30 checks, against 29 in V1R1.

V1R2 checklistV1R1 checklist Compare V1R1 and V1R2 in STIG Compare

  • 30 added
  • 29 removed
  • 0 updated

Added in V1R2 (30)

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

Removed since V1R1 (29)

  • V-71519CAT IThe CA API Gateway must be installed on Red Hat Enterprise Linux (RHEL) Version 6.7 or higher.
  • V-71521CAT IIThe CA API Gateway must employ RADIUS + LDAPS or LDAPS to centrally manage authentication settings.
  • V-71523CAT IIThe CA API Gateway must shut down by default upon audit failure (unless availability is an overriding concern).
  • V-71525CAT IIIThe CA API Gateway must forward all log audit log messages to the central log server.
  • V-71527CAT IIThe CA API Gateway must not have any default manufacturer passwords when deployed.
  • V-71529CAT IIIn the event the authentication server is unavailable, there must be one local account of last resort.
  • V-71531CAT IIThe CA API Gateway must enforce a minimum 15-character password length.
  • V-71533CAT IIIf 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-71535CAT IIThe CA API Gateway must automatically remove or disable emergency accounts, except the emergency administration account, after 72 hours.
  • V-71537CAT IIThe CA API Gateway must activate a system alert message, send an alarm, and/or automatically shut down when a component failure is detected.
  • V-71539CAT IIThe CA API Gateway must notify System Administrators (SAs) and Information System Security Officers (ISSMs) when accounts are created, or enabled when previously disabled.
  • V-71541CAT IIThe 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-71543CAT IIIThe 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-71545CAT IIIThe 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-71547CAT IIIThe CA API Gateway must record time stamps for audit records that meet a granularity of one second for a minimum degree of precision.
  • V-71549CAT IIThe 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-71551CAT IIIThe CA API Gateway must authenticate NTP endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based.
  • V-71553CAT IIThe CA API Gateway must authenticate SNMP endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based.
  • V-71555CAT IIThe CA API Gateway must authenticate RADIUS endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based.
  • V-71557CAT IIThe CA API Gateway must authenticate LDAPS endpoint devices before establishing a network connection using bidirectional authentication that is cryptographically based.
  • V-71559CAT IIThe CA API Gateway must obtain LDAPS server certificates securely to use bidirectional authentication that is cryptographically based.
  • V-71561CAT IIThe 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-71563CAT IIThe CA API Gateway must generate audit records when successful/unsuccessful logon attempts occur.
  • V-71565CAT IIThe CA API Gateway must generate audit records showing starting and ending time for administrator access to the system.
  • V-71567CAT IIThe CA API Gateway must generate audit records when concurrent logons from different workstations occur.
  • V-71569CAT IIIThe CA API Gateway must off-load audit records onto a different system or media than the system being audited.
  • V-71571CAT IIThe CA API Gateway must generate audit log events for a locally developed list of auditable events.
  • V-71573CAT IIThe CA API Gateway must employ automated mechanisms to assist in the tracking of security incidents.
  • V-71575CAT IIThe CA API Gateway must employ automated mechanisms to detect the addition of unauthorized components or devices.

How these changes are found

Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V1R2 no longer has.

Comparing other releases, or this one against an older release? Pick any two in STIG Compare.