Kaduu consists of two plattforms:

• Deepweb (https://deepweb.leak.center)
• Control (https://control.leak.center)

Deepweb is used for live queries that can take up to 3 hours. Control is mainly DB driven. API access is currently only available for "Control". Control uses a REST API which you can reach via SSL.

Please find the API documentation here kaduu-2.2-swagger_3_.zip. The PDF documentation has some more details about authentication and filters.

Please note that Kaduu SaaS API is based on a REST/HTTPS protocol with JSON format. All endpoints except the authentication expect the JSON input and Content-Type: application/json header provided with the request. All endpoint results are in JSON format. Before using any other API calls, you should obtain an authentication token – it is required for all subsequent API calls. In order to obtain the token, you should send a POST request to the

https://app.leak.center/uaa/oauth/token URL with the following data: Headers Content-Type application/x-www-form-urlencoded Form client_id client-api client_secret comfy-litigate-embargo-forelimb grant_type password username <your username> password <your password>

All fields in form should be URL-encoded.

The server responds with a token in JSON format: {

"access_token": "<your token>",
"token_type": "bearer",
"expires_in": 43199,
"scope": "svc-saas",
"jti": "fcea19dc-091c-4b58-901e-3e9bb8df162f"

}

The API consumer should copy the resulting access_token value from the response and use it in Authorization header with Bearer scheme for all other requests:

Authorization: Bearer <your token>

Please define your webhook under your account settings. You need to define "http" as a alerting method. The system will POST all new findings to that URL as a JSON list of alert objects. You may leave this field blank in order to disable alert notifications.

The customer has various options in Kaduu for accessing the query data: • Via dashboard: data can be displayed and then exported (CSV, XML, DOCX etc) • Via webhook • Via REST API • Via alerting (email)

The REST API allows you great flexibility in automation and integration into your existing processes and applications. You can use the API according to the official documentation https://wiki.kaduu.ch/doku/lib/exe/fetch.php?media=kaduu-2.0.pdf. In this document we illustrate how the API can be used with a customizable Python script which could assist you with few business use cases:

• White labeled alerts: You use Kaduu to regularly provide end customers or specific people with email alerts on certain topics (e.g. leaked data). To do this, you want to use an email with your design, company name and structure and also send this via your infrastructure.
• Ticketing System Integration: You want to integrate Kaduu into your existing environment and create tickets or incidents automatically in Splunk, Jira, Slack or similar systems.
• Automated Output Parsing: You want to store all results for certain search queries daily in an easy-to-process format (CSV, XLS, etc.) locally in a folder of your choice for analysis and further processing.
• Reduce Workload in Alerting: You want to save time when using Kaduu's email alerts: Instead of logging into the system for email alerts and researching the cause of the alerts, you want to receive the specific raw data of the alerts via email.

How to use the script? Run the script either by giving the input in the terminal or operate it with an input file. Type "csv" as an option and then if your input file is in the same directory, type yourinputfile.csv. Please make sure you type the correct name of the input file. Before running the input file, put your username and password in the first two rows and adjust the different columns. For example enter one or multiple domains belonging to the same client under asset_name without the subdomain.

Using the input file (example_input.csv)

The script can operate with an input file. Here is the syntax for the different fields:

What are the API Endpoints integrated into the script?

We didn’t integrate all API endpoints available, but just a few relevant ones from control.leak.center:

• 'domain': "https://app.leak.center/svc-saas/domain/search", https://wiki.kaduu.ch/doku/doku.php?id=domain_database_search
• 'accounts': "https://app.leak.center/svc-saas/account/search", (account is just an extraction of leaks, we therefore recommend using leaks as it contains more data)
• 'leaks': "https://app.leak.center/svc-saas/leak/search", https://wiki.kaduu.ch/doku/doku.php?id=leak_search
• 'certificates': "https://app.leak.center/svc-saas/certificate/search", https://wiki.kaduu.ch/doku/doku.php?id=certificate_monitoring
• 'botnets': "https://app.leak.center/svc-saas/bot/record/search", https://wiki.kaduu.ch/doku/doku.php?id=bot_search
• 'ransomware': "https://app.leak.center/svc-saas/ransomware/search", https://wiki.kaduu.ch/doku/doku.php?id=ransomware_site_monitoring
• 'cc': https://app.leak.center/svc-saas/cc/search, https://wiki.kaduu.ch/doku/doku.php?id=credit_card_search

How to use the script for daily alerting? Alert Option “1” Use the Script for a daily Job. The script will ignore the date range, but fetch the current day and execute the query for the current day only. If alerting is set to 0: It will use the date range. You can customize the HTML Email in the Python code here:

If you want to run the script in Crontab: • Locate Your Python Script: Ensure your script (V1.py) is executable and located in a suitable directory. You might also want to make sure that the script has the appropriate permissions to execute. You can make it executable using the command: bash  chmod +x /path/to/V1.py • Find the Path to Your Python Interpreter: You need to know the path to the Python interpreter that will run your script. You can find this with: bash  which python (Or if your script is written for Python 3 specifically: bash  which python3; This command will return a path like /usr/bin/python3) • Edit Your Crontab: Open your crontab for editing by running: bash  crontab -e (This will open the crontab file in your default text editor) • Add a Cron Job: In the crontab file, add a line that specifies when the script should run and what command should be executed. The general format is: * * * * command to execute. For daily execution, you might use something like: 0 0 * * * /usr/bin/python3 /path/to/V1.py (This means the script V1.py will run at midnight every day. The five asterisks represent minute (0-59), hour (0-23), day of the month (1-31), month (1-12), and day of the week (0-7, where both 0 and 7 mean Sunday), respectively) • Save and Exit: Save the crontab file and exit the editor. Your cron job is now scheduled. The cron daemon will automatically pick up the new job. • Check the Crontab List: To make sure your cron job is listed, you can view your current cron jobs with: crontab -l • Logging: If you want to log the output of your script, you can modify the cron job line like this: 0 0 * * * /usr/bin/python3 /path/to/V1.py » /path/to/logfile.log 2>&1 (This command will append the output of your script to logfile.log and include both standard output and standard error) • Environment Issues: If your script depends on environment variables or a specific environment setup, you might need to either export the necessary variables directly in the crontab or run a shell script from cron that sets up the environment before running your Python script. • Remember to replace /path/to/V1.py with the actual path to your Python script and /usr/bin/python3 with the path to the Python interpreter on your system.