| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2024-10-07 |
supported controls, controls available, supported environments, rule, profile, compliance issue, predefined rules, user-defined rules |
security-compliance |
{{site.data.keyword.attribute-definition-list}}
{: #faqs}
Frequently asked questions for {{site.data.keyword.compliance_full}} might include questions about managing profiles, defining custom rules, attaching scopes, and evaluating resources for compliance. To find all FAQs for {{site.data.keyword.cloud_notm}}, see the FAQ library.
{: #faq-monitor-rule} {: faq} {: support}
{{site.data.keyword.compliance_short}} supports two types of rules - predefined and custom. Predefined rules are associated with specifications by default and are automatically monitored when you create an attachment to a profile. Custom rules can be monitored after they are associated with a specification by customizing a control library. Then, you select those controls when you create an attachment.
{: #faq-provisioned-rule} {: faq} {: support}
Yes, you can create rules for services or resources that are not already provisioned in your accounts. When the service or resource is created, it is automatically evaluated according to your rule definition.
{: #faq-evidence} {: faq} {: support}
The results that have "Additional details" are associated with the Toolchain service. The Toolchain pipeline sends the associated details and evidence along with the results to {{site.data.keyword.compliance_short}}.
{: #faq-control-support} {: faq} {: support}
{{site.data.keyword.compliance_short}} supports various controls that are designed to help organizations manage and maintain the security and compliance of their systems and data. To view a list of available profiles, see Available predefined profiles. To view all of the controls that are supported by the product, go to the {{site.data.keyword.compliance_short}} UI in the {{site.data.keyword.cloud_notm}} console.
{: #faq-exclusions} {: faq}
As a user, you can define exclusions at both the scope and subscope level. Exclusions at the scope level exclude the resource from an evaluation. The resource is not part of the scope and is not being evaluated, or charged by {{site.data.keyword.compliance_short}}. Exclusions at the subscope level are more like a filter. The excluded resource still exists in your scope and is being evaluated. But, the results are not visible at the subscope level.