Executable choreography: Difference between revisions

Revision as of 12:20, 16 July 2018

Revision as of 12:29, 16 July 2018

Line 17:

=== Encrypted choreographies ===

Encrypted cryptography supposes that, in addition to verification, they offer higher-level solutions for advanced cryptographic methods without the need for programmers to become cryptography specialists. Distributed applications could be built from subsystems that allow identification or verification of architectural points that expose secret data. For example, ideally, a programming system that uses encrypted choreographs guarantees, or at least helps, minimize situations where a person (legally licensed or hacker) holds both encrypted private data and encryption keys related to the same resources . In this way, the administrators or programmers of these subsystems have fewer possibilities to perform internal attacks on privacy (the level with frequent attacks). Even if some applications can not use this approach, encrypted choreographies can minimize the security risks caused by the people inside who administer or program these systems. Thus, the number of points with discreet access to data (ideally never) is formally ensured. This form of choreography is useful to allow companies to secure by code the application of the legislation or security rules assumed.

The implementation of encrypted choreographies implies, for example, the existence of storage systems using cryptographic techniques with practical implementation of homomorphic encryption, such as the CryptDB [CRYPTDB2011] [CRYPTDB2013] implementation from MIT. In Chapter 4, we will describe a method proposed by us and published in the article "Private Data System enabling self-sovereign storage managed by executable choregraphies" [CHORE2017], a method we can also call a "storage, division and anonymization method" with the help of encrypted choreographies, can lead us to the ideal of having total "sovereignty" (within the limits of the law) on private data. In this paper we show how choreographies anonymize and divide data in a way that ensures that data can not be copied by a single administrator or hacker that controls only one of the participating nodes. The implemented mechanisms can also include interfaces that are easy to use by programmers for advanced cryptographic methods. Our privateSky research work on encrypted choreographies is still in its infancy, but we can recall the article "Operations on encrypted data in an ORM made for encrypted choreographies" [HMMF2017].