- Notifications
You must be signed in to change notification settings - Fork 513
ti_misp: harmonise object fields between datastreams #5917
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
6840890 to be7a37c Compare 🌐 Coverage report
|
| Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
kcreddy left a comment
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.
Need clarification about sample log
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 response doesn't seem to belong to threat attributes API
Was this supposed to be added to threat datastream instead?
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, good catch. Thanks
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.
We are already renaming event.original to misp.attribute earlier in the pipeline.
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.
Fixed.
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.
Sorry, what I actually meant to say was that all these renaming with misp.event.* fields never exists in the Attributes API. It has fields named misp.attribute.* i.e., misp.attribute.Object, misp.attribute.Event, misp.attribute.Tag which were already renamed in the pipeline earlier.
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.
Indeed, you're correct, fixed fixed.
be7a37c to 2b762c1 Compare 2b762c1 to 6446f1e Compare ab82a1c to 473dfb6 Compare
kcreddy left a comment
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 👍🏼 Minor suggestion
packages/ti_misp/changelog.yml Outdated
| # newer versions go on top | ||
| - version: "1.13.1" | ||
| changes: | ||
| - description: Harmonise object and org fields. |
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.
org is probably not relevant anymore in this PR
| Package ti_misp - 1.13.1 containing this change is available at https://epr.elastic.co/search?package=ti_misp |
What does this PR do?
Brings field definitions into agreement. This is the second part of addressing #5834,
Note that if the event added in tests here is add to the threat datastream test, it fails due to a failure of the uri_parts processor to handle
\in the host part of a URL.Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots