**Monitored apps** - Number of SaaS apps that DoControl monitors for compliance drifts
* 
**App instances** - Number of discrete SaaS app platforms that DoControl monitors for misconfigurations. For example, Okta instance 1 and Okta instance 2.
{% hint style="success" %}
* To drill-down into details of your misconfigurations, click **Security checks**.
* To view your integrated SaaS apps or integrate more apps, click **More > Integrations:**
{% endhint %}
\
{% hint style="warning" %}
**Troubleshooting**: A red dot in the App instance icon 
indicates an integration issue with one of your app instances. You need to [re-integrate ](/docontrol-user-guide/risk-management/misconfigurations-premium/integrate-apps.md)the affected app instances.
{% endhint %}
## Total compliance score
View your overall compliance score for all integrated SaaS apps, based on these parameters:
| Compliance score parameter | Description |
|---|---|
| Total score |
|
| Coverage achieved | The number of security checks that are compliant with industry benchmarks out of the total number of security checks across all integrated SaaS apps |
| Critical issues | The number of high-risk misconfigurations out of the total number of failed security checks across all integrated SaaS apps. These issues pose a severe risk to sensitive data or system operations. |
| Percentage bracket | Overall compliance posture | What it means |
|---|---|---|
 76-100% | Strong | Your SaaS environment is highly secure with only minor improvements needed to strengthen your security posture |
 51-75% | Fair | Your SaaS environment is moderately secure, but requires attention to address notable compliance gaps |
 26-50% | Weak | Your SaaS environment has significant security gaps resulting from misconfigurations that require prioritized remediation |
 0-25% | At risk | Your SaaS environment is poorly configured and highly vulnerable, with critical misconfigurations requiring urgent remediation |
| Misconfiguration severity | Description |
|---|---|
| Critical | Number of misconfigurations that pose a severe risk to sensitive data or system operations, and require immediate remediation |
| High | Number of misconfigurations that present a significant security risk and could be exploited if left unresolved. These issues should be remediated promptly. |
| Medium | Number of misconfigurations that indicate moderate security exposure or operational risk. These issues are important to address,, but are not immediately urgent. |
| Low | Number of misconfigurations with minimal impact on security or operations. These issues are typically best addressed during routine maintenance. |
| Security check status | What it means |
|---|---|
| Failed | Number of security checks that didn't pass out of the total number of security checks. These security checks require remediation. |
| Passed | Number of security checks that are compliant |
| Info | Number of informational security checks that require review |
 N/A | Number of security checks that are not available for verification |
 Ignored | Number of security checks that you manually skipped |
| Security check impact level | What it means |
|---|---|
| Critical | Number of misconfigurations that pose a severe risk to sensitive data or system operations, and require immediate remediation |
| High | Number of misconfigurations that present a significant security risk and could be exploited if left unresolved. These issues should be remediated promptly. |
| Medium | Number of misconfigurations that indicate moderate security exposure or operational risk. These issues are important to address, but are not immediately urgent. |
| Low | Number of misconfigurations with minimal impact on security or operations. These issues are typically best addressed during routine maintenance. |
| Compliance posture bracket | What it means |
|---|---|
| Less than 40% | This SaaS environment is poorly configured and highly vulnerable, with critical misconfigurations requiring urgent remediation |
| 40-69% | This SaaS environment is moderately secure, but requires attention to address notable compliance gaps |
| 70-100% | This SaaS environment is highly secure with only minor improvements needed to strengthen your security posture |
| Security domain | What it means |
|---|---|
| Access control | All security checks involving how users enter a specific app, including excessive or inappropriate permissions |
| Account governance | Ensures user accounts are created, managed, and secured according to policy |
| AI governance | Controls how AI systems are used, secured, and monitored to prevent misuse and data leakage |
| API governance | Controls and monitors how APIs are exposed, accessed, and managed to avoid risks such as unauthorized access or data leaks |
| App governance | Manages permissions, configurations, and risks associated with applications and integrations |
| Authentication | Ensures that only legitimate users or systems can gain access, so there are no unauthorized entry points. |
| Authorization | Defines what authenticated users or systems are allowed to do, ensuring there are no excessive or insufficient privileges. |
| Configuration management | Enforces and maintains secure baseline configurations for systems and applications to prevent vulnerabilities from drift or weak settings |
| Data access | Acceptable methods of retrieving data from other apps, or making sensitive data accessible to authorized users |
| Data classification | 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. |
| Data governance | Policies for managing and classifying organizational data to prevent exposure, misuse, or regulatory violations |
| Data protection | Ensures technical controls such as encryption and masking are enforced to keep data secure, with misconfiguration potentially leading to data breaches. |
| Device security | Correct configuration of physical and virtual devices to protect against unauthorized access, vulnerabilities, and exposure resulting from mismanaged hardware or endpoints. |
| Domain security | Protects domain configuration, DNS settings, and domain ownership against hijacking or misuse |
| Email security | Methods that protect email systems from threats and data leakage, to minimize exposure from phishing or unauthorized access |
| Endpoint governance | Ensures devices accessing corporate resources meet security and compliance requirements |
| External sharing | Controls and monitors how data is shared outside the organization to prevent exposure |
| Incident response | Defines how security events are detected, managed, escalated, and resolved |
| Integration governance | Manages and secures how systems, services, or applications connect and share data |
| Monitoring | Provides continuous visibility into system activity, configurations, and potential security issues |
| Network boundary | Protects the perimeter between internal and external networks with proper segmentation and controls |
| Network security | Secures internal networks through policies, access restrictions, and threat prevention technologies |
| Non-human access | Methods to secure and configure automated accounts, service identities, and machines to prevent privilege escalation or unauthorized activities by scripts or bots. |
| Platform governance | Oversees policy and controls for the overall SaaS environment to uniformly manage security, compliance, and access risks. |
| Privacy | Compliance score for security checks that protect personal or regulated data |
| Privileged access | Manages and restricts high-level access to critical systems to reduce insider and external risk |
| Resilience | Ensures systems are configured for availability and recovery, so the SaaS environment is not exposed to downtime or service disruptions |
| Secret management | 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. |
| Secure SDLC | Integrates security practices throughout the software development lifecycle |
| Session security | Controls how user or system sessions are handled to prevent unauthorized access through session hijacking or timeouts |
| User lifecycle | Ensures users are onboarded, updated, and offboarded securely and consistently |
| Vendor management | Evaluates and monitors third-party vendors to ensure they meet security and compliance standards |
| Vulnerability management | Methods that keep your SaaS apps safe from cyberattacks and data breaches |
| Compliance parameter | What it means |
|---|---|
| Pass | Percentage of security checks that meet requirements for that specific compliance standard |
| Fail | Number of security checks that don't meet requirements for that specific compliance standard, out of the total number of security checks |
| App instance parameter | What it means |
|---|---|
| App name | Name of app instance that's being monitored for misconfigurations |
| Compliance score per domain | Compliance score for the top failed security domains, based on the number of failed security checks in this app instance |
| View details | Opens the filtered list of security checks for the integrated SaaS app |
| Total score bracket | Compliance posture | What it means |
|---|---|---|
| 76-100% | Strong | Your SaaS app environment is highly secure with only minor improvements needed to strengthen your security posture |
| 51-75% | Fair | Your SaaS app environment is moderately secure, but requires attention to address notable compliance gaps |
| 26-50% | Weak | Your SaaS app environment has significant security gaps resulting from misconfigurations that require prioritized remediation |
| 0-25% | At risk | Your SaaS app environment is poorly configured and highly vulnerable, with critical misconfigurations requiring urgent remediation |
| Impact level | What it means |
|---|---|
| Critical | Number of misconfigurations that pose a severe risk to sensitive data or app operations, and require immediate remediation |
| High | Number of misconfigurations that present a significant security risk and could be exploited if left unresolved. These issues should be remediated promptly. |
| Medium | Number of misconfigurations that indicate moderate security exposure or operational risk. These issues are important to address, but are not immediately urgent. |
| Low | Number of misconfigurations with minimal impact on security or operations. These issues are typically best addressed during routine maintenance. |