Aptible Comply Documentation

Issues

Issues are the result of automations in Comply. When an automation runs it has 2 potential outcomes. One is "OK" where evidence is collected. The other outcome is "Issue" where evidence is collected and an issue is created.

Issues are aggregated into a single view and can be found in Automations > Issues.

Continuous and Discrete Issues

Issues come in two classifications; continuous and discrete. Continuous issues are issues generated where Comply is continuously monitoring an asset or service and the issue generated is part of a series of persistent checks. Discrete issues are generated when Comply is monitoring a service and the issue is generated from an event that is not tied to a series or continuous check.

For example, Github automations on PR merges are discrete as Comply checks for the merge on the initial request but doesn't continue to follow that individual request into perpetuity. AWS automations on storage assets checking for encryption will follow those assets and their setting as long as there's a connection, generating continuous issues.

Reminders

Comply will remind team members to address their issues on a weekly basis. If a team member has an issue that is not resolved they will receive an email once a week reminding them of the outstanding issue.

Resolving Issues

Resolving issues is slightly different for continuous and discrete issues.

For continuous issues, simply resolving the issue at the source and then re-syncing in Comply will automatically resolve the issue and remove it from the dashboard.

For discrete issues, you must resolve the issue at the source and then in Comply mark the issue as resolved which will then remove it from the dashboard. Marking many issues as resolved at once is simple.

Updated 3 months ago


Issues


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.