> 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/view-security-checks.md). # View security checks To manage your misconfigurations, you can detect security drifts across your integrated SaaS apps: * [Global view ](#global-misconfiguration-view)- See all results for all security checks * [Detailed view](#detailed-misconfiguration-view) - Click any security check to view its details, including affected entities, compliance requirements, and activity log {% hint style="info" %} After you integrate your apps, it can take up to an hour to see all your compliance data. {% endhint %}

To manage your misconfigurations, view all your security checks in a single view

## Global misconfiguration view Misconfiguration data for security checks is displayed according to these parameters.
Security check parameterWhat it means
App instance
  • The specific environment of an integrated SaaS app where the security check was run.
  • Each instance of an integrated app is monitored separately.
Security check
  • DoControl's operational check to verify if the compliance standard's recommendation is enforced or not.
  • Interactive tip: Click the security check to open the Remediation recommendations.
Status

Result of comparing your SaaS configuration with the security check recommendation:

  • Pass - Your SaaS configuration complies with the security check
  • Fail - Your SaaS configuration does not comply with the security check. Remediation is required.
  • Info - You need to manually review this security check
  • N/A - The SaaS configuration for this check is not available for verification
  • Ignore - Security check was manually skipped
Security domainEach security check that's run by DoControl corresponds to a specific domain in SaaS security, such as access control, device security, privacy, or vulnerability management.
Impact

Severity level of a potential misconfiguration and its impact on your organization:

  • Critical - Poses a severe risk to sensitive data or app operations, and requires immediate remediation.
  • High - Presents a significant security risk and could be exploited if left unresolved. This issue should be remediated promptly.
  • Medium - Indicates moderate security exposure or operational risk. This issue is important to address, but not immediately urgent.
  • Low - Has minimal impact on security or operations. This issue is typically best addressed during routine maintenance.
Affected

Number of assets or resources impacted by a misconfiguration. Click the number to view all affected entities.

  • Global - This misconfiguration impacts your entire environment and isn't limited to specific users or groups
  • N/A - This data is not available
Compliance

The industry standard that recommends implementing this security check in your SaaS environment:

  • CIS (Center for Internet Security) - Consensus-driven best practices and configuration benchmarks for hardening IT systems against cyberattacks.
  • SOC 2 - Auditing standard for service organizations that evaluates controls relating to security, availability, processing integrity, confidentiality, and privacy of customer data.
  • NIST (CSF) (National Institute of Standards and Technology) - Cybersecurity standards and guidelines for risk management and control
  • ISO 27001 - The ISO 27001 standard establishes international requirements and guidelines for setting up and maintaining an information security management system (ISMS) across organizations
Detected on
  • Date when the security check last failed
  • Detection date is not displayed for security checks with the Pass, Info or Ignore status
RemediationClick Fix to view recommendations for manually fixing any security issues
## Detailed misconfiguration view DoControl gives you a detailed overview of each security check, together with its affected entities, compliance requirements, and activity log. 1. Click any security check to open its details.\
2. Click any tab to display relevant data for that security check: * **Details** - Description of the compliance requirement, major findings, and how to locate the relevant SaaS setting in your app interface. * **Remediation** - Guided steps describing how to remediate the issue. * **Affected** - Details about users and resources impacted by a potential misconfiguration. For each affected entity, you can see when it was last detected by DoControl. * **Compliance** - The relevant compliance standards and their specifications * **Activity** - Audit log of all misconfiguration activity performed by DoControl team members --- # 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/view-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.