STIGhubSTIGhub
STIGsSearchCompare

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
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 3 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to CA API Gateway ALG Security Technical Implementation Guide

V-237413

CAT II (Medium)

The CA API Gateway providing user access control intermediary services must generate audit records showing starting and ending time for user access to the system.

Rule ID

SV-237413r643789_rule

STIG

CA API Gateway ALG Security Technical Implementation Guide

Version

V1R3

CCIs

CCI-000172

Discussion

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 records can be generated from various components within the information system (e.g., module or policy filter). This requirement applies to the ALG traffic management functions, such as content filtering or intermediary services. This does not apply to audit logs generated on behalf of the device (device management). By default, the CA API Gateway audits all starting events for each Registered Service. An ending event can be generated through the use of a "logout service/API", which is called by the user's application at the time of logout or session termination. If the Registered Service/API already has the logout capability included, the ending event will be generated automatically at logout without the need for an additional logout service.

Check Content

Open the CA API Gateway - Policy Manager.

Verify that each Registered Service requiring starting and ending event auditing includes the logout/terminate session capability as part of the Registered Service/API. 

If it does not, this is a finding.

Fix Text

If any of the Registered Services/API's do not provide a logout/terminate session capability as part of the API, create and register a "Logoff" Registered Service and call this service from the user's application upon ending a session. This will automatically generate the ending event as required and be audited on the Gateway. 

For more details on registering and authoring services, refer to the “CA API Management Documentation Wiki" at https://wiki.ca.com/display/GATEWAY90/CA+API+Gateway+Home.