[Yandex Cloud documentation](../../../index.md) > [Yandex Security Deck](../../index.md) > [Step-by-step guides](../index.md) > Alerts > Working with alerts

# Working with alerts

{% note tip %}

If you need to, you can change the info columns displayed in the table. Do it by clicking ![gear](../../../_assets/console-icons/gear.svg) in the row with the table column headers, selecting the info columns you need, and clicking **Apply**.

{% endnote %}

## Changing alert status {#status}

{% list tabs group=instructions %}

- Security Deck UI {#cloud-sd}

  1. Go to [Yandex Security Deck](https://center.yandex.cloud/security/).
  1. In the left-hand panel, select ![alerts](../../../_assets/security-deck/alerts.svg) **Alerts**.
  1. At the top of the window, select the [workspace](../../concepts/workspace.md).
  1. Click the table row containing the [alert](../../concepts/alerts.md) name.
  1. In the window that opens, select the status in the top-left corner.

{% endlist %}


## Updating multiple alerts {#update-batch}

{% list tabs group=instructions %}

- Security Deck UI {#cloud-sd}

  1. Go to [Yandex Security Deck](https://center.yandex.cloud/security/).
  1. In the left-hand panel, select ![alerts](../../../_assets/security-deck/alerts.svg) **Alerts**.
  1. At the top of the window, select the [workspace](../../concepts/workspace.md).
  1. Select one or more alerts using the options to the left of the alert names.
  1. Select an action on the panel below.
  1. In the window that opens, make the changes and click **Save**.

{% endlist %}


## Analyzing alerts with the help of AI {#ai-analysis}

{% list tabs group=instructions %}

- Security Deck UI {#cloud-sd}

  1. Go to [Yandex Security Deck](https://center.yandex.cloud/security/).
  1. In the left-hand panel, select ![alerts](../../../_assets/security-deck/alerts.svg) **Alerts**.
  1. At the top of the window, select the [workspace](../../concepts/workspace.md).
  1. Click the table row containing the alert name.
  1. In the window that opens, click ![sparkles](../../../_assets/console-icons/sparkles-fill.svg) **Alert analysis**.

      The AI ​​assistant's dialog panel with its analysis will open on the right.

{% endlist %}


## Leaving a comment on an alert {#comment}

{% list tabs group=instructions %}

- Security Deck UI {#cloud-sd}

  1. Go to [Yandex Security Deck](https://center.yandex.cloud/security/).
  1. In the left-hand panel, select ![alerts](../../../_assets/security-deck/alerts.svg) **Alerts**.
  1. At the top of the window, select the [workspace](../../concepts/workspace.md).
  1. Click the table row containing an alert name.
  1. In the window that opens, go to the **Comments** tab.
  1. Enter and finalize your comment, then click ![paper-plane](../../../_assets/console-icons/paper-plane.svg) **Send**.

{% endlist %}


## Creating an alert exception {#create-exception}

{% list tabs group=instructions %}

- Security Deck UI {#cloud-sd}

  1. Go to [Yandex Security Deck](https://center.yandex.cloud/security/).
  1. In the left-hand panel, select ![alerts](../../../_assets/security-deck/alerts.svg) **Alerts**.
  1. At the top of the window, select the [workspace](../../concepts/workspace.md).
  1. Select an alert.
  1. In the window that opens:

      * To create an exception for all alert resources, click ![slasheye](../../../_assets/console-icons/eye-slash.svg) **Create exception**.
      * To create an exception for only some resources, on the **Overview** tab, under **Access scope**, select the resources and click ![slasheye](../../../_assets/console-icons/eye-slash.svg) **Create exception**.

  1. In the window that opens, configure the exception settings based on the relevant module:

      {% list tabs %}

      - CSPM

        1. Under **Exception type**, select an action option for the exception you are creating:

            * `Checked manually`: If the conditions specified in the exception are met, the resource will generate only rule compliance signals.
            * `No check required`: If the conditions specified in the exception are met, the resource will not generate any signals, neither on compliance nor on violation.

        1. Under **Rules**, select the CSPM module rules for which the selected resources should not be checked:

            * `All rules`: To exclude the selected resources from the check for compliance with all the CSPM module rules.
            * `Selected rules`: To exclude the selected resources from the check for compliance with a given set of rules. To select the rules:

                * Click ![circle-plus](../../../_assets/console-icons/circle-plus.svg) **Select rules**.
                * In the window that opens, select the rules you want to exclude from compliance checks. If required, use the filter or search at the top of the window.
                * Click **Save selection**.

        1. Under **Reason for exclusion**, give in any format the reason why you are creating an exception.
        1. Click **Create exception**.

      - KSPM

        1. Under **Rules**, select the Kubernetes control rules the selected resources should not be checked against:

            * `All rules`: To exclude the selected resources from the check for compliance with all the Kubernetes control rules.
            * `Selected rules`: To exclude the selected resources from the check for compliance with a given set of rules. To select the rules:

                * Click ![circle-plus](../../../_assets/console-icons/circle-plus.svg) **Select rules**.
                * In the window that opens, select the rules you want to exclude from compliance checks. If required, use the filter or search at the top of the window.
                * Click **Save selection**.

        1. Under **Objects (optional)**, use a namespace to specify the objects to exclude from the check:
            * Enable **Namespaces**.
            * Enter the object name from the namespace. The naming requirements are as follows:

              * Length: between 3 and 63 characters.
              * It can only contain lowercase Latin letters, numbers, and hyphens.
              * It must start with a letter and cannot end with a hyphen.

            To exclude multiple objects at once, use wildcards. For example, a pattern like `*-ns` will exclude objects with the `ns` suffix, such as `prod-ns` and `test-ns`.

        1. Under **Reason for exclusion**, give in any format the reason why you are creating an exception.
        1. Select ![image](../../../_assets/console-icons/toggle-on.svg) **Activate exception**.
        1. Click **Create exception**.

      {% endlist %}

{% endlist %}

The created exception will be displayed in the ![file-text](../../../_assets/console-icons/file-text.svg) **Rules and exceptions** section of the relevant module.