Otto-js

Otto-js is a security-focused JavaScript monitoring platform that detects and prevents data leaks in real time. It provides visibility into script behavior, protecting sensitive data in web apps and third-party integrations. For detailed information, please refer to the Otto-js documentation.

Integration Method: API

Tables: Vulnerability Finding (2002), Incident Finding (2005)

This integration supports the following types of events.

This integration was tested against the following versions.

Prerequisites

• The user should have the API token of Otto-js.

• The user should have access to the DataBee console.

Configuration Overview

1. Get an API token from Otto-js.

2. Create Otto-js Data Feed in the DataBee console with the required Client credentials.

   DataBee Parameter	Otto-js Parameter
   Token	API Token
   Account ID	Account ID

Otto-js Configuration

To get an API Token, submit a request to support@otto-js.com with the subject "API KEY REQUEST. ". Request for your Account ID at the same time. The account id is used when making API calls to Otto-js.

DataBee Configuration

1. Login to the DataBee UI, navigate to Data > Data Feeds and click the Add New Data Feed button.
    

2. Search for the Otto-Js and click it as shown below.
    

3. Click on the API Ingest option for collection method.
    

4. Enter feed contact information and click Next.
    

5. In the configuration page, confirm the following:

   • API Base URL: this is the base URL that DataBee will interact with.

   • Authorization Method: Bearer Token

   • Token: paste the API Token generated earlier in the Otto-js configuration.

   • Account ID: paste the Account ID.

   • Event types: preselected for all the events types the integration pulls.
      

6. Click Submit.

Troubleshooting Tips

• Ensure the token is pasted correctly. Since you cannot view the token after the 1^st time, re-create the token, paste it on a text editor to ensure no spaces or unexpected characters are included and reconfigure the DataBee feed.

• Ensure the Otto-js scope/permissions is set correctly.