-
Notifications
You must be signed in to change notification settings - Fork 469
[ti_cyware_threat_intelligence] Initial release of Cyware Threat Intelligence #14500
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
base: main
Are you sure you want to change the base?
[ti_cyware_threat_intelligence] Initial release of Cyware Threat Intelligence #14500
Conversation
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
/test |
🚀 Benchmarks reportTo see the full report comment with |
|
💚 Build Succeeded
|
}) | ||
).flatten(), | ||
"want_more": has(body.next) && body.next != null, | ||
"page_number": has(body.next) && body.next != null ? int(state.?page_number.orValue(1)) + 1 : 1, |
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.
Please split this over lines.
What happens when state.page_number
does not exist and body.next
does and is not null? Then we start at 2. Is that intended? Can it ever happen?
}, | ||
}) | ||
: | ||
{ |
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.
In this branch, we lose all the accumulated state
fields. Is that acceptable?
Proposed commit message
The initial release includes an indicator data stream for supporting indicators via REST API, along with their corresponding dashboards and visualizations.
Cyware Threat Intelligence fields are mapped to their corresponding ECS fields where possible.
Test samples were derived from documentation.
Checklist
changelog.yml
file.How to test this PR locally
Related issues
Screenshots