Search filters this STIG's checks locally. Separate terms must all match (use quotes for an exact phrase). A search you ran on the Search page carries over here.
Assessment Title
Rule Text
The CA API Gateway providing user access control intermediary services must provide a logoff capability for user-initiated communications sessions.
Description
Discussion Text
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.
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.
New to STIG checklists? Read What is a STIG checklist? and CKL vs CKLB.