The CA API Gateway providing user access control intermediary services must provide a logoff capability for user-initiated communications sessions.
An XCCDF Rule
Description
<VulnDiscussion>If a user cannot explicitly end a session, the session may remain open and be exploited by an attacker. However, for some types of interactive sessions, including, for example, remote logon, information systems typically send logoff messages as final messages prior to terminating sessions. This policy only applies to gateways (e.g., identity management or authentication gateways) that provide user account services as part of the intermediary services. The CA API Gateway must register, protect, and expose the API responsible for logoff capability. Policy can then be configured to allow the Logoff Registered Service to be initiated through the application requiring the user logoff capability.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-86107r1_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
Open the CA API Gateway - Policy Manager and register the Logoff APIs as Registered Services.
Assign the proper policy to the Registered Service in accordance with organizational requirements for securing/protecting Registered Services/APIs.
For more details, refer to the "Layer 7 Policy Authoring User Manual".