Skip to main content

Attack events Hosted customers only

Note

The Attacks events view is for hosted customers.

If you are an on-premises customer, visit Attacks.

Attack events are any actions that unauthorized individuals or groups take to damage, disrupt, or gain illegal access to an application's systems, data, or functionality. Examples of attack events include:

  • SQL injection: An attacker inserts malicious code into your application's database queries to steal data or take control of your systems.

  • Cross-site scripting (XSS): An attacker injects malicious scripts into your application to steal user data or redirect them to malicious websites.

  • API attacks: An attacker exploits vulnerabilities in your APIs to gain unauthorized access to data or functionality.

Event data retention

Contrast keeps attack event data for up to a year. You can also:

  • Output to syslog

  • Set up a generic webhook

    A webhook receives data in a POST request only when a specified event occurs. When the webhook sees the event, it collects the data and sends it to the specified URL.

  • Integrate ADR with Security Information and Event Management (SIEM) tools

Exclusion of PROBED event data

You can choose to stop saving data for attack events with a PROBED result. You might want to do this to improve performance in the Contrast web interface.

To stop saving PROBED event data, contact Customer Support .

Tasks

In Contrast you can:

In this section: