-
Notifications
You must be signed in to change notification settings - Fork 206
[DOCS] Threat Intelligence - Indicators Page and Indicator Details #2526
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
Merged
Merged
Changes from all commits
Commits
Show all changes
76 commits
Select commit
Hold shift + click to select a range
51a8076
First draft
nastasha-solomon 8f14424
More changes
nastasha-solomon 163a973
Fixing heading
nastasha-solomon b470be8
Removed pre-reqs
nastasha-solomon cc0e172
Input from Dhru
nastasha-solomon e97e4c4
Resize image
nastasha-solomon 4e4ca4c
Re-org
nastasha-solomon d79e14f
Adding more sections
nastasha-solomon 7b4185f
Merge branch 'main' into issue-2497-TIP
nastasha-solomon 9c196be
Adding background
nastasha-solomon aa9ca53
Merge branch 'issue-2497-TIP' of github.com:elastic/security-docs int…
nastasha-solomon 71ef3e5
Updating Elastic UI topic
nastasha-solomon 5133f5d
Revisions
nastasha-solomon f7ef7b0
Adding gif
nastasha-solomon 06d3f92
Removed unfinished parts
nastasha-solomon 78dc0a3
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon c3e1149
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 62a1e69
Merge branch 'main' into issue-2497-TIP
nastasha-solomon d88f855
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 39f7269
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon f86bce6
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon f6c8ef0
Update docs/events/index.asciidoc
nastasha-solomon 7c00ab8
Update docs/getting-started/security-ui.asciidoc
nastasha-solomon 8c20a4d
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 9cc8543
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 39f8360
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon aae27d1
Merge branch 'main' into issue-2497-TIP
nastasha-solomon 8cc4361
Merge branch 'main' into issue-2497-TIP
nastasha-solomon e14c4eb
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 8eea0a7
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 6f80faf
Merge branch 'main' into issue-2497-TIP
nastasha-solomon 68baa9e
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 794c2d9
Merge branch 'main' into issue-2497-TIP
nastasha-solomon 40e1554
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 87815d8
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 2663339
Adding preqs and troubleshooting section
nastasha-solomon 91b13ed
Merge branch 'issue-2497-TIP' of github.com:elastic/security-docs int…
nastasha-solomon ee038d2
Updated screenshot
nastasha-solomon 9063db6
Merge branch 'main' into issue-2497-TIP
nastasha-solomon 0d7e785
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 608f2b0
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 744abdf
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon a833a54
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon f5c34a4
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 5b78453
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 3ef3da1
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 7c2bb9e
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon d3f3cb2
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 778588e
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon c6075c6
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 0f5c11a
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 23e3831
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon fbac7f8
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 17709b2
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon dbae18d
Breaking up example in last section
nastasha-solomon 271d272
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon adca02b
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 66bf56d
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 1758f9d
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 57e6fc9
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 6aa94b7
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon f34f339
Update docs/events/indicators-of-compromise.asciidoc
nastasha-solomon 668ec80
Merge branch 'main' into issue-2497-TIP
nastasha-solomon 52f4a6d
Updated TOC and added Joe's other suggest
nastasha-solomon a474493
Update docs/cases/indicators-of-compromise.asciidoc
nastasha-solomon 078d31d
Update docs/cases/indicators-of-compromise.asciidoc
nastasha-solomon 91aa600
Merge branch 'main' into issue-2497-TIP
nastasha-solomon 4baf66f
Merge branch 'main' into issue-2497-TIP
nastasha-solomon e837936
Update docs/getting-started/security-ui.asciidoc
nastasha-solomon 736a86d
Update docs/getting-started/security-ui.asciidoc
nastasha-solomon 4fa6728
Update docs/cases/indicators-of-compromise.asciidoc
nastasha-solomon b5f1904
Update docs/cases/indicators-of-compromise.asciidoc
nastasha-solomon f6a0fbf
Merge branch 'main' into issue-2497-TIP
nastasha-solomon 2398bee
Update docs/cases/indicators-of-compromise.asciidoc
nastasha-solomon d6bf691
Merge branch 'main' into issue-2497-TIP
nastasha-solomon 8f17bd5
Merge branch 'main' into issue-2497-TIP
nastasha-solomon File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,94 @@ | ||
| [[indicators-of-compromise]] | ||
| = Indicators of compromise | ||
|
|
||
| The Indicators page (*Intelligence -> Indicators*) collects data from enabled threat intelligence feeds and provides a centralized view of indicators, also known as indicators of compromise (IoCs). This topic helps you set up the Indicators page and explains how to work with IoCs. | ||
|
|
||
| .Requirements | ||
| [sidebar] | ||
| -- | ||
| You must have _one_ of the following installed on the hosts you want to monitor: | ||
|
|
||
| * *{agent}* - Install a {fleet-guide}/install-fleet-managed-elastic-agent.html[{fleet}-managed {agent}] and ensure the agent's status is `Healthy`. Refer to {fleet-guide}/fleet-troubleshooting.html[{fleet} Troubleshooting] if it isn't. | ||
| * *{filebeat}* - Install {filebeat-ref}/filebeat-installation-configuration.html[{filebeat}] version 8.x or later. Earlier {filebeat} versions are incompatible with ECS and will prevent indicator data from displaying in the Indicators table. | ||
| -- | ||
|
|
||
| [role="screenshot"] | ||
| image::images/indicators-table.png[Shows the Indicators page] | ||
|
|
||
| [discrete] | ||
| [[ti-indicators]] | ||
| == Threat intelligence and indicators | ||
| Threat intelligence is a research function that analyzes current and emerging threats and recommends appropriate actions to strengthen a company's security posture. Threat intelligence requires proactivity to be useful, such as gathering, analyzing, and investigating various threat and vulnerability data sources. | ||
|
|
||
| An indicator, also referred to as an IoC, is a piece of information associated with a known threat or reported vulnerability. There are many types of indicators, including URLs, files, domains, email addresses, and more. Within SOC teams, threat intelligence analysts use indicators to detect, assess, and respond to threats. | ||
|
|
||
| [discrete] | ||
| [[setup-indicators-page]] | ||
| == Set up the Indicators page | ||
|
|
||
| Install a threat intelligence integration to add indicators to the Indicators page. | ||
|
|
||
|
|
||
| . Choose one of the following: | ||
| * From the {security-app} main menu, go to *Intelligence* -> *Indicators* -> *Add Integrations*. | ||
| * From the {kib} main menu, click *Add integrations*. Scroll down the list of integration categories and select *Threat Intelligence* to filter by threat intelligence integrations. | ||
| . Select a threat intelligence integration, then complete the integration's guided installation. | ||
| + | ||
| NOTE: For more information about available fields, go to the https://docs.elastic.co/integrations[Elastic integration documentation] and search for a specific threat intelligence integration. | ||
|
|
||
| . Return to the Indicators page in {elastic-sec}. Refresh the page if indicator data isn't displaying. | ||
|
|
||
| [discrete] | ||
| [[troubleshoot-indicators-page]] | ||
| === Troubleshooting | ||
| If indicator data is not appearing in the Indicators table after you installed a threat intelligence integration: | ||
|
|
||
| * Verify that the index storing indicator documents is included in the <<update-sec-indices,default {elastic-sec} indices>> (`securitySolution:defaultIndex`). The index storing indicator documents will differ based on the way you're collecting indicator data: | ||
| ** *{agent} integrations* - `logs_ti*` | ||
| ** *{filebeat} integrations* - `filebeat-*` | ||
| * Ensure the indicator data you're ingesting is mapped to {ecs-ref}[Elastic Common Schema (ECS)]. | ||
|
|
||
| [discrete] | ||
| [[intelligence-page-ui]] | ||
| == Indicators page UI | ||
|
|
||
| After you add indicators to the Indicators page, you can <<examine-indicator-details, examine>>, search, filter, and take action on indicator data. Indicators also appear in the Trend view, which shows the occurrence of indicators over time. | ||
|
|
||
| [role="screenshot"] | ||
| image::images/interact-with-indicators-table.gif[width=90%][height=90%][Shows how to interact with the Intelligence page] | ||
|
|
||
| [discrete] | ||
| [[examine-indicator-details]] | ||
| === Examine indicator details | ||
| Learn more about an indicator by clicking *View details*, then opening the Indicator details flyout. The flyout contains these informational tabs: | ||
|
|
||
| * *Overview*: A summary of the indicator, including the indicator's name, the threat intelligence feed it came from, the indicator type, and additional relevant data. | ||
| + | ||
| NOTE: Some threat intelligence feeds provide https://www.cisa.gov/tlp#:~:text=Introduction,shared%20with%20the%20appropriate%20audience[Traffic Light Protocol (TLP) markings]. The `TLP Marking` and `Confidence` fields will be empty if the feed doesn't provide that data. | ||
|
|
||
| * *Table*: The indicator data in table format. | ||
| * *JSON*: The indicator data in JSON format. | ||
| + | ||
| [role="screenshot"] | ||
| image::images/indicator-details-flyout.png[Shows the Indicator details flyout, 600] | ||
|
|
||
| [discrete] | ||
| [[find-related-sec-events]] | ||
| == Find related security events | ||
|
|
||
| Investigating an indicator in <<timelines-ui,Timeline>> helps you find related security events in your environment. You can add an indicator to Timeline from the Indicators table or the Indicator details flyout. | ||
|
|
||
| [role="screenshot"] | ||
| image::images/indicator-in-timeline.png[Shows the results of an indicator being investigated in Timeline] | ||
|
|
||
| When you add an indicator to Timeline, a new Timeline opens with a pre-populated KQL query. The query contains the indicator field-value pair that you selected plus the field-value pair of the mapped source event. | ||
|
|
||
| For example, imagine you've added this file hash indicator to Timeline: | ||
|
|
||
| `threat.indicator.file.hash.sha256 : c207213257a63589b1e1bd2f459b47becd000c1af8ea7983dd9541aff145c3ba` | ||
|
|
||
| A new Timeline opens with an automatically populated KQL query. The query contains the indicator field-value pair (mentioned previously) and the mapped source event field-value pair, which is: | ||
|
|
||
| `file.hash.sha256 : c207213257a63589b1e1bd2f459b47becd000c1af8ea7983dd9541aff145c3ba`. | ||
|
|
||
| Using a KQL query that includes both the indicator and source event allows Timeline to find all events and alerts that have matching field-value pairs. | ||
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.