Modify RF Playbooks: Check for "Recorded Future v2" instead of "Recorded Future" integration instance #27020
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
…ded Future" integration instance (#26589) * Update playbook-Recorded_Future_CVE_Reputation.yml * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Check for "Recorded Future v2" instead of "Recorded Future" integration instance * Create 1_5_3.md * update currentVersion to 1.5.3 * scriptarguments inputs.url not needed * scriptarguments inputs.url not needed * ${inputs.URL} instead of ${RecordedFuture.URL.name} playbook currently fails when no RF results are returned * ${inputs.URL} instead of ${RecordedFuture.URL.name} playbook currently fails when no RF results are returned * ${inputs.CVE} instead of ${RecordedFuture.CVE.name} playbook currently fails when no RF results are returned * ${inputs.CVE} instead of ${RecordedFuture.CVE.name} playbook currently fails when no RF results are returned * ${inputs.Domain} instead of ${RecordedFuture.Domain.name} playbook currently fails when no RF results are returned * ${inputs.Domain} instead of ${RecordedFuture.Domain.name} playbook currently fails when no RF results are returned * ${inputs.IP} instead of ${RecordedFuture.IP.name} playbook currently fails when no RF results are returned * ${inputs.IP} instead of ${RecordedFuture.IP.name} playbook currently fails when no RF results are returned * Bump version --------- Co-authored-by: Danny_Fried <[email protected]>
…-Future-Playbooks
thefrieddan1
approved these changes
May 30, 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
@randomizerxd
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
fixes: link to the issue
Description
A few sentences describing the overall goals of the pull request's commits.
Screenshots
Paste here any images that will help the reviewer
Minimum version of Cortex XSOAR
Does it break backward compatibility?
Must have