# Leakage of sensitive data to Airbrake

## Overview

* **Rule ID**: `java_third_parties_airbrake_javabrake`
* **Applicable Languages**: Java
* **Weakness ID**: CWE-201

## Description

Leaking sensitive data to third-party loggers such as Airbrake is a common cause of data breaches.

## Remediation Guidelines

* **Ensure** that all sensitive data is removed when logging errors or events to Airbrake.

## References

* [**Airbrake Docs**](https://docs.airbrake.io/docs/platforms/java/)
* [**CWE-201: Insertion of Sensitive Information Into Sent Data**](https://cwe.mitre.org/data/definitions/201.html)
* [**A01:2021 - Broken Access Control**](https://owasp.org/Top10/A01_2021-Broken_Access_Control/)

## Configuration

To omit this rule during a scan, and to provide you with continuous 24/7 code-level scanning, you can employ our [**SAST TOOL**](https://scopy.sec1.io/login)