Asana states that it holds a SOC 2 Type II report and ISO/IEC 27001 certification, along with SOC 2 Type I, SOC 3, ISO/IEC 27017:2015, ISO/IEC 27018:2019 and others. A data processing agreement is published, and so is its subprocessor list. It signs a HIPAA business associate agreement on some plans.
Certifications and reports
As Asana lists them. Scope varies by product, so check each report or certificate against the service you buy.
| Certification or report | Scope | Source |
|---|---|---|
| Audit reports 3 | ||
| SOC 2 Type II | Security, availability, confidentiality and privacy criteria; 2026 report combined with HIPAA | asana.com |
| SOC 2 Type I | Asana Gov platform (2026 report) | trustcenter.asana.com |
| SOC 3 | – | asana.com |
| ISO standards 4 | ||
| ISO/IEC 27001:2022 | – | asana.com |
| ISO/IEC 27017:2015 | – | asana.com |
| ISO/IEC 27018:2019 | – | asana.com |
| ISO/IEC 27701:2019 | – | asana.com |
| Government and regional 1 | ||
| TX-RAMP | – | trustcenter.asana.com |
| Industry and privacy 1 | ||
| CSA STAR Level 1 | Self-assessment | asana.com |
How to get the SOC 2 report
The SOC 2 Type II report is listed as a document in the Asana Trust Center, where access is requested through the portal's Get Access option.
Source: trustcenter.asana.com
Data and contracts
- DPA and transfers
The DPA is incorporated by reference into the subscription agreement and entering it is deemed to sign the EU Standard Contractual Clauses (Modules Two and Three), with the UK Addendum and Swiss adaptations. Asana states it is self-certified under the EU-US Data Privacy Framework, which takes first priority as a transfer mechanism.
- Subprocessors
Customers who subscribe to updates are notified by email ten business days before a new subprocessor is authorised, or as soon as reasonably practicable in an emergency. Customers may object within 30 days.
- Data residency
Asana offers data residency with data centres in Europe, Australia and Japan in addition to the United States. The pricing page lists data residency as part of the Enterprise+ plan.
Source: asana.com
- AI and your data
Asana's product terms state it does not use or permit third-party AI partners to use Customer Data to train generative AI models used to provide Asana AI, and partners must delete customer data after each query. Admins can turn AI request access on or off per user.
Source: asana.com
- HIPAA BAA
On some plans. A Business Associate Addendum takes effect when the customer enables the HIPAA feature on an eligible paid subscription tier; PHI may not be submitted to the free version, and some Asana AI tools, certain third-party integrations and personal access tokens are unavailable once HIPAA is enabled.
Source: asana.com
- Vulnerability disclosure
- Service status
Security incidents since 2020
Publicly confirmed incidents, as the vendor or its investigators described them.
A bug in Asana's opt-in Model Context Protocol (MCP) server could expose certain information from one organisation's Asana domain to other MCP users; Asana took the server offline from 5 to 17 June 2025, reset all MCP connections and contacted affected organisations directly.
Source: status.asana.com
What to ask Asana
What the public record leaves open, written to paste into your request.
- Does the SOC 2 report cover the product and plan you buy?
Asana offers several products. Compare the system description in section 3 of the report with your order form, and ask for a bridge letter if the period ended more than three months ago.
- Which complementary user entity controls fall on you?
Cloud services assume the customer configures access, retention and sharing. List the controls the report expects you to run and give each an owner.
- Which subprocessors touch your data?
The public list covers every product. Ask which entries apply to your plan, region and features, and subscribe to change notices.
- How are AI features governed in your tenant?
Confirm in writing whether your content is used to train models, which AI features are on by default, and which model providers process prompts.
- Where will your data be stored and processed?
Residency options often depend on plan and region. Record the region in the contract and ask where support and backups are handled.
- What changed after the incidents on record?
Ask for the remediation evidence and whether any of it touched the product or region you use.
- Is the BAA available on your plan?
The business associate agreement is limited to certain plans or products. Confirm before any protected health information reaches the service.
When the documents arrive, ProcureCortex reads them clause by clause and keeps the page behind every finding.
Sources
- Asana trust centertrustcenter.asana.com
- Asana: certifications and attestationsasana.com/trust
- Asana: data processing agreementasana.com/terms/data-processing
- Asana: AI and customer dataasana.com/terms/asana-product-specific-terms
- Asana: HIPAAasana.com/terms/hipaa-requirements-and-limitations
- Asana: subprocessor listasana.com/terms/subprocessors
- Incident, Jun 2025status.asana.com/incidents/5b9hhtgs3mxs
- Asana service statusstatus.asana.com
Compiled from Asana’s public pages on 17 Nov 2026. Not affiliated with or endorsed by Asana, Inc. Certifications, terms and lists change; check the source before relying on any line here.
Claim this profile for free to add your trust center, a link where buyers request documents and a short statement, shown as provided by Asana. The public record above stays as compiled from public sources.