-
Notifications
You must be signed in to change notification settings - Fork 474
[ti_threatq] Update confidence scoring logic, IOC ingestion batch size, ECS field mapping issues and dashboard #12968
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…mapping issues and dashboard
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
threat |
2557.54 | 1375.52 | -1182.02 (-46.22%) | 💔 |
To see the full report comment with /test benchmark fullreport
packages/ti_threatq/data_stream/threat/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
], | ||
"threat": { | ||
"indicator": { | ||
"description": "This is a sample description.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you give an real-world (anonymized) example of this value?
I would like to see if it fits the ECS description: https://www.elastic.co/guide/en/ecs/current/ecs-threat.html#field-threat-indicator-description
packages/ti_threatq/data_stream/threat/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/ti_threatq/data_stream/threat/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
packages/ti_threatq/data_stream/threat/elasticsearch/ingest_pipeline/default.yml
Outdated
Show resolved
Hide resolved
@@ -154,7 +154,7 @@ | |||
"description": "", | |||
"params": { | |||
"fontSize": 12, | |||
"markdown": "**Navigation**\n\n**[ThreatQ Overview (This Page)](/app/dashboards#/view/ti_threatq-a05fd810-78f1-11ec-a97c-7db1518ab848)** \n[ThreatQ Files](/app/dashboards#/view/ti_threatq-ab289de0-78f1-11ec-a97c-7db1518ab848) \n[ThreatQ URLs](/app/dashboards#/view/ti_threatq-b45b0c40-78f1-11ec-a97c-7db1518ab848) \n\n[Integrations Page](/app/integrations/detail/ti_threatq/overview)\n\n\n**Overview**\n\nThis dashboard is a health overview related to the ThreatQ integration.\n\nThe dashboard is made to provide general statistics and show the health of the ingestion of indicators from ThreatQ. \n\nIt shows the ingestion rates (by default it fetches new updates every 10 minutes) and provides a few filters for drilling down to specific indicator types retrieved from ThreatQ.", | |||
"markdown": "**Navigation**\n\n**This Page** \n[ThreatQ Files](/app/dashboards#/view/ti_threatq-ab289de0-78f1-11ec-a97c-7db1518ab848) \n[ThreatQ URLs](/app/dashboards#/view/ti_threatq-b45b0c40-78f1-11ec-a97c-7db1518ab848) \n\n[Integrations Page](/app/integrations/detail/ti_threatq/overview)\n\n\n**Overview**\n\nThis dashboard is a health overview related to the ThreatQ integration.\n\nThe dashboard is made to provide general statistics and show the health of the ingestion of indicators from ThreatQ. \n\nIt shows the ingestion rates (by default it fetches new updates every 10 minutes) and provides a few filters for drilling down to specific indicator types retrieved from ThreatQ.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is not right. The "This Page" in the gist is a place-holder, this should be "ThreatQ Overview". The 'this page'-ness is indicated by the bolding and non-link status of the text.
Also, all the lines have two spaces before the new line; this is not necessary.
Same below.
@@ -627,7 +627,7 @@ processors: | |||
tag: date_sources_created_at | |||
target_field: _ingest._value.created_at | |||
formats: | |||
- ISO8601 | |||
- 'yyyy-MM-dd HH:mm:ss' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we know that all the timestamps are in this format?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, In live logs we have date in this format. And also in the existing pipeline, we have used this format.
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From previous review:
#12968 (comment)
and
#12968 (comment)
], | ||
"threat": { | ||
"indicator": { | ||
"description": "IP x.x.x.x was observed delivering the Angler EK.", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this value is taken from ECS doc. What I meant is to add a real-world sample value (sanitized) from Threatq.
field: threatq.ioc_expired_at | ||
field: threatq.ioc_expires_at |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, here the intention is to set threatq.ioc_expired_at
to either threatq.expires_at
or threatq.expired_at
. Based on that, we do indicator expiration. There is no field threatq.ioc_expires_at
that we are going to need.
💚 Build Succeeded
History
|
|
@@ -452,7 +452,7 @@ | |||
], | |||
"threat": { | |||
"indicator": { | |||
"description": "IP x.x.x.x was observed delivering the Angler EK.", | |||
"description": "No longer poses a serious threat", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This value doesn't bode well with the ECS definition of threat.indicator.description
, https://www.elastic.co/guide/en/ecs/current/ecs-threat.html#field-threat-indicator-description which represents an action. Lets remove this field.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually we are not getting description in live logs. We have taken this response from the sample log which is already present in existing integration. And also threat.indicator.description
ecs mapping is also present in existing integration.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Can be merged after @efd6 approval.
packages/ti_threatq/kibana/dashboard/ti_threatq-a05fd810-78f1-11ec-a97c-7db1518ab848.json
Show resolved
Hide resolved
packages/ti_threatq/kibana/dashboard/ti_threatq-ab289de0-78f1-11ec-a97c-7db1518ab848.json
Show resolved
Hide resolved
packages/ti_threatq/kibana/dashboard/ti_threatq-b45b0c40-78f1-11ec-a97c-7db1518ab848.json
Show resolved
Hide resolved
Package ti_threatq - 1.32.0 containing this change is available at https://epr.elastic.co/package/ti_threatq/1.32.0/ |
…e, ECS field mapping issues and dashboard (#12968) * Update confidence scoring logic, IOC ingestion batch size, ECS field mapping issues and dashboard * Update changelog * Resolve review comments * Update id and indicator_id field type to long and dashboard * Update description in log and set threatq.ioc_expired_at from threatq.expires_at
Type of change
Proposed commit message
Checklist
changelog.yml
file.How to test this PR locally
Related issues
Screenshot