How is user authentication and access control managed in your system?
Coda utilizes a variety of security measures to manage user authentication and access control in its system. These include multi-factor authentication, strong password policies, role-based access restrictions, and compartmentalized access to data based on job function. Access to Coda's internal administration tools is logged and regularly reviewed, and access to sensitive user data is restricted to on-call engineering teams with approval required. Coda is GDPR and CCPA compliant and has entered into Data Privacy Agreements with all its data subprocessors. For more information on Coda's security measures, refer to https://help.coda.io/en/articles/5557780-overview-of-security-features.
What measures do you have in place to protect against unauthorized access and data breaches?
Our security measures include SOC 2 compliance, data encryption in transit and at rest using industry standard protocols, organizational security practices, GDPR and CCPA compliance, and regular security training and penetration testing. We also utilize Amazon Web Services for our cloud infrastructure and employ secure development lifecycle practices, disaster recovery planning, and user data privacy policies and procedures. Our security incident management process is constantly monitored and audited for suspicious activities, and we have a 24/7 pager rotation on our infosec team to respond to any security incidents that may arise.
How is data encrypted in transit and at rest?
Our customers' data is encrypted when in transit and at rest, using the highest industry standard procedures and protocols, including TLS 1.2, FIPS 140-2 validated HSMs (AWS KMS), and AES-256 symmetric encryption algorithms where appropriate.
What is your incident response plan in case of a security breach?
Coda has a comprehensive incident response plan in place in case of a security breach. This includes logging audit events and security information in every layer of the infrastructure and monitoring those logs for suspicious activity. Additionally, Coda staffs a 24/7 pager rotation on their infosec team to respond to and handle any security incident that may arise.
Can you provide documentation of your security audits and compliance certifications?
Coda undergoes regular Service Organization Controls audits (SOC 2 Type II) performed by an independent third-party auditing firm. For customers on an Enterprise subscription, contact your account manager or [sales@coda.io](mailto:sales@coda.io) to request a copy of our most recent report. Additionally, we are GDPR and CCPA compliant and have entered into DPAs with all our subprocessors; we have a DPA available for customers in the EU upon request. For more information on our security features, please refer to . How are third-party integrations and APIs secured?
Coda ensures the security of third-party integrations and APIs by encrypting data in transit and at rest using industry standard procedures and protocols such as TLS 1.2, FIPS 140-2 validated HSMs (AWS KMS), and AES-256 symmetric encryption algorithms where appropriate. Coda also uses Amazon Key Management Service (KMS) for creating, maintaining, and rotating all symmetric encryption keys. Access to Coda infrastructure is restricted based on roles and responsibilities, and all operations activities are audited and analyzed for suspicious activities. Additionally, Coda undergoes regular Service Organization Controls audits (SOC 2 Type II) performed by an independent third-party auditing firm.
Do you have a disaster recovery plan in place?
Yes, Coda has a disaster recovery plan that addresses multiple site availability and replication of critical customer data. All customer data is backed up regularly across geographic locations, and regular disaster recovery testing is performed.
How is data backup and recovery managed?
Coda utilizes the highest industry standard procedures and protocols to ensure data backup and recovery. Customers' data is encrypted in transit and at rest, and Coda utilizes the Amazon Key Management Service (KMS) for creating, maintaining, and rotating all symmetric encryption keys. End user document data is stored by services managed by Amazon, such as Relational Data Service (RDS) for structured data and Simple Storage Service (S3) for file data. RDS instances are configured to store data in encrypted form using the industry standard AES-256 symmetric encryption algorithm for the database, backups, snapshots, and logs. Content stored in S3 is also encrypted at rest via server-side encryption integration with AWS KMS. In addition, Coda performs regular disaster recovery testing and has a disaster recovery plan that addresses multiple site availability and replication of critical customer data.
Can you provide a list of your security controls and protocols?
Our security controls and protocols include regular SOC 2 compliance audits, encryption of data in transit and at rest using industry standard procedures and protocols, strict organizational security measures including annual security training and regular 3rd party penetration tests, GDPR and CCPA compliance, cloud infrastructure hosted on Amazon Web Services with managed firewall rules and network ACLs, key management using Amazon KMS with no cleartext private key material stored on disk or in-memory, TLS 1.2 for protection of user data in transit, encryption of end user document data stored by services managed by Amazon, single-sign-on system using multi-factor authentication, strong password policies, and access restriction based on roles and responsibilities, security incident management process with 24/7 pager rotation on our infosec team, secure development lifecycle program integrated into every phase of our software development process, business continuity and disaster recovery plan that addresses multiple site availability and replication of critical customer data, and user data privacy policies and procedures with access to sensitive user data restricted to on-call engineering teams and approval required for access. For more details on our security features, please refer to this .