Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Control test processing

Log in to subscribe to topics and get notified when content changes.

Control test processing

When performing a control test, processing dependencies are evaluated.

  • If a control test definition is active, the system generates the control test instances dynamically, according to definition. To generate a control test manually:
    1. Navigate to IT GRC > Administration > Control Test Definitions.
    2. Open a control test definition record.
    3. Click Execute Now.

      ServiceNow generates a control test instance, marks it Pending, and assigns it to the group or individual responsible for the test according to the control test definition.

  • If sample data was requested in the definition, any sample data that matches the conditions is found in the Supporting Data section. The Test Complete Data Values related list holds references to the records returned by the sample data query.
  • If a control test has a condition type of Basic, the value in the Sample size field limits the number of failures that are stored as support data. If the result is passed or compliant, all the matching data is stored.
  • If a control test has advanced conditions, the system evaluates them as follows:
    1. The condition collection in the In scope definition reference is processed.
      1. The primary condition is processed on the fields specified in Table and Fields on the control test definition and returns an array of elements.
      2. For each element in the array returned by the primary condition, supplemental conditions are processed, filtering the array of elements further.
      3. The In Scope field is updated with the number of elements in the array.
    2. The condition collection in the Configuration reference is processed on the array of elements returned from the In scope definition. The choices for Configuration to retrieve are:
      • None: These conditions are skipped. Supporting Data includes all the elements that were in scope.
      • Matching: The control test checks the array of elements, returning any elements that match the Configuration.
      • Non-matching: The control test checks the array of elements, returning any elements where at least one condition did not match the Configuration.
    3. The final array of elements is recorded as Supporting Data records.

Remediation Tasks

If the control test reveals problems in the process, create a task from the Remediation Task related list. You can relate remediation tasks to any task in the system with the related items tool from the Many to Many Task Relations plugin.