Caseware Legal

The Caseware Legal page provides centralized access to Caseware’s legal policies, agreements, and compliance resources. Explore important information related to privacy, security, AI, accessibility, and product usage in one place.

Four diverse colleagues collaborating around computers in an office with large windows and digital wave graphics.

Caseware Data Processing Agreement

Version: 5.0

Last Updated: November 2026

RECITALS

(A) Customer is the controller of the Personal Data processed under this DPA and is responsible for ensuring that the processing is carried out in accordance with applicable Data Protection Laws.

(B) Caseware is the processor of the Personal Data under this DPA and shall process Personal Data only in accordance with Customer’s documented instructions and the terms of this DPA.

(C) The Parties wish to set out in this DPA the terms and conditions under which Caseware will process Personal Data on behalf of Customer.

1.          Introduction & Scope

This Data Processing Agreement (“DPA”) is incorporated by reference into the Master Product and Services Agreement (“MPSA”) entered into by Caseware International Inc.

or the Affiliate of Caseware International Inc. identified in the applicable Order Form (collectively “Caseware” or the “Processor”) and the customer identified therein (the “Customer” or “Controller”).

Caseware may update this DPA from time to time. As the Processor may have access to Personal Data in providing Services (defined below), the Customer (as the Controller) and Caseware (as the Processor) require a contractual agreement concerning the collection, processing and use of Personal Data accessed by the Processor to help ensure the Personal Data receives protection substantially equivalent to that afforded by the Controller. This DPA governs the duration of the processing, the nature and purpose of the processing, the type of Personal Data being processed, the categories of Data Subjects and the rights and obligations of the Controller and of the Processor.

Customer and Caseware are separately referred to as “Party” and collectively as “Parties”.

2.         Definitions

Capitalized terms not defined in this DPA shall have the meaning given to them in the MPSA.

“CCPA” means the California Consumer Privacy Act of 2018, as amended by the California Privacy Rights Act of 2020 (Cal. Civ. Code §§ 1798.100 et seq.), together with its implementing regulations.

“Customer Information” means business contact and account information relating to Customer’s personnel, including names, work email addresses, work telephone numbers, job titles and account details, that Caseware processes for account administration, contracting, billing, relationship management or direct communications with Customer’s personnel. To the extent Caseware determines the purposes and means of such processing, Caseware processes Customer Information as an independent controller in accordance with Caseware’s Privacy Statement, as updated from time to time (https://www.caseware.com/legal/privacy-statement).

“Data Protection Laws” shall mean all data protection and privacy laws applicable to the processing of Personal Data according to the territorial origin of the Personal Data.

“Data Subject” shall mean an identified or identifiable natural person related to the Personal Data. Data Subject shall be equivalent to “Consumer” (as defined pursuant to the CCPA).

“GDPR” shall mean Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation). Terms used but not otherwise defined in this DPA that are defined in the GDPR shall have the meaning given to them in the GDPR.

“Personal Data” or “personal data” means any information relating to an identified or identifiable natural person. For the purposes of this DPA, Personal Data means Personal Data processed by Caseware on behalf of Customer in connection with the Caseware Offerings. This DPA does not apply to Customer Information.

“Restricted Transfer” shall mean (i) a transfer of Personal Data from Customer to Caseware; or (ii) an onward transfer of Personal Data from Caseware to a Sub-Processor, or (iii) an onward transfer between two establishments of Caseware or a Sub-Processor; in each case, where such transfer would be prohibited by Data Protection Laws (or by the terms of data transfer agreements put in place to address the data transfer restrictions of Data Protection Laws), authorisation mechanisms will be applied as required by applicable Data Protection Laws.

“Services” means, for purposes of this DPA, the Caseware Offerings as defined in the MPSA.

“Standard Contractual Clauses” shall mean the standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council approved by decision of the European Commission on June 4, 2021.

“Sub-Processor” shall mean any person or entity appointed by or on behalf of Caseware to process Personal Data on behalf of Caseware in connection with the Services and shall include any Sub-Processor rightfully appointed by a Sub-Processor (a Sub-Sub-Processor) to process Personal Data on behalf of Caseware in connection with the Services but shall not include any individual employee of Caseware or a Sub-Processor.

3.         Type of Data

The following types/categories of data that may be collected, processed and/or used by Caseware include:

·       Personal Data (e.g., last name, first name, address and date of birth);

·       Communication data (e.g., telephone number, fax, email);

·       Contract data (e.g., billing and payment details);

·       IT usage data (e.g., user ID, passwords and roles);

·       Bank data (e.g., bank account details and credit card number); and/or

·       Any other categories of Personal Data that the Customer, in its capacity as controller, chooses to process using the Caseware Offerings.

4.         Data Subjects

Data Subjects which may be affected by using their Personal Data include:

·       The Customer’s clients/service recipients;

·       The Customer’s employees or contractors;

·       The Customer’s suppliers/service providers and/or;

·       Any other categories of Data Subjects whose Personal Data the Customer, in its capacity as controller, processes using the Caseware Offerings.

5.         Place of Data Processing

Caseware uses third-party hosting and infrastructure providers, including Amazon Web Services (AWS), to provide the Caseware Offerings. The primary hosting location applicable and / or available to a Customer is determined by the relevant Caseware Offering, the Customer's location and the applicable Order Form or product documentation. Caseware currently operates primary cloud hosting environments in Australia, Canada, Ireland and the United States.

Certain support, security, document-processing and AI-enabled functionality may involve the processing of Personal Data outside the Customer's primary hosting region. Where such processing constitutes an international or Restricted Transfer, Caseware will use reasonable efforts to make sure that the transfer is made in accordance with applicable Data Protection Laws and is subject to an appropriate transfer mechanism and supplementary safeguards where required. These measures may include an applicable adequacy decision, the Standard Contractual Clauses, the UK Addendum, a transfer impact assessment and appropriate contractual, technical and organizational safeguards.

Where a Customer’s data hosted in Canada uses AI-enabled features, including Caseware Verity, model inference requests (the prompt and the generated response) may be processed in AWS regions in Canada or the United States through Amazon Bedrock cross-region inference. This does not change the Customer's primary hosting region, where Customer Data is stored. Current processing locations for each Sub-Processor are set out in Attachment 2.  

6.         Instructions

Caseware shall process Personal Data for the purposes of: (i) processing as required by Customers in their use of the Services; (ii) processing in accordance with the MPSA, this DPA and any other agreements between the Parties; (iii) processing to comply with other reasonable instructions provided by Customer where such instructions are consistent with the terms of the MPSA, applicable laws and DPA. Caseware will inform Customer if, in Caseware’s opinion, the Customer’s instructions or requests are contrary to Data Protection Laws, with reasons therefore by email.

7.         Confidentiality Commitment by Caseware

Caseware shall use reasonable efforts to make sure (a) the reliability of all individuals who could potentially access the Personal Data through appropriate screening measures, including background checks where permitted by applicable law and proportionate to the individual’s role; (b) that all such individuals are subject to confidentiality undertakings at least as restrictive as those set forth in the MPSA and will treat the Personal Data as Confidential Information; and (c) that all such individuals have undergone training in the care, protection, and handling of Personal Data.

Where Customer is a professional subject to statutory professional secrecy obligations under §203 StGB (Berufsgeheimnisträger), including Wirtschaftsprüfer, Steuerberater and Rechtsanwälte, the parties shall supplement this DPA with the applicable §203 StGB addendum. Where required, all Caseware personnel and Sub-Processors with access to protected data shall be bound by substantially equivalent confidentiality obligations.

Caseware shall not use Customer Data, Input or Outputs to train or fine-tune AI Models without Customer’s prior written authorization. The Parties agree that Customer discloses Personal Data to Caseware only for these limited and specified Business Purposes.

8.         Technical & Organizational Measures

Caseware shall implement the necessary technical and organizational measures (“TOMs”) to ensure a level of security appropriate to the risk. These may include, as appropriate:

-              the pseudonymization and encryption of Personal Data;

-              availability and resilience of processing systems and services;

-              the ability to restore the availability of and access to Personal Data in a timely manner in the event of a physical or technical incident; and

-              a process for regularly testing, assessing and evaluating the effectiveness of technical and organizational measures for ensuring the security of the processing and maintaining these measures for the duration of the contract.

Caseware will implement appropriate technical and organizational measures to protect Customer’s Personal Data against unauthorized or unlawful processing and against accidental loss, destruction, damage, alteration or disclosure. When implementing and updating such technical and organizational measures ensuring a level of security appropriate to the risk, Caseware will have regard to the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons. Without limiting the generality of the foregoing, Caseware has carried out the technical and organizational measures (“TOMs”) specified in Attachment 1 to this DPA.

Caseware engages approved Sub-Processors to provide parts of the Services. The TOMs therefore depend partially on these Sub-Processors, as also described in Attachment 1, provided that Caseware remains responsible for its compliance with the TOMs regardless of its reliance on Sub-Processors. Caseware may decide on commercially reasonable improvements of the TOMs and provide the Customer on request with an updated Attachment 1.

9.         Global Data Protection Officer

Caseware has appointed a Global Data Protection Officer (DPO) pursuant to Article 37 GDPR. The DPO can be contacted at:

·       Anouschka van de Graaf, Global Data Protection Officer;

·       Caseware International Inc.;

·       privacy@caseware.com.

Current DPO contact details are also accessible on Caseware’s website at www.caseware.com/legal.

10.        Sub-Processors

Customer acknowledges and agrees that Caseware may engage Sub-Processors in the provision of Services, subject to the terms and conditions of this DPA, and that (i) a Caseware Affiliate may be retained as a Sub-Processor; and (ii) Caseware or a Caseware Affiliate may engage third-party Sub-Processors.

This DPA applies under Module 2 (Controller to Processor) where Customer acts as controller of the Personal Data. Where Customer acts as processor for its own clients (for example, accounting firms, trust and administration service providers), and engages Caseware as sub-processor, Customer warrants that it has obtained the necessary authorizations and/or consents from its own clients. The parties acknowledge that Module 3 (Processor to Processor) Standard Contractual Clauses may be required in such cases and will be made available upon written request.

Where Caseware engages a Sub-Processor in the provision of Services, a data processing agreement will be entered into with the Sub-Processor. A list of Caseware’s current Sub-Processors is available in Attachment 2.

Caseware will notify Customer of any intended addition or replacement of a Sub-Processor by updating the Sub-Processor List at trust.caseware.com/subprocessors. Customers may subscribe to receive notifications of updates via the Trust Center. Customer may object in writing within a reasonable period after notification where Customer reasonably believes that the intended appointment would violate applicable Data Protection Laws or present a material data protection risk. In the event of a reasonable objection, the Parties will endeavour to resolve the matter without undue delay. Caseware will use reasonable efforts to make available to Customer a change in Services to avoid processing of Customer Information or Personal Data by the objected-to Sub-Processor without unreasonably burdening Customer. If Customer objects to a new Sub-Processor that is necessary for the provision of the Services, Customer may terminate the affected subscription without penalty by providing written notice before the end of the notice period.

If use of a Sub-Processor involves a Restricted Transfer, Caseware shall ensure that the authorisation required under applicable law is incorporated into an agreement between Caseware and the Sub-Processor; and between the Sub-Processor and any Sub-Sub-Processor.

11.         Data Subject Requests

Caseware shall reasonably support the Customer in the case of  Data Subject access, rectification or erasure requests, insofar as Customer cannot fulfill such a request on its own, to the extent legally permitted and technically possible. Customers shall pay Caseware’s costs for such support, to the extent legally permitted.  If a Data Subject request is received by Caseware that relates to Personal Data transferred by the Customer, Caseware will refer the request to the Customer. Unless required by law, Caseware will not respond to such a request but shall instead support Customer as provided in this Section.

12.        Data Breach Notification

Caseware shall inform Customer promptly and in any event within 72 hours after becoming aware of a breach of the Personal Data (meaning a breach of security leading to destruction, loss, alteration, unauthorised disclosure of, or access to, Personal Data transmitted, stored or otherwise processed), including a breach at a Sub-Processor, and shall provide the necessary information to allow Customer to inform authorities and Data Subjects. Where not all information is available at the time of notification, Caseware may provide information in phases as it becomes available. Caseware shall take reasonable efforts to remediate the cause of such data breach and mitigate (potential) damage resulting from the breach.

The notification to Customer will include at least a) the nature of the breach, b) the impacted data categories, c) the identified and potential consequences of the breach and d) the measures Caseware takes to mitigate the consequences of the breach. At the request of Customer, Caseware shall assist Customer in notifying the breach to a Supervisory Authority and/or the Data Subjects concerned.

13.        Data Protection Impact Assessment (DPIA)

Upon request by Customer, Caseware shall provide reasonable assistance to Customer in conducting a DPIA, solely in relation to Caseware’s processing of Customer’s Personal Data and taking into account the nature of the processing and information available to Caseware and Sub-Processors. Customers shall pay Caseware’s costs for such support, to the extent legally permitted.

14.        Deletion or Returning Personal Data

Upon termination or expiry of the MPSA, Caseware will make Customer’s Personal Data available for export or return in accordance with the offboarding provisions of Section 11.6 of the MPSA. Following the applicable offboarding period, Caseware will delete or destroy the remaining Personal Data, except to the extent retained in accordance with Caseware’s standard backup, archival or legal retention practices or as otherwise required by applicable law. Personal Data retained in backups or archives will remain subject to the protections of this DPA and will not be processed for any other purpose, except as required by applicable law, until deleted in accordance with Caseware’s applicable retention practices.

15.        Information & Audit Rights

Customers may obtain information on existing Caseware security certifications at Caseware’s Trust Center (trust.caseware.com). Upon Customer’s request, Caseware shall make available to Customer, or a third-party auditor instructed by Customer, once a year, information regarding Caseware’s compliance with this DPA and Data Protection Laws. Caseware may satisfy such requests by providing copies of its then-current third-party audit reports or certifications; if Customer reasonably demonstrates that such reports are insufficient onsite audits may be conducted. Any audit may include Caseware submitting its data processing facilities, data files and documentation needed for processing Personal Data (and/or those of its agents, affiliates and Sub-Processors) to reviewing, auditing and/or certifying by Customer (or any independent or impartial inspection agents or auditors selected by Customer and not reasonably objected to by Caseware), with reasonable notice and during regular business hours. Customer shall bear the costs of any audit and shall ensure that all audit findings are treated as Caseware’s Confidential Information. Before any information or audit is provided, the Parties shall mutually agree on the scope, timing, and duration of such audit.

16.        Restricted Transfers from the EU, Switzerland and the UK

Any transfer of Personal Data from the EU, Switzerland, the UK or the EEA to a country outside such areas that does not ensure an adequate level of protection as determined by decision of the EU Commission, or UK or Swiss regulatory authorities, will be subject to the applicable Standard Contractual Clauses (or applicable equivalent promulgated by the UK or Swiss regulatory authorities), at Attachment 3 and any transfer of Personal Data from the UK or Switzerland to a country that does not ensure an adequate level of protection as determined by decision of the EU, UK, or Swiss regulatory authorities, will be subject to the applicable equivalent to the SCCs used at the time, including the UK International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, at Attachment 4.

Customers transferring Personal Data from the EU, Switzerland, the EEA or the UK to Caseware will be considered a “Data Exporter”, and Caseware will be considered a “Data Importer” (both terms as defined in the Standard Contractual Clauses). Customer (as "data exporter") and Caseware (as "data importer") hereby enter into the Standard Contractual Clauses or the UK International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, as applicable, in respect of any Restricted Transfer from Customer to Caseware.

The Standard Contractual Clauses or the equivalent Swiss or UK International Data Transfer Addendum to the EU Commission Standard Contractual Clauses, as applicable, shall come into effect upon execution of the MPSA.

17.        California Specific Provisions

To the extent that Caseware processes any Personal Data relating to individuals who are California residents, Caseware shall comply with the requirements of the CCPA, including any amendments and implementing regulations that become effective on or after the effective date of this DPA, and shall provide the same level of privacy protection as is required by the CCPA. Capitalized terms used but not defined in this Section 17 shall have the same meaning as in the CCPA. For the purposes of the CCPA, the parties agree that Caseware is a “Service Provider” in the performance of its obligations, and that Customer is a “Business,” and that the transfer of Personal Data to Caseware shall not be considered a “Sale” or “Sharing.” To the extent required by the CCPA, Caseware shall (a) grant Customer the right to take reasonable and appropriate steps to help ensure that Caseware uses Personal Data in a manner consistent with Customer’s obligations under the CCPA; (b) notify Customer if Caseware determines that it can no longer meet its obligations under the CCPA; and (c) grant Customer the right, upon reasonable notice, to take reasonable and appropriate steps to stop and remediate any unauthorised use of Personal Data. To the extent required by the CCPA, Customer shall

inform Caseware of any consumer requests made pursuant to the CCPA with which it must comply, and shall provide all information necessary for Caseware to comply with such request.

Caseware shall Process Personal Data only for the “Business Purposes” specified in the MPSA and this DPA, including but not limited to (a) providing, operating, evaluating, monitoring, supporting, maintaining, securing, developing and improving the Services; (b) auditing Customer’s use of the Services; (c) helping to ensure security and integrity; (d) debugging to identify and repair errors that impair existing intended functionality; (e) short-term, transient use; and (f) undertaking internal research for technological development and demonstration, in each case solely to the extent permitted by applicable law and reasonably necessary and proportionate for those Business Purposes. Caseware shall not use Customer Data, Input or Outputs to train or fine-tune AI Models without Customer’s prior written authorization. The Parties agree that Customer discloses Personal Data to Caseware only for these limited and specified Business Purposes.

As a Service Provider, Caseware shall not:

-              Sell or Share Personal Data;

-              retain, use, or disclose Personal Data for any purpose other than for the Business Purposes specified in the MPSA and this DPA, including retaining, using, or disclosing Personal Data for a commercial purpose other than the Business Purposes specified in the MPSA and this DPA, or as otherwise permitted by the CCPA;

-              retain, use, or disclose Personal Data outside of the direct business relationship between Caseware and Customer; or

-              combine Personal Data that Caseware receives from, or on behalf of, Customer with personal information that it receives from, or on behalf of, another person or persons, or collects from its own interaction with the consumer, provided that Caseware may combine personal information to perform any Business Purpose as defined in the regulations adopted pursuant to paragraph (10) of subdivision (a) of Cal. Civ. Code § 1798.185, except as provided for in paragraph (6) of subdivision (e) of Cal. Civ. Code § 1798.140 and in regulations adopted by the California Privacy Protection Agency.

18.        Other U.S. Data Protection Laws

To the extent that Caseware Processes any Personal Data relating to individuals who are “Consumers” as that term is defined in the Colorado Privacy Act, Colo. Rev. Stat. §§ 6-1-1301 et seq. (“CPA”), the Connecticut Data Privacy Act, Public Act No. 22-15 (“CTDPA”), the Utah Consumer Privacy Act, Utah Code Ann. §§ 13-61-101 et seq. (“UCPA”), and the Virginia Consumer Data Protection Act, Va. Code Ann. §§59.1575 et seq. (“VCDPA”) (collectively, the “Consumer Privacy Laws” or “CPL”), respectively, and upon the respective effective dates of the CPL, Caseware shall comply with the CPL’s requirements, including any amendments and implementing regulations that become effective on or after the effective date of this DPA.

19.        Liability

The liability of the Parties under this DPA shall be subject to the liability provisions of the MPSA.

20.       Term & Termination

This DPA becomes effective upon agreement with the MPSA and shall remain in force as long as Caseware processes Personal Data or throughout the term of the MPSA, whichever is longer.

21.        Miscellaneous

In case of a conflict, between this DPA or any other agreement between the parties and the Standard Contractual Clauses, the Standard Contractual Clauses shall take precedence. In case of a conflict, between the provisions of this DPA and any other agreement between the Parties, this DPA shall take precedence. Should individual provisions of this DPA be or become invalid, this shall not affect the validity of the remaining conditions of this DPA. Without prejudice to Clause 17 (Governing Law) and Clause 18 (Forum and Jurisdiction) of the Standard Contractual Clauses, the Parties submit to the choice of jurisdiction and venue stipulated in the MPSA.

Attachment 1:

Technical and Organizational Measures (“TOMs”)

Action Description Technical & Organizational Measures
Pseudonymization Caseware employs tools to selectively anonymize sensitive data, which may include Personal Data. Pseudonymization is not necessarily used on all Personal Data elements, as not all Personal Data is identifiable as such to Caseware.
Encryption Encryption is used for data at rest, and this encryption is provided by Amazon Web Services Inc. (“AWS”), an approved Sub-Processor (see Attachment 2). Digital certificates are in place to manage encrypted communications to the Amazon Web Servers.
Confidentiality

All Caseware Employees are required to sign a confidentiality agreement and accept company policies and procedures upon hire.

An Information Security Incident Response Policy & Procedure is in place to address actual and potential data breaches.

Integrity

The Services provide administrative controls for clients to control who can access files within their firm. Caseware does not have these rights.

Caseware is ISO 27001 and SOC 2 Type 2 certified, and controls are in place to ensure that only those required to perform administrative operations have required access. An access control policy and procedures are in place to review access control lists.

Potential risks and the mitigation of potential risks are reviewed on a regular basis.

Availability

Monitoring is performed through an external health check and internally with capacity management monitoring solutions.

Quality assurance processes are in place and under regular review, to mitigate against potential downtime.

Resilience of Processing Systems The Services are hosted on AWS platform. The Services are ISO 27001 and SOC 2 Type 2 certified for security, confidentiality, integrity, privacy and availability.
Restoration Backup Policy and procedures are in place, with daily automated backup reports to ensure restoration is achievable. Reports are monitored by an operational team.
Auditing/Testing Regular audits take place for purposes of both ISO 27001 and SOC 2 Type 2 compliance. In addition, from time to time the company engages with a third party for penetration testing services.
Certification(s) ISO 27001 and SOC 2 Type 2.

Attachment 2:

The following Sub-Processors are listed in alphabetical order. Not all Sub-Processors are engaged for all Caseware Offerings — the service description indicates the relevant products and contexts. Caseware ensures that each Sub-Processor is bound by data protection obligations no less protective than those set out in this DPA. The current live Sub-Processor list is available at trust.caseware.com/subprocessors.

Sub-Processor / Address Service provided Processing location
Amazon Web Services, Inc.
410 Terry Ave N.,
Seattle, WA 98108, USA

Cloud infrastructure for hosting, storage and processing of Caseware Offerings and Customer Data, including AI inference via AWS Bedrock.

EU/EEA customers: processed via Amazon Web Services EMEA SARL (38 Avenue John F. Kennedy, L-1855 Luxembourg) in the AWS Ireland region. AI inference is processed within EU member states only and is not routed to the United Kingdom.

UK customers: processed via Amazon Web Services EMEA SARL in the AWS Ireland region. AI inference is processed within EU member states only.

Canadian customers: primarily processed in the AWS Canada (Central) region; where AI-enabled features are in use, certain inference requests may be routed to AWS US regions through Amazon Bedrock cross-region inference as described in Section 5.

Australian customers: processed in the AWS Asia Pacific (Sydney) region. AI inference is processed within Australia only.

US customers: processed in AWS US regions. Amazon Bedrock is configured with zero data retention: prompts and responses are not stored by AWS and are not used to train AI models. The model provider has no access to Customer Data, Input or Outputs.

Amazon Textract: Document text extraction and OCR service used within Verity (cloud and desktop). Data is processed in the same AWS region as the Customer's data, with no cross-region routing.

Varies by region – see service description
Cloudflare, Inc.
101 Townsend St.,
San Francisco, CA 94107, USA
Content delivery network, DDoS protection and network security for Caseware cloud products. Processes IP addresses, request metadata and web traffic logs of cloud product users. Global (Cloudflare network)
ConvertAPI, UAB
Lauksargio g. 111,
LT-10105 Vilnius,
Lithuania
PDF-to-Word conversion within certain Caseware cloud products. Processing is transient; no data is stored after conversion. Although ConvertAPI is an EU-registered entity, processing occurs via its Toronto, Canada datacenter. Canada (Toronto)
Google Analytics
(Google LLC),
1600 Amphitheatre Pkwy,
Mountain View,
CA 94043, USA
A web analytics service offered by Google that tracks and reports website traffic that can help to identify trends and patterns in how visitors interact with Caseware's website. USA
LaunchDarkly
(Catamorphic, Inc.)
1 Embarcadero Center
Suite 1500,
San Francisco, CA 94111, USA
Feature management and controlled rollout for Caseware cloud products including Verity and Collaborate. Processes pseudonymous user identifiers, firm identifiers and feature-flag evaluation data. USA
NetSuite (Oracle)
2300 Oracle Way,
Austin, TX 78741, USA
A cloud-based business platform that provides enterprise resource planning (ERP) services for Caseware's Back Office, invoicing and financial account management, inventory and supply chain management. USA
New Relic, Inc.
188 Spear St #1000,
San Francisco, CA 94105, USA
Application performance monitoring for Caseware cloud products. Processes technical and application logs, including IP addresses, host identifiers and pseudonymous user, firm and engagement identifiers. Caseware configures its logging pipeline to minimise the inclusion of Customer Data, Input and Outputs in logs sent to New Relic. USA
Pendo.io, Inc.
418 South Dawson Street,
Raleigh, NC 27601, USA
Product analytics and in-app guidance for Caseware cloud products. Processes user interaction events, firm name, IP address and pseudonymous user identifiers. USA
Salesforce, Inc.
Salesforce Tower,
415 Mission Street,
3rd Floor,
San Francisco, CA 94105, USA
A customer relationship management (CRM) platform for Caseware, and its customers and partners. Used for marketing, leads and communication campaign management. USA
TeamStaff Pty Ltd.
65 Gilbert St.,
Adelaide SA 5000,
Australia
Personnel for test and support functions for Extractly and Validate. Access to customer environments exclusively from Australia for support and testing purposes only. Australia
Usersnap GmbH
Herrenstrasse 6,
A-4020 Linz,
Austria
User feedback and support request tool integrated in Validate. Processes Personal Data only to the extent voluntarily submitted by users in support requests. EU (Austria)
Veeam Software Group GmbH
Lindenstrasse 16,
6341 Baar,
Switzerland
Backup and recovery for the Germany/EU server environment. May process system backup data including Customer Personal Data where present on backed-up systems. EEA / Switzerland

Attachment 3:

Standard Contractual Clauses

See attached.

           

STANDARD CONTRACTUAL CLAUSES SECTION I Clause 1 Purpose and scope

The purpose of these standard contractual clauses is to ensure compliance with the requirements of Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) for the transfer of personal data to a third country.

The Parties:

the natural or legal person(s), public authority/ies, agency/ies or other body/ies (hereinafter “entity/ies”) transferring the personal data, as listed in Annex I.A. (hereinafter each “data exporter”), and

the entity/ies in a third country receiving the personal data from the data exporter, directly or indirectly via another entity also Party to these Clauses, as listed in Annex I.A. (hereinafter each “data importer”) have agreed to these standard contractual clauses (hereinafter: “Clauses”).

These Clauses apply with respect to the transfer of personal data as specified in Annex I.B.

The Appendix to these Clauses containing the Annexes referred to therein forms an integral part of these Clauses.

Clause 2 Effect and invariability of the Clauses

These Clauses set out appropriate safeguards, including enforceable data subject rights and effective legal remedies, pursuant to Article 46(1) and Article 46 (2)(c) of Regulation (EU) 2016/679 and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679, provided they are not modified, except to select the appropriate Module(s) or to add or update information in the Appendix. This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a wider contract and/or to add other clauses or additional safeguards, provided that they do not contradict, directly or indirectly, these Clauses or prejudice the fundamental rights or freedoms of data subjects.

These Clauses are without prejudice to obligations to which the data exporter is subject by virtue of Regulation (EU) 2016/679.

Clause 3 Third-party beneficiaries

(a) Data subjects may invoke and enforce these Clauses, as third-party beneficiaries, against the data exporter and/or data importer, with the following exceptions:

Clause 1, Clause 2, Clause 3, Clause 6, Clause 7;

Clause 8 - Module One: Clause 8.5 (e) and Clause 8.9(b); Module Two: Clause 8.1(b), 8.9(a), (c), (d) and (e); Module Three: Clause 8.1(a), (c) and (d) and Clause 8.9(a), (c), (d), (e), (f) and (g); Module Four: Clause 8.1 (b) and Clause 8.3(b);

Clause 9 - Module Two: Clause 9(a), (c), (d) and (e); Module Three: Clause 9(a), (c), (d) and (e);

Clause 12 - Module One: Clause 12(a) and (d); Modules Two and Three: Clause 12(a), (d) and (f);

Clause 13;

Clause 15.1(c), (d) and (e);

Clause 16(e);

Clause 18 - Modules One, Two and Three: Clause 18(a) and (b); Module Four: Clause 18.

(b)        Paragraph (a) is without prejudice to rights of data subjects under Regulation (EU) 2016/679.

Clause 4 Interpretation

Where these Clauses use terms that are defined in Regulation (EU) 2016/679, those terms shall have the same meaning as in that Regulation.

These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679.

These Clauses shall not be interpreted in a way that conflicts with rights and obligations provided for in Regulation (EU) 2016/679.

Clause 5 Hierarchy

In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties, existing at the time these Clauses are agreed or entered into thereafter, these Clauses shall prevail.

Clause 6 Description of the transfer(s)

The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are specified in Annex I.B.

Clause 7 - Docking clause

An entity that is not a Party to these Clauses may, with the agreement of the Parties, accede to these Clauses at any time, either as a data exporter or as a data importer, by completing the Appendix and signing Annex I.A.

Once it has completed the Appendix and signed Annex I.A, the acceding entity shall become a Party to these Clauses and have the rights and obligations of a data exporter or data importer in accordance with its designation in Annex I.A.

The acceding entity shall have no rights or obligations arising under these Clauses from the period prior to becoming a Party.

SECTION II – OBLIGATIONS OF THE PARTIES Clause 8 Data protection safeguards

The data exporter warrants that it has used reasonable efforts to determine that the data importer is able, through the implementation of appropriate technical and organisational measures, to satisfy its obligations under these Clauses.

8.1        Instructions

The data importer shall process the personal data only on documented instructions from the data exporter. The data exporter may give such instructions throughout the duration of the contract.

The data importer shall immediately inform the data exporter if it is unable to follow those instructions.

Purpose limitation

The data importer shall process the personal data only for the specific purpose(s) of the transfer, as set out in Annex I.B, unless on further instructions from the data exporter.

Transparency

On request, the data exporter shall make a copy of these Clauses, including the Appendix as completed by the Parties, available to the data subject free of charge. To the extent necessary to protect business secrets or other confidential information, including the measures described in Annex II and personal data, the data exporter may redact part of the text of the Appendix to these Clauses prior to sharing a copy, but shall provide a meaningful summary where the data subject would otherwise not be able to understand the content or exercise his/her rights. On request, the Parties shall provide the data subject with the reasons for the redactions, to the extent possible without revealing the redacted information. This Clause is without prejudice to the obligations of the data exporter under Articles 13 and 14 of Regulation (EU) 2016/679.

Accuracy

If the data importer becomes aware that the personal data it has received is inaccurate, or has become outdated, it shall inform the data exporter without undue delay. In this case, the data importer shall cooperate with the data exporter to erase or rectify the data.

Duration of processing and erasure or return of data

Processing by the data importer shall only take place for the duration specified in Annex I.B. After the end of the provision of the processing services, the data importer shall, at the choice of the data exporter, delete all personal data processed on behalf of the data exporter and certify to the data exporter that it has done so, or return to the data exporter all personal data processed on its behalf and delete existing copies. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit return or deletion of the personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process it to the extent and for as long as required under that local law. This is without prejudice to Clause 14, in particular the requirement for the data importer under Clause 14(e) to notify the data exporter throughout the duration of the contract if it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under Clause 14(a).

Security of processing

The data importer and, during transmission, also the data exporter shall implement appropriate technical and organisational measures to ensure the security of the data, including protection against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to that data (hereinafter “personal data breach”). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purpose(s) of processing and the risks involved in the processing for the data subjects. The Parties shall in particular consider having recourse to encryption or pseudonymisation, including during transmission, where the purpose of processing can be fulfilled in that manner. In case of pseudonymisation, the additional information for attributing the personal data to a specific data subject shall, where possible, remain under the exclusive control of the data exporter. In complying with its obligations under this paragraph, the data importer shall at least implement the technical and organisational measures specified in Annex II. The data importer shall carry out regular checks to ensure that these measures continue to provide an appropriate level of security.

The data importer shall grant access to the personal data to members of its personnel only to the extent strictly necessary for the implementation, management and monitoring of the contract. It shall ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.

In the event of a personal data breach concerning personal data processed by the data importer under these Clauses, the data importer shall take appropriate measures to address the breach, including measures to mitigate its adverse effects. The data importer shall also notify the data exporter without undue delay after having become aware of the breach. Such notification shall contain the details of a contact point where more information can be obtained, a description of the nature of the breach (including, where possible, categories and approximate number of data subjects and personal data records concerned), its likely consequences and the measures taken or proposed to address the breach including, where appropriate, measures to mitigate its possible adverse effects. Where, and in so far as, it is not possible to provide all information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.

The data importer shall cooperate with and assist the data exporter to enable the data exporter to comply with its obligations under Regulation (EU) 2016/679, in particular to notify the competent supervisory authority and the affected data subjects, taking into account the nature of processing and the information available to the data importer.

Sensitive data

Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter “sensitive data”), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.

Onward transfers

The data importer shall only disclose the personal data to a third party on documented instructions from the data exporter. In addition, the data may only be disclosed to a third party located outside the European Union (in the same country as the data importer or in another third country, hereinafter “onward transfer”) if the third party is or agrees to be bound by these Clauses, under the appropriate Module, or if:

the onward transfer is to a country benefitting from an adequacy decision pursuant to Article 45 of Regulation (EU) 2016/679 that covers the onward transfer;

the third party otherwise ensures appropriate safeguards pursuant to Articles 46 or 47 Regulation of (EU) 2016/679 with respect to the processing in question;

the onward transfer is necessary for the establishment, exercise or defence of legal claims in the context of specific administrative, regulatory or judicial proceedings; or

the onward transfer is necessary in order to protect the vital interests of the data subject or of another natural person.

Any onward transfer is subject to compliance by the data importer with all the other safeguards under these Clauses, in particular purpose limitation.

8.9       Documentation and compliance

The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.

The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter.

The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.

The data exporter may choose to conduct the audit by itself or mandate an independent auditor. Audits may include inspections at the premises or physical facilities of the data importer and shall, where appropriate, be carried out with reasonable notice.

The Parties shall make the information referred to in paragraphs (b) and (c), including the results of any audits, available to the competent supervisory authority on request.

Clause 9 Use of sub-processors

The data importer has the data exporter’s general authorisation for the engagement of subprocessor(s) from an agreed list. The data importer shall specifically inform the data exporter in writing of any intended changes to that list through the addition or replacement of sub-processors […]. The data importer shall provide the data exporter with the information necessary to enable the data exporter to exercise its right to object.

Where the data importer engages a sub-processor to carry out specific processing activities (on behalf of the data exporter), it shall do so by way of a written contract that provides for, in substance, the same data protection obligations as those binding the data importer under these Clauses, including in terms of third-party beneficiary rights for data subjects. The Parties agree that, by complying with this Clause, the data importer fulfills its obligations under Clause 8.8. The data importer shall ensure that the sub-processor complies with the obligations to which the data importer is subject pursuant to these Clauses.

The data importer shall provide, at the data exporter’s request, a copy of such a sub-processor agreement and any subsequent amendments to the data exporter. To the extent necessary to protect business secrets or other confidential information, including personal data, the data importer may redact the text of the agreement prior to sharing a copy.

The data importer shall remain fully responsible to the data exporter for the performance of the subprocessor’s obligations under its contract with the data importer. The data importer shall notify the data exporter of any failure by the sub-processor to fulfil its obligations under that contract.

The data importer shall agree a third-party beneficiary clause with the sub-processor whereby - in the event the data importer has factually disappeared, ceased to exist in law or has become insolvent - the data exporter shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.

Clause 10 Data subject rights

The data importer shall promptly notify the data exporter of any request it has received from a data subject. It shall not respond to that request itself unless it has been authorised to do so by the data exporter.

The data importer shall assist the data exporter in fulfilling its obligations to respond to data subjects’ requests for the exercise of their rights under Regulation (EU) 2016/679. In this regard, the Parties shall set out in Annex II the appropriate technical and organisational measures, taking into account the nature of the processing, by which the assistance shall be provided, as well as the scope and the extent of the assistance required.

In fulfilling its obligations under paragraphs (a) and (b), the data importer shall comply with the instructions from the data exporter.

Clause 11 Redress

The data importer shall inform data subjects in a transparent and easily accessible format, through individual notice or on its website, of a contact point authorised to handle complaints. It shall deal promptly with any complaints it receives from a data subject.

The data importer agrees that data subjects may also lodge a complaint with an independent dispute resolution body at no cost to the data subject. It shall inform the data subjects, in the manner set out in paragraph (a), of such redress mechanism and that they are not required to use it, or follow a particular sequence in seeking redress.

In case of a dispute between a data subject and one of the Parties as regards compliance with these Clauses, that Party shall use its best efforts to resolve the issue amicably in a timely fashion. The Parties shall keep each other informed about such disputes and, where appropriate, cooperate in resolving them.

Where the data subject invokes a third-party beneficiary right pursuant to Clause 3, the data importer shall accept the decision of the data subject to:

lodge a complaint with the supervisory authority in the Member State of his/her habitual residence or place of work, or the competent supervisory authority pursuant to Clause 13;

refer the dispute to the competent courts within the meaning of Clause 18.

The Parties accept that the data subject may be represented by a not-for-profit body, organisation or association under the conditions set out in Article 80(1) of Regulation (EU) 2016/679.

The data importer shall abide by a decision that is binding under the applicable EU or Member State law.

The data importer agrees that the choice made by the data subject will not prejudice his/her substantive and procedural rights to seek remedies in accordance with applicable laws.

Clause 12 Liability

Each Party shall be liable to the other Party/ies for any damages it causes the other Party/ies by any breach of these Clauses.

Each Party shall be liable to the data subject, and the data subject shall be entitled to receive compensation, for any material or non-material damages that the Party causes the data subject by breaching the third-party beneficiary rights under these Clauses. This is without prejudice to the liability of the data exporter under Regulation (EU) 2016/679.

Where more than one Party is responsible for any damage caused to the data subject as a result of a breach of these Clauses, all responsible Parties shall be jointly and severally liable and the data subject is entitled to bring an action in court against any of these Parties.

The Parties agree that if one Party is held liable under paragraph (c), it shall be entitled to claim back from the other Party/ies that part of the compensation corresponding to its / their responsibility for the damage.

The data importer may not invoke the conduct of a processor or sub-processor to avoid its own liability.

Clause 13 Supervision

Where the data exporter is established in an EU Member State: The supervisory authority with responsibility for ensuring compliance by the data exporter with Regulation (EU) 2016/679 as regards the data transfer, as indicated in Annex I.C, shall act as competent supervisory authority.

Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of Regulation (EU) 2016/679: The supervisory authority of the Member State in which the representative within the meaning of Article 27(1) of Regulation (EU) 2016/679 is established, as indicated in Annex I.C, shall act as competent supervisory authority.

Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of Regulation (EU) 2016/679 in accordance with its Article 3(2) without however having to appoint a representative pursuant to Article 27(2) of Regulation (EU) 2016/679: The supervisory authority of one of the Member States in which the data subjects whose personal data is transferred under these Clauses in relation to the offering of goods or services to them, or whose behaviour is monitored, are located, as indicated in Annex I.C, shall act as competent supervisory authority.

The data importer agrees to submit itself to the jurisdiction of and cooperate with the competent supervisory authority in any procedures aimed at ensuring compliance with these Clauses. In particular, the data importer agrees to respond to enquiries, submit to audits and comply with the measures adopted by the supervisory authority, including remedial and compensatory measures. It shall provide the supervisory authority with written confirmation that the necessary actions have been taken.

SECTION III – LOCAL LAWS AND OBLIGATIONS IN CASE OF ACCESS BY PUBLIC AUTHORITIES Clause 14 Local laws and practices affecting compliance with the Clauses

The Parties warrant that they have no reason to believe that the laws and practices in the third country of destination applicable to the processing of the personal data by the data importer, including any requirements to disclose personal data or measures authorising access by public authorities, prevent the data importer from fulfilling its obligations under these Clauses. This is based on the understanding that laws and practices that respect the essence of the fundamental rights and freedoms and do not exceed what is necessary and proportionate in a democratic society to safeguard one of the objectives listed in Article 23(1) of Regulation (EU) 2016/679, are not in contradiction with these Clauses.

The Parties declare that in providing the warranty in paragraph (a), they have taken due account in particular of the following elements:

the specific circumstances of the transfer, including the length of the processing chain, the number of actors involved and the transmission channels used; intended onward transfers; the type of recipient; the purpose of processing; the categories and format of the transferred personal data; the economic sector in which the transfer occurs; the storage location of the data transferred;

the laws and practices of the third country of destination– including those requiring the disclosure of data to public authorities or authorising access by such authorities – relevant in light of the specific circumstances of the transfer, and the applicable limitations and safeguards;

any relevant contractual, technical or organisational safeguards put in place to supplement the safeguards under these Clauses, including measures applied during transmission and to the processing of the personal data in the country of destination.

The data importer warrants that, in carrying out the assessment under paragraph (b), it has made its best efforts to provide the data exporter with relevant information and agrees that it will continue to cooperate with the data exporter in ensuring compliance with these Clauses.

The Parties agree to document the assessment under paragraph (b) and make it available to the competent supervisory authority on request.

The data importer agrees to notify the data exporter promptly if, after having agreed to these Clauses and for the duration of the contract, it has reason to believe that it is or has become subject to laws or practices not in line with the requirements under paragraph (a), including following a change in the laws of the third country or a measure (such as a disclosure request) indicating an application of such laws in practice that is not in line with the requirements in paragraph (a).

Following a notification pursuant to paragraph (e), or if the data exporter otherwise has reason to believe that the data importer can no longer fulfil its obligations under these Clauses, the data exporter shall promptly identify appropriate measures (e.g. technical or organisational measures to ensure security and confidentiality) to be adopted by the data exporter and/or data importer to address the situation [for Module Three: , if appropriate in consultation with the controller]. The data exporter shall suspend the data transfer if it considers that no appropriate safeguards for such transfer can be ensured, or if instructed by [for Module Three: the controller or] the competent supervisory authority to do so. In this case, the data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses. If the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise. Where the contract is terminated pursuant to this Clause, Clause 16(d) and (e) shall apply.

Clause 15 Obligations of the data importer in case of access by public authorities

15.1       Notification

(a)        The data importer agrees to notify the data exporter and, where possible, the data subject promptly (if necessary, with the help of the data exporter) if it:

receives a legally binding request from a public authority, including judicial authorities, under the laws of the country of destination for the disclosure of personal data transferred pursuant to these Clauses; such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided; or

becomes aware of any direct access by public authorities to personal data transferred pursuant to these Clauses in accordance with the laws of the country of destination; such notification shall include all information available to the importer.

If the data importer is prohibited from notifying the data exporter and/or the data subject under the laws of the country of destination, the data importer agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicating as much information as possible, as soon as possible. The data importer agrees to document its best efforts in order to be able to demonstrate them on request of the data exporter.

Where permissible under the laws of the country of destination, the data importer agrees to provide the data exporter, at regular intervals for the duration of the contract, with as much relevant information as possible on the requests received (in particular, number of requests, type of data requested, requesting authority/ies, whether requests have been challenged and the outcome of such challenges, etc.).

The data importer agrees to preserve the information pursuant to paragraphs (a) to (c) for the duration of the contract and make it available to the competent supervisory authority on request.

Paragraphs (a) to (c) are without prejudice to the obligation of the data importer pursuant to Clause 14(e) and Clause 16 to inform the data exporter promptly where it is unable to comply with these Clauses.

15.2      Review of legality and data minimization.

The data importer agrees to review the legality of the request for disclosure, in particular whether it remains within the powers granted to the requesting public authority, and to challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful under the laws of the country of destination, applicable obligations under international law and principles of international comity. The data importer shall, under the same conditions, pursue possibilities of appeal. When challenging a request, the data importer shall seek interim measures with a view to suspending the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the personal data requested until required to do so under the applicable procedural rules. These requirements are without prejudice to the obligations of the data importer under Clause 14(e).

The data importer agrees to document its legal assessment and any challenge to the request for disclosure and, to the extent permissible under the laws of the country of destination, make the documentation available to the data exporter. It shall also make it available to the competent supervisory authority on request. [For Module Three: The data exporter shall make the assessment available to the controller.]

The data importer agrees to provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request.

SECTION IV – FINAL PROVISIONS Clause 16 Non-compliance with the Clauses and termination

The data importer shall promptly inform the data exporter if it is unable to comply with these Clauses, for whatever reason.

In the event that the data importer is in breach of these Clauses or unable to comply with these Clauses, the data exporter shall suspend the transfer of personal data to the data importer until compliance is again ensured or the contract is terminated. This is without prejudice to Clause 14(f).

The data exporter shall be entitled to terminate the contract, insofar as it concerns the processing of personal data under these Clauses, where:

the data exporter has suspended the transfer of personal data to the data importer pursuant to paragraph (b) and compliance with these Clauses is not restored within a reasonable time and in any event within one month of suspension;

the data importer is in substantial or persistent breach of these Clauses; or

the data importer fails to comply with a binding decision of a competent court or supervisory authority regarding its obligations under these Clauses.

In these cases, it shall inform the competent supervisory authority of such non-compliance. Where the contract involves more than two Parties, the data exporter may exercise this right to termination only with respect to the relevant Party, unless the Parties have agreed otherwise.

Personal data that has been transferred prior to the termination of the contract pursuant to paragraph (c) shall at the choice of the data exporter immediately be returned to the data exporter or deleted in its entirety. The same shall apply to any copies of the data. The data importer shall certify the deletion of the data to the data exporter. Until the data is deleted or returned, the data importer shall continue to ensure compliance with these Clauses. In case of local laws applicable to the data importer that prohibit the return or deletion of the transferred personal data, the data importer warrants that it will continue to ensure compliance with these Clauses and will only process the data to the extent and for as long as required under that local law.

Either Party may revoke its agreement to be bound by these Clauses where (i) the European Commission adopts a decision pursuant to Article 45(3) of Regulation (EU) 2016/679 that covers the transfer of personal data to which these Clauses apply; or (ii) Regulation (EU) 2016/679 becomes part of the legal framework of the country to which the personal data is transferred. This is without prejudice to other obligations applying to the processing in question under Regulation (EU) 2016/679.

Clause 17 Governing law

These Clauses shall be governed by the law of the EU Member State in which the data exporter is established. Where such law does not allow for third-party beneficiary rights, they shall be governed by the law of another EU Member State that does allow for third-party beneficiary rights. The Parties agree that this shall be the law of Ireland.

Clause 18 Choice of forum and jurisdiction

Any dispute arising from these Clauses shall be resolved by the courts of an EU Member State.

The Parties agree that those shall be the courts of Ireland.

A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of the Member State in which he/she has his/her habitual residence.

The Parties agree to submit themselves to the jurisdiction of such courts.

           

ANNEX I

Defined terms used in this Annex 1 shall have the meaning given to them in the MPSA between Caseware and Customer, and/or the DPA.

A. LIST OF PARTIES

Data exporter(s):

1. Name: The Customer (the legal entity entering into the MPSA with Caseware). Address: As specified in the applicable Order Form. Contact person: As specified in the applicable Order Form.

Activities relevant to the data transferred under these Clauses: Transfer of Customer's Personal Data to Caseware for processing in connection with the Services. Role (controller/processor): Controller

Data importer(s):

1. Name: Caseware International Inc. or the Affiliate of Caseware International Inc. identified in the applicable Order Form. Address: As applicable per the relevant entity; see Section 1 of the DPA. Contact person: Global Data Protection Officer; privacy@caseware.com.

Activities relevant to the data transferred under these Clauses: Processing of Customer's Personal Data in connection with the provision of the Services as described in the MPSA. Role (controller/processor): Processor

B. DESCRIPTION OF TRANSFER

Categories of data subjects whose personal data is transferred:

Please see the DPA, which describes the Categories of personal data transferred:

Please see the DPA, which describes the categories of data.

Sensitive data transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialized training), keeping a record of access to the data, restrictions for onward transfers or additional security measures.

The parties do not anticipate the transfer of special categories of data.

The frequency of the transfer (e.g., whether the data is transferred on a one-off or continuous basis).

Please see the DPA

Nature of the processing

Please see the DPA

Purpose(s) of the data transfer and further processing

Please see the DPA

The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period

Please see the DPA

For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing

Please see the DPA

C. COMPETENT SUPERVISORY AUTHORITY

Identify the competent supervisory authority/ies in accordance with Clause 13

●    The competent supervisory authority that shall apply will be the competent supervisory authority of the country in which the Customer’s client’s data originates

           

ANNEX II TECHNICAL AND ORGANISATIONAL MEASURES TO ENSURE THE SECURITY OF THE DATA

See Attachment 1 of the DPA, which describes the technical and organizational security measures implemented by Caseware.

           

ANNEX III

LIST OF SUB-PROCESSORS

See Attachment 2 of the DPA, which lists Caseware's current Sub-Processors.

           

Attachment 4:

UK International Data Transfer Addendum to the EU Commission Standard Contractual Clauses

See attached.

           

This Addendum has been issued by the Information Commissioner for Parties making Restricted Transfers. The Information Commissioner considers that it provides Appropriate Safeguards for Restricted Transfers when it is entered into as a legally binding contract.

           ○          Part 1: Tables

           ■          Table 1: Parties

Start date
The Parties
Exporter (who sends the Restricted Transfer)
Importer (who receives the Restricted Transfer)
Parties’ details

Full legal name:


Trading name (if different):

Main address (if a company registered address):

Official registration number (if any) (company number or similar identifier):

Full legal name:

Trading name (if different):

Main address (if a company registered address):

Official registration number (if any) (company number or similar identifier):

Key Contact

Full Name (optional):

Job Title:

Contact details including email:

Full Name (optional):

Job Title:

Contact details including email:

Signature (if required for the purposes of Section 2)

           ■          Table 2: Selected SCCs, Modules and Selected Clauses

Addendum EU SCCs
The version of the Approved EU SCCs which this Addendum is appended to, detailed below, including the Appendix Information:

Date:


Reference (if any):

Other identifier (if any):

Or

the Approved EU SCCs, including the Appendix Information and with only the following modules, clauses or optional provisions of the Approved
EU SCCs brought into effect for the purposes of this Addendum:

Module Module in operation Clause 7
(Docking Clause)
Clause 11
(Option)
Clause 9a
(Prior Authorisation or General Authorisation)
Clause 9a
(Time period)
Is personal data received from the Importer combined with personal data collected by the Exporter?
1
2
3
4

■          Table 3: Appendix Information

“Appendix Information” means the information which must be provided for the selected modules as set out in the Appendix of the Approved EU SCCs (other than the Parties), and which for this Addendum is set out in:

Annex 1A: List of Parties:

Annex 1B: Description of Transfer:

Annex II: Technical and organisational measures including technical and organisational measures to ensure the security of the data:

Annex III: List of Sub processors (Modules 2 and 3 only):

           ■          Table 4: Ending this Addendum when the Approved Addendum Changes

Ending this Addendum when the Approved

Which Parties may end this Addendum as set out in Section 19:

Importer
Exporter
Addendum changes
neither Party

           ○          Part 2: Mandatory Clauses

           ■          Entering into this Addendum

Each Party agrees to be bound by the terms and conditions set out in this Addendum, in exchange for the other Party also agreeing to be bound by this Addendum.

Although Annex 1A and Clause 7 of the Approved EU SCCs require signature by the Parties, for the purpose of making Restricted Transfers, the Parties may enter into this Addendum in any way that makes them legally binding on the Parties and allows data subjects to enforce their rights as set out in this Addendum. Entering into this Addendum will have the same effect as signing the Approved EU SCCs and any part of the Approved EU SCCs.

           ■          Interpretation of this Addendum

Where this Addendum uses terms that are defined in the Approved EU SCCs, those terms shall have the same meaning as in the Approved EU SCCs. In addition, the following terms have the following meanings:

Addendum
This International Data Transfer Addendum which is made up of this Addendum incorporating the Addendum EU SCCs.
Addendum EU SCCs
The version(s) of the Approved EU SCCs which this Addendum is appended to, as set out in Table 2, including the Appendix Information.
Appendix Information
As set out in Table 3.
Appropriate Safeguards
The standard of protection over the personal data and of data subjects’ rights, which is required by UK Data Protection Laws when you are making a Restricted Transfer relying on standard data protection clauses under Article 46(2)(d) UK GDPR.
Approved Addendum
The template Addendum issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18.
Approved EU SCCs
The Standard Contractual Clauses set out in the Annex of Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
ICO
The Information Commissioner.
Restricted Transfer
A transfer which is covered by Chapter V of the UK GDPR.
UK
The United Kingdom of Great Britain and Northern Ireland.
UK Data Protection Laws
All laws relating to data protection, the processing of personal data, privacy and/or electronic communications in force from time to time in the UK, including the UK GDPR and the Data Protection Act 2018.
UK GDPR
As defined in section 3 of the Data Protection Act 2018.

This Addendum must always be interpreted in a manner that is consistent with UK Data Protection Laws and so that it fulfils the Parties’ obligation to provide the Appropriate Safeguards.

If the provisions included in the Addendum EU SCCs amend the Approved SCCs in any way which is not permitted under the Approved EU SCCs or the Approved Addendum, such amendment(s) will not be incorporated in this Addendum and the equivalent provision of the Approved EU SCCs will take their place.

If there is any inconsistency or conflict between UK Data Protection Laws and this Addendum, UK Data Protection Laws applies.

If the meaning of this Addendum is unclear or there is more than one meaning, the meaning which most closely aligns with UK Data Protection Laws applies.

Any references to legislation (or specific provisions of legislation) means that legislation (or specific provision) as it may change over time. This includes where that legislation (or specific provision) has been consolidated, re-enacted and/or replaced after this Addendum has been entered into.

           ■          Hierarchy

Although Clause 5 of the Approved EU SCCs sets out that the Approved EU SCCs prevail over all related agreements between the parties, the parties agree that, for Restricted Transfers, the hierarchy in Section 10 will prevail.

Where there is any inconsistency or conflict between the Approved Addendum and the Addendum

EU SCCs (as applicable), the Approved Addendum overrides the Addendum EU SCCs, except where (and in so far as) the inconsistent or conflicting terms of the Addendum EU SCCs provides greater protection for data subjects, in which case those terms will override the Approved Addendum.

Where this Addendum incorporates Addendum EU SCCs which have been entered into to protect

transfers subject to the General Data Protection Regulation (EU) 2016/679 then the Parties acknowledge that nothing in this Addendum impacts those Addendum EU SCCs.

           ■          Incorporation of and changes to the EU SCCs

This Addendum incorporates the Addendum EU SCCs which are amended to the extent necessary so that:

together they operate for data transfers made by the data exporter to the data importer, to the extent that UK Data Protection Laws apply to the data exporter’s processing when making that data transfer, and they provide Appropriate Safeguards for those data transfers;

Sections 9 to 11 override Clause 5 (Hierarchy) of the Addendum EU SCCs; and

this Addendum (including the Addendum EU SCCs incorporated into it) is (1) governed by the laws of England and Wales and (2) any dispute arising from it is resolved by the courts of England and Wales, in each case unless the laws and/or courts of Scotland or Northern Ireland have been expressly selected by the Parties.

Unless the Parties have agreed alternative amendments which meet the requirements of Section 12, the provisions of Section 15 will apply.

No amendments to the Approved EU SCCs other than to meet the requirements of Section 12 may be made.

The following amendments to the Addendum EU SCCs (for the purpose of Section 12) are made:

a. References to the “Clauses” means this Addendum, incorporating the Addendum EU SCCs; b. In Clause 2, delete the words:

“and, with respect to data transfers from controllers to processors and/or processors to processors, standard contractual clauses pursuant to Article 28(7) of Regulation (EU) 2016/679”;

Clause 6 (Description of the transfer(s)) is replaced with:

“The details of the transfer(s) and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred are those specified in Annex I.B where UK Data Protection Laws apply to the data exporter’s processing when making that transfer.”;

Clause 8.7(i) of Module 1 is replaced with:

“it is to a country benefitting from adequacy regulations pursuant to Section 17A of the UK GDPR that covers the onward transfer”;

Clause 8.8(i) of Modules 2 and 3 is replaced with:

“the onward transfer is to a country benefitting from adequacy regulations pursuant to Section 17A of the UK GDPR that covers the onward transfer;”

References to “Regulation (EU) 2016/679”, “Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation)” and “that Regulation” are all replaced by “UK Data Protection Laws”. References to specific Article(s) of “Regulation (EU) 2016/679” are replaced with the equivalent Article or Section of UK Data Protection Laws;

References to Regulation (EU) 2018/1725 are removed;

References to the “European Union”, “Union”, “EU”, “EU Member State”, “Member State” and “EU or Member State” are all replaced with the “UK”;

The reference to “Clause 12(c)(i)” at Clause 10(b)(i) of Module one, is replaced with “Clause 11(c)(i)”;

Clause 13(a) and Part C of Annex I are not used;

The “competent supervisory authority” and “supervisory authority” are both replaced with the “Information Commissioner”;

In Clause 16(e), subsection (i) is replaced with:

“the Secretary of State makes regulations pursuant to Section 17A of the Data Protection Act 2018 that cover the transfer of personal data to which these clauses apply;”; m. Clause 17 is replaced with:

“These Clauses are governed by the laws of England and Wales.”;

Clause 18 is replaced with:

“Any dispute arising from these Clauses shall be resolved by the courts of England and Wales. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of any country in the UK. The Parties agree to submit themselves to the jurisdiction of such courts.”; and

The footnotes to the Approved EU SCCs do not form part of the Addendum, except for footnotes 8, 9, 10 and 11.

           ■          Amendments to this Addendum

The Parties may agree to change Clauses 17 and/or 18 of the Addendum EU SCCs to refer to the laws and/or courts of Scotland or Northern Ireland.

If the Parties wish to change the format of the information included in Part 1: Tables of the Approved Addendum, they may do so by agreeing to the change in writing, provided that the change does not reduce the Appropriate Safeguards.

From time to time, the ICO may issue a revised Approved Addendum which:

makes reasonable and proportionate changes to the Approved Addendum, including correcting errors in the Approved Addendum; and/or

reflects changes to UK Data Protection Laws;

The revised Approved Addendum will specify the start date from which the changes to the Approved Addendum are effective and whether the Parties need to review this Addendum including the Appendix Information. This Addendum is automatically amended as set out in the revised Approved Addendum from the start date specified.

If the ICO issues a revised Approved Addendum under Section 18, if any Party selected in Table 4 “Ending the Addendum when the Approved Addendum changes”, will as a direct result of the changes in the Approved Addendum have a substantial, disproportionate and demonstrable increase in:

its direct costs of performing its obligations under the Addendum; and/or

its risk under the Addendum,

and in either case it has first taken reasonable steps to reduce those costs or risks so that it is not substantial and disproportionate, then that Party may end this Addendum at the end of a reasonable notice period, by providing written notice for that period to the other Party before the start date of the revised Approved Addendum.

The Parties do not need the consent of any third party to make changes to this Addendum, but any changes must be made in accordance with its terms.

           -           Alternative Part 2 Mandatory Clauses:

Mandatory Clauses

Part 2: Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the ICO and laid before Parliament in accordance with s119A of the Data Protection Act 2018 on 2 February 2022, as it is revised under Section 18 of those Mandatory Clauses.

‍

See what your
audit workflow looks like

with Ai built in.
Get in touch
Version: 3.0
Last Updated: January 2023

Data Processing Agreement

Seguridad de la aplicación y la interfaz

Nuestro ciclo de vida de desarrollo de software (SDLC) garantiza que nuestras aplicaciones e interfaces de programación (API) se diseñen, implementen y prueben de conformidad con los estándares líderes del sector (como OWASP, ISO y SOC), y se ajusten a las obligaciones de cumplimiento legales, reglamentarias o regulatorias.

Una vez que todos los acuerdos y políticas se hayan aceptado para el uso del servicio. Usted es responsable de asegurarse de que el uso que hace de Caseware Cloud sea conforme a las leyes y reglamentos aplicables. Puede consultar los detalles legales en el Acuerdo de Servicios en la nube aquí: https://docs.caseware.com/latest/webapps/en/Setup/Licenses/CaseWare-Cloud-Services-Agreement.htm.

Hemos establecido y mantenemos políticas y procedimientos en apoyo a la seguridad de los datos para incluir confidencialidad, integridad y disponibilidad en diferentes interfaces del sistema, jurisdicciones y funciones empresariales con el fin de evitar la inadecuada divulgación, alteración o eliminación.

Cumplimiento y garantía de auditoría

Para nuestros servicios en la nube, y como parte de nuestro programa de cumplimiento de la ISO 27001 y SOC 2, se realizan auditorías independientes llevadas a cabo por terceros. Además, contamos con un programa de auditoría interna y pruebas externas de penetración, y planificamos con regularidad pruebas de vulnerabilidad interna. Los resultados de las pruebas de vulnerabilidad se comparten con los clientes tal como se indica en la Política de pruebas iniciadas por el cliente. Asimismo, a través de nuestro proceso de mejoras, se hace un seguimiento de los resultados de estos procesos. La metodología y las herramientas utilizadas para realizar las pruebas de penetración se ajustan de acuerdo a cada evaluación para objetivos específicos y perfiles de atacantes. Los informes SOC 2 se proporcionan a los clientes en virtud del Acuerdo de Confidencialidad (NDA, en inglés). Nuestro informe SOC 3 está disponible en formato PDF aquí.

Los datos de producción se almacenan en Amazon Web Services (AWS). La aplicación gestiona separación lógica de datos de clientes a través de un aislamiento de la base de datos. Los datos que se transfieren hacia y desde nuestro servicio (incluidas las copias de seguridad) están totalmente cifrados mediante una conexión SSL (AES de 256 bits, que es la que se utiliza en la banca online). La transmisión de datos tiene lugar entre el cliente y el servidor, y las bases de datos. Se realizan controles para garantizar que las transferencias de conjuntos masivos de datos se realizan de forma segura y cifrada. No hay transmisiones de correos electrónicos. Para obtener más información sobre seguridad, consulte: https://www.casewarecloud.com/security.html. Nuestro equipo legal supervisa nuestras obligaciones reglamentarias. Para conocer los requisitos legales, consulte nuestro contrato de servicios en la nube. https://docs.caseware.com/latest/webapps/en/Setup/Licenses/CaseWare-Cloud-Services-Agreement.htm.

Gestión de continuidad empresarial y resiliencia operativa

Caseware cuenta con un marco unificado coherente para la planificación de la continuidad empresarial y lo ha establecido, documentado y adoptado para garantizar que todos los planes de continuidad empresarial sean coherentes a la hora de abordar las prioridades en cuanto a pruebas, mantenimiento y requisitos de seguridad de la información. Los requisitos para los planes de continuidad empresarial incluyen los siguientes:

  • Propósito y alcance definidos, ajustados a las dependencias pertinentes.
  • Accesibles y comprensibles para aquellos que vayan a utilizarlos.
  • Propiedad de una o varias personas designadas que serán responsables de su revisión, actualización y aprobación.
  • Líneas definidas de comunicación, funciones y responsabilidades.
  • Procedimientos detallados de recuperación, operación manual e información de referencia.
  • Método para la invocación de planes

Nuestros planes de continuidad empresarial y de respuesta de incidentes de seguridad se prueban en intervalos planificados o tras cambios significativos a nivel de organización o del entorno. Los planes de respuesta de incidentes incluyen a clientes que se vean afectados (arrendatarios) y a otras relaciones empresariales que representan dependencias fundamentales de procesos empresariales de la cadena interna de suministros.

Nuestro servicio está alojado en el AWS de Amazon y los servicios de suministros y condiciones ambientales (por ejemplo, controles de agua, electricidad, temperatura y humedad, telecomunicaciones y conexión a internet) están protegidos, monitorizados, conservados y probados para una eficacia continuada a intervalos planificados para garantizar la protección ante daños u obstaculización no autorizada, y están diseñados con conmutación por error automatizada u otras redundancias en el caso de interrupciones planificadas o no.

Nuestro servicio en la nube es completamente virtual y está alojado en Amazon Web Services (AWS). Amazon también cumple con ISO y SOC2, y es responsable de que solo personas autorizadas accedan a las instalaciones que alojen los sistemas de producción. Asimismo, AWS es responsable de la protección ambiental y mantenimiento preventivo de los sistemas de producción. AWS ha publicado más detalles al respecto aquí: https://aws.amazon.com/compliance/data-center/controls. Estas certificaciones tratan cuestiones como la seguridad física, la disponibilidad del sistema, el acceso a la red y a la red central de IP, el aprovisionamiento de clientes y la gestión de problemas. El acceso físico y los controles ambientales los gestiona y controla AWS. La información de aseguramiento de protección física de AWS puede consultarse en: https://aws.amazon.com/compliance.

En Caseware, hemos ajustado nuestro programa de seguridad a la ISO 27001 y tenemos implementados procesos de continuidad empresarial para abordar las interrupciones en servicios esenciales. Hacemos seguimiento de todas las instancias de la nube en cuanto a rendimiento y disponibilidad, además de:

  • Identificar productos y servicios esenciales.
  • Identificar todas las dependencias, incluidos procesos, aplicaciones, socios empresariales y proveedores de servicios de terceros.
  • Comprender las amenazas a los servicios y productos esenciales.
  • Determinar el impacto resultante de interrupciones planificadas o no, y cómo varían en el tiempo.
  • Establecer el periodo máximo tolerable de la interrupción.
  • Establecer prioridades para la recuperación.
  • Establecer objetivos de tiempo de recuperación para la reanudación de productos y servicios esenciales dentro de su periodo de interrupción máximo tolerable.
  • Estimar los recursos requeridos para la reanudación.

Los clientes pueden ver nuestro estado operativo en tiempo real en nuestra página de estado aquí: https://caseware.statuspage.io/. Mantenemos un sistema central para la documentación y formación de los procesos para todo el personal. Los procedimientos incluyen gestión de cambios, procesos de seguridad y funciones y responsabilidades de los usuarios internos. Nuestros procedimientos se actualizan según sea necesario y se registran historiales de revisiones. Además, las políticas y procedimientos incluirán funciones y responsabilidades definidas, y el personal recibirá formación al respecto de forma periódica.

Caseware mantiene una política de conservación y registro para los servicios en la nube. La política de conservación no es específica del cliente. Los procedimientos de recuperación y de copias de seguridad están documentados y cada día se envían alertas automatizadas al personal de operaciones. Las medidas de recuperación y de copias de seguridad se han incorporado a la planificación de continuidad empresarial y se ha probado su eficacia de la manera pertinente. A continuación, puede consultar la política de conservación de cada categoría de registros. Registros de transacciones del sistema Descripción: Diarios de bases de datos y otros registros utilizados para la recuperación de bases de datos. Periodo de conservación: 30 días. Motivo de la conservación: se basa en la estrategia de recuperación y de copia de seguridad. Medios de almacenamiento admitidos: electrónicos. Registros de auditoría Descripción: registros de seguridad, por ejemplo, registros de inicio/cierre de sesión y cambios de permisos. Periodo de conservación: 30 días. Motivo de la conservación: periodo máximo de retraso antes de investigación forense. Medios de almacenamiento admitidos: electrónicos. Procedimientos operativos Descripción: registros asociados con la finalización de los procedimientos operativos. Periodo de conservación: 2 años. Motivo de la conservación: periodo máximo transcurrido en relación a la disputa. Medios de almacenamiento admitidos: electrónicos. Cliente Descripción:Copias de seguridad del cliente. Periodo de conservación: 90 días. Motivo de la conservación: requisito de protección de datos. Medios de almacenamiento admitidos: electrónicos.

Control de cambios y gestión de configuración

Los controles de gestión de cambios se han establecido para cualquier nuevo desarrollo o adquisición de nuevos datos, aplicaciones físicas o virtuales, componentes de sistemas y red de infraestructura, o para cualquier instalación corporativa, operativa o centro de datos que la gerencia empresarial de la organización o cualquier otra función o rol empresarial haya autorizado previamente. Nuestro SDLC dispone de un proceso definido de pruebas y de control de cambios de calidad con referencias establecidas, pruebas y normas de publicación, que se centran en la disponibilidad del sistema y en la confidencialidad e integridad de los sistemas y servicios.

Se han establecido políticas y procedimientos, y se han implementado medidas técnicas y procesos empresariales de apoyo, para limitar la instalación de software no autorizado en componentes de sistemas y red de infraestructura de TI y en dispositivos terminales gestionados por el usuario o propiedad de la organización, dentro del entorno de la nube de producción. Nuestras políticas y procedimientos de gestión de cambios incluyen la gestión de riesgos asociados con la aplicación de cambios en aplicaciones que impactan en el cliente o que son esenciales para la empresa, y en diseños y configuraciones de interfaz sistema a sistema (API). También se han implementado medidas técnicas para garantizar que todos los cambios se corresponden directamente con una solicitud de cambio registrada, ya sea esencial para la empresa o para el cliente, o el cliente las ha autorizado según lo acordado antes de la implementación.

Gestión del ciclo de vida de la información y seguridad de los datos

Caseware tiene implementadas políticas y procedimientos, además de medidas técnicas y procesos empresariales de soporte, para realizar inventarios y mantener los flujos de datos dentro de los sistemas y la red SaaS en cada ubicación geográfica. Los controles implementados garantizan que dichos datos se ubiquen en la zona geográfica determinada por el cliente. Los datos de suscriptores dentro del entorno de la nube de producción residen en arquitectura de dos niveles y no se puede acceder directamente desde internet.

Nuestra política de seguridad define cuatro niveles de clasificación de datos: confidencial, restringido, operativo y público. Todos los datos almacenados dentro de la infraestructura de la nube de producción se consideran confidenciales, que es nuestro máximo nivel de seguridad, y solo personal autorizado puede acceder a este entorno. El acceso lógico al entorno de la nube de producción se limita únicamente al equipo de operaciones.

Todos los datos de los suscriptores se almacenan en el entorno de la nube de producción. El uso de datos de clientes en entornos que no sean el de producción se controla a través de procesos seguros de gestión de datos, que requieren una aprobación explícitamente documentada de los clientes cuyos datos se ven afectados, y deben cumplir con los requisitos legales y reglamentarios para la limpieza de elementos de datos confidenciales. Hay un equipo de operaciones específico responsable de todas las funciones operativas en lo referente a la infraestructura y el almacenamiento, y tiene responsabilidades asignadas que se han definido, documentado y comunicado. Caseware Cloud se aloja en servidores web de Amazon en todo el mundo. Tras realizar la suscripción en los Servicios Caseware Cloud, CWC informa a los clientes acerca de la jurisdicción en la que se encuentra ubicado el servidor que se ha designado para que aloje sus datos de suscriptor y su información personal. Puede dar su consentimiento para dicha asignación o rechazarla. Por motivos de rendimiento, lo habitual será que la configuración se realice en:

  • Estados Unidos/Virginia del Norte, si usted se encuentra en los Estados Unidos o Sudamérica
  • Canadá/Montreal, si se encuentra en Canadá
  • Australia/Nueva Gales del Sur, si se encuentra en la región de Asia-Pacífico
  • Irlanda/Leinster, si se encuentra en cualquier otra región

Seguridad de los centros de datos

La infraestructura de producción se aloja por completo dentro de AWS de Amazon. AWS es responsable de permitir que solo las personas autorizadas accedan a las instalaciones que alojen los sistemas de producción. Asimismo, AWS es responsable de la protección ambiental y mantenimiento preventivo de los sistemas de producción. El acceso físico lo controla AWS en el perímetro y en puntos de ingreso al edificio. Puede encontrar todos los detalles aquí: https://aws.amazon.com/whitepapers/#security. AWS ha publicado más detalles al respecto aquí: https://aws.amazon.com/compliance/data-center/controls/.

Nuestra infraestructura de producción se aloja por completo dentro de AWS de Amazon. AWS tiene informes SOC 2, que se revisan cada año. Los procesos de gobernanza de AWS puede encontrarlos aquí: https://aws.amazon.com/compliance/.

Gestión de claves y cifrado

Nuestras políticas y procedimientos de cifrado se diseñan para dar soporte al proceso empresarial. Se han implementado medidas técnicas con base en los requisitos empresariales para la protección de datos en reposo y datos en tránsito de acuerdo a las obligaciones de cumplimiento legales, reglamentarias y regulatorias aplicables.

Nuestra política de cifrado requiere que todas las claves de cifrado tengan propietarios identificables dentro de la organización. La gestión del ciclo de vida de claves cifradas garantiza que los controles de acceso estén funcionando para la generación, intercambio y almacenamiento seguros de claves, lo que incluye segregación de claves utilizadas para sesiones o datos cifrados.

Los datos almacenados a nivel de servidor (datos en reposo) se cifran mediante el algoritmo AES-256, estándar de la industria. Los datos que se transfieren hacia y desde nuestro servicio (datos en tránsito) se cifran mediante TLS con intercambio de claves efímeras y paquetes de cifrado seguros aceptados por la industria. Los certificados utilizan una seguridad mínima de clave de 2048 bits con SHA-2 o un algoritmo de firma más seguro. Las claves privadas se generan y almacenan en nuestros sistemas de gestión de secretos y, según sea necesario, se implementan y usan en los sistemas de producción a través de nuestro proceso de control de cambios. Los certificados se obtienen a través de un proveedor reconocido y siguen el proceso de renovación/rotación, incorporado y estándar del sector, que se basa en el vencimiento o revocación según sea necesario.

Gestión de riesgos y gobernanza

Las evaluaciones de riesgo relacionadas con la seguridad se completan al menos una vez al año y tienen en cuenta lo siguiente:

  • Conocimiento de dónde se almacenan y transmiten los datos confidenciales en las aplicaciones, bases de datos, servidores e infraestructura de red.
  • Cumplimiento con los periodos de conservación definidos.
  • Clasificación y protección de datos ante el uso y acceso no autorizados, pérdida, eliminación y falsificación.

Hemos implementado un sistema de gestión de seguridad de la información (ISMS) basado en controles de ISO 27001 y SOC 2. Nuestro ISMS incluye las siguientes áreas en la medida en que se relacionan con las características de la empresa:

  • Política de seguridad de la información (este documento)
  • Política de control de acceso
  • Gestión de disponibilidad
  • Política de escritorio limpio (clean desk)
  • Política criptográfica
  • Política de gestión de proveedores de seguridad de la información
  • Política de registros y supervisión
  • Política de dispositivos móviles
  • Política de seguridad de redes
  • Política de gestión de contraseñas
  • Política de gestión de parches
  • Política de software
  • Política de gestión de vulnerabilidad técnica
  • Metodología de gestión de riesgos
  • Política de ISMS, malware y correos electrónicos
  • Política de uso aceptable de internet
  • Política de pruebas de penetración
  • Política de teletrabajo
  • Conservación y protección de registros

Los gerentes de los departamentos son responsables de mantenerse informados y cumplir con las políticas, procedimientos y normas de seguridad que sean relevantes para su área de responsabilidad. Los niveles de aceptación de riesgos se han definido dentro de la metodología de gestión de riesgos, y todos los riesgos se mitigan a un nivel aceptable con plazos razonables para su resolución y con la aprobación de las partes interesadas.

Nuestras políticas y procedimientos de seguridad de la información se publican y estarán disponibles para que todo el personal al que afecten, así como las relaciones empresariales externas, puedan revisarlos. El Comité Directivo de Seguridad de la Información es responsable de desarrollar, conservar y hacer cumplir las políticas de seguridad de la información de nuestro servicio, además de revisarlas y aprobarlas cada año. Los directivos ejecutivos e intermedios proporcionan apoyo para la seguridad de la información a través de un compromiso y dirección claramente documentados; además, se asegurarán de asignar las tareas pertinentes. El responsable de las operaciones y gobernanza de la seguridad de la información, lo que incluye la protección de los datos de los clientes, será un miembro de alto nivel de la dirección, quién deberá mantener informado al director financiero.

Con el fin de garantizar que se sigan cumpliendo la estrategia de seguridad, eficacia, precisión, relevancia y aplicabilidad conforme a las obligaciones de cumplimiento legales, reglamentarias o regulatorias, el Comité Directivo de Seguridad de la Información revisa la política anualmente o cuando se producen cambios en la organización.

Las evaluaciones formales de riesgos se realizan anualmente y cuando se produce cualquier cambio en los sistemas de información para determinar la probabilidad e impacto de todos los riesgos identificados. La probabilidad y el impacto asociados con el riesgo inherente y residual se determina de forma independiente, teniendo en cuenta todas las categorías de riesgo según los resultados de auditoría, el análisis de amenazas y vulnerabilidad, y el cumplimiento reglamentario. Los resultados de la evaluación de riesgos pueden incluir actualizaciones en las políticas, procedimientos, normas y controles de seguridad para garantizar que sigan siendo relevantes y eficaces. Los resultados de las evaluaciones de riesgos:

  • se informan a la alta gerencia, que participa en un proceso de tratamiento de riesgos;
  • se actualizan en un registro de riesgos; y
  • se priorizan según el posible impacto en los sistemas de producción

Nuestro departamento de RR. HH. tiene un proceso de selección definido para todo el personal. En el momento de la contratación, se obtienen verificaciones de referencia con respecto a todos los empleados y se realizan comprobaciones de antecedentes penales y crediticios para aquellos que realizan funciones operativas en el entorno de la nube de productos. Todo el personal debe firmar un acuerdo de confidencialidad antes de la contratación para garantizar la protección de la información del cliente con fines de protección de datos. Durante el periodo de incorporación del empleado, se proporciona formación de concienciación en materia de seguridad de la información, se brinda una formación específica a desarrolladores sobre prácticas de cifrado seguro y se conservan registros formales para la finalización de la formación del personal interno. Por su parte, los gerentes de departamento son los encargados de iniciar rescisiones de contrato de empleados y cambios en los puestos de trabajo, y nuestro equipo de R.R. H.H. revisa estas solicitudes y las envía a través de nuestro sistema de tickets para los requisitos de aprovisionamiento y desaprovisionamiento. Asimismo, el equipo de R.R. H.H. cuenta con un proceso para los empleados que dejan la empresa, cuya finalidad es garantizar que todo el equipo se devuelve y las cuentas se cancelan, y asegurar que se ha retirado el acceso a los entornos de producción.

Se establece un programa de formación de concienciación en materia de seguridad para todos los empleados, contratistas y terceros usuarios, el cual es obligatorio. Todas las personas con acceso a datos confidenciales y restringidos reciben una adecuada formación de concienciación y actualizaciones periódicas sobre los procedimientos, procesos y políticas de la organización en relación a su puesto de trabajo en la organización. Las funciones y responsabilidades de empleados, contratistas y terceros usuarios se documentan en la medida que se relacionan con la seguridad y los activos de información.

Las responsabilidades de todo el personal se definen dentro de las descripciones del puesto de trabajo y se han realizado teniendo en cuenta sus funciones y responsabilidades con respecto a lo siguiente:

  • Tener conocimiento en todo momento y cumplir con las políticas y procedimientos establecidos y las obligaciones de cumplimiento legales, reglamentarias o regulatorias.
  • Mantener un entorno laboral seguro.
  • Informar, si se detecta, de cualquier actividad sospechosa.

Contamos con una política de control clara que requiere que los espacios de trabajo desatendidos no tengan a la vista documentos confidenciales y las sesiones de ordenador se desactiven tras un periodo establecido de inactividad.

Tenemos implementada una política de control de acceso que especifica cómo gestionar el control de acceso a todos los componentes del sistema y a información confidencial en la organización. En la política de privacidad de Caseware (https://www.caseware.com/privacy-statement/) encontrará las políticas que rigen el uso o acceso aceptable a los datos y metadatos de los suscriptores. Caseware recopila, usa y divulga información solo con los siguientes fines:

  • Verificar su identidad.
  • Proporcionarle los servicios de Caseware Cloud.
  • Comunicarse con usted para informarle de productos, actualizaciones del servicio, notificaciones de facturas o notificaciones relacionadas con los servicios de Caseware Cloud.
  • Para controlar o mejorar el uso del sistema, el servidor y el rendimiento del software.
  • Para asistir con cuestiones de soporte técnico.
  • Para cumplir con cualquier ley, reglamento, órdenes judiciales, citaciones o cualquier otro proceso legal de investigación, y para proteger a CWC, sus afiliados y otras personas de cualquier perjuicio.
  • Para mejorar y aumentar la oferta de servicios de CWC.

Gestión de identidad y acceso

Se han establecido políticas y procedimientos para almacenar y gestionar información de identidad sobre cada persona que accede a la infraestructura de la nube de producción, así como para determinar su nivel de acceso. Se han establecido políticas y procedimientos de control de acceso, y se han implementado medidas técnicas y procesos empresariales de apoyo para restringir el acceso de usuarios, de acuerdo a una segregación de tareas definida con el fin de abordar riesgos empresariales asociados a un conflicto de intereses en las funciones de usuarios. El repositorio de control de acceso lo gestiona el proveedor. Usamos un administrador de identidades con privilegios y un sistema de gestión de contraseñas.

El acceso a, y el uso de, herramientas de auditoría que interactúan con el entorno de la nube de producción está segmentado y restringido para evitar poner en riesgo los datos de registro y un uso inadecuado de estos. El acceso de usuario a puertos de diagnóstico y configuración está restringido a personas y aplicaciones autorizados.

Hay controles implementados para garantizar que solo se instale software aprobado dentro de la infraestructura de la nube de producción.

El acceso a las aplicaciones desarrolladas por la propia organización, al programa o al código fuente del objeto, o a cualquier otra forma de propiedad intelectual (PI), así como el uso de software propietario, se controla mediante la regla de privilegios mínimos basada en la función del puesto de trabajo según las políticas y procedimientos establecidos de acceso de usuarios.

Caseware Cloud Service requiere autenticación de contraseña para acceder al sistema base. Una vez dentro del sistema, a los usuarios se les asignan roles de seguridad para realizar las operaciones adicionales y acceder a contenido específico. Con los roles de seguridad, puede controlar quién tiene acceso a ese contenido. Su organización es responsable de desarrollar políticas de seguridad adecuadas en torno a las contraseñas y roles de seguridad que usan funciones de seguridad suministradas en Caseware Cloud. Caseware proporciona acceso a los clientes, quienes tendrán entonces el control de sus propios usuarios y cuentas de administración, incluido el aprovisionamiento y desaprovisionamiento. Se emplea la autenticación en dos fases. El acceso de usuarios se autoriza y valida de nuevo cada trimestre para garantizar la regla de privilegios mínimos basada en la función del puesto de trabajo. Para infracciones de acceso identificadas, se adoptan actividades de corrección basadas en las políticas y procedimientos establecidos para el acceso de usuarios. El desaprovisionamiento oportuno (revocación o modificación) del acceso de usuarios a datos o aplicaciones gestionadas, sistemas de infraestructura y componentes de red, se ha establecido de acuerdo a las políticas y procedimientos establecidos y según los cambios de estado del usuario, tales como finalización del contrato o de otra relación empresarial, cambio de puesto de trabajo o traslado. El proveedor gestiona el aprovisionamiento y desaprovisionamiento de cuenta del servicio. La autenticación de cuenta del servicio utiliza autenticación de varias fases.

Seguridad de virtualización e infraestructura

Caseware Cloud, para todos los hosts de su infraestructura, implementa un punto de conexión de seguridad de detección y respuesta de puntos de conexión basado en Saas. Todo usuario, proceso y actividad de red se recopila y almacena en una ubicación central segura y se analiza prácticamente en tiempo real para detectar comportamientos sospechosos o realizar análisis forenses manuales. La protección, conservación y gestión del ciclo de vida de los registros de auditoría son conformes a las obligaciones de cumplimiento legales, reglamentarias o regulatorias aplicables, y proporcionan responsabilidad del acceso único de usuario para detectar comportamientos de red potencialmente sospechosos y anomalías en la integridad de los archivos, que se requieren para asistir a capacidades de investigación forense en el caso de una infracción de la seguridad. Nuestras herramientas tienen la capacidad detectar y prevenir comportamientos no autorizados o anómalos según el tráfico de red o la actividad de host. Todos los eventos de autenticación, correctos y erróneos, se registran.

Nuestros entornos de producción están separados del resto de entornos para evitar el acceso no autorizado o cambios en los activos de información. La separación de los entornos incluye separación lógica y segregación de tareas para el personal que accede a estos entornos como parte de las tareas de su puesto de trabajo.

Nuestro sistema de producción y entorno de red se protege por firewalls gestionados a nivel central y garantiza la separación de los entornos de producción del resto de entornos. Nuestro entorno de producción se ha diseñado, desarrollado, implementado y configurado para garantizar que el equipo de operaciones y el acceso de usuarios clientes esté adecuadamente segmentado de otros usuarios clientes, según las siguientes consideraciones:

  • Políticas y procedimientos establecidos
  • Aislamiento de activos esenciales empresariales y sesiones y datos confidenciales de usuarios, que obliga a controles internos más seguros y altos niveles de seguridad
  • Seguimiento de las obligaciones de cumplimiento legales, reglamentarias y reguladoras

La infraestructura de la nube de producción tiene un origen de la hora externo, fiable y mutuamente acordado, que se utiliza para sincronizar los relojes del sistema de todos los sistemas de procesamiento de información relevantes para facilitar el seguimiento y la reconstitución de líneas de tiempo de actividades.

Gestión de la cadena de suministro, transparencia y rendición de cuentas

Las políticas y procedimientos se han implementado para garantizar una revisión continuada de los acuerdos de servicios entre los proveedores y los clientes en toda la cadena de suministro que proceda. Las revisiones se realizan como mínimo anualmente e identifican disconformidades con los acuerdos establecidos. Cualquier disconformidad se identifica como medidas para abordar inconsistencias o conflictos a nivel de servicio.

Gestión de amenazas y vulnerabilidad

Se han establecido políticas y procedimientos, y se han implementado medidas técnicas y procesos empresariales de apoyo, para evitar la ejecución de malware dentro del entorno de la nube de producción o en dispositivos de usuarios finales, red de infraestructura de TI y componentes de sistemas. Se han establecido políticas y procedimientos, y se han implementado medidas técnicas y procesos de apoyo, para la detección oportuna de vulnerabilidades dentro de las aplicaciones gestionadas o propiedad de la organización, red de infraestructura y componentes de sistemas. Además, realizamos evaluaciones continuas de vulnerabilidad de código y aplicación en nuestros productos, así como revisiones duales de código del mismo nivel de todos los cambios de código con el fin de garantizar la eficiencia de los controles de seguridad implementados. Nuestra metodología de gestión de riesgos se utiliza para priorizar la corrección de vulnerabilidades identificadas. Los cambios se gestionan a través de nuestro proceso de cambios de gestión definidos para todas las revisiones suministradas por el vendedor, cambios de configuración o cambios en nuestras aplicaciones. Nuestra solución antimalware se gestiona a nivel central y se ejecuta en todos los sistemas. La solución antimalware incluye mecanismos para detectar o prevenir el phishing. Las actualizaciones de firma de malware se implementan en un plazo de 1 día a partir de su lanzamiento.

Lleve a su firma precisión, eficiencia y crecimiento con Caseware.

La autoridad en auditorías impulsadas por la IA.

Contacte con nosotros