Resolving Manual Controls in Standards to Improve Compliance Score

Resolving Manual Controls in Standards to Improve Compliance Score

After executing a Standard in CoreStack for a cloud account, some controls may require manual resolution to be fully compliant. Follow the steps below to resolve these manual controls and improve your compliance score.

Steps to Resolve Manual Controls:
1. Navigate to Standards Page
Go to Governance > Guardrails > Standards in the CoreStack portal.

2. Locate the Relevant Standard
Find the Standard that was executed for the target account.
Click on the Status button associated with it.







3. Open Manual Actions
Select the specific control that requires manual input.
Navigate to the Manual Actions tab.

4. Choose the Correct Account
From the list of accounts shown, select the one where the Standard was executed.

5. Provide Resolution Details
Enter relevant remarks describing the resolution.
Select the appropriate date when the control was completed.

6. Mark Control as Resolved
Click the Action button and choose Resolve to mark the manual control as completed.

7. Verify Compliance Score
Once all required manual controls are resolved, the system will automatically update the compliance score for the associated Standard.

Why It Matters:
Manually resolving controls ensures your organization's compliance posture is accurately reflected and up to date. Completing these steps promptly helps maintain a strong governance framework across your cloud environments.


    • Related Articles

    • AWS External ID change

      AWS External ID Change An External ID in AWS is a unique identifier used in cross-account access scenarios to ensure that a request from one account to another is intended. Here's an elaboration on the process and considerations for managing AWS ...

    • AWS EC2 Cost Report not showing data.

      Scenario: When accessing the AWS EC2 Cost report, users may encounter situations where the report appears empty, despite the presence of EC2 instances in the Cloud. In some cases, users may encounter issues with AWS EC2 cost reports, specifically ...

    • Required Permissions for GCP SQL and BigQuery Resource Tagging Governance

      Required Permissions for GCP SQL and BigQuery Resource Tagging Governance SQL Resources: To enable tagging for SQL resources in Google Cloud Platform (GCP), such as Cloud SQL instances, the following permissions and configurations are required: Cloud ...

    • Implementing Markup and Discounts for the Current Month

      Scenario: The customer intends to apply a markup for a Cloud Account. However, when creating the markup, CoreStack defaults to the upcoming month for the Rule start month, even if it's the first day of the current month. This situation prompts the ...

    • FAQ on Custom Role Creation

      How are Permissions Determined for Custom Roles? Permissions for custom roles are determined based on the role type you select. These permissions are highly flexible and can be tailored to suit your specific use cases. Here's a breakdown: For ...