> 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.md).

# Misconfigurations (premium)

Detect and fix risky SaaS misconfigurations before they become security incidents

Misconfigurations cause about 70% of successful cyberattacks, and are one of the most common, yet preventable causes of data breaches and compliance failures.

With DoControl’s premium Misconfiguration solution, you can protect your SaaS ecosystem against data breaches, system outages, compliance violations, and financial loss across multiple apps and user settings, all with centralized visibility and control.&#x20;

{% hint style="success" %}

* All DoControl customers can monitor these apps for misconfigurations:
  * Google Workspace
  * GitHub
  * Zoom
* To unlock more apps in DoControl's Premium Misconfiguration solution, contact Customer Success.
* The legacy version of SPM Misconfigurations will be phased out by the end of March 2026.&#x20;
  {% endhint %}

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2F9BBDNTrGRI7mRI9kYi7X%2Fposture%20SPM.png?alt=media&amp;token=1930963b-8343-4090-9a75-ea456d2535e5" alt=""><figcaption></figcaption></figure>

With DoControl's Premium Misconfiguration solution, you get:

* **Automatic monitoring -** Detect configuration drifts and compliance gaps across your SaaS apps to surface any critical risks
* **Extensive app coverage** - Monitor dozens of SaaS apps in real-time to protect your entire SaaS stack from misconfigurations
* **Expanded compliance framework** - Enforce security best practices from industry standards: CIS, NIST (CSF), SOC 2 and ISO 27001
* **Misconfiguration posture** - View any compliance drifts in a centralized posture to make timely and informed security decisions&#x20;
* **Guided remediation** - Follow remediation steps to fix mission-critical misconfigurations and stay compliant

## What are SPM misconfigurations?

Misconfigurations occur when there are errors in the setup of an application or service that can lead to security vulnerabilities.&#x20;

SPM misconfigurations are a major threat to SaaS security, and one of the leading causes of data breaches and compliance failures. When it comes to SaaS security posture management (SPM), CISOs aim to detect and prevent SaaS misconfigurations that span multiple app and user settings.&#x20;

### Misconfiguration threats

Misconfigurations can lead to severe consequences if they're not fixed, including:

* **Data breaches** - If users have excessive or unauthorized permissions, they can easily access data which is off limits. If multi-factor authentication is not enforced, hackers can easily infiltrate an organization's SaaS network with only a user name and password. It's then very easy for hackers to potentially steal and publish sensitive data, such as personal information of millions of customers.
* **System outages** - Security incidents that are not detected or responded to in time can lead to disruption of critical services, resulting in significant damage.
* **Compliance violations** - Failure to meet regulatory requirements, such as purging PII  after a certain period, can result in hefty fines and legal issues.
* **Financial loss** - The costs associated with mending security breaches and legal liabilities can be huge.&#x20;

### Multiple settings and admin users are a configuration nightmare

Typical organizations use over 100 SaaS apps, making it challenging to manage multiple configurations since each app has unique settings. It’s also difficult to standardize configuration settings when there are multiple admin users in a single organization.

Misconfigured SaaS settings are a leading cause of sensitive data exposure, exfiltration, and even malicious attacks. It can take up to weeks to detect and fix misconfigurations. Multiple SaaS admin users tend to configure different settings, and unfortunately, there’s no cross-team visibility into all security settings.

Organizations face an urgent need to harden their SaaS app settings without the overhead and time-consuming process of tracking app configurations. Manual tracking is not the answer, since it’s usually done in spreadsheets that aren't even scalable.

### Make your organization compliant&#x20;

Being compliant with industry standards is a basic prerequisite for organizations to do business. Misconfiguration detection ensures SaaS security follows the same rules as the organization, based on compliance regulations, such as, CIS, SOC 2, NIST and ISO 27001.&#x20;

It’s important to check both recommended and not-recommended practices, to help evaluate, monitor, and improve security across all SaaS tools. These security checks aim to focus on critical security holes that expose the entire organization to threats and can be fixed quickly if monitored correctly.&#x20;

### Preventing SPM misconfigurations

Organizations can mitigate the risks of SPM misconfigurations by:

* Employing third-party tools - such as DoControl - to regularly monitor for drifts in security settings
* Conducting regular security audits and vulnerability assessments
* Providing security training to staff responsible for system configuration

## DoControl’s misconfiguration solution

DoControl’s Misconfiguration solution detects security drifts and compliance shortcomings across your integrated SaaS apps, and allows your security team to easily remediate any gaps. &#x20;

DoControl is unique in that we leverage additional data - SaaS activity, data exposure and users - to provide additional context for your SaaS misconfigurations.

To protect your organization against unauthorized access and data breaches that could be caused by misconfigurations, DoControl ensures your SaaS configurations are secure, via:

* **Misconfiguration mapping and prioritization**  \
  Evaluate the strength of your SaaS security posture and risk levels. DoControl performs comprehensive security checks on your SaaS app and user settings, and maps misconfigurations by application, security domain and level of impact.<br>
* **Compliance checks**\
  To be compliant, organizations can have thousands of settings that require continuous monitoring.  Monitor compliance of your SaaS apps against relevant security standards, regulatory frameworks and company policy. DoControl aligns security checks with industry standards, best practices and regulations, such as CIS (Center for Internet Security) and SOC 2 benchmarks. \
  \
  DoControl continually compares each security check with industry benchmarks and compliance standards before giving a pass/fail score. <br>
* **Recommended remediation**\
  Implement recommendations to remediate inadequate security controls. DoControl offers guided remediation steps for each misconfiguration, coupled with the ability to establish automated remediation workflows triggered by misconfiguration events in real time. To save you time, automatically open a prep-populated Jira ticket.

### Benefits

With DoControl, you can manage your organization’s SaaS security posture and get full visibility into any misconfigurations via an interactive dashboard:

* **Dive into security settings** - Twice a day, DoControl scans each security setting for a variety of SaaS apps and users to check if they meet compliance standards. This automation helps to eliminate manual SaaS security checks across thousands of configurations, and reduces your audit time from weeks to minutes.
* **Prioritize your risk mitigation** - Filter misconfigurations by app, impact level, security check, status and category to efficiently manage the different areas of your SaaS security posture.
* **Fix any security issue** - DoControl provides best practices and recommendations to repair any security misconfiguration and make your SaaS apps fully compliant.
* **Map your compliance** - See how your SaaS security posture affects your overall compliance score when stacking up your configurations with major industry compliance standards, such as CIS.
* **Get enriched context** - Leverage DoControl’s inventory mapping and posture data, including events, alerts and workflows, to get more critical security checks on top of just standard configuration validation.&#x20;

### Misconfiguration use cases

DoControl runs compliance checks for a range of misconfiguration use cases in multiple security domains. You can focus on those domains that are the most critical for your organization, and prioritize where to invest your remediation efforts:

<table><thead><tr><th width="287.8046875">Security domain</th><th>What it means</th></tr></thead><tbody><tr><td>Access control</td><td>All security checks involving how users enter a specific app, including excessive or inappropriate permissions</td></tr><tr><td>Account governance</td><td>Ensures user accounts are created, managed, and secured according to policy</td></tr><tr><td>AI governance</td><td>Controls how AI systems are used, secured, and monitored to prevent misuse and data leakage</td></tr><tr><td>API governance</td><td>Controls and monitors how APIs are exposed, accessed, and managed to avoid risks such as unauthorized access or data leaks</td></tr><tr><td>App governance</td><td>Manages permissions, configurations, and risks associated with applications and integrations</td></tr><tr><td>Authentication</td><td>Ensures that only legitimate users or systems can gain access, so there are no unauthorized entry points.​</td></tr><tr><td>Authorization</td><td>Defines what authenticated users or systems are allowed to do, ensuring there are no excessive or insufficient privileges.​</td></tr><tr><td>Configuration management</td><td>Enforces and maintains secure baseline configurations for systems and applications to prevent vulnerabilities from drift or weak settings</td></tr><tr><td>Data access</td><td>Acceptable methods of retrieving data from other apps, or making sensitive data accessible to authorized users</td></tr><tr><td>Data classification</td><td>Methods ensuring that information is categorized and handled according to sensitivity level. These security checks enforce policies for secure storage, transmission, and access to prevent leakage or unauthorized data exposure.</td></tr><tr><td>Data governance</td><td>Policies for managing and classifying organizational data to prevent exposure, misuse, or regulatory violations</td></tr><tr><td>Data protection</td><td>Ensures technical controls such as encryption and masking are enforced to keep data secure, with misconfiguration potentially leading to data breaches.​</td></tr><tr><td>Device security</td><td>Correct configuration of physical and virtual devices to protect against unauthorized access, vulnerabilities, and exposure resulting from mismanaged hardware or endpoints.​</td></tr><tr><td>Domain security</td><td>Protects domain configuration, DNS settings, and domain ownership against hijacking or misuse</td></tr><tr><td>Email security</td><td>Methods that protect email systems from threats and data leakage, to minimize exposure from phishing or unauthorized access</td></tr><tr><td>Endpoint governance</td><td>Ensures devices accessing corporate resources meet security and compliance requirements</td></tr><tr><td>External sharing</td><td>Controls and monitors how data is shared outside the organization to prevent exposure</td></tr><tr><td>Incident response</td><td>Defines how security events are detected, managed, escalated, and resolved</td></tr><tr><td>Integration governance</td><td>Manages and secures how systems, services, or applications connect and share data</td></tr><tr><td>Monitoring</td><td>Provides continuous visibility into system activity, configurations, and potential security issues</td></tr><tr><td>Network boundary</td><td>Protects the perimeter between internal and external networks with proper segmentation and controls</td></tr><tr><td>Network security</td><td>Secures internal networks through policies, access restrictions, and threat prevention technologies</td></tr><tr><td>Non-human access</td><td>Methods to secure and configure automated accounts, service identities, and machines to prevent privilege escalation or unauthorized activities by scripts or bots.​</td></tr><tr><td>Platform governance</td><td>Oversees policy and controls for the overall SaaS environment to uniformly manage security, compliance, and access risks.</td></tr><tr><td>Privacy </td><td>Compliance score for security checks that protect personal or regulated data</td></tr><tr><td>Privileged access</td><td>Manages and restricts high-level access to critical systems to reduce insider and external risk</td></tr><tr><td>Resilience</td><td>Ensures systems are configured for availability and recovery, so the SaaS environment is not exposed to downtime or service disruptions</td></tr><tr><td>Secret management</td><td>Methods for secure storage, rotation, and access controls of sensitive credentials such as API keys and passwords. These security checks ensure that secrets are not exposed, hardcoded, or accessible to unauthorized entities.​</td></tr><tr><td>Secure SDLC</td><td>Integrates security practices throughout the software development lifecycle</td></tr><tr><td>Session security</td><td>Controls how user or system sessions are handled to prevent unauthorized access through session hijacking or timeouts</td></tr><tr><td>User lifecycle</td><td>Ensures users are onboarded, updated, and offboarded securely and consistently</td></tr><tr><td>Vendor management</td><td>Evaluates and monitors third-party vendors to ensure they meet security and compliance standards</td></tr><tr><td>Vulnerability management</td><td>Methods that keep your SaaS apps safe from cyberattacks and data breaches</td></tr></tbody></table>

## Compliance standards

DoControl checks your SaaS configurations against these industry standards: &#x20;

* [CIS](https://www.cisecurity.org/cis-benchmarks) (Center for Internet Security) - Consensus-driven best practices and configuration benchmarks for hardening IT systems against cyberattacks.
* [SOC 2 ](https://www.aicpa-cima.com/topic/audit-assurance/audit-and-assurance-greater-than-soc-2)- Auditing standard for service organizations that evaluates controls relating to security, availability, processing integrity, confidentiality, and privacy of customer data.
* [NIST (CSF) ](https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.29.pdf)(National Institute of Standards and Technology, Cybersecurity Framework) - Cybersecurity standards and guidelines for risk management and control
* [ISO 27001](https://www.iso.org/standard/27001) - The ISO 27001 standard establishes international requirements and guidelines for setting up and maintaining an information security management system (ISMS) across organizations

### Controls and recommendations

Each compliance standard includes a number of controls. In turn, each control includes a number of recommendations:

* **Control** - DoControl runs security checks across all integrated apps, based on the most common compliance standard controls.
* **Recommendation** - Each security control has a set of recommendations that is validated automatically using APIs. DoControl verifies if each recommendation is enforced or not by running a security check against your integrated SaaS apps.

<table><thead><tr><th width="281">Compliance parameter</th><th>Example</th></tr></thead><tbody><tr><td>Control</td><td>Set minimum passcode strength requirements </td></tr><tr><td>Recommendation</td><td><ul><li>Ensure minimum passcode length is set to 8 characters or greater</li><li>Ensure passcode has at least 1 letter set to enabled </li><li>Ensure passcode has at least 1 number set to enabled</li><li>Ensure passcode has at least 1 special character set to enabled</li><li>Ensure allow numeric passcode is set to disabled </li></ul></td></tr></tbody></table>

The hierarchy of a compliance standard benchmark, consisting of controls and recommendations, is as follows:

<figure><img src="https://3236294211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MesrnyDMZGYg1V-tOBo%2Fuploads%2Fe4y9H8ntuuJn8OVIyx9k%2Fbenchmark%20hierarchy.png?alt=media&amp;token=8e8ff06f-1db3-4d70-89f0-b3bae2e8c171" alt=""><figcaption></figcaption></figure>

### Benchmark levels

DoControl runs security checks for CIS recommendations based on 2 levels:&#x20;

* **Level 1** - Recommendations that are practical, provide a clear security benefit, and don’t inhibit the technology being used in your organization.&#x20;
* **Level 2** - Recommendations that are intended for environments or use cases where security is paramount, act as a defense, and might inhibit the use or performance of technology at your organization.


---

# 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.md?ask=<question>&goal=<user_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.
