<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Behavior Veri cation for Business Processes based on Testing and Anomaly Detection</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Kristof Bohmer</string-name>
          <email>kristof.boehmer@univie.ac.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Vienna, Faculty of Computer Science</institution>
        </aff>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Business processes are applied in a wide range of areas, implementing various
mission critical functionalities. For example, today's processes enable the
collaboration of multiple organizations, integrate multiple resources, and handle data
from various sources. The latter frequently includes private, sensitive and
condential information (e.g., private user data or medical records). To provide all
these functionalities and to meet numerous requirements business processes must
be deeply integrated into organizations and related IT systems, cf. [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ]. Thus, it
is vital to ensure that today's process are as fault and security incident free as
possible to prevent potential negative e ects on process driven organizations.
      </p>
      <p>
        Current research has already picked up challenges regarding the detection
and handling of faults (e.g., based on testing, cf. [
        <xref ref-type="bibr" rid="ref10 ref2">10, 2</xref>
        ]) and security incidents
(e.g., based on anomaly detection, cf. [
        <xref ref-type="bibr" rid="ref13 ref7">13, 7</xref>
        ]). Nevertheless, the current state
of research was found to be limited regarding the analysis of dynamic business
process runtime behavior. As only runtime behavior represents the real {
potentially faulty or insecure { behavior that occurs during the execution of prede ned
process behavior (e.g., given by process models, cf. [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]) we see this as a major
limitation. Moreover, additional limitations in existing work were identi ed:
      </p>
      <p>
        First of all, a common understanding, an overview, and requirements for
testing approaches { to identify faults in business processes { are currently missing,
cf. [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Further, it was found that existing process testing approaches frequently
require a signi cant amount of expert knowledge and skills in various areas, such
as, lesser-used formal test de nition languages, which we assume as being hardly
available at process modeling experts. Finally, various process execution
scenarios, such as parallel executions are insu ciently supported - rendering a major
area in the process domain uncovered.
      </p>
      <p>
        When analyzing the state of research in the business process runtime security
domain (i.e., anomaly detection during business process executions) a di erent
picture emerges, cf. [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Existing anomaly detection approaches were found to be
severely limited in regard to their robustness and anomaly detection capabilities.
For example, anomalies can occur in multiple forms and complexities, cf. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ],
but only the most basic ones are currently supported [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Further, existing work
only focuses on single individual process instances, where the detection of hidden
malicious actions requires to aggregate multiple behavior sources (perspectives,
resp.). Moreover, processes handle information from various data sources and
formats. Hence, anomaly detection approaches are required that can
automatically analyze various data formats for anomalies, to reduce manual e orts.
      </p>
      <p>Finally, we want to point out that business processes have a life cycle that
describes their design, execution, monitoring, and optimization. So far the de
nition of behavior (i.e., process modeling and optimization) and the occurrence
of behavior (i.e., process execution and monitoring) have been considered
separately. However, both areas are closely connected and must be taken into
consideration at once to foster fault free and secure processes.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Contribution</title>
      <p>
        This thesis concerns on the fault free de nition of process behavior and the
secure anomaly free execution of such behavior, cf. Fig 1, and tackles both areas
with multiple publications: [
        <xref ref-type="bibr" rid="ref1 ref2 ref3 ref4 ref5 ref6 ref7 ref8 ref9">2, 6, 1, 3, 9, 7, 4, 8, 5</xref>
        ] Speci cally, process testing
approaches are de ned and analyzed to investigate their applicability, for example,
to prevent faults, in the process modeling and optimization phase. Through this
the quality of process models is assumed to be increased so that faults are less
likely to hamper an organization's performance or to a ect the bound of trust
between organizations, partners, and customers. For the other two phases, i.e.,
the execution and monitoring phase, anomaly detection approaches are proposed
and applied to prevent security incidents and data breaches. Hereby, anomalous
process execution behavior can be identi ed, detected, and its impact is analyzed
to identify abnormal behavior that potentially indicates outside attacks or inside
threats. A condensed overview on the contribution is given in the following:
Fig. 1. Classic Business Process Life Cycle and its relation to the Behavior Life Cycle.
{ Two systematic literature reviews on business process testing and anomaly
detection have been conducted [
        <xref ref-type="bibr" rid="ref2 ref7">2, 7</xref>
        ]. Both provide a detailed investigation
along with an analysis of the given support for upcoming challenges, such
as, concurrent process behavior { to provide research directions.
{ Two approaches are presented to generate, prioritize, and select business
process test cases based on historic behavior and machine learning concepts
[
        <xref ref-type="bibr" rid="ref1 ref3 ref6">6, 1, 3</xref>
        ]. Hereby, the rst approach focuses on the veri cation of complex
interleaving concurrent process model executions and test case prioritization.
The latter approach investigates the application of genetic algorithms to
select business process test cases. Test case selection and prioritization are a
necessity because today's process test suites are frequently auto-generated
and through this signi cantly larger than manually created ones. So
executing all test cases would result in escalating test execution times. Hence,
reaching a su cient test execution performance requires to identify, select,
and prioritize test cases based on their relevance for given requirements, such
as, a chosen minimum process activity coverage.
{ A novel testing approach evaluates the applicability of process mining based
veri cation and conformance checking techniques to identify faults [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Hereby,
it can be exploited that the chosen mining approaches are already deeply
rooted in the process domain and include support for a range of
characteristics that are unique for that domain. A related experimental evaluation is
conducted based on realistic processes from the energy domain.
{ A generic unsupervised anomaly detection approach for arbitrary textual
data is proposed [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. The presented approach enables to generate signatures
based on historic data exchanges. Furthermore we provide a detailed
evaluation with hundreds of thousands of realistic anomalous and non-anomalous
data instances to analyze its feasibility and applicability.
{ A multi perspective anomaly detection prototype that is capable of detecting
point, contextual, and collective anomalies in process executions is presented
[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. It is capable of calculating the likelihood of process execution behavior to
di erentiate between benign and unlikely anomalous behavior. In addition
techniques are proposed to exibly deal with unexpected and unknown
behavior to reduce the number of incorrectly identi ed anomalies when dealing
with evolving, volatile, and changing processes.
{ Process models are executed in complex execution scenarios where multiple
processes and process instances are executed concurrently and overlap each
other. These dynamics are hard to analyze and could, therefore, be utilized
by { inside { attackers to hide their malicious intentions. Hence, a
multiinstance anomaly detection approach is presented [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. It transforms recorded
historic executions of all processes utilized in an organization into signatures
to detect temporal anomalies in concurrently executed large scale process
execution scenarios (i.e., it is capable of securing and monitoring all process
executions in an organization at once). Its feasibility is shown based on a
prototypical implementation and multiple real world data sources.
      </p>
    </sec>
    <sec id="sec-3">
      <title>Methodology</title>
      <p>
        This thesis follows the so called design science methodology. For this it applies a
design science information system research framework that was proposed in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ].
The following list describes how each of the design science research guidelines,
as outlined in [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], were taken into account by the thesis:
GL1: Design as an artifact This thesis creates several artifacts that foster
the fault-freeness and security of business processes { which is relevant for
process driven organizations. For this all the testing and anomaly detection
approaches proposed in this work were also prototypically implemented.
GL2: Problem relevance The conducted systematic literature reviews
enabled to identify key challenges, gaps, and limitations in the process testing
and anomaly detection domain and showed that both research areas are
relevant and broadly accepted. This motivated the research questions addressed
within this thesis and shows their relevance. Moreover it was found that
security is a key concern in the process domain, cf. [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]. This is not surprising,
as security incidents can result in a substantial damage to an organization.
GL3: Design evaluation This thesis rigorously evaluates each created
artifact. For example, the algorithms, approaches, and concepts presented in
this thesis were all prototypically implemented and evaluated based on real
life and/or realistic synthetic data. Hereby, the applicability, performance,
and functionality of the proposed approaches were shown. In addition
identi ed limitations and future work were pointed out and discussed.
GL4: Research contributions This thesis contributes by creating artifacts
that tackle open challenges in the testing and security domain (e.g.,
algorithms that enable to identify various anomaly types). Moreover
methodologies are presented. These are, for example, metrics that enable to measure
the fault detection likelihood of test cases or a fault risk for process activities.
GL5: Research rigor This thesis applied rigorous methods and techniques to
construct and evaluate the designed artifacts. For this the presented research
is evaluated and compared with competing techniques whenever possible.
For example, the presented test case selection approach is compared with
multiple alternatives. In addition fundamental design decisions are discussed
and motivated and formal concepts are applied whenever appropriate.
GL6: Design as a search process This motivated the applied research
process. For example, the systematic literature reviews enabled to identify and
organize existing knowledge and shortcomings. In addition the iterative
nature of the search process, cf. [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ], is re ected by our research process. For
example, the presented security focused research tackles multiple successive
and interrelated research areas { which will, as future work, be joined to a
coherent security framework. The intermediate results identi ed throughout
the conducted research and search process have in uenced our approaches
and are re ected by our research and the constructed artifacts.
      </p>
      <p>
        GL7: Communication of research The research has been presented on
conferences, in proceedings, and journals addressing the BPM, Service, and
Database research community: [
        <xref ref-type="bibr" rid="ref1 ref2 ref3 ref4 ref5 ref6 ref7 ref8 ref9">2, 6, 1, 3, 9, 7, 4, 8, 5</xref>
        ]
      </p>
    </sec>
    <sec id="sec-4">
      <title>Conclusion</title>
      <p>This thesis is focusing on two aspects, i.e., the secure and fault free de nition and
execution of business processes. Through this the thesis can provide a holistic
approach that combines process testing and anomaly detection to ensure not
only fault free but also secure process model executions. As the world and our
lifes tend to become more and more a ected by and oriented towards processes
we assume this to be a necessity for organizations, but also for today's society.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. Bohmer,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Rinderle-Ma</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.:</surname>
          </string-name>
          <article-title>A genetic algorithm for automatic business process test case selection</article-title>
          .
          <source>In: On the Move: CoopIS</source>
          . pp.
          <volume>166</volume>
          {
          <fpage>184</fpage>
          . Springer (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. Bohmer,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Rinderle-Ma</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.:</surname>
          </string-name>
          <article-title>A systematic literature review on process model testing: Approaches, challenges</article-title>
          , and research directions.
          <source>CoRR abs/0902</source>
          .0885 (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. Bohmer,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Rinderle-Ma</surname>
          </string-name>
          , S.:
          <article-title>Automatic business process test case selection: Coverage metrics, algorithms, and performance optimizations</article-title>
          .
          <source>Cooperative Information</source>
          Systems pp.
          <volume>174</volume>
          {
          <issue>190</issue>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. Bohmer,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Rinderle-Ma</surname>
          </string-name>
          , S.:
          <article-title>Automatic signature generation for anomaly detection in business process instance data</article-title>
          .
          <source>In: Enterprise, Business-Process and Information Systems Modeling</source>
          , pp.
          <volume>184</volume>
          {
          <fpage>199</fpage>
          . Springer (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. Bohmer,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Rinderle-Ma</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.:</surname>
          </string-name>
          <article-title>Multi-perspective anomaly detection in business process execution events</article-title>
          .
          <source>In: On the Move: CoopIS</source>
          . pp.
          <volume>80</volume>
          {
          <fpage>98</fpage>
          . Springer (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6. Bohmer,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Rinderle-Ma</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.:</surname>
          </string-name>
          <article-title>A testing approach for hidden concurrencies based on process execution logs</article-title>
          .
          <source>In: Service-Oriented Computing</source>
          . Springer (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7. Bohmer,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Rinderle-Ma</surname>
          </string-name>
          , S.:
          <article-title>Anomaly detection in business process runtime behavior - challenges and limitations</article-title>
          .
          <source>CoRR abs/1705</source>
          .06659 (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. Bohmer,
          <string-name>
            <given-names>K.</given-names>
            ,
            <surname>Rinderle-Ma</surname>
          </string-name>
          ,
          <string-name>
            <surname>S.:</surname>
          </string-name>
          <article-title>Multi instance anomaly detection in business process executions</article-title>
          .
          <source>In: Business Process Management</source>
          . pp.
          <volume>80</volume>
          {
          <fpage>98</fpage>
          . Springer (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. Bohmer,
          <string-name>
            <surname>K.</surname>
          </string-name>
          , et al.:
          <article-title>Application and testing of business processes in the energy domain</article-title>
          .
          <source>Datenbanksysteme fur Business</source>
          ,
          <source>Technologie und Web</source>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Bures</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cerny</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Klima</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Prioritized process test: More e ciency in testing of business processes and work ows</article-title>
          .
          <source>In: International Conference on Information Science and Applications</source>
          . pp.
          <volume>585</volume>
          {
          <fpage>593</fpage>
          . Springer (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Chandola</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Banerjee</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kumar</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Anomaly detection: A survey</article-title>
          .
          <source>ACM Computing Surveys</source>
          <volume>41</volume>
          (
          <issue>3</issue>
          ),
          <volume>15</volume>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Halfond</surname>
            ,
            <given-names>W.G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Orso</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Combining static analysis and runtime monitoring to counter sql-injection attacks</article-title>
          .
          <source>In: ACM SIGSOFT software engineering notes</source>
          . vol.
          <volume>30</volume>
          , pp.
          <volume>1</volume>
          {
          <issue>7</issue>
          .
          <string-name>
            <surname>ACM</surname>
          </string-name>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Hsu</surname>
          </string-name>
          , P.Y.,
          <string-name>
            <surname>Chuang</surname>
            ,
            <given-names>Y.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lo</surname>
            ,
            <given-names>Y.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>He</surname>
            ,
            <given-names>S.C.</given-names>
          </string-name>
          :
          <article-title>Using contextualized activity-level duration to discover irregular process instances in business operations</article-title>
          .
          <source>Information Sciences</source>
          <volume>391</volume>
          ,
          <volume>80</volume>
          {
          <fpage>98</fpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Leitner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rinderle-Ma</surname>
            ,
            <given-names>S.:</given-names>
          </string-name>
          <article-title>A systematic review on security in process-aware information systems{constitution, challenges, and future directions</article-title>
          .
          <source>Information and Software Technology</source>
          <volume>56</volume>
          ,
          <issue>273</issue>
          {
          <fpage>293</fpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Niedermann</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          , Radeschutz,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Mitschang</surname>
          </string-name>
          ,
          <string-name>
            <surname>B.</surname>
          </string-name>
          :
          <article-title>Deep business optimization: A platform for automated process optimization</article-title>
          .
          <source>ISSS/BPSC</source>
          <year>2010</year>
          ,
          <volume>168</volume>
          {
          <fpage>180</fpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Von</surname>
            <given-names>Alan</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>R.H.</given-names>
            ,
            <surname>March</surname>
          </string-name>
          , S.T.,
          <string-name>
            <surname>Park</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ram</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Design science in information systems research</article-title>
          .
          <source>MIS quarterly 28(1)</source>
          ,
          <volume>75</volume>
          {
          <fpage>105</fpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>