Decentralized enforcement of document lifecycle constraints

Abstract

Artifact-centric workflows describe possible executions of a business process through constraints expressed from the point of view of the documents exchanged between principals. A sequence of manipulations is deemed valid as long as every document in the workflow follows its prescribed lifecycle at all steps of the process. So far, establishing that a given workflow complies with artifact lifecycles has mostly been done through static verification, or by assuming a centralized access to all artifacts where these constraints can be monitored and enforced. We present in this paper an alternate method of enforcing document lifecycles that requires neither static verification nor single-point access. Rather, the document itself is designed to carry fragments of its history, protected from tampering using hashing and public-key encryption. Any principal involved in the process can verify at any time that the history of a document complies with a given lifecycle. Moreover, the proposed system also enforces access permissions: not all actions are visible to all principals, and one can only modify and verify what one is allowed to observe. These concepts have been implemented in a software library called Artichoke, and empirically tested for performance and scalability.

Asynchronous Wait-Free Runtime Verification and Enforcement of Linearizability

“…As far as we know, so far there have been proposed only a few distributed runtime enforcement algorithms (e.g. [9,46,48,53,81]).…”

Decent: A Benchmark for Decentralized Enforcement

“…We note that fewer methods have been actually implemented for centralized enforcement, see TiPEX [18] or GREP [21] for instance. Although there are a few approaches [14,15] considering decentralized enforcement in decentralized systems, these are tailored to specific systems and our work is the first generic approach able to enforce any property expressed in linear-temporal logic.…”

On the Runtime Enforcement of Timed Properties

“…Regarding applications for usage control, runtime enforcement was applied to enforce usage control policies in [73], enforcement of the usage of the Android library in [41], disabling Android advertisements in [36]. Regarding applications in the domain of security, runtime enforcement was applied to enforce the opacity of secrets in [46,55,109], access control policies in [76][77][78], confidentiality in [28,53], information-flow policies [28,49,64,64], security and authorization policies in [22,38], privacy policies in [28,56,65], control-flow integrity in [2,34,52,57,62], and memory safety in [24,25,35,100].…”