Skip to main content
Checks that a ticketing system for change management is set up in Asana.

​
About

When you connect Asana to DSALTA, the platform syncs your change tickets using read-only API access. DSALTA activates this check when tickets do not meet your change-management requirements.

​
Why This Matters

Untracked or unassigned changes mean nobody is accountable and security regressions can slip through unnoticed. A documented change-management process with clear ownership is required by SOC 2 and ISO 27001.

​
How to Fix

Before you begin
  • Ensure you have administrator access to Asana.
Configure change management
  1. In Asana, create a dedicated project or board for tracking change requests.
  2. Ensure each change has an assignee, a description, and a target resolution date.
  3. Connect this system to DSALTA so change activity is captured as evidence.
Once change management is configured, DSALTA retrieves the change on the next sync and sets the check status to Passing.

​
Frequently Asked Questions

This check runs automatically every 24 hours while the Asana integration is connected. You can also trigger a manual sync from Integrations in the sidebar.
A failing check appears in your Data Library → Tests dashboard. Work through the steps above; once the underlying configuration is fixed, the status updates automatically on the next sync.
Yes. If it does not apply to your environment, mark it as Not Applicable with a justification. The exclusion is documented for auditors.
No. DSALTA uses read-only API access and never modifies, creates, or deletes resources. All remediation is performed by your team directly in Asana.