---
title: "Customise a benchmark"
description: "Exclude checks or change parameters of a benchmark for one node group."
product: "Guardian"
edition: "Classic"
type: "workflow"
url: "https://docs.cloudhouse.com/guardian/classic/control/benchmarks/actions/customize-benchmarks/"
---
# Customise a benchmark

Exclude checks or change parameters of a benchmark for one node group. However, the checks stipulated by the CIS may not be compliant with your individual requirements. As such, Guardian provides the option to customise your benchmarks by excluding certain checks within a benchmark and modifying the values for parameter-based checks on a per node group basis.

Applies to: `Guardian Classic`

## Exclude a benchmark check from a node group

Once a benchmark has been assigned to a node group, you can begin to ascertain what checks may or may not be required and customise the CIS benchmark by excluding individual checks for certain node groups. The following process assumes that the benchmark in question has already been assigned to a node group.

!!! note

    For more information on how to add a benchmark to a node group, see [Add Benchmark / Policy to Node Group](https://docs.cloudhouse.com/guardian/classic/control/benchmarks/actions/add-benchmarkpolicy-to-node-group/index.md).

**To exclude a benchmark check from a node group, complete the following steps**:

1. Navigate to the **Benchmarks** tab (**Control** > **Benchmarks**). The list of public CIS benchmarks are displayed.

    ![Benchmarks tab](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/benchmarks/benchmarks-tab.png)

2. Select the benchmark you want to customise. The benchmark is then displayed with the complete list of checks included.

    !!! tip

        Click on the description of a check to display more details in a side panel. Here, a list of **Involved Node Groups** are displayed, listing each of the groups that are assigned to the benchmark. Exclude any of the node groups from the individual check by deselecting the corresponding check box.
        ![](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/benchmarks/customising/side-panel.png)

3. In the **Node Groups** drop-down menu, locate the node group that you want to exclude the checks from.

    ![Node group located](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/benchmarks/customising/node-group-located.png)

4. Then, click the **Settings** button (![Settings button as shown in the Guardian user interface.](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/buttons/settings.png)) and select **Exclude checks**.

    ![Exclude checks](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/benchmarks/customising/exclude-checks.png)

5. Click the **Enabled** button (![Tick trasnparent backgr 9x9](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/buttons/tick-trasnparent-backgr-9x9.png)) to exclude a check from the selected node group. The button will then display the **Excluded** button (![Excluded check](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/buttons/excluded-check.png)) once the change has registered.

    1. Additionally, you can click to **Disable All Checks** and then work backwards by enabling individual checks, or sections of checks, one at a time.

        ![Exclude list](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/benchmarks/customising/exclude-list.png)

        !!! tip

            When getting started with a new benchmark, it can be beneficial to disable most checks to start with and then incrementally enable individual checks to confirm that they pass, instead of enabling them all by default. This method can prevent unnecessary data being returned each time the benchmark is run.

6. Once you've excluded (or enabled) the required checks, click **Done excluding checks for [node group]** to save your changes.

Next, you can run the benchmark against the node group to see what checks are passing and failing. For more information, see [Run Benchmark](https://docs.cloudhouse.com/guardian/classic/control/benchmarks/actions/run-benchmark/index.md).

## Modify a benchmark parameter for a node group

In addition to excluding benchmark checks, you can also modify a parameter within a benchmark check to further customise your benchmarks according to your individual node group's needs.

!!! note

    Checks that have a modifiable parameter will be listed with a button labeled **Modify X value(s)**.
    ![](https://docs.cloudhouse.com/guardian/classic/assets/images/import-guardian/customizing-benchmarks-2022-12-02/customizing-benchmarks-6.png)

**To modify a benchmark parameter for a node group, complete the following steps**:

1. In the **Benchmarks** tab, select the benchmark you want to modify. The benchmark is then displayed with the complete list of checks included.
2. Click the **Modify X value(s)** button to display the value (or values) eligible for modification.

    ![Modify values](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/benchmarks/customising/modify-values.png)

3. Click on the **Check Title** for the relevant parameter to display the parameter settings in a side panel. Here, the list of node groups currently assigned to each check is displayed.

    ![Settingns side panel](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/benchmarks/customising/settingns-side-panel.png)

4. Click the **Modified Values** field next to the required node group to display the **Modify values for [parameter]** side panel. Here, you can modify the value in the field according to your needs.

    !!! tip

        If a value has not been modified, the **Modified Values** field is displayed as 'Default'. If a check has an existing modification you can click to **Undo Modification** or enter a new value.

    ![Modify values for group](https://docs.cloudhouse.com/guardian/classic/assets/images/guardian/control/benchmarks/customising/modify-values-for-group.png)

5. Once complete, click to **Save** your changes.

Once you have customised benchmarks to meet your needs, you can schedule benchmarks to be executed against a set of nodes in your environment. For more information, see [Schedule Benchmark Reports](https://docs.cloudhouse.com/guardian/classic/tech-articles/schedule-benchmark-reports/index.md).