You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<description>Incident Response Plan Introduction The purpose of the document is to establish the goals and the vision for the incident management process in the MYRTLE GROUP S.A. (“we” or “Cloudback”). This document discusses the steps taken during an incident response plan.
244
+
<description>Incident Response Plan Introduction The purpose of the document is to establish the goals and the vision for the incident management process in the MYRTLELABS S.A.S. (“we” or “Cloudback”). This document discusses the steps taken during an incident response plan.
245
245
Incident Response Process The person who discovers the incident should contact Cloudback by one of the following ways: Send an email to the [email protected] Raise a request in the Cloudback issue tracker Use any contacts from Contact Us web page If the person discovering the incident is a member of the Cloudback team, they will proceed to step four (4).</description>
246
246
</item>
247
247
@@ -349,7 +349,7 @@ Getting Started HTTP headers for S3 Object Tagging x-amz-tagging: The tag-set fo
349
349
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<description>Disaster Recovery Plan Policy Overview The purpose of the policy is to establish the goals and the vision for the disaster recovery process in the MYRTLE GROUP S.A. (&ldquo;we&rdquo; or &ldquo;Cloudback&rdquo;). It is important to understand that having a contingency plan in the event of a disaster gives Cloudback a competitive advantage. This policy requires management to financially support and diligently attend to disaster contingency planning efforts. Disasters are not limited to adverse weather conditions.</description>
352
+
<description>Disaster Recovery Plan Policy Overview The purpose of the policy is to establish the goals and the vision for the disaster recovery process in the MYRTLELABS S.A.S. (&ldquo;we&rdquo; or &ldquo;Cloudback&rdquo;). It is important to understand that having a contingency plan in the event of a disaster gives Cloudback a competitive advantage. This policy requires management to financially support and diligently attend to disaster contingency planning efforts. Disasters are not limited to adverse weather conditions.</description>
353
353
</item>
354
354
355
355
<item>
@@ -358,7 +358,7 @@ Getting Started HTTP headers for S3 Object Tagging x-amz-tagging: The tag-set fo
358
358
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<description>Data Breach Response Policy Purpose The purpose of the policy is to establish the goals and the vision for the breach response process in the MYRTLE GROUP S.A. (&ldquo;we&rdquo; or &ldquo;Cloudback&rdquo;). This policy will clearly define to whom it applies and under what circumstances, and it will include the definition of a breach, staff roles and responsibilities, standards and metrics (e.g., to enable prioritization of the incidents), as well as reporting, remediation, and feedback mechanisms.</description>
361
+
<description>Data Breach Response Policy Purpose The purpose of the policy is to establish the goals and the vision for the breach response process in the MYRTLELABS S.A.S. (&ldquo;we&rdquo; or &ldquo;Cloudback&rdquo;). This policy will clearly define to whom it applies and under what circumstances, and it will include the definition of a breach, staff roles and responsibilities, standards and metrics (e.g., to enable prioritization of the incidents), as well as reporting, remediation, and feedback mechanisms.</description>
362
362
</item>
363
363
364
364
<item>
@@ -367,7 +367,7 @@ Getting Started HTTP headers for S3 Object Tagging x-amz-tagging: The tag-set fo
367
367
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
<description>Vulnerability Management Workflow Introduction The purpose of the document is to describe the established vulnerability management workflow in the MYRTLE GROUP S.A. (“we” or “Cloudback”).
370
+
<description>Vulnerability Management Workflow Introduction The purpose of the document is to describe the established vulnerability management workflow in the MYRTLELABS S.A.S. (“we” or “Cloudback”).
371
371
Overview Vulnerability Management is the recurring process of identifying, classifying, prioritizing, mitigating, and remediating vulnerabilities. This document will focus on infrastructure vulnerabilities and the vulnerability management process. This process is designed to provide informationregarding Cloudback vulnerability workflow, promote healthy patch management among other preventative best-practices, and remediate risk; all with the end goal to better secure our environments.</description>
<p>We, the MYRTLE GROUP S.A., have built the Cloudback application as a Commercial service. This service is provided by us and is intended for use as is. We fully comply with the European General Data Protection Regulation (GDPR) laws, requirements and regulations.</p>
3501
+
<p>We, the MYRTLELABS S.A.S. (previosly
3502
+
<ahref="https://docs.cloudback.it/posts/myrtlelabs/">MYRTLE GROUP S.A.</a>), have built the Cloudback application as a Commercial service. This service is provided by us and is intended for use as is. We fully comply with the European General Data Protection Regulation (GDPR) laws, requirements and regulations.</p>
3502
3503
<p>This Policy is used to inform visitors and users regarding our policies about the collection, use, and disclosure of Personal Information of anyone using the Service.</p>
3503
3504
<p>By using the Service, you agree to the collection and use of information mentioned in this policy. The Personal Information that we collect is used for providing and improving the Service. We respect the privacy of our users and will not use or share the information with anyone except as described in this Privacy Policy. The terms used in this Privacy Policy have the same meanings as in our Terms of Service, which can be accessed
3504
3505
<ahref="https://docs.cloudback.it/terms/">here</a> unless otherwise defined in this Privacy Policy.</p>
@@ -3559,12 +3560,12 @@ <h2 id="for-data-subjects-in-the-eu">For Data Subjects in the EU</h2>
3559
3560
<p>Prighter.com <br/>
3560
3561
Maetzler Rechtsanwalts GmbH & Co KG <br/>
3561
3562
Attorneys at Law <br/>
3562
-
c/o MYRTLE GROUP S.A. <br/>
3563
+
c/o MYRTLELABS S.A.S. <br/>
3563
3564
Schellinggasse 3/10, 1010 Vienna, Austria <br/></p>
3564
3565
<p>Please add the following subject to all correspondence:
3565
3566
GDPR-REP ID: 15719145</p>
3566
3567
<p><strong>Information according to Art 27 EU GDPR</strong></p>
3567
-
<p>MYRTLE GROUP S.A. is a company located outside of the European Union. In order to comply with Art 27 EU GDPR, Prighter.com has been nominated as our representative in the European Union. If you want to
3568
+
<p>MYRTLELABS S.A.S. is a company located outside of the European Union. In order to comply with Art 27 EU GDPR, Prighter.com has been nominated as our representative in the European Union. If you want to
3568
3569
make use of your data privacy rights, please visit
@@ -3573,9 +3574,9 @@ <h2 id="controller-name-and-address">Controller Name and Address</h2>
3573
3574
<p>Controller for the purposes of the General Data Protection Regulation (GDPR), other data protection laws applicable in Member states of the European Union and other provisions related to data protection is:</p>
<p>The purpose of the policy is to establish the goals and the vision for the breach response process in the MYRTLE GROUP S.A. (“we” or “Cloudback”). This policy will clearly define to whom it applies and under what circumstances, and it will include the definition of a breach, staff roles and responsibilities, standards and metrics (e.g., to enable prioritization of the incidents), as well as reporting, remediation, and feedback mechanisms. The policy shall be well publicized and made easily available to all personnel whose duties involve data privacy and security protection.</p>
3500
+
<p>The purpose of the policy is to establish the goals and the vision for the breach response process in the MYRTLELABS S.A.S. (“we” or “Cloudback”). This policy will clearly define to whom it applies and under what circumstances, and it will include the definition of a breach, staff roles and responsibilities, standards and metrics (e.g., to enable prioritization of the incidents), as well as reporting, remediation, and feedback mechanisms. The policy shall be well publicized and made easily available to all personnel whose duties involve data privacy and security protection.</p>
3501
3501
<p>Cloudback Information Security’s intentions for publishing a Data Breach Response Policy are to focus significant attention on data security and data security breaches and how Cloudback’s established culture of openness, trust and integrity should respond to such activity. Cloudback Information Security is committed to protecting Cloudback’s employees, partners and the company from illegal or damaging actions by individuals, either knowingly or unknowingly.</p>
3502
3502
<h2id="background">Background</h2>
3503
3503
<p>This policy mandates that any individual who suspects that a theft, breach or exposure of Cloudback Protected data or Cloudback Sensitive data has occurred must immediately provide a description of what occurred via email to
<articleclass="markdown-body"><h1id="disaster-recovery-plan-policy">Disaster Recovery Plan Policy</h1>
3499
3499
<h2id="overview">Overview</h2>
3500
-
<p>The purpose of the policy is to establish the goals and the vision for the disaster recovery process in the MYRTLE GROUP S.A. (“we” or “Cloudback”). It is important to understand that having a contingency plan in the event of a disaster gives Cloudback a competitive advantage. This policy requires management to financially support and diligently attend to disaster contingency planning efforts. Disasters are not limited to adverse weather conditions. Any event that could likely cause an extended delay of service is considered.</p>
3500
+
<p>The purpose of the policy is to establish the goals and the vision for the disaster recovery process in the MYRTLELABS S.A.S. (“we” or “Cloudback”). It is important to understand that having a contingency plan in the event of a disaster gives Cloudback a competitive advantage. This policy requires management to financially support and diligently attend to disaster contingency planning efforts. Disasters are not limited to adverse weather conditions. Any event that could likely cause an extended delay of service is considered.</p>
3501
3501
<h2id="purpose">Purpose</h2>
3502
3502
<p>This policy defines the requirement for a baseline disaster recovery plan to be developed and implemented by Cloudback that will describe the process to recover IT Systems, Applications and Data from any type of disaster that causes a major outage.</p>
0 commit comments