> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/security-and-compliance/control-groups.md). # Control Groups The building blocks of a secure and compliance Cloud infrastructure Cloud Infrastructure security can be approached by having the following control groups or building blocks and each of these has to be applied to each cloud resource being provisioned. These configurations, when applied to various cloud resources, often amount to 200+ controls per cloud provider. All of these controls come out of the box with the DuploCloud platform and are implicitly implemented while the users can focus on deploying the application. * Isolation and Firewall * Network Segmentation * IAM * Security Groups * WAF * VPN * Encryption * At Rest * At Transit * Access Management * Cloud console and resources * VM SSH * Container Shell * Kubernetes * Application Environment (DuploCloud Tenants) * Tags and Labels * Audit * Monitoring * Agent Management * SIEM * Host Vulnerabilities * Anti-Virus * HIDS * NIDS * Hardening Benchmarks (Like CIS) * Application Security Testing * DAST * Manual VAPT * Compliance Frameworks --- # 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.duplocloud.com/docs/automation-platform/security-and-compliance/control-groups.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.