Fix for 'MDE Malware - Incident Enrichment' playbook #29842
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
...oftDefenderAdvancedThreatProtection/Playbooks/playbook-MDE_Malware_-_Incident_Enrichment.yml
Show resolved
Hide resolved
… the 'key' value of tasks 46 and 47.
…E_Malware_-_Incident_Enrichment � Conflicts: � Packs/MicrosoftDefenderAdvancedThreatProtection/ReleaseNotes/1_16_10.md � Packs/MicrosoftDefenderAdvancedThreatProtection/TestPlaybooks/Test_Playbook_-_MDE_Malware_-_Incident_Enrichment.yml
…ional task to check the incident fields value before setting the new keys
…from the test playbook file. removed the 'SetIfEmpty' transformer from tasks number 46 & 47 within the MDE playbook file.
ssokolovich
reviewed
Oct 1, 2023
...oftDefenderAdvancedThreatProtection/Playbooks/playbook-MDE_Malware_-_Incident_Enrichment.yml
Show resolved
Hide resolved
...oftDefenderAdvancedThreatProtection/Playbooks/playbook-MDE_Malware_-_Incident_Enrichment.yml
Outdated
Show resolved
Hide resolved
Packs/MicrosoftDefenderAdvancedThreatProtection/ReleaseNotes/1_16_11.md
Outdated
Show resolved
Hide resolved
… the 'manageremailaddress' incident field to the 'setIncident' automation used within task number 52.
ssokolovich
approved these changes
Oct 1, 2023
…E_Malware_-_Incident_Enrichment
wolyslager
pushed a commit
to wolyslager/content
that referenced
this pull request
Oct 2, 2023
* Fix for 'MDE Malware - Incident Enrichment' playbook * updated PNG playbook file * RN * RN * removed the new conditional task and changed the DT expression within the 'key' value of tasks 46 and 47. * DT was removed from the playbook * re-added changes after merging from master * DT was removed from the problematic playbook tasks & added new conditional task to check the incident fields value before setting the new keys * removed the validation for 'MicrosoftATP.Alert.Evidence' context key from the test playbook file. removed the 'SetIfEmpty' transformer from tasks number 46 & 47 within the MDE playbook file. * changed the name, description and condition for task number 56. added the 'manageremailaddress' incident field to the 'setIncident' automation used within task number 52.
xsoar-bot
pushed a commit
to xsoar-contrib/content
that referenced
this pull request
Oct 5, 2023
* Fix for 'MDE Malware - Incident Enrichment' playbook * updated PNG playbook file * RN * RN * removed the new conditional task and changed the DT expression within the 'key' value of tasks 46 and 47. * DT was removed from the playbook * re-added changes after merging from master * DT was removed from the problematic playbook tasks & added new conditional task to check the incident fields value before setting the new keys * removed the validation for 'MicrosoftATP.Alert.Evidence' context key from the test playbook file. removed the 'SetIfEmpty' transformer from tasks number 46 & 47 within the MDE playbook file. * changed the name, description and condition for task number 56. added the 'manageremailaddress' incident field to the 'setIncident' automation used within task number 52.
sapirshuker
pushed a commit
that referenced
this pull request
Dec 21, 2023
* Fix for 'MDE Malware - Incident Enrichment' playbook * updated PNG playbook file * RN * RN * removed the new conditional task and changed the DT expression within the 'key' value of tasks 46 and 47. * DT was removed from the playbook * re-added changes after merging from master * DT was removed from the problematic playbook tasks & added new conditional task to check the incident fields value before setting the new keys * removed the validation for 'MicrosoftATP.Alert.Evidence' context key from the test playbook file. removed the 'SetIfEmpty' transformer from tasks number 46 & 47 within the MDE playbook file. * changed the name, description and condition for task number 56. added the 'manageremailaddress' incident field to the 'setIncident' automation used within task number 52.
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.
Status
Related Issues
fixes: https://jira-hq.paloaltonetworks.local/browse/CIAC-8486?filter=-2
Description
The DT expression fails due to the differences between the DB tables in XSOAR 8 and the other versions of XSOR.
Screenshots