Details
| ID | MISP Feed |
|---|---|
| Provider | OpenSource |
| Category | Data Enrichment & Threat Intelligence |
| From Version | 5.5.0 |
| Docker Image | demisto/python3:3.12.13.10116658 |
| Supported Modules | Agentix XSIAM |
README
Indicators feed from MISP.
This integration was integrated and tested with version 1.0 of MISP Feed.
MISP Feed integration allows you to ingest feeds into TIM via an MISP instance.
To ingest feeds via MISP, you must first configure a MISP instance and have the proper credentials.
To ingest specific feeds (Bambenek Consulting Feed, BruteForceBlocker Feed, etc.) directly to TIM without any authorization, you can use one of our dedicated feed content packs available in Marketplace.
To ingest feeds via a URL, you could use one of the following content packs:
- CSV Feed
- JSON Feed
- Plain Text Feed
- RSS Feed
Configure MISP Feed in Cortex
| Parameter | Description | Required |
|---|---|---|
| Your server URL | True | |
| API Key | The API Key to use for the connection. | True |
| Client Certificate | False | |
| Private Key | False | |
| Timeout | The timeout of the HTTP requests sent to the MISP API (in seconds). If no value is provided, the timeout will be set to 60 seconds. | False |
| Trust any certificate (not secure) | False | |
| Use system proxy settings | False | |
| Fetch indicators | False | |
| Indicator Reputation | Indicators from this integration instance will be marked with this reputation. | False |
| Source Reliability | Reliability of the source providing the intelligence data. | True |
| Feed Fetch Interval | False | |
| Bypass exclusion list | When selected, the exclusion list is ignored for indicators from this feed. This means that if an indicator from this feed is on the exclusion list, the indicator might still be added to the system. | False |
| Max. indicators per fetch | Limit the number of indicators retrieved in a fetch run. | False |
| MISP Attribute Tags | Attributes having one of the tags, or being an attribute of an event having one of the tags, will be returned. You can enter a comma-separated list of tags, for example <tag1,tag2,tag3>. The list of MISP tags can be found in your MISP instance under ‘Event Actions’>’List Tags’ | False |
| MISP Attribute Types | Attributes of one of these types will be returned. You can enter a comma-separated list of types, for example <type1,type2,type3>. The list of MISP types can be found in your MISP instance then ‘Event Actions’>’Search Attributes’>’Type dropdown list’ | False |
| Query | JSON query to filter MISP attributes. When the query parameter is used, Attribute Types and Attribute Tags parameters are not used. You can check for the correct syntax at https://<Your MISP url>/servers/openapi#operation/restSearchAttributes | False |
| Traffic Light Protocol Color | The Traffic Light Protocol (TLP) designation to apply to indicators fetched from the feed. | False |
| Tags | Supports CSV values. | False |
Commands
You can execute these commands from the 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.
misp-feed-get-indicators
Gets indicators from the feed.
Base Command
misp-feed-get-indicators
Input
| Argument Name | Description | Required |
|---|---|---|
| limit | The maximum number of results to return. Default is 10. | Optional |
| tags | Tags of the attributes to search for. | Optional |
| attribute_type | Types of the attributes to search for. | Optional |
| query | JSON query to filter MISP attributes. When a query argument is used attribute_type and tags arguments are not used. You can check for the correct syntax at https://<Your MISP url>/servers/openapi#operation/restSearchAttributes. | Optional |
Context Output
{
"MISPFeed": {
"Indicators": {
"0": {
"fields": {
"Category": "Payload delivery",
"Description": "desc",
"SHA256": "somehash",
"Updated Date": 1607517728,
"trafficlightprotocol": "GREEN"
},
"rawJSON": {
"FeedURL": "someurl",
"type": "File",
"value": {
"Event": {
"distribution": 1,
"id": 123,
"info": "some info",
"org_id": 1,
"orgc_id": 7,
"uuid": "some uuid"
},
"category": "Payload delivery",
"comment": "desc",
"deleted": false,
"disable_correlation": false,
"distribution": 5,
"event_id": 143,
"first_seen": null,
"id": 69548,
"last_seen": null,
"object_id": 0,
"object_relation": null,
"sharing_group_id": 0,
"timestamp": 1607517728,
"to_ids": true,
"type": "sha256",
"uuid": "some uuid",
"value": "some hash"
}
},
"service": "MISP",
"type": "File",
"value":"somehash"
}
}
}
}
Command Example
!misp-feed-get-indicators tags=tlp:% attribute_type=ip-src
Human Readable Output
Retrieved 7 indicators.
Additional Information
If you experience a timeout error while fetching indicators, the following query configuration may be helpful for you.
You can configure the feed to return results from the last 24 hours as shown below:
{
"returnFormat": "json",
"type": {
"OR": []
},
"tags": {
"OR": []
},
"last":"24h"
}
Both of the above queries can be modified however you would like depending on your specific use case. Additional information can be found here https://www.misp-project.org/openapi/#tag/Attributes/operation/restSearchAttributes
Configuration parameters
url— Server URL (required)credentials— (required)certificate— Client Certificatemax_indicator_to_fetch— Max. indicators per fetchtimeout— Timeoutfeed— Fetch indicatorsfeedIncremental— Incremental FeedfeedReputation— Indicator Reputationperformance— Remove rawJSON from indicatorsfeedReliability— Source Reliability (required)feedExpirationPolicy—feedExpirationInterval—feedFetchInterval— Feed Fetch IntervalfeedBypassExclusionList— Bypass exclusion listattribute_tags— MISP Attribute Tagsattribute_types— MISP Attribute Typesquery— Querytlp_color— Traffic Light Protocol ColorfeedTags— Tagsproxy— Use system proxy settingsinsecure— Trust any certificate (not secure)
Commands (1)
-
misp-feed-get-indicatorsGets indicators from the feed.
category: Data Enrichment & Threat Intelligence provider: OpenSource commonfields: id: MISP Feed version: -1 sectionorder: - Connect - Collect configuration: - defaultvalue: https://example.com/ display: Server URL name: url required: true type: 0 section: Connect - displaypassword: API Token name: credentials type: 9 required: true hiddenusername: true section: Connect - display: Client Certificate displaypassword: Private Key name: certificate type: 9 required: false section: Connect - display: Max. indicators per fetch name: max_indicator_to_fetch type: 0 additionalinfo: In case of performance issues leading to timeouts, try limiting the number of indicators retrieved in a fetch run.``` required: false advanced: true section: Collect - display: Timeout name: timeout defaultvalue: "60" type: 0 additionalinfo: The timeout of the HTTP requests sent to the MISP API (in seconds). If no value is provided, the timeout will be set to 60 seconds. required: false section: Connect - display: Fetch indicators name: feed defaultvalue: 'true' type: 8 required: false section: Collect - additionalinfo: Incremental feeds pull only new or modified indicators that have been sent from the integration. The determination if the indicator is new or modified happens on the 3rd-party vendor's side and only indicators that are new or modified are sent to Cortex XSOAR. Therefore, all indicators coming from these feeds are labeled new or modified. display: Incremental Feed name: feedIncremental defaultvalue: 'true' type: 8 hidden: true required: false section: Collect - display: Indicator Reputation name: feedReputation defaultvalue: Suspicious type: 18 options: - None - Good - Suspicious - Bad additionalinfo: Indicators from this integration instance will be marked with this reputation. required: false section: Collect - additionalinfo: 'Should be used in case of performance issues leading to timeouts. Note: When selecting this checkbox, indicator mapping cannot be performed.' display: Remove rawJSON from indicators name: performance defaultvalue: "false" type: 8 required: false section: Collect - display: Source Reliability name: feedReliability defaultvalue: F - Reliability cannot be judged type: 15 required: true options: - A - Completely reliable - B - Usually reliable - C - Fairly reliable - D - Not usually reliable - E - Unreliable - F - Reliability cannot be judged additionalinfo: Reliability of the source providing the intelligence data. section: Collect - display: "" name: feedExpirationPolicy defaultvalue: indicatorType type: 17 options: - never - interval - indicatorType required: false section: Collect - display: "" name: feedExpirationInterval defaultvalue: "20160" type: 1 required: false section: Collect - display: Feed Fetch Interval name: feedFetchInterval defaultvalue: "240" type: 19 required: false section: Collect - display: Bypass exclusion list name: feedBypassExclusionList type: 8 additionalinfo: When selected, the exclusion list is ignored for indicators from this feed. This means that if an indicator from this feed is on the exclusion list, the indicator might still be added to the system. required: false section: Connect - display: MISP Attribute Tags additionalinfo: Attributes having one of the tags, or being an attribute of an event having one of the tags, will be returned. You can enter a comma-separated list of tags, for example <tag1>,<tag2>,<tag3>. The list of MISP tags can be found in your MISP instance under 'Event Actions'>'List Tags'. name: attribute_tags type: 0 required: false section: Collect - display: MISP Attribute Types additionalinfo: Attributes of one of these types will be returned. You can enter a comma-separated list of types, for example <type1>,<type2>,<type3>. The list of MISP types can be found in your MISP instance then 'Event Actions'>'Search Attributes'>'Type dropdown list'. name: attribute_types type: 0 required: false section: Collect - display: Query additionalinfo: JSON query to filter MISP attributes. When the query parameter is used Attribute Types and Attribute Tags parameters are not used. You can find the query syntax in the link provided in the integration documentation. name: query type: 12 required: false section: Collect - additionalinfo: The Traffic Light Protocol (TLP) designation to apply to indicators fetched from the feed. display: Traffic Light Protocol Color name: tlp_color options: - RED - AMBER - GREEN - WHITE type: 15 required: false section: Collect - name: feedTags display: Tags type: 0 additionalinfo: Supports CSV values. required: false section: Collect - display: Use system proxy settings name: proxy type: 8 required: false section: Connect - display: Trust any certificate (not secure) name: insecure type: 8 required: false section: Connect description: 'Indicators feed from MISP.' display: MISP Feed name: MISP Feed script: commands: - arguments: - name: limit defaultValue: '10' description: The maximum number of results to return. - name: page defaultValue: '1' description: The page number of the results to retrieve. - name: tags description: Attributes having one of the tags, or being an attribute of an event having one of the tags, will be returned. You can enter a comma-separated list of tags, for example <tag1>,<tag2>,<tag3>. The list of MISP tags can be found in your MISP instance under 'Event Actions'>'List Tags'. - name: attribute_type description: Attributes of one of these types will be returned. You can enter a comma-separated list of types, for example <type1>,<type2>,<type3>. The list of MISP types can be found in your MISP instance under 'Event Actions'>'Search Attributes'>'Type dropdown list'. - name: query description: JSON query to filter MISP attributes. When the query argument is used, attribute_type and tags arguments are not used. You can check for the correct syntax at https://<Your MISP url>/servers/openapi#operation/restSearchAttributes. description: Gets indicators from the feed. name: misp-feed-get-indicators feed: true script: '-' type: python subtype: python3 dockerimage: demisto/python3:3.12.13.10116658 fromversion: 5.5.0 tests: - MISPfeed Test - Fetch Indicators Test