Action Modules
Cortex XDR IOC Publish¶
Upload missing Cortex XDR IOC rules from IDS-marked MISP event and object attributes. [source code]
-
features:
Publishes MD5/SHA-256, domain and IP indicators through indicators/insert_jsons with validation. Skips observed existing rules, supports Standard/Advanced API keys and defaults to a credential-free dry run. Explicit expiry and per-indicator outcomes are reported. See https://github.com/MISP/misp-modules/blob/main/documentation/action_mod/cortex_xdr_ioc_publish.md.
-
config:
{'params': {'source': {'type': 'string', 'description': 'Stable publisher label included in the IOC comment', 'value': 'misp-modules'}, 'severity': {'type': 'string', 'description': 'INFO, LOW, MEDIUM, HIGH or CRITICAL', 'value': 'MEDIUM'}, 'reputation': {'type': 'string', 'description': 'SUSPICIOUS or BAD', 'value': 'SUSPICIOUS'}, 'expiration_days': {'type': 'string', 'description': 'Explicit IOC lifetime: 7, 30, 90 or 180 days', 'value': '30'}, 'dry_run': {'type': 'string', 'description': 'true previews payloads without any network requests; false publishes', 'value': 'true'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
Selected MISP events in workflow data; only non-deleted IDS-marked supported attributes are eligible.
-
output:
Publication summary and per-indicator outcomes; an error signals incomplete or uncertain publication.
-
references:
-
requirements:
Cortex XDR Pro and API credentials with IOC lookup and upload permissions on the module server.
Cortex XSOAR Incident Create¶
Create a Cortex XSOAR 8 incident with a MISP event reference and selected-data counts. [source code]
-
features:
Creates a new incident through /xsoar/public/v1/incident, with dry run enabled by default. Distinguishes HTTP 201 creation from HTTP 200 processing without creation. Supports Standard/Advanced keys and an explicit investigation opt-in. Sends source UUID/counts rather than event contents. See https://github.com/MISP/misp-modules/blob/main/documentation/action_mod/cortex_xsoar_incident_create.md.
-
config:
{'params': {'incident_type': {'type': 'string', 'description': 'Existing XSOAR incident type', 'value': 'Unclassified'}, 'name_prefix': {'type': 'string', 'description': '1–64 ASCII letters, digits, spaces, ._-', 'value': 'MISP event'}, 'severity': {'type': 'string', 'description': 'Numeric XSOAR severity from 0 to 4', 'value': '2'}, 'create_investigation': {'type': 'string', 'description': "true starts the incident type's investigation/playbook", 'value': 'false'}, 'dry_run': {'type': 'string', 'description': 'true previews; false requests a new incident', 'value': 'true'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
Exactly one selected, non-deleted MISP event with a valid UUID in workflow data.
-
output:
Preview or created/not-created/uncertain incident outcome, source UUID and selected-data counts.
-
references:
-
requirements:
Cortex XSOAR 8 API credentials with incident creation permissions.
CrowdStrike IOC Publish¶

Create and renew module-owned Falcon custom IOCs from MISP event and object attributes. [source code]
-
features:
Publishes to_ids MD5, SHA-256, domain and IP attributes, including attributes in objects. Requires explicit host-group or global scope. Existing IOCs are updated only when both their source and module ownership tag match; foreign IOCs are left unchanged. Credentials come from server-side CROWDSTRIKE_CLIENT_ID and CROWDSTRIKE_CLIENT_SECRET environment variables. Supports expiration, dry runs and per-indicator outcomes. See the usage guide.
-
config:
{'params': {'region': {'type': 'string', 'description': 'Falcon region: us1, us2 or eu1', 'value': 'us1'}, 'source': {'type': 'string', 'description': 'Stable ownership namespace, unique to this MISP publisher', 'value': 'misp-modules'}, 'action': {'type': 'string', 'description': 'detect or prevent (prevent is restricted to file hashes)', 'value': 'detect'}, 'severity': {'type': 'string', 'description': 'INFORMATIONAL, LOW, MEDIUM, HIGH or CRITICAL', 'value': 'MEDIUM'}, 'platforms': {'type': 'string', 'description': 'Comma-separated windows, mac and/or linux', 'value': 'windows,mac,linux'}, 'host_groups': {'type': 'string', 'description': 'Comma-separated Falcon host-group IDs (32 hexadecimal characters)'}, 'apply_globally': {'type': 'string', 'description': 'true applies across the tenant; otherwise host_groups is required', 'value': 'false'}, 'expiration_days': {'type': 'string', 'description': 'Days from this publication until expiration (1-365)', 'value': '30'}, 'dry_run': {'type': 'string', 'description': 'true returns planned payloads without authenticating or publishing', 'value': 'false'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
MISP events in standard, bare or legacy format, supplied in workflow data.
-
output:
Publishing summary and per-indicator outcomes; an error signals incomplete publication.
-
references:
-
requirements:
- crowdstrike-falconpy
- Falcon IOC Management Read/Write API scopes
Doppel Alert and Takedown¶
Create Doppel alerts or explicitly request takedown for an existing alert. [source code]
-
features:
Actions use the Doppel V1 API. Existing actioned or resolved alerts are not actioned again.
-
config:
{'params': {'action': {'type': 'string', 'value': 'create_alert', 'description': 'create_alert or request_takedown'}, 'entity': {'type': 'string', 'description': 'HTTP(S) URL; exactly one of entity or alert_id for takedown'}, 'alert_id': {'type': 'string', 'description': 'Existing Doppel alert ID, such as ACM-1234'}, 'comment': {'type': 'large_string', 'description': 'Optional rationale, sent with a takedown request'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': False}
-
data-source:
external
-
input:
Explicit entity URL or alert ID and action parameters.
-
output:
Alert ID, workflow state, link and whether a request was performed.
-
references:
-
requirements:
- requests
- DOPPEL_API_KEY in the module server environment
Export to Sentinel or Defender¶
Export indicators to Microsoft Sentinel or Microsoft Defender. Requires an existing installation of MISP2Sentinel or MISP2Defender. [source code]
-
features:
-
config:
{'params': {'misp2_venv': {'type': 'string', 'description': 'Where is the MISP2Sentinel or MISP2Defender Python virtual environment?', 'value': '/var/www/MISP/misp-custom/misp2sentinel/venv/'}, 'misp2_script': {'type': 'string', 'description': 'Where is the MISP2Sentinel or MISP2Defender installation?', 'value': '/var/www/MISP/misp-custom/misp2sentinel/script.py'}}, 'blocking': False, 'support_filters': True, 'expect_misp_core_format': False}
IRC¶
Send a message to an IRC channel. [source code]
-
features:
Renders Jinja2 templates using matchingData when present, otherwise data, with a JSON fallback. Supports verified TLS, server passwords and channel keys. Splits multiline and long UTF-8 messages into IRC PRIVMSG lines. See the usage guide.
-
config:
{'params': {'irc_server': {'type': 'string', 'description': 'IRC server hostname', 'value': 'irc.example.org'}, 'irc_port': {'type': 'string', 'description': 'IRC server port', 'value': '6697'}, 'use_tls': {'type': 'string', 'description': 'true for verified TLS, false for a plaintext connection', 'value': 'true'}, 'nickname': {'type': 'string', 'description': 'Nickname for this connection', 'value': 'misp'}, 'channel': {'type': 'string', 'description': 'IRC channel to join', 'value': '#misp'}, 'server_password': {'type': 'string', 'description': 'Optional server PASS password', 'value': ''}, 'channel_key': {'type': 'string', 'description': 'Optional channel JOIN key', 'value': ''}, 'message_template': {'type': 'large_string', 'description': 'Jinja2 message template; leave empty to send the workflow data as JSON', 'value': 'MISP event: {{ Event.info }}', 'jinja_supported': True}}, 'blocking': False, 'support_filters': True, 'expect_misp_core_format': False}
-
input:
Workflow data or matchingData, and an optional Jinja2 message template.
-
output:
Boolean success after server processing; IRC provides no recipient delivery receipt.
-
references:
Matrix¶
Send a message to an unencrypted Matrix room. [source code]
-
features:
Renders Jinja2 templates using matchingData when present, otherwise data, with a JSON fallback. Sends plain-text m.room.message events using a bot access token. The bot must already be a room member with permission to send messages. End-to-end encrypted rooms and HTML/Markdown formatting are unsupported. See the usage guide.
-
config:
{'params': {'matrix_homeserver': {'type': 'string', 'description': 'The Matrix homeserver base URL, including scheme and optional path prefix', 'value': 'https://matrix.example.org'}, 'bot_access_token': {'type': 'string', 'description': 'Access token for a Matrix bot that has joined the room'}, 'room_id': {'type': 'string', 'description': 'The unencrypted room ID (starting with !), not a room alias'}, 'message_template': {'type': 'large_string', 'description': 'Jinja2 template for the plain-text message; leave empty to send the workflow data as JSON', 'value': 'MISP event: {{ Event.info }}', 'jinja_supported': True}}, 'blocking': False, 'support_filters': True, 'expect_misp_core_format': False}
-
input:
Workflow data or matchingData, and an optional Jinja2 message template.
-
output:
Boolean success; errors indicate an unsuccessful or unacknowledged send.
-
references:
https://spec.matrix.org/latest/client-server-api/#put_matrixclientv3roomsroomidsendeventtypetxnid
-
requirements:
requests
Mattermost¶
Simplistic module to send message to a Mattermost channel. [source code]
-
features:
-
config:
{'params': {'mattermost_hostname': {'type': 'string', 'description': 'The Mattermost domain or URL', 'value': 'example.mattermost.com'}, 'bot_access_token': {'type': 'string', 'description': 'Access token generated when you created the bot account'}, 'channel_id': {'type': 'string', 'description': 'The channel you added the bot to'}, 'message_template': {'type': 'large_string', 'description': 'The template to be used to generate the message to be posted', 'value': 'The template will be rendered using Jinja2!', 'jinja_supported': True}}, 'blocking': False, 'support_filters': True, 'expect_misp_core_format': False}
n8n Webhook¶
Send selected MISP event attributes to an authenticated n8n Webhook trigger. [source code]
-
features:
Delivers one selected MISP event as bounded JSON to a server-configured webhook. Includes a credential-free dry run, optional IDS-only selection, source UUIDs and a deterministic payload digest. Excludes deleted data and binary attachments. HTTP delivery does not confirm downstream workflow execution. See https://github.com/MISP/misp-modules/blob/main/documentation/action_mod/n8n_webhook.md.
-
config:
{'params': {'dry_run': {'type': 'string', 'description': 'true previews; false delivers once to n8n', 'value': 'true'}, 'to_ids_only': {'type': 'string', 'description': 'Only include IDS attributes when true', 'value': 'false'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
One selected MISP event with event, object and attribute UUIDs in workflow data.
-
output:
Preview payload or HTTP delivery status, payload SHA-256 and selected/skipped counts.
-
references:
-
requirements:
Published n8n workflow with a POST Webhook trigger using Header authentication.
Nextcloud talk¶
Simplistic module to send a message to a Nextcloud talk conversation. [source code]
-
features:
-
config:
{'params': {'nextcloud_baseurl': {'type': 'string', 'description': 'The Nexctloud domain or URL', 'value': 'https://example.nextcloud.org:443'}, 'nextcloud_app_uuid_login': {'type': 'string', 'description': 'The nextcloud username'}, 'app_access_token': {'type': 'string', 'description': 'The nextcloud application token'}, 'nextcloud_conversation_token': {'type': 'string', 'description': 'The token of the conversation the message should be sent to'}, 'message_template': {'type': 'large_string', 'description': 'The template to be used to generate the message to be posted', 'value': 'The template will be rendered using Jinja2!', 'jinja_supported': True}}, 'blocking': False, 'support_filters': True, 'expect_misp_core_format': False}
OSQuery Pack Publish¶

Publish a MISP query pack to a configured local osquery pack directory. [source code]
-
features:
Atomically publishes a named pack under OSQUERY_PACK_DIRECTORY. Defaults to dry run; existing packs require explicit overwrite. Reuses the export's platform selectors, IDS filtering and bounded scan paths. Publication does not execute queries or reload osquery. See the usage guide.
-
config:
{'params': {'pack_name': {'type': 'string', 'description': 'Required: pack basename, letters/digits/_/- only'}, 'interval': {'type': 'string', 'description': 'Query interval in seconds', 'value': '3600'}, 'scan_path': {'type': 'string', 'description': 'Absolute osquery file path pattern for file scans'}, 'dry_run': {'type': 'string', 'description': 'Preview without writing files', 'value': 'true'}, 'overwrite': {'type': 'string', 'description': 'Replace the complete named pack with this snapshot', 'value': 'false'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
Selected MISP events and object attributes in workflow data.
-
output:
Publication status, pack content, counts, provenance and content SHA-256.
-
references:
https://osquery.readthedocs.io/en/stable/deployment/configuration/#query-packs
-
requirements:
OSQUERY_PACK_DIRECTORY on the module server; filesystem pack distribution and config reload
QRadar Reference Set Publish¶
Publish typed MISP indicators to an existing QRadar reference set and explicit domain. [source code]
-
features:
Adds or refreshes IDS-marked event and object indicators through reference_data_collections/set_entries. Requires an existing reference-set ID and explicit domain ID, validates the target entry type and checks each write acknowledgement. Supports credential-free dry runs and reports partial failures. Set expiry remains controlled by QRadar. Credentials come from the module server environment. See the usage guide.
-
config:
{'params': {'reference_set_id': {'type': 'string', 'description': 'Required: existing QRadar reference-set numeric ID'}, 'domain_id': {'type': 'string', 'description': 'Required: numeric domain ID (0 is Default Domain), or SHARED'}, 'indicator_type': {'type': 'string', 'description': 'ipv4, ipv6, domain, url, md5, sha1, sha256 or sha512', 'value': 'ipv4'}, 'source': {'type': 'string', 'description': 'QRadar entry source label', 'value': 'misp-modules'}, 'dry_run': {'type': 'string', 'description': 'true previews entry payloads without network access', 'value': 'false'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
Selected MISP events and object attributes in workflow data.
-
output:
Counts and per-value created, updated, planned or failed outcomes with MISP provenance.
-
references:
-
requirements:
- requests
- QRadar API 20.0 and an authorized service token with reference-data access
SentinelOne IOC Publish¶
Publish MISP event and object indicators to SentinelOne Threat Intelligence with explicit scope. [source code]
-
features:
Publishes IDS-marked hashes, domains, URLs and IP addresses from supplied events and objects. Requires account or site scope, uses stable external IDs, checks existing records, and supports expiry and dry runs. Existing records are not changed or deleted. Credentials and console URL come from the module server environment. See the usage guide.
-
config:
{'params': {'scope': {'type': 'string', 'description': 'Required: account or site'}, 'scope_id': {'type': 'string', 'description': 'Required: the single SentinelOne account or site ID'}, 'source': {'type': 'string', 'description': 'Stable source namespace, unique to this MISP publisher', 'value': 'misp-modules'}, 'expiration_days': {'type': 'string', 'description': '1-180 days; maximum 30 when publishing IP addresses', 'value': '14'}, 'severity': {'type': 'string', 'description': 'SentinelOne severity score, integer 0-7', 'value': '4'}, 'dry_run': {'type': 'string', 'description': 'true previews payloads without credentials or network access', 'value': 'false'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
MISP events in standard, bare or legacy format, supplied in workflow data.
-
output:
Per-indicator publication outcomes and counts; errors signal incomplete publication.
-
references:
-
requirements:
- requests
- SentinelOne Threat Intelligence.view and Threat Intelligence.manage permissions
Shuffle Workflow Execute¶
Start a Shuffle workflow with selected MISP event and object attributes as its JSON execution argument. [source code]
-
features:
Submits one selected event to the documented workflow execution API. Supports a credential-free dry run by default and optional IDS-only selection. Excludes deleted data and binary attachments, validates the execution acknowledgement, and returns the execution ID without its authorization token. See https://github.com/MISP/misp-modules/blob/main/documentation/action_mod/shuffle_workflow_execute.md.
-
config:
{'params': {'workflow_id': {'type': 'string', 'description': 'Required UUID of the Shuffle workflow to execute'}, 'dry_run': {'type': 'string', 'description': 'true previews; false submits a new workflow execution', 'value': 'true'}, 'to_ids_only': {'type': 'string', 'description': 'Only include IDS attributes when true', 'value': 'false'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
One explicitly selected MISP event with event, object and attribute UUIDs in workflow data.
-
output:
Preview request or submitted execution ID, source UUID, payload digest and selected/skipped counts.
-
references:
-
requirements:
Shuffle API key permitted to execute the selected workflow in the configured organization.
Signal¶
Send a message to Signal recipients or a group through signal-cli-rest-api. [source code]
-
features:
Renders Jinja2 templates using matchingData when present, otherwise data, with a JSON fallback. Sends plain-text messages through POST /v2/send. See the usage guide.
-
config:
{'params': {'signal_api_url': {'type': 'string', 'description': 'Base URL of your signal-cli-rest-api service, including any proxy path prefix', 'value': 'http://localhost:8080'}, 'sender_number': {'type': 'string', 'description': 'Registered or linked Signal account number in international format, e.g. +33123456789'}, 'recipients': {'type': 'string', 'description': 'Comma-separated international phone numbers or signal-cli-rest-api group IDs (group.…)'}, 'message_template': {'type': 'large_string', 'description': 'Jinja2 message template; leave empty to send the workflow data as JSON', 'value': 'MISP event: {{ Event.info }}', 'jinja_supported': True}}, 'blocking': False, 'support_filters': True, 'expect_misp_core_format': False}
-
input:
Workflow data or matchingData, and an optional Jinja2 message template.
-
output:
Boolean success; errors indicate an unsuccessful or unacknowledged send.
-
references:
-
requirements:
- requests
- A configured signal-cli-rest-api service with a registered or linked account
Slack¶
Simplistic module to send messages to a Slack channel. [source code]
-
features:
-
config:
{'params': {'slack_bot_token': {'type': 'string', 'description': 'The Slack bot token generated when you created the bot account'}, 'channel_id': {'type': 'string', 'description': 'The channel ID you want to post messages to'}, 'message_template': {'type': 'large_string', 'description': 'The template to be used to generate the message to be posted', 'value': 'The template will be rendered using Jinja2!', 'jinja_supported': True}}, 'blocking': False, 'support_filters': True, 'expect_misp_core_format': False}
Test action¶
This module is merely a test, always returning true. Triggers on event publishing. [source code]
-
features:
-
config:
{'params': {'foo': {'type': 'string', 'description': 'blablabla', 'value': 'xyz'}, 'Data extraction path': {'type': 'hash_path', 'description': 'Only post content extracted from this path', 'value': 'Attribute.{n}.AttributeTag.{n}.Tag.name'}}, 'blocking': False, 'support_filters': False, 'expect_misp_core_format': False}
Tines Case Create¶
Create a Tines Cases v2 case with a MISP event reference and selected-data counts. [source code]
-
features:
Creates one OPEN case with POST /api/v2/cases. Sends the selected event UUID, active attribute/object counts and an optional MISP link, without copying observable values or attachments. Supports a credential-free dry run (default), explicit team/priority and server-side connection settings. Each live invocation creates a new case; no automatic retries or duplicate suppression. See https://github.com/MISP/misp-modules/blob/main/documentation/action_mod/tines_case_create.md.
-
config:
{'params': {'team_id': {'type': 'string', 'description': 'Required positive numeric Tines team ID'}, 'name_prefix': {'type': 'string', 'description': 'Case name prefix (1–64 ASCII letters, digits, spaces, ._-)', 'value': 'MISP event'}, 'priority': {'type': 'string', 'description': 'info, low, medium, high or critical', 'value': 'medium'}, 'dry_run': {'type': 'string', 'description': 'true previews without network access; false creates a new case', 'value': 'true'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
Exactly one selected MISP event in workflow data, with a valid event UUID.
-
output:
Planned case payload or acknowledged case ID, team, priority and event reference.
-
references:
-
requirements:
Tines API key permitted to create cases in the configured team.
Torq Case Create¶
Create a Torq case with a MISP event reference, provenance tags and selected-data counts. [source code]
-
features:
Creates one new case using POST /public/v1alpha/cases. Includes a credential-free dry run by default, explicit reporter/severity and server-side credentials. Sends source UUID and counts rather than event contents. Repeated live invocations create new cases; no automatic retries. See https://github.com/MISP/misp-modules/blob/main/documentation/action_mod/torq_case_create.md.
-
config:
{'params': {'reporter_email': {'type': 'string', 'description': 'Required email of the Torq case reporter'}, 'title_prefix': {'type': 'string', 'description': '1–64 ASCII letters, digits, spaces, ._-', 'value': 'MISP event'}, 'severity': {'type': 'string', 'description': 'informational, low, medium, high or critical', 'value': 'medium'}, 'dry_run': {'type': 'string', 'description': 'true previews; false creates a new case', 'value': 'true'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
Exactly one explicitly selected MISP event in workflow data, with a valid event UUID.
-
output:
Planned case payload or confirmed Torq case ID, state, severity and source event UUID.
-
references:
-
requirements:
Torq API credentials permitted to create cases and a valid case reporter email.
Wazuh CDB Publish¶
Upload MISP event and object indicators to an explicitly named Wazuh CDB source list. [source code]
-
features:
Uploads one typed, deduplicated list of to_ids indicators using PUT /lists/files/{filename}. Credentials come from the module server environment. Supports a credential-free dry run and explicit overwrite; overwrite replaces the entire list with the supplied snapshot. Checks the Wazuh acknowledgement, refuses empty lists and optionally requests an analysisd reload on the manager or cluster without a full manager restart. See the usage guide.
-
config:
{'params': {'filename': {'type': 'string', 'description': 'Required: dedicated list basename, e.g. misp-ipv4'}, 'indicator_type': {'type': 'string', 'description': 'ipv4, ipv6, domain, md5, sha1, sha256 or sha512', 'value': 'ipv4'}, 'overwrite': {'type': 'string', 'description': 'true replaces the complete existing file with this snapshot', 'value': 'false'}, 'dry_run': {'type': 'string', 'description': 'true previews the upload without network access', 'value': 'false'}, 'reload': {'type': 'string', 'description': 'none (upload only), manager (local node) or cluster (all nodes): reload analysisd after upload', 'value': 'none'}}, 'blocking': True, 'support_filters': False, 'expect_misp_core_format': True}
-
input:
Selected MISP events and object attributes in workflow data.
-
output:
Upload and reload status, selected filename, indicator counts, content SHA-256 and activation notice.
-
references:
- https://documentation.wazuh.com/current/user-manual/api/reference.html#tag/Lists
- https://documentation.wazuh.com/current/user-manual/api/reference.html#tag/Manager
- https://documentation.wazuh.com/current/user-manual/api/reference.html#tag/Cluster
- https://documentation.wazuh.com/current/user-manual/ruleset/cdb-list.html
-
requirements:
- requests
- Wazuh server API credentials with lists:update and lists:delete permissions
- Optional reload: manager:read/manager:restart or cluster:read/cluster:restart permissions