> For the complete documentation index, see [llms.txt](https://docs.sec1.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sec1.io/user-docs/4-sast/3-javascript/leakage-of-sensitive-data-to-algolia.md).

# Leakage of sensitive data to Algolia

## Overview

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

## Description

Leaking sensitive data to third-party loggers like Algolia is a common cause of data leaks and can lead to data breaches.

## Remediation Guidelines

* **Do** ensure all sensitive data is removed when logging errors or events to Algolia
* **Do use** unique identifiers from the database if you really need to identify users.

  ```javascript
  const algoliaSearch = require('algoliasearch')
  const myAlgolia = algoliaSearch("123", "123")
  const index = myAlgolia.initIndex(user.uuid)
  ```

## References

* [**Algolia docs**](https://www.algolia.com/doc/)
* [**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)