Leakage of sensitive data to Datadog

• Rule ID: javascript_third_parties_datadog
• Languages: javascript
• Source: datadog.yml

Description

Leaking sensitive data to third-party loggers is a common cause of data leaks and can lead to data breaches. This rule looks for instances of sensitive data sent to Datadog.

Remediations

When logging errors or events, ensure all sensitive data is removed.

If you really need to identify users, use unique identifiers from the database.

  const StatsD = require("hot-shots");
  const client = new StatsD({
    port: 8020,
    globalTags: { env: process.env.NODE_ENV },
    errorHandler: errorHandler,
  });

  client.event(user.uuid, "logged_in", {});

Resources

• Datadog docs
• Scrubbing data
• OWASP logging cheat sheet

Associated CWE

• CWE-201: Insertion of Sensitive Information Into Sent Data

OWASP Top 10

• A01:2021 - Broken Access Control

Configuration

To skip this rule during a scan, use the following flag

bearer scan /path/to/your-project/ --skip-rule=javascript_third_parties_datadog

To run only this rule during a scan, use the following flag

bearer scan /path/to/your-project/ --only-rule=javascript_third_parties_datadog