Indicators of Compromise #325
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
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 |
|---|---|---|
| @@ -1,26 +1,22 @@ | ||
| --- | ||
| navigation_title: "Indicators of compromise" | ||
| mapped_pages: | ||
| - https://www.elastic.co/guide/en/security/current/indicators-of-compromise.html | ||
| - https://www.elastic.co/guide/en/serverless/current/security-indicators-of-compromise.html | ||
| --- | ||
|
|
||
| # Troubleshoot indicators of compromise [troubleshoot-indicators-page] | ||
|
|
||
| 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 [default {{elastic-sec}} indices](../../solutions/security/get-started/configure-advanced-settings.md#update-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 [Elastic Common Schema (ECS)](https://www.elastic.co/guide/en/ecs/{{ecs_version}}). | ||
|
|
||
| ::::{note} | ||
| These troubleshooting steps also apply to the [Threat Intelligence view](../../solutions/security/get-started/enable-threat-intelligence-integrations.md). | ||
| :::: | ||
|
|
||
Oops, something went wrong.
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.
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.
@Mpdreamz @reakaleek, could you help me out with the correct syntax here since we shouldn’t use attributes in links? 🙏
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, I don't actually know the answer to that.
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.
@Mpdreamz, would you be able to help with this? Thanks!