Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create incidenttype-ExtraHop_Detection.json
- Loading branch information
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| { | ||
| "autorun": false, | ||
This comment has been minimized.
Sorry, something went wrong. |
||
| "closureScript": "", | ||
| "color": "#e55100", | ||
| "days": 0, | ||
| "daysR": 0, | ||
| "default": false, | ||
| "disabled": false, | ||
| "hours": 0, | ||
| "hoursR": 0, | ||
| "id": "ExtraHop Detection", | ||
| "locked": false, | ||
| "name": "ExtraHop Detection", | ||
| "playbookId": "ExtraHop - Default", | ||
| "preProcessingScript": "", | ||
| "readonly": false, | ||
| "reputationCalc": 2, | ||
| "sortValues": null, | ||
| "system": false, | ||
| "version": -1, | ||
| "weeks": 0, | ||
| "weeksR": 0 | ||
| } | ||
@yaakovi does this mean we are able to ship the incident type with the integration? or should I still keep the section in the detailed setup instructions for the user to manually add the ExtraHop Detection incident type? Also the incident type needs to have the playbook run automatically in order for ticket tracking to work properly. Thanks