The CA API Gateway must produce audit records containing information to establish the outcome of the events.
An XCCDF Rule
Description
<VulnDiscussion>Without information about the outcome of events, security personnel cannot make an accurate assessment as to whether an attack was successful or if changes were made to the security state of the network. Event outcomes can include indicators of event success or failure and event-specific results (e.g., the security state of the network after the event occurred). They also provide a means to measure the impact of an event and help authorized personnel to determine the appropriate response. The CA API Gateway policies must be configured to provide the required level of auditing in accordance with organizational requirements.</VulnDiscussion><FalsePositives></FalsePositives><FalseNegatives></FalseNegatives><Documentable>false</Documentable><Mitigations></Mitigations><SeverityOverrideGuidance></SeverityOverrideGuidance><PotentialImpacts></PotentialImpacts><ThirdPartyTools></ThirdPartyTools><MitigationControl></MitigationControl><Responsibility></Responsibility><IAControls></IAControls>
- ID
- SV-85957r1_rule
- Severity
- Medium
- References
- Updated
Remediation - Manual Procedure
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 that 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 outcomes of events occurring 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 outcome displaying its results.