{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":43667,"path":"security-management/configuration-compliance/cc-assignment-rules.md","title":"Configuration Compliance assignment rules overview","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configuration Compliance assignment rules overview\n\nDefine the criteria by which test results are automatically assigned to an assignment group for remediation.\n\n**Note:** Starting with v14.9 of Configuration Compliance, the following terms have been renamed:\n\n|Terminology prior to v14.9|Terminology v14.9 onwards|\n|--------------------------|-------------------------|\n|Test Result Group|Remediation Task|\n|Group Rules|Remediation Task Rules|\n|Policy|Test group|\n\nA default assignment rule, **Assign to CI support group**, is included in the base system assigning test results to the **CI Support Group**. Inactive by default.\n\nThe Assignment groups set by the Assignment Rules are used by **Remediation Task Rules** to assign owners to remediation tasks \\(RTs\\).\n\n## Assigning test results automatically\n\nThere are three different ways to assign test results using **Assign using**:\n\n-   Assignment group: This option allows you to select any of the existing ServiceNow AI Platform® user groups.\n-   Assignment Group Field: This option allows you to choose any assignment group field available using the cmdb\\_ci table. By default you see the following three group fields:\n    -   None: Indicates no default value for this mandatory field\n    -   Configuration Item: Approval Group\n    -   Configuration Item: Assignment Group\n    -   Configuration Item: Support Group\n-   Script: This option allows you to define the conditions using a script. This option requires coding or advanced ServiceNow® expertise.\n\nSee [Create or edit Configuration Compliance assignment rules](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/configuration-compliance/create-cc-assign-rules.md) for more information on creating assignment rules.\n\nWith the sn\\_vulc.remediation\\_owner role, you can view and update test results and remediation tasks that are assigned to them or to their assignment groups. To view the modules, navigate to **All** > **Configuration Compliance** > **Test Results** > **My Open Test Results**, or **Configuration Compliance** > **Remediation Tasks** > **My Open Tasks**.\n\nThe sn\\_vulc.remediation\\_owner role can be assigned directly to a user, or, it is automatically assigned when you assign a user the itil role.\n\n## Assignment rule evaluation process\n\nWhen a new test result is imported, or reopened after being closed, the assignment rules are evaluated against it. The assignment rules are evaluated after CI matching, and Risk Score calculations. A test result is only automatically evaluated upon initial import and when a rule is changed, unless it is reopened after being closed. You can manually reapply rules after changes.\n\nThe following process is used for each new or reopened test result:\n\n-   For each test result assignment rule, the test result is compared to the assignment filter, lowest order rule first.\n-   Where the condition matches, the test result is assigned an assignment group. The lookup stops.\n-   Where the conditions do not find a match among all the rules, the test result remains unassigned.\n\n## Reapplying assignment rules\n\nWhen you change an assignment rule, use the **Apply Changes** button on the Assignment Rules list page to rerun all the changed rules on all active Open test results, except those that were manually assigned.\n\n**Note:** The assignment rules do not reevaluate manually created assignments.\n\nThe scheduled job \\[**Reapply all assignment rules**\\] is inactive, by default. When activated, it evaluates all the open test results against all active rules except those manually assigned. It can run Daily, Weekly, Monthly, Periodically, Once or On Demand.\n\n**Important:** As an admin and analyst, you can obtain the latest assignments for selected test results in the Vulnerability Manager Workspace. This method is more efficient than reapplying the Assignment Rules for all test results in the classic UI, which is a time-consuming process. For more information, see [Re-evaluate the remediation properties of the records in the Vulnerability Manager Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/security-management/vulnerability-manager-workspace/vmws-reevaluate-remediation-parameters.md).\n\n## Assignment rules and remediation task assignment\n\nUsually, you would assign your remediation task \\(RT\\) to the same assignment group as the test results in it. That is what the remediation task rules do, by default.\n\nFor example, if your RT groups by configuration item class, the remediation task created can be broken apart by the different assignment groups. An Oracle Database TRG can be assigned to Group 1, and an Oracle Database TRG assigned to Group 2.\n\nWhen the assignment group is changed at the remediation task level, all the test results in that remediation task which have same assignment group are updated to the new assignment group. The test results are marked as manually assigned and are not eligible for further rule evaluation.\n\n"}}