Skip to content

Control testing

Control testing runs each control’s test against the platform’s records every day and opens an Issue for each failure.

Trigger

Runs every day. Part of Compliance, run by the Legal Team.

Steps

  1. Query the records for each Control’s test.
  2. Record each result as Evidence against the published root.
  3. Open an Issue for every Control without a current passing result.

Outputs

Example

The access-review control has no Evidence for last month. Evidence collection opens an Issue for the Engineering Team that morning.