Asana’s Statement on Security


We use Asana every day to keep our team organized, connected, and focused on results. Ensuring our platform remains secure is vital to protecting our own data, and protecting your information is our highest priority.

Our security strategy covers all aspects of our business, including:

  • Asana corporate security policies
  • Physical and environmental security
  • Operational security processes
  • Scalability & reliability of our system architecture
  • Data model access control in Asana
  • Systems development and maintenance
  • Service development and maintenance
  • Regularly working with third party security experts

Asana Corporate Security Policies & Procedures

Every Asana employee signs a Data Access Policy that binds them to the terms of our data confidentiality policies, available at and Access rights are based on employee's job function and role.

SOC 2 (Type 1 and 2)

Asana has successfully completed its SOC 2 (Type I) and (Type II) audits for controls relevant to security, availability, and confidentiality. This means that an independent third party has both validated our processes and practices with respect to these three trust services criteria and confirmed our ability to maintain compliance with the controls we've implemented.

Security in our Software Development Lifecycle

Asana uses the git revision control system. Changes to Asana’s code base go through a suite of automated tests and are reviewed and go through a round of manual review. When code changes pass the automated testing system, the changes are first pushed to a staging server wherein Asana employees are able to test changes before an eventual push to production servers and our customer base. We also add a specific security review for particularly sensitive changes and features. Asana engineers also have the ability to "cherry pick" critical updates and push them immediately to production servers.

In addition to a list where all access control changes are published, we have a suite of automated unit tests that check that access control rules are written correctly and enforced as expected. We also work with third-party security professionals to:

  • Test our code for common exploits
  • Use network scanning tools against our production servers

Security at the Asana office

Our office is secured via keycard access which is logged, and visitors are recorded at our front desk.

We monitor the availability of our office network and the devices on it. We collect logs produced by networking devices such as firewalls, DNS servers, DHCP servers, and routers in a central place. The network logs are retained for the security appliance (firewall), wireless access points, and switches.

Asana Architecture & Scalability

Scalability/Reliability of Architecture

Asana uses Amazon Web Services (RDS & S3) to manage user data. The database is replicated synchronously so that we can quickly recover from a database failure. As an extra precaution, we take regular snapshots of the database and securely move them to a separate data center so that we can restore them elsewhere as needed, even in the event of a regional Amazon failure.

We currently host data in secure SSAE 16 audited data centers via Amazon RDS in the United States.

Encrypted Transactions

Web connections to the Asana service are via TLS 1.1 and above. We support forward secrecy and AES-GCM, and prohibit insecure connections using TLS 1.0 and below or RC4.

Asana Information Security

Employee Workstations, Laptops, & Mobile Devices

All laptops and workstations are secured via full disk encryption and centrally managed. We diligently apply updates to employee machines and monitor employee workstations for malware. We also have the ability to apply critical patches and remote wipe a machine. We use industry-standard OTP technology to further secure access to our corporate infrastructure.

Security Consulting and Application Review

We work with external security advisor, and maintain an external bounty program where we pay security researchers who discover vulnerabilities.

Data Center Security


Amazon employs a robust physical security program with multiple certifications, including an SSAE 16 certification. For more information on Amazon's physical security processes, please visit

Product Features

Administrator Management Features

  • Authentication - Asana administrators can force employees to authenticate via Google Accounts or set up SAML. If passwords are stored directly with Asana, we secure them using salted bcrypt.

  • User Management - Administrators can see Last Activity, Guest/Member status, and deprovision users from a central administration interface.

User Features

  • Privacy, Visibility, & Sharing Settings - Customers determine who can access different categories of data like Teams, projects, and tasks. Access to an Asana Organization is based on your company email domain. You can limit a user’s access by inviting them as a Guest.


Privacy Policy

Asana's privacy policy, which describes how we handle data input into Asana, can be found at


We are committed to making Asana consistently available to you and your teams. Our systems have built-in redundancy to withstand failures and are constantly monitored to keep your work uninterrupted. You can always monitor our availability at our trust page.

Want to report a security concern?

We offer a Security Exploit Bounty Program. Email us at