> 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/filter-security-checks.md). # Filter security checks In a SaaS environment with hundreds of security checks, filtering is essential for streamlined remediation and work processes. The ability to filter all your security checks by a range of parameters allows you to focus on critical or high-impact misconfigurations that require immediate resolution.

Filter	Description
App instance	Include or exclude one or more SaaS app instances with their relevant security checks. Each instance of an integrated app is monitored separately.
Security check	Search for a specific security check using any of these operators: Equals - An exact match. This operator is case-sensitive. Doesn't equal - Doesn't have the exact match Starts with - Begins with the entered string Ends with - Ends with the entered string Contains - Has the partial string Doesn't contain - Doesn't have the partial string Includes - An exact match. This operator is case-sensitive. Excludes - Doesn't have the exact match Each security check verifies if the compliance standard's recommendation is enforced or not.
Security domain	Include or exclude one or more categories corresponding to a specific domain in SaaS security, such as access control, device security, privacy, or vulnerability management.
Compliance	Include or exclude one or more industry standards that recommend implementing a specific security check in your SaaS environment: CIS SOC 2 NIST (CSF) ISO 27001
Status	Include or exclude one or more security check results: Fail - Your SaaS configuration does not comply with the security check. Remediation is required. Ignore - Security check was manually skipped Info - You need to manually review this security check N/A - The SaaS configuration for this check is not available for verification Pass - Your SaaS configuration complies with the security check
Impact	Include or exclude one or more severity levels for a potential misconfiguration: 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.
More filters
Affected	Search for the number of assets or resources impacted by a misconfiguration using any of these operators: Equals More than Less than Is global - This misconfiguration impacts your entire environment and isn't limited to specific users or groups
Last run	Search for the date when DoControl last ran a security check Use any of these operators: equals, after, before, is between
Detected on	Search for the date when the misconfiguration was detected by DoControl Use any of these operators: equals, after, before, is between

{% hint style="success" %} You can export the list of all your filtered misconfigurations to a CSV file by clicking the **Export to CSV**

icon. {% 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/filter-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.