---
title: "Asset Ignore Rules"
slug: "asset-ignore-rules"
tags: ["automation", "assets", "asset processing"]
updated: 2021-05-24T19:35:05Z
published: 2021-05-24T19:35:05Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.nucleussec.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Asset Ignore Rules

## Overview

The Nucleus Automation Engine provides **Asset Ignore** rules to help you to only import the assets you want to manage in Nucleus. These rules give you greater control within a scan to choose which assets you would like to import and manage.

Asset Ignore rules work similarly to [Asset Processing](/v1/docs/asset-processing-rules) rules. When a scan is importing, Nucleus checks if you have any Asset Ignore rules set up and then runs the scan through these rules to determine what to import, and how to group those assets upon import.

## Create an Asset Ignore Rule

1. From within a project, navigate to the **Automation** page.
2. Select the **Asset Ignore** option.
3. Click **Add Rule**.
4. In Step 1 of the **Add Asset Ignore Rule** pop-up, complete the **Rule Name** field and then click the Next button.
5. In Step 2 of the rule set up pop-up, add the criteria and conditions on which you want the rule to trigger. When finished, click the **Next** button.

| Condition | Info |
| --- | --- |
| Asset Name | Use wildcard or regex matching to ignore assets with certain hostnames. |
| Asset IP | Is there a certain subnet you care about? You can use ranges in addition to using a single IP. |
| Source | The source of the asset or vulnerability data. |

1. **OPTIONAL**: In Step 3 of the pop-up, you can test the rule against the conditions and critiera you have set.
2. When you're satisifed with how the rule is set up, click the **Save & Finish** button.

If you have any questions, please contact us through the [support center](https://nucleussec.atlassian.net/servicedesk/customer/portal/3).

## Related

- [Automation Workflows](/automation-workflows.md)