Shared Responsibility

For terms not defined herein, please refer to our Terms of Service.

 

Customer’s responsibility

Let’s look at how you are responsible for protecting your data in the cloud and the security of your devices.

 

Data accountability

You are responsible for:

  • The data you share and receive over the cloud. You decide whom you share it with, the period, and the means of sharing.
  • Ensuring the privacy of data you handle using Assyst’s Services, to ensure that you do not accidentally or willingly make any private content publicly available.
  • Maintaining the accuracy of the data that you process in your system.
  • Ensuring that your Assyst service account is not used by you or others on your behalf for spamming or illegal activities, that Assyst’s Services are only used for their intended purposes.

 

Passwords

You are responsible for creating a strong password and safeguarding it when you use it to log in and access the cloud.

 

Client and end-point security
  • The compromise of one of your endpoints (whether your laptop, desktop, or smart phone) will render all other controls ineffective.
  • You are responsible for your end-point security and are expected to keep your browser services, mobile OS, and mobile applications updated to the latest version and protected against vulnerabilities.

 

Shared responsibility

Responsibility of control that will apply to both you and Assyst.

Identity and access management

For our cloud-based services we provide infrastructure for managing user accounts through:

  • User registration, de-registration options, and specifications on how to use them.
  • Functionality for managing access rights of your cloud users.
  • Strong authentication techniques such as multi-factor authentication.

 

You are responsible for:

  • Implementing strong user access management controls.
  • Configuring strong passwords based on the organization’s policy and protecting them.
  • Enabling Multi-Factor Authentication for your organization’s users.
  • Administering user accounts and privileges—configuring user roles according to the principle of least privilege.
  • Defining the administrator(s) of the organization’s account and having a proper process for ownership transfers. Taking necessary steps to ensure that your organization does not lose control of its administrator accounts.
  • Periodically reviewing the list of users with access to data and removing access for anyone who should not have it.
  • Frequently reviewing devices linked to the organization’s user accounts and removing unused or unauthorized devices.
  • Monitoring your organization’s user accounts for malicious access or usage.
  • Notifying Assyst of any unauthorized use of your organization’s accounts.
  • Educating your users on the importance of good password management, the risks on credential reuse, social logins, and phishing attacks.

 

Data Management

For our cloud based services, we provide a platform for you to manage your data with:

  • Data sharing features for administrator and user-level controls.
  • Data interoperability—the option to take a complete backup of data and configurations to migrate all or a part of your data to another SaaS provider.
  • Data retention and disposal—we hold the data in your account as long as you choose to use Assyst Services. Once you terminate your Assyst user account, your data will be deleted from the active database during the next cleanup that occurs, once every six to twelve months. The data deleted from the active database will be deleted from backups after three months.
  • Access limitations features to limit staff members from accessing customer data and ensure that they can only do so if there is a specific reason.

 

You are accountable for:

  • Due diligence while processing information belonging to special categories (for example, personal/sensitive data) by applying appropriate controls to comply with the requirements of applicable legislation.
  • Configuring proper sharing and viewing permissions.
  • Regularly reviewing audit reports to identify any suspicious activity.
  • Maintaining up-to-date contact information with Assyst.
  • Taking your data out of the system once you stop using our services. Otherwise, it will be subject to permanent deletion without any scope for recovery.

 

Managing data to other parties

We work towards having secure integrations and extensions to our applications by:

  • Marketplace Applications: Performing functional testing, security testing, and privacy testing once an application is submitted to us. We also perform product review and content review.
  • Sub-processors: Evaluating the security and privacy practices of sub-processors whom we wish to contract to ensure that they are in line with Assyst’s information security and privacy standards. We then execute appropriate data protection agreements with them.

 

We expect you to:

  • Enable or disable third-party integrations after taking into consideration the data that gets shared to third-party environments. You must review the terms and the privacy policy of the third-party service regarding the collection, use, or disclosure of data.
  • Mark your preference on whether you would like to share your details with vendors every time an extension is installed.
  • Assess the suitability of the Marketplace Apps and the reasonableness of the requested permissions prior to installation.
  • Notify Assyst of any malicious behaviour identified in the Marketplace Apps.

 

Data subject rights

We are accountable for:

  • Providing features that enable customers to cater to and protect the rights of your customers.
  • Notifying you of requests from your customers when they contact us directly for exercising their rights.

 

You are obliged to:

  • Honour and handle requests from customers for data access, rectification, deletion, and restrictions in processing of their personal information.

 

Encryption

For our cloud based services, we safeguard your data using encryption at transit and at rest in the following ways:

  • Data in transit: Customer data transmitted to our servers over public networks is protected using strong encryption protocols. We mandate all connections to our servers use Transport Layer Security (TLS 1.2/1.3) encryption with strong ciphers for all connections including web access, API access, our mobile apps, and IMAP/POP/SMTP access.
  • Data at rest: Personally identifiable information in the customer data is encrypted at rest using Advanced Encryption Standard (AES) 256-bit algorithm.

 

We suggest you to:

  • When the data from our cloud is downloaded or exported into your environment or synced within integrations in Assyst or with any other third-party integration, you need to ensure that relevant encryption controls are applied. For example, enable disk encryption on your devices and use the export feature with password protection enabled, etc.

 

Backups

For our cloud based services, we are equipped with a robust system to:

  • Maintain system-level backups encrypted with AES-256 bit algorithm and stored securely. Automatically run integrity and validation checks of the full backups.
  • Enable requests for data restoration and provide secure access to it within the retention period.
Incident management

From our side, we ensure to:

  • Report all incidents of breach that we are aware of and that applies to you along with impact details and suitable actions. For incidents specific to an individual user or an organization, we will notify the concerned party through the email(s) registered with us.
  • Track such incidents and close them.
  • Implement controls to prevent recurrence of similar incidents.
  • If requested, we will provide additional evidence related to the incident that applies to you.

 

We expect you to:

  • Take actions suggested by Assyst in case of a breach.
  • Meet your data breach disclosure and notification requirements, such as notifying your end users and data protection authorities when relevant.
  • Report security and privacy incidents that you are aware of to [email protected].

 

Awareness and training

We take complete responsibility for:

  • Training our staff members ( the term “staff” collectively referred to herein is to both employees and independent contractors) to be security-conscious and to adhere to a secure development standard. Newly hired staff members take part in mandatory security and privacy training in addition to receiving regular security awareness training via informational emails, presentations, and resources available on our intranet.
  • Training our staff members on appropriate handling of cloud service customer data.

 

You are responsible for training cloud users on:

  • Standards and procedures for the use of our services.
  • How the risks related to our services are managed.
  • Risks on the general system and the network environment.
  • Applicable legal and regulatory considerations.

 

Policy and compliance

We adhere to a set of guidelines, such as:

  • We have a comprehensive risk management program in place and effectively implement the controls.
  • We operate within the law of various jurisdictions where we operate from.
  • We provide evidence of compliance with applicable legislations and based on our contractual requirements.
  • We will assist in DPIA assessments of our customers to the extent allowed by the applicable laws.

 

We expect you to:

  • Evaluate regulations and laws that are applicable to you and to review our compliance with regulations and standards that are needed for your business. You can request for additional information to serve as evidence of our compliance.
  • Understand our policies, our policy assessment methods, and how we process data.
  • Conduct DPIA as required by the data protection laws applicable to your organisation before / while processing data
  • Before you process any personal/sensitive data, assess your lawful basis. In case your lawful basis is consent, ensure you obtain the consent from your customers.
  • Assess the suitability of our cloud-based services based on the information we provide and ensure it is sufficient to meet your compliance needs.
  • Understand the risk profile and sensitivity of the data hosted in the Assyst services and apply appropriate controls.

 

 

Assyst’s responsibility

We are responsible for the protection of the cloud and related controls that run all Assyst services.

Data security
  • We are responsible for the isolation of your data stored with us. Each customer’s service data is logically separated from other customers’ data using a set of secure protocols in the framework.
  • We are responsible for the confidentiality of your data stored with us at rest, in transmission, and during processing.
  • We are responsible for the integrity of both your data and system data such as logs and configuration data.
  • We are responsible for traceability and control of your data, such that at any given time, the physical location and processing of data can be known.

 

Availability
  • We are responsible for ensuring that our services are available, however we do not offer an uptime SLA.
  • As a customer, you can contact us  at any time to know the current site status, as well as past disruptions.

 

Business continuity
  • We are responsible for having a business continuity plan in place for our major operations such as support and infrastructure management.
  • We keep the application data on industry leading cloud providers such as the Google Cloud Platform.

 

Network controls

We are responsible for operating a secure production network. We use firewalls to prevent our network from unauthorized access and undesirable traffic. Access to production networks is strictly controlled.

 

Host infrastructure and Physical security

Our applications are hosted by reputable cloud providers such as AWS, Google Cloud Platform and Microsoft Azure and we rely on their physical security protocol and infrastructure.

 

Conclusion

The shared responsibility model for cloud security provides clarity on security expectations for cloud users and cloud service providers. However, an understanding of the expectation is just the first step. Users must take action on these responsibilities by creating policies and procedures for their portion of cloud security. Assyst will continue to work hard to keep your data secure.

For any further queries on this topic, feel free to contact us at [email protected].