The Lumu Defender API offers a framework to help you leverage Lumu’s integrations with your existing cybersecurity stack, including Security Information and Event Management (SIEM), Security Orchestration, Automation, and Response (SOAR), Endpoint Detection and Response (EDR); incident response systems; and more.
This article shows how to leverage adversarial information from Lumu and feed destination lists to Cisco Umbrella.
First, contact the
Lumu support team to request the package we created to deploy the required files.
Once you receive the Python package provided by Lumu, unpack the file in your preferred path / folder. Keep in mind, this location will be required for further configurations. This folder will be referred from now on as
For using the script, you must locate yourself on the path selected for deployment (
). Use the following command to show all options available for the package:
This is a reference of the options you have access to through this script:
We provide here some examples of how to use the script:
Task: query and add all adversarial data for the last 30 days
Use the following command for querying and posting to Umbrella all adversarial data found in your organization by Lumu in the last 30 days:
Task: query and add all adversarial data since the last runtime
For control purposes, the script stores the latest runtime in a file called
. If it is the first time you run the script, you will automatically get all the data of the last 30 days. The next time you run this query, it will get the latest runtime timestamp from the
To ignore the saved timestamp, remove the
Task: Query and add all adversarial data of the last X hours
Use the following command to query all adversarial data from your Lumu subscription for the specified numbers of hours:
Task: query and add all adversarial data since a specific date
For filtering data from a specific date, use the flag
followed by a date string in the standard format published in RFC 3339 and ISO 8601:
Task: filter adversarial types
To query filtered adversarial types before adding them to your Cisco Umbrella's destination list, use the parameter
followed by a list of the adversarial types separated by commas.
For this particular example, the adversary types to filter are
Task: save output to file
Use the parameter
to store a record of all tasks run. With this parameter, all the script output will be redirected to a file named
in the root of the selected path for the deployment of the script (
For each script run, it is expected that the defined Destination List will be populated with more indicators, as in the following example:
To run this script on a timely-basis, consider implementing a
in Windows or a
in Unix-based systems. We recommend using the
flag to query and add different adversarial data for each runtime.
Use the -v flag to investigate errors on the script. This will provide you with details for identifying failures in the script execution.