> 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/security-checks/manage-security-checks.md). # Manage security checks When it comes to misconfiguration management, you can: * [Export misconfigurations ](#export-misconfigurations)- Export the list of all your current or filtered misconfigurations to a CSV file for security audits, compliance reviews, analysis and reporting. * [Modify status](#modify-misconfiguration-status) - Manually override the status of a security check * [Modify impact](#modify-misconfiguration-impact) - Manually change a security check impact to a different level * [Modify status and impact in bulk](#modify-status-and-impact-in-bulk) - Use a bulk action to change the status and impact of several security checks * [Reset security check status](#reset-security-check-status) - Schedule an automatic reset of security checks that have been modified for status ## Export misconfigurations A CSV export creates a point-in-time record of misconfigurations, which is useful for security audits, compliance reviews, and evidence for meeting regulatory requirements. You can also import CSV files into analysis tools (such as Google Sheets or business intelligence platforms) to perform custom trend analysis, enabling deeper insights into your security posture. #### To export the list of all your current or filtered misconfigurations to a CSV file: 1. In the DoControl menu, go to **Security checks**. 2. Click the **Export to CSV** icon to download your current misconfigurations. ## Modify status DoControl gives you the ability to make manual changes to the status of a security check, allowing for organization-specific risk management so you can prioritize your compliance efforts. You can manage your compliance efforts by manually overriding the status of a security check to a different status:
Change status toWhat it means
PassYour SaaS configuration complies with the security check
FailYour SaaS configuration does not comply with the security check. Remediation is required.
IgnoreSecurity check was reviewed and dismissed. Ignored security checks are not included in the total compliance score or 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](#modify-status-and-impact-in-bulk). {% endhint %} #### To manually modify 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 Ignore.\ \
3. You can apply **Ignore** to any status: Pass, Error, Fail or Info. A changed status is indicated with the **Modified** ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FZ8QlyC3r9CiWK5xhCrb8%2Fpencil%20icon.png?alt=media\&token=13a11e2f-eb34-4752-aa37-94139beaaee7)icon, the name of the user who changed the status, and when they changed it.
#### To revert to the original status: You can always change a manually modified status back to the previous status. 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 impact DoControl gives you the ability to make manual changes to the impact of a security check, allowing for organization-specific risk management so you can prioritize your compliance efforts. #### When is it necessary to modify the impact of a security check? * A failed security check labeled "critical" might only be "medium" in your environment due to compensating controls in place. * Some security checks might have a higher or lower impact on your organization than what's indicated. DoControl empowers you 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** ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FZ8QlyC3r9CiWK5xhCrb8%2Fpencil%20icon.png?alt=media\&token=13a11e2f-eb34-4752-aa37-94139beaaee7)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 previous impact and scan again. {% hint style="info" %} Note: The **Modified** ![](https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2FZ8QlyC3r9CiWK5xhCrb8%2Fpencil%20icon.png?alt=media\&token=13a11e2f-eb34-4752-aa37-94139beaaee7) 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. ## Modify status and impact in bulk 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**. 3. Change the status of the selected security checks to the relevant status: * Pass * Fail * Ignore
4. Click **Modify impact**. 5. Change the impact of the selected security checks to the relevant impact: * Critical * High * Medium * Low {% hint style="success" %} Click [Reset](#reset-security-check-status) to revert to the previous status or impact. {% endhint %} ## Reset security check status If you wish to return to default settings, you can schedule an automatic reset of all modified statuses (pass, fail, ignore). 1. Click the **Settings** icon.
2. Toggle the **On** button to schedule a reset. 3. Select the frequency for resetting modified statuses: * Every month * Every quarter * 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/security-checks/manage-security-checks.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.