Devo integration v2 Improvement #25817
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Update .devcontainer.json name * [Devo] Updated .pack-ignore for v3 * [Devo] Added Devo_v3 python file * [Devo] Added Devo_v3 yaml file * [Devo] Added Devo_v3 description file * [Devo] Added Devo_v3 README file * [Devo] Inherited Devo_v3 test file * [Devo] Inherited Devo_v3 python file * [Devo] Deprecated Devo_v2 * [Devo] Added release notes for v3 (1.2.0 version) * [Devo] Updated pack_metadata.json * [Devo] Simplified exception handling * [Devo] Specified some pip package versions to avoid conflicts * [Devo] Fixed problematic dependency versions * [Devo] Missing default value for INCIDENTS_FETCH_INTERVAL in python file * [Devo] Updated missing entry in 1.2.0 release notes * [Devo] Python file is now Flake8 compliant * [Devo] Updated Devo_v2.py * [Devo] Updated Devo_v2.yml * [Devo] Updated Devo_v2 README.md * [Devo] Updated Release notes * [Devo] Remove wrong version (Devo_v3) * [Devo] Added minimum version of devo-sdk pip package * [Devo] Changed required field in Devo_v2.yml * Fixed MyPy lint errors * Minor changes to meet lint standards * Removed package version in Devo v2 * [Devo] Reverting devcontainer.json change * [Devo] Fixed README.md "Devo_v3" occurrence * [Devo] Changed "items_per_page" from required to optional * [Devo] Fixed "items_per_page" requirement and added default value * [Devo] Added default value to "items_per_page" in .py * [Devo] Refactorized query strings * [Devo] Removed unnecesarry Devo_v3 section from .pack-ignore * [Devo] Updated docker image version * test new devo docker image * update new devo docker image * update docker image * modify unit test * modify unit test --------- Co-authored-by: j-lopezal <j-lopezal@users.noreply.github.com> Co-authored-by: rohan-metron <rohan@metronlabs.com>
content-bot
added
Contribution
dansterenson
approved these changes
Apr 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Original External PR
external pull request
Contributor
@j-lopezal
Contributing to Cortex XSOAR Content
Make sure to register your contribution by filling the contribution registration form
The Pull Request will be reviewed only after the contribution registration form is filled.
Status
Related Issues
Description
This Devo XSOAR v2 Integration carries over everything from version 2 and adds two new features:
Items per page: helps manage number of Devo items (incidents i.e. alerts, query responses) to be processed by XSOAR to avoid overwhelming XSOAR
Custom alert table: allows XSOAR to query/process Devo data stored in my.app.alert.info table
Use Cases
Ingest all user-defined alerts from Devo into Cortex XSOAR
Query any data source available in Devo
Manage alert processing speed of XSOAR
Run needle-in-haystack multi-table queries for threat-hunting incidents
Write results back to Devo as searchable records or alerts
Write new entries into lookup tables to be used in synthesis tables (ALPHA)
Screenshots
Minimum version of Cortex XSOAR
Does it break backward compatibility?
Must have