Browse Definitions :
Definition

Melbourne shuffle algorithm

Contributor(s): Matthew Haughn, Michael Cobb

The Melbourne shuffle algorithm is a sequence of actions intended to obscure the patterns by which cloud-based data is accessed. The goal is to make it difficult for unauthorized parties to draw conclusions about what type of data is being stored in the cloud by observing patterns that emerge as the data is accessed.

Even when data is encrypted, details about how often the data is accessed or what action is taken after the data has been accessed can be revealing. By analyzing digital footprints, an outsider can predict such things as who is likely to own a particular data set or what business announcement is likely to correlate with a particular access pattern.

As with a deck of cards, a data shuffle rearranges the array to achieve a random permutation of its elements. The Melbourne shuffle moves small amounts of data from the cloud server to the user's local memory, where it is rearranged before being returned to the server. Even when the same user repeatedly accesses the same data, shuffling ensures the access path will not be consistent.

The algorithm, which obfuscates access patterns by making them look quite random, was written by computer scientists at Brown University in 2014. It is named for another kind of shuffle -- a popular dance move in Australia during the 1990s.

This was last updated in August 2017

Continue Reading About Melbourne shuffle algorithm

Join the conversation

3 comments

Send me notifications when other members comment.

Please create a username to comment.

What strategies do you use to keep your data safe in the cloud?
Cancel
This is good and clever enough to actually work. It's a fine start, a fix for a piece of the puzzle, but it only chips away at one tiny bit of a huge (and growing) problem.

We already know our patch-a-day whack-a-mole approach doesn't work very well. How many breaches do we have to suffer before we start dealing with the core problem instead of fixing all the edges...?
Cancel
This is good and clever enough to actually work. It's a fine start, a fix for a piece of the puzzle, but it only chips away at one tiny bit of a huge (and growing) problem.

We already know our patch-a-day whack-a-mole approach doesn't work very well. How many breaches do we have to suffer before we start dealing with the core problem instead of fixing all the edges...?
Cancel

SearchCompliance

  • risk assessment

    Risk assessment is the identification of hazards that could negatively impact an organization's ability to conduct business.

  • PCI DSS (Payment Card Industry Data Security Standard)

    The Payment Card Industry Data Security Standard (PCI DSS) is a widely accepted set of policies and procedures intended to ...

  • risk management

    Risk management is the process of identifying, assessing and controlling threats to an organization's capital and earnings.

SearchSecurity

SearchHealthIT

SearchDisasterRecovery

  • call tree

    A call tree is a layered hierarchical communication model that is used to notify specific individuals of an event and coordinate ...

  • Disaster Recovery as a Service (DRaaS)

    Disaster recovery as a service (DRaaS) is the replication and hosting of physical or virtual servers by a third party to provide ...

  • cloud disaster recovery (cloud DR)

    Cloud disaster recovery (cloud DR) is a combination of strategies and services intended to back up data, applications and other ...

SearchStorage

  • RAM (Random Access Memory)

    RAM (Random Access Memory) is the hardware in a computing device where the operating system (OS), application programs and data ...

  • business impact analysis (BIA)

    Business impact analysis (BIA) is a systematic process to determine and evaluate the potential effects of an interruption to ...

  • M.2 SSD

    An M.2 SSD is a solid-state drive that is used in internally mounted storage expansion cards of a small form factor.

Close