You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Run Osquery from investigation guides[security-invest-guide-run-osquery]
8
8
9
9
% What needs to be done: Align serverless/stateful
10
10
@@ -18,7 +18,8 @@ Detection rule investigation guides suggest steps for triaging, analyzing, and r
18
18
::::{admonition} Requirements
19
19
* The [Osquery manager integration](/solutions/security/investigate/manage-integration.md) must be installed.
20
20
* {{agent}}'s [status](asciidocalypse://docs/docs-content/docs/reference/ingestion-tools/fleet/monitor-elastic-agent.md) must be `Healthy`. Refer to [{{fleet}} Troubleshooting](/troubleshoot/ingest/fleet/common-problems.md) if it isn’t.
21
-
* Your role must have [Osquery feature privileges](/solutions/security/investigate/osquery.md).
21
+
* In {{stack}}, your role must have [Osquery feature privileges](/solutions/security/investigate/osquery.md).
22
+
* In {{serverless-short, you must have the appropriate user role to use this feature.}}
22
23
23
24
::::
24
25
@@ -56,7 +57,7 @@ You can only add Osquery to investigation guides for custom rules because prebui
0 commit comments