Flashpoint Release 2.1.0
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
- [ ] In Progress
- [x] Ready
- [ ] In Hold - (Reason for hold)
Description
Updated the "Flashpoint Ignite" integration for the following:
- Added the flashpoint-ignite-indicator-get command to retrieve details for specific indicator of types "url", "domain", "file hash", and "ip" using the indicator ID.
- Updated the following commands to use the new IOC v2 API:
- ip
- domain
- url
- file
- flashpoint-ignite-common-lookup
- Added support for the following parameters to filter incoming compromised credentials alerts based on password characteristics:
- Fetch compromised credentials alerts having numbers in password
- Fetch compromised credentials alerts having minimum length of password
- Fetch compromised credentials alerts having uppercase in password
- Fetch compromised credentials alerts having lowercase in password
- Fetch compromised credentials alerts having symbol in password
- Fixed an issue where the "ip" command could return a "NoneType" error.
- Deprecated the filename and email command.
Must have
- [x] Tests
- [x] Documentation
Thank you for your contribution. Your generosity and caring are unrivaled! Make sure to register your contribution by filling the Contribution Registration form, so our content wizard @itssapir will know the proposed changes are ready to be reviewed. For your convenience, here is a link to the contributions SLAs document.
Hi @crestdatasystems, thanks for contributing to the XSOAR marketplace. To receive credit for your generous contribution please follow this link.
For the Reviewer: Trigger build request has been accepted for this contribution PR.
For the Reviewer: Successfully created a pipeline in GitLab with url: https://gitlab.xdr.pan.local/xdr/cortex-content/content/-/pipelines/3681010
Validate summary The following errors were thrown as a part of this pr: RM110, RN106. The following errors can be ignored: RM110. The following errors cannot be ignored: RN106. The following errors don't run as part of the nightly flow and therefore can be force merged: RN106.
Verdict: PR can be force merged from validate perspective? ❌
Thank you for your contribution. Your external PR has been merged and the changes are now included in an internal PR for further review. The internal PR will be merged to the master branch within 3 business days.