# Leakage of sensitive data to RollBar

## Overview

* **Rule ID**: `javascript_third_parties_rollbar`
* **Applicable Languages**: Javascript
* **Weakness ID**: CWE-201

## Description

Exposing sensitive data to third-party loggers such as RollBar is a frequent cause of data leaks and can result in data breaches.

## Remediation Guidelines

* **Make sure that all sensitive data is removed** before sending information to third-party loggers such as Rollbar.
* **Use** unique database identifiers if user identification is necessary.

  ```javascript
  Rollbar.critical("Connection error from remote Payments API", user.uuid);

  ```

## References

* [**Rollbar docs**](https://docs.rollbar.com/docs/javascript)
* [**OWASP logging cheat sheet**](https://cheatsheetseries.owasp.org/cheatsheets/Logging_Cheat_Sheet.html)
* [**CWE-201: Insertion of Sensitive Information Into Sent Data**](https://cwe.mitre.org/data/definitions/201.html)
* [**OWASP Top 10: 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)