> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/risk-management/misconfigurations-premium/spm-customization.md).
# SPM customization
You can fully manage the entire misconfiguration lifecycle using DoControl's manual customization capability to override scanned security checks. You can manually modify both:
* [Misconfiguration status](#modify-misconfiguration-status) - Manually indicate if a security check passed, failed, or was skipped.
* [Misconfiguration impact](#modify-misconfiguration-impact) - Manually change a security check impact to a different level.
{% hint style="success" %}
If you wish, you can [schedule an automatic reset](#schedule-reset-for-modified-statuses) of security checks that have been modified for status (Pass, Fail, Error, Info, Skipped).
{% endhint %}
## Modify misconfiguration status
Some security checks cannot be validated by automatic scanning. DoControl empowers admin users to manage your compliance efforts by manually changing the security check status to a permanent status:
* **Pass** - Security check is compliant
* **Fail** - Security check is not compliant
* **Skip** - Security check was reviewed and dismissed. Skipped security checks are not included in the total compliance score or SPM dashboard analytics.
{% hint style="info" %}
* A manually changed status is not overridden in the next hourly scan.
* You can also modify misconfiguration statuses [in bulk](#spm-bulk-modification).
{% endhint %}
#### To manually change the misconfiguration status:
1. Click the arrow next to the status for a specific security check.
2. Select the new status from the dropdown list: Pass, Fail or Skip.\
\
3. You can apply **Skip** to any status: Pass, Error, Fail or Info.
A changed status is indicated with the **Modified** icon, the name of the user who changed the status, and when.
#### To revert to the original misconfiguration status:
If you change your mind, you can always change a manually modified status back to the previously detected status and scan again.
{% hint style="info" %}
Note: The **Modified**  icon indicates a status was manually modified.
{% endhint %}
1. Click the arrow next to a manually changed status for a specific security check.
2. Select **Reset**.\
\
\
\
The misconfiguration status reverts to the previously detected status.
## Modify misconfiguration impact
Some companies might consider specific security checks as having a higher or lower impact. Misconfiguration impacts are also not determined by a compliance standard, such as CIS. DoControl empowers admin users to manage your compliance efforts by manually changing the security check impact to a different level:
* **Critical** - Security checks that have a severe impact on your organization if not remediated.
* **High** - Security checks that have a major impact on your organization if not remediated.
* **Medium** - Security checks that have a moderate impact on your organization if not remediated.
* **Low** - Security checks that don't really affect your organization if not remediated.
{% hint style="info" %}
* A manually changed impact is not overridden in the next hourly scan.
* You can also modify misconfiguration impacts [in bulk](#spm-bulk-modification).
* Use the filters to search for all **modified** impacts.
{% endhint %}
#### To manually change the misconfiguration impact:
1. Click the arrow next to the impact for a specific security check.
2. Select the new impact from the dropdown list: Critical, High, Medium, or Low.\
\
A changed impact is indicated with the **Modified** icon, the name of the user who changed the impact, and when.
#### To revert to the original misconfiguration impact:
If you change your mind, you can always change a manually modified impact back to the previously detected impact and scan again.
{% hint style="info" %}
Note: The **Modified**  icon indicates an impact was manually modified.
{% endhint %}
1. Click the arrow next to a manually changed impact for a specific security check.
2. Select **Reset**.\
\
\
\
The misconfiguration impact reverts to the previously detected impact.
## SPM bulk modification
You can modify both the status and impact level of multiple security checks in bulk, saving you time and effort.
1. Select multiple security checks.
2. Click **Modify status**.\
Change the status of the selected security checks to the relevant status.\
OR
3. Click **Modify impact**.\
Change the impact of the selected security checks to the relevant impact.
## Schedule reset for modified statuses
To keep aligned with your compliance standard, you can automatically reset security checks that have been modified for status (Pass, Fail, Error, Info, Skipped) on a recurring basis.
1. In **SPM misconfigurations**, click the **Settings** icon.
2. Toggle **on** to reset security checks whose status has been modified.
3. Select the frequency for DoControl to reset your modified security checks:
* 1st day of every month
* 1st day of every quarter
* 1st day of every year
4. Click **Save**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.docontrol.io/docontrol-user-guide/risk-management/misconfigurations-premium/spm-customization.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
icon.
2. Toggle **on** to reset security checks whose status has been modified.
3. Select the frequency for DoControl to reset your modified security checks:
* 1st day of every month
* 1st day of every quarter
* 1st day of every year
4. Click **Save**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.docontrol.io/docontrol-user-guide/risk-management/misconfigurations-premium/spm-customization.md?ask=