Hoxhunt
Hoxhunt Pack.#
This Integration is part of theSupported versions
Supported Cortex XSOAR versions: 6.10.0 and later.
Use the Hoxhunt integration to send feedback to reporters of incidents, set incident sensitivity, and apply SOC classification to incidents. This integration was integrated and tested with version August 2024 of Hoxhunt.
#
Configure Hoxhunt on Cortex XSOARNavigate to Settings > Integrations > Servers & Services.
Search for Hoxhunt.
Click Add instance to create and configure a new integration instance.
Parameter Description Required Server URL (e.g. https://api.hoxhunt.com/graphql-external) True Trust any certificate (not secure) False Use system proxy settings False API Key Input your api key from Hoxhunt False Fetch incidents False Incidents Fetch Interval False Incident type False First fetch timestamp (<number> <time unit>, e.g., 12 hours, 7 days) False Query Filter Input a query filter for incidents to be fetched False Click Test to validate the URLs, token, and connection.
#
CommandsYou can execute these commands from the Cortex XSOAR CLI, as part of an automation, or in a playbook. After you successfully execute a command, a DBot message appears in the War Room with the command details.
#
hoxhunt-get-current-userGets the current user information from Hoxhunt.
#
Base Commandhoxhunt-get-current-user
#
InputArgument Name | Description | Required |
---|
#
Context OutputPath | Type | Description |
---|---|---|
HoxHunt.CurrentUser | string | Current User information from Hoxhunt. |
#
hoxhunt-get-incidentsGets incidents from Hoxhunt.
#
Base Commandhoxhunt-get-incidents
#
InputArgument Name | Description | Required |
---|---|---|
filter | Input here the filter or other arguments. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
Hoxhunt.Incidents | string | Incidents from Hoxhunt. |
#
hoxhunt-get-threatsGets threats from Hoxhunt.
#
Base Commandhoxhunt-get-threats
#
InputArgument Name | Description | Required |
---|---|---|
filter | Input here the filter or other arguments. | Optional |
#
Context OutputPath | Type | Description |
---|---|---|
Hoxhunt.Threats | string | Threats from Hoxhunt. |
#
hoxhunt-add-incident-noteAdd Incident note.
#
Base Commandhoxhunt-add-incident-note
#
InputArgument Name | Description | Required |
---|---|---|
incident_id | The ID of the incident to which the note will be added. | Required |
note | The content of the note to add to the incident. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
Hoxhunt.addIncidentNode | string | Add Incident note. |
#
hoxhunt-remove-incident-threatsRemove all threats that belong to an incident.
#
Base Commandhoxhunt-remove-incident-threats
#
InputArgument Name | Description | Required |
---|---|---|
incident_id | The ID of the incident from which threats will be removed. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
Hoxhunt.removeIncidentThreats | number | Returns number of removed threats. |
#
hoxhunt-send-incident-soc-feedbackSend feedback to reporters of incident about whether the reported email was safe, spam or malicious.
#
Base Commandhoxhunt-send-incident-soc-feedback
#
InputArgument Name | Description | Required |
---|---|---|
incident_id | The ID of the incident for which SOC feedback will be sent. | Required |
custom_message | A custom message to include with the SOC feedback. | Required |
threat_feedback_reported_at_limit | Datetime limit. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
Hoxhunt.sendIncidentSocFeedback | string | The reporter will be informed the incident has been resolved and that no further actions are required from them. |
#
hoxhunt-set-incident-sensitiveSet incident to contain sensitive information.
#
Base Commandhoxhunt-set-incident-sensitive
#
InputArgument Name | Description | Required |
---|---|---|
incident_id | The ID of the incident to be marked as sensitive or not sensitive. | Required |
is_sensitive | True or False Boolean. Possible values are: TRUE, FALSE. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
Hoxhunt.setIncidentSensitive | string | Incident sensitivity information. |
#
hoxhunt-set-incident-soc-classificationSet soc classification for an incident.
#
Base Commandhoxhunt-set-incident-soc-classification
#
InputArgument Name | Description | Required |
---|---|---|
incident_id | The ID of the incident to classify. | Required |
classification | The SOC classification to apply to the incident. Possible values are: MALICIOUS, SPAM, SAFE. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
Hoxhunt.setIncidentSocClassification | string | Incident SOC classification information. |
#
hoxhunt-update-incident-stateUpdates Incident state.
#
Base Commandhoxhunt-update-incident-state
#
InputArgument Name | Description | Required |
---|---|---|
incident_id | The ID of the incident to update. | Required |
state | The new state of the incident. Possible values are: OPEN, RESOLVED. | Required |
#
Context OutputPath | Type | Description |
---|---|---|
Hoxhunt.updateIncidentState | string | Incident state information. |
#
Incident MirroringYou can enable incident mirroring between Cortex XSOAR incidents and Hoxhunt corresponding events (available from Cortex XSOAR version 6.0.0). To set up the mirroring:
- Enable Fetching incidents in your instance configuration.
Newly fetched incidents will be mirrored in the chosen direction. However, this selection does not affect existing incidents. Important Note: To ensure the mirroring works as expected, mappers are required, both for incoming and outgoing, to map the expected fields in Cortex XSOAR and Hoxhunt.