Browse the latest events all over the world!

Virtual events help the community stay connected 24/7. Click to see upcoming events.

Understanding the Atlassian Shared Responsibility Model: A 3-Part Series

Jul 31, 11:00 PM – Aug 1, 12:00 AM

Understanding the Atlassian Shared Responsibility Model: A 3-Part Series on your Data Backup and Compliance Responsibilities with Revyz

8
RSVPs

CloudCommunityLive LearningMarketplace AppsMigrations

About this event

This series will explore the Atlassian Shared Responsibility Model and why backing up your data is your responsibility within this model. By understanding these aspects of the Atlassian Shared Responsibility Model, you can make informed decisions about data protection and choose a backup provider that meets your specific needs.


The Shared Responsibility Model

     - Key Points:

          > We'll define the Atlassian Shared Responsibility Model and how it divides security and compliance between Atlassian and the customer.

          > We'll discuss compliance requirements and how they apply in the context of the model. The Atlassian Shared Responsibility Model clarifies which security responsibilities fall under Atlassian and which fall under the customer. However, compliance with various regulations is a shared effort.

     - Understanding the Shared Model and Compliance:

           > The Atlassian Shared Responsibility Model clarifies which security responsibilities fall under Atlassian and which fall under the customer. However, achieving compliance with various regulations often requires a shared effort.


Your Data and Backups with Revyz

     - Key Points:

          > We'll delve into data storage location and residency.

               - Where is your data legally obligated to reside?

          > We'll explore backup ownership, control, storage capacity, and restore options.

               - Who has access and how is it managed?

          > We'll discuss storage capacity.

               - How much space is allocated for backups?

           > We'll compare restoration options: Point-in-time, single space, entire page, etc.

                - We'll also explore why backups are superior to scripting for data recovery.

          > We'll introduce Recovery Time Objective (RTO) and Recovery Point Objective (RPO) for defining your backup strategy.

               - These metrics define how quickly data needs to be recovered and how much data loss is acceptable after an incident. Understanding these will help you determine your backup frequency and restore options.

Speakers

  • Stu Lees

    Revyz

    Head of Marketing and Partnership

  • Vish Reddy

    Revyz

    CEO

Moderators

  • Stu Lees

    Revyz

    Head of Marketing and Partnership

  • Vish Reddy

    Revyz

    CEO

Community Leaders

  • Larry Brock

    Praecipio

    Sr. Technical Architect

  • Ben Garcia

    FlightAware

    Technical Project Manager

  • Anthony D'ambrosio

    Mumo Systems

    Community Leader

Contact host

Global sponsor

Atlassian logo

Atlassian

Sponsor

REVYZ logo

REVYZ

Where Atlassian users meet and share best practices

RSVP