> 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/remediate-security-issues.md).
# Remediate security issues
With DoControl's Premium Misconfiguration solution, you can follow remediation steps to fix mission-critical misconfigurations, secure your SaaS environment, and stay compliant with industry benchmarks, such as CIS, SOC 2, NIST (CSF) and ISO 27001.
Fixing any misconfigurations across your SaaS stack helps you to:
* **Prevent data breaches and unauthorized access** - Ensure your sensitive data is not exposed to unauthorized users, external attackers, or the public.
* **Maintain compliance with regulations** - Standards like CIS, ISO 27001, SOC 2, NIST (CSF) require secure configurations and proper access controls. Misconfigurations can lead to compliance violations, fines, and legal consequences.
* **Reduce the attack surface** - Attackers can exploit misconfigurations to escalate privileges, install malicious apps, or exfiltrate data. Correcting these gaps minimizes entry points for cyberattacks.
* **Control shadow IT and risky integrations** - Unmonitored SaaS apps and over-permissive integrations increase risk. Remediation ensures apps and APIs adhere to security policies.
## View recommendations to fix
Follow DoControl's recommendations to manually fix any misconfiguration, secure your SaaS stack, and stay compliant with industry standards.
1. For each security check:
* Click the security check name, and then the **Remediation** tab, OR
* Click the **Fix**  icon next to the relevant security check.
2. View the recommendations in the **Remediation** tab to understand how to fix the issue and make the security check compliant with the relevant industry standard.
3. Click [Ticket](/docontrol-user-guide/risk-management/misconfigurations-premium/security-checks/open-jira-ticket.md) to open a ticket in Jira to fix the issue.
4. Click **Ignore** to disregard this security check from now on.
5. Click **Share** to copy the URL for the security check.
## Monitor configuration drifts with workflows
DoControl now supports monitoring and remediating configuration drifts using workflows. This enhancement is a key DoControl differentiator, enabling you to:
* **Continuously monitor for misconfigurations**, even when the SaaS platform itself lacks built-in validation or API-based visibility
* **Maintain ongoing configuration assurance** across your entire SaaS environment, ensuring policies stay enforced over time
* **Validate configuration integrity continuously**, not just at a single point — helping verify that security settings remain intact as your environment evolves.
New capabilities supported by DoControl Include:
* **Fail/pass monitoring** based on SaaS activity logs for real-time visibility
* **Continuous drift detection -** Eliminating the need for once-a-day validation
* **Automated remediation** **through DoControl workflows** - Ensuring misconfigurations are corrected immediately and stay that way
For applicable security checks, a new option appears in the Remediation tab: **Remediate and monitor with DoControl**. From here, you can:
1. Attach an existing workflow
2. Monitor activity related to configuration changes
3. Automatically remediate or notify when a drift is detected
{% hint style="info" %}
To remediate configuration drifts, click **Remediate and monitor with DoControl** in the Misconfigurations > Remediation tab.
{% endhint %}
---
# 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/remediate-security-issues.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.
