Rule ID
SV-237353r643609_rule
Version
V1R3
CCIs
CCI-000133
Without establishing the source of the event, it is impossible to establish, correlate, and investigate the events leading up to an outage or attack. In order to compile an accurate risk assessment and provide forensic analysis, security personnel need to know the source of the event. In addition to logging where events occur within the network, the audit records must also identify sources of events such as IP addresses, processes, and node or device names. The CA API Gateway policies must be configured to provide the required level of auditing in accordance with organizational requirements.
Open the CA API Gateway - Policy Manager. Select "Gateway Audit Events" from the "View" menu. Execute a logon failure of one of the Registered Services using an approved testing tool or an Application that accesses the service. View the Audit logs to notice the logging of the Authentication failure as well as the source of the failure showing the individual client ID's IP address. If the failure is not logged or the source is not properly displayed, this is a finding.
If a logon failure is not recorded, check the Registered Service for the existence of an Authentication Mechanism using an Access Control Assertion such as "Authenticate Against Identity Provider". Also verify a Credential Source is added from the Access Control Assertions, such as "Require HTTP Basic Credentials" or "Require WS-Security Username Token Profile Credentials". Other attacks on a Registered Service, such as SQL Injection or PHP Evaluation Injections, will be automatically logged when the Assertion checking for the attack is added to a Registered Service or set in Global Policy. The event will include the source of the attack indicated by the client ID.