﻿---
title: Add Osquery Response Actions
description: Osquery Response Actions allow you to add live queries to custom query rules so you can automatically collect data on systems the rule is monitoring...
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/solutions/security/investigate/add-osquery-response-actions
products:
  - Elastic Cloud Serverless
  - Elastic Security
---

# Add Osquery Response Actions
<warning>
  This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features.
</warning>

Osquery Response Actions allow you to add live queries to custom query rules so you can automatically collect data on systems the rule is monitoring. Use this data to support your alert triage and investigation efforts.
<admonition title="Requirements">
  - Ensure you have the appropriate [Elastic Stack subscription](https://www.elastic.co/pricing) or [Serverless project feature tier](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/deploy-manage/deploy/elastic-cloud/project-settings).
  - The [Osquery manager integration](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/solutions/security/investigate/manage-integration) must be installed.
  - Elastic Agent's [status](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/reference/fleet/monitor-elastic-agent) must be `Healthy`. Refer to [Common problems with Fleet and Elastic Agent](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/troubleshoot/ingest/fleet/common-problems) if it isn’t.
  - Your role must have [Osquery feature privileges](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/solutions/security/investigate/osquery).
  - You can only add Osquery Response Actions to custom query rules.
</admonition>

![The Osquery response action](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/solutions/images/security-available-response-actions-osquery.png)


## Add Osquery Response Actions to rules

You can add Osquery Response Actions to new or existing custom query rules. Queries run every time the rule executes.
1. Choose one of the following:
   - **New rule**: When you are on the last step of [custom query rule](/elastic/docs-content/pull/4435/solutions/security/detect-and-alert/create-detection-rule#create-custom-rule) creation, go to the Response Actions section and click the **Osquery** icon.
- **Existing rule**: Edit the rule’s settings, then go to the **Actions** tab. In the tab, click the **Osquery** icon under the Response Actions section.
  <note>
  If the rule’s investigation guide is using an Osquery query, you’ll be asked if you want to add the query as an Osquery Response Action. Click **Add** to add the investigation guide’s query to the rule’s Osquery Response Action.
  </note>
2. Specify whether you want to set up a single live query or a pack:
   - **Query**: Select a saved query or enter a new one. After you enter the query, you can expand the **Advanced** section to set a timeout period for the query, and view or set [mapped ECS fields](/elastic/docs-content/pull/4435/solutions/security/investigate/osquery#osquery-map-fields) included in the results from the live query (optional).
  <note>
  Overwriting the query’s default timeout period allows you to support queries that take longer to run. The default and minimum supported value for the **Timeout** field is `60`. The maximum supported value is `86400` (24 hours).
  </note>
  <tip>
  You can use [placeholder fields](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/solutions/security/investigate/use-placeholder-fields-in-osquery-queries) to dynamically add alert data to your query.
  </tip>
- **Pack**: Select from available query packs. After you select a pack, all of the queries in the pack are displayed.
  <tip>
  Refer to [prebuilt packs](/elastic/docs-content/pull/4435/solutions/security/investigate/osquery#osquery-prebuilt-packs-queries) to learn about using and managing Elastic prebuilt packs.
  </tip>
  ![Shows how to set up a single query](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/solutions/images/security-setup-single-query.png)
3. Click the **Osquery** icon to add more live queries (optional).
4. Click **Create & enable rule** (for a new rule) or **Save changes** (for existing rules) to finish adding the queries.


## Edit Osquery Response Actions

If you want to choose a different query or query pack for the Osquery Response Action to use, edit the rule to update the Response Action.
<important>
  If you edited a saved query or query pack that an Osquery Response Action is using, you must reselect the saved query or query pack on the related Osquery Response Action. Query changes are not automatically applied to Osquery Response Actions.
</important>

1. Edit the rule’s settings, then go to the **Actions** tab.
2. Modify the settings for Osquery Response Actions you’ve added.
3. Click **Save changes**.


## Find query results

When a rule generates an alert, Osquery automatically collects data on the host. Query results are displayed within the **Response** tab in the left panel of the alert details flyout. The number next to the **Response Results** tab represents the number of queries attached to the rule, in addition to endpoint response actions run by the rule.
<note>
  Refer to [Examine Osquery results](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/solutions/security/investigate/examine-osquery-results) for more information about query results.
</note>

![Shows how to set up a single query](https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/4435/solutions/images/security-osquery-results-tab.png)