-
Notifications
You must be signed in to change notification settings - Fork 190
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
[DOCS] Threat Intelligence - Indicators Page and Indicator Details #2497
Comments
here is the list of PRs related to the work described in the description. The PRs span between 8.4 and 8.5 as in 8.4 the features were under the feature flag but there was no mention of them in the release notes. In parenthesis my comments to extend on the PR title, happy to elaborate more if needed. Now the question is what is the good way to tag the PRs for the best representation in the release notes, especially when it comes to
|
btw as far as I understand the PRs that we merged in 8.4 won't be picked up by the automation for 8.5 release notes. How do we go about it? |
I tagged all the 8.5 PRs with |
Description
With the work done over the last few release cycles:
threat.indicator.file.hash.sha256 = "c207213257a63589b1e1bd2f459b47becd000c1af8ea7983dd9541aff145c3ba"
) along with the associated value in the source index (file.hash.sha256 = "c207213257a63589b1e1bd2f459b47becd000c1af8ea7983dd9541aff145c3ba"
) into a new timeline. The goal with this functionality is so the user can easily find any matched activity within their environment, along with any alerts and other events that may have triggered. (Epic)Definitions
What is Threat Intelligence?
Threat Intelligence is a research function that sits within the security operation center who is responsible for understanding current and emerging threats and recommending actions against these threats to protect their organizations.
What are IoCs?
An Indicator of Compromise - or IoC in short - is a document, a piece of information, that represents a known malicious threat or reported vulnerability. There are different types of IoCs, for example, URL, file, domain, email address, etc…
Acceptance Test Criteria
Notes
The text was updated successfully, but these errors were encountered: