<!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>Strategic Planning for Secure Digital Transformation: A Socio-Technical Approach</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Martin Koch[</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kent Illemann</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniel Riddarvinge</string-name>
        </contrib>
      </contrib-group>
      <fpage>34</fpage>
      <lpage>41</lpage>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        “[Strategic Planning] is not a box of tricks, a bundle of techniques. It
is analytical thinking and commitment of resources to action. Many
techniques may be used in the process – but, then again, none may
be needed.”
        <xref ref-type="bibr" rid="ref4">(Drucker, 1973,1974)</xref>
        1
      </p>
      <p>The Socio-Technical Digital Transformation Design</p>
      <p>
        Approach for Security
The socio-technical approach is adding a broad perspective to security including not
only technical solutions and external risks, but also taking the social factors of security
into consideration
        <xref ref-type="bibr" rid="ref9">(Kowalski, 1994)</xref>
        . Peoples ability to understand and accept the
additional complexity driven by security is increasingly vital to the enterprise:
“The capacity of people to deal with technical and organizational complexity and find
meaning and satisfaction working in these systems lags the capacity of organizations
to create digitally enabled work systems that technically should work—if only humans
can be trained to understand, embrace, and be able to operate effectively and thrive
within them”
        <xref ref-type="bibr" rid="ref12">(Scheiber, 2017)</xref>
        Digital transformation of business is driving the appearance of new threats to the
enterprise. Security can no longer be perceived as protecting assets from the outside, since
tight interdependence across multiple complex entities blurs the border between what
is inside and what should be kept outside:
“The tight technical interdependence across complex organizations means that errors
in one location may cause service disruptions, delays, and even shut-downs in others”
        <xref ref-type="bibr" rid="ref8">(Kerstetter, 2017)</xref>
        The digital socio-technical design approach
        <xref ref-type="bibr" rid="ref15">(Winby &amp; Albers Mohrman, 2018)</xref>
        is
suggesting adding strategic planning tools to the socio-technical design model in order to
create a strategy driven approach. From a security perspective, this would imply an
approach with the combination of a well-known socio-technical security model
combined with a commonly used tool for strategic planning.
2
      </p>
      <p>
        Selecting the model and tools
There are many alternative tools and models that could be used for a digital
socio-technical security approach. It is outside of scope of this paper to find the optimal
combination but as guidance the following adapted the S.M.A.R.T. checklist for Goals
        <xref ref-type="bibr" rid="ref3">(Doran, 1981)</xref>
        summarizes the “design criteria” used:
      </p>
    </sec>
    <sec id="sec-2">
      <title>Area (S)pecific (M)easurable (A)chiavable</title>
    </sec>
    <sec id="sec-3">
      <title>Design Criteria</title>
      <p>Well known. Selecting model and tool with
accepted use and terminology.</p>
      <p>Results should be easily qualifiable and
comparable.</p>
      <p>Ease of use. Understandable across a wide set of
audience with disparate background, not drawing
unnecessary attention from the subject.
Area
(R)ealistic
(T)imely</p>
    </sec>
    <sec id="sec-4">
      <title>Design Criteria</title>
      <p>The models should not claim to prescribe or
control but aim for strategic guidance, influence and
support understanding.</p>
      <p>
        To quote Sheryl Sandberg “Done is better than
perfect”. Quick turn-around time to a useful result.
The Capability Maturity Model (CMM) was first described by Humphrey
        <xref ref-type="bibr" rid="ref6">(Humphrey,
et al., 1987)</xref>
        using five different maturity levels. The work is generally perceived as
originating from Nolan’s stage theory
        <xref ref-type="bibr" rid="ref10">(Nolan, 1973)</xref>
        . The model has recently gained
popularity with usage in several international standards (ISO/IEC, u.d.) and adaptions
by commercial actors like ISACA
        <xref ref-type="bibr" rid="ref7">(ISACA, 2012)</xref>
        , its subsidiary CMMI Institute
        <xref ref-type="bibr" rid="ref2">(CMMI Institute, 2019)</xref>
        among others. A Google search on the term “Capability
Maturity Model” results in more than 26MM hits.
        <xref ref-type="bibr" rid="ref2">(April 2019)</xref>
        Maturity models can be both descriptive and prescriptive
        <xref ref-type="bibr" rid="ref1">(Berghaus &amp; Back, 2016)</xref>
        . In
Cobit 5
        <xref ref-type="bibr" rid="ref7">(ISACA, 2012)</xref>
        the model used both to describe the current status of the
enterprise and later to set a desired target level (and track changes). Note that the highest
level is not always the desired one due to high cost compared with reduced risk.
Example of maturity levels for process maturity with an additional level “0” for
nonexisting
        <xref ref-type="bibr" rid="ref7">(ISACA, 2012)</xref>
        :
      </p>
    </sec>
    <sec id="sec-5">
      <title>Maturity Level</title>
    </sec>
    <sec id="sec-6">
      <title>Name</title>
    </sec>
    <sec id="sec-7">
      <title>Non-existent</title>
      <p>Ad-hoc
Repeatable
Defined Process
Managed and Measurable</p>
      <p>Optimized
To conclude, the CMM is one of the most widely used models to measure and prescribe
maturity in general and particularly in IT and IT-related processes.
SWOT Analysis and TOWS Strategies as a Tool for Strategic</p>
      <p>
        Planning
The SWOT Analysis is ”[…] a useful tool for reviewing a firm’s competitive position.”
        <xref ref-type="bibr" rid="ref11">(Sammut-Bonnici &amp; Galea, 2014)</xref>
        and consist of a simple 4-box matrix to assess the
enterprise internal (S)trength, (W)eakness and external (O)pportunities, (T)hreats. The
model has no official creator but is generally known to be first used by the SRI
International in the 1960-70
        <xref ref-type="bibr" rid="ref5">(Humphrey, 2005)</xref>
        . A Google search on “SWOT Analysis”
gives over 48MM hits
        <xref ref-type="bibr" rid="ref2">(April 2019)</xref>
        .
The TOWS matrix
        <xref ref-type="bibr" rid="ref14">(Weihrich, 1982)</xref>
        creates a suggested path from the SWOT analysis
to a generic set of four main business strategies:
Focusing on the weakness of the organization and the treats. This
is an avoidance strategy. Use as a core strategy for a business it
typically results in merger or liquidation since being in business
is taking risk.
      </p>
      <p>Focusing on the opportunities in the market by quickly acquiring
capabilities either by acquisition or internal build up.</p>
      <p>Focusing on using the company strength to reduce an external
threat. This could be by using an internal R&amp;D knowledge to
prepare for a shift in the market, replacing a current product.</p>
      <p>
        Focus on maximizing existing strength to (continue) to harvest a
market opportunity. Sometimes referred to as a “Fat Cat”
strategy.
The SWOT and accompanying TOWS model continues to be very popular and
practitioners favor it since it is easy to explain and use to a wide set of audience when taking
a collaborative approach to strategy
        <xref ref-type="bibr" rid="ref13">(Seebohm, 2014)</xref>
        .
      </p>
      <p>
        Our proposed Combined Approach
A Socio-Technical Capability Model
We propose a CMM that use dimensions that covers both social and technological
aspects of security. As an example, we have created dimensions based on various best
practice including SBC
        <xref ref-type="bibr" rid="ref9">(Kowalski, 1994)</xref>
        . The below table shows these dimensions and
some sample questions for illustration:
      </p>
    </sec>
    <sec id="sec-8">
      <title>Dimension</title>
    </sec>
    <sec id="sec-9">
      <title>Cultural</title>
    </sec>
    <sec id="sec-10">
      <title>Legal</title>
    </sec>
    <sec id="sec-11">
      <title>Compliance</title>
    </sec>
    <sec id="sec-12">
      <title>Operations Technology</title>
      <p>•
•
•
•
•
•
•
•
•
•
•
•
•
•
•</p>
    </sec>
    <sec id="sec-13">
      <title>Sample Questions</title>
      <p>Does the company understand the culture in the country?
Does the company promote the company culture?
Is there a company “Code of conduct” and how is it promoted?
Does the company see regulation as a business driver or a
business inhibitor?
Does the company see the regulations as risks or opportunities?
Does the company make money on laws and regulations?
Is there a policy for information security?
Is there a policy for Architecture?
Is there a policy for Code of Conduct?
Is the operational management based on ITIL or other
frameworks?
Is operational management part of company strategy?
Are there routines for recovery?
Are there automated controls over computers and software used?
Is there automated backup and restore of our information?</p>
      <p>Are there technical installations to protect our data?
• Internal state of the socio-technical security posture
• Competitors (perceived) position
The SWOT model implicitly assumes that one is stronger or weaker compared to a
baseline. The analysis can be done without explicitly describing this the baseline, but
with the risk for tacit bias. By explicitly stating the baseline the purpose of the SWOT
is more clearly described. Example of baselines that could be used would be external
cyber threat capabilities or customers/users’ general expectations on security
capability.</p>
      <p>Based on the result of the CMM assessment, the SWOT can be populated.</p>
    </sec>
    <sec id="sec-14">
      <title>Area</title>
      <p>(S)trength
(W)eakness
(O)pportunity
(T)hreat</p>
      <p>Relationship
When the internal socio-technical security posture is stronger than
the competitors.</p>
      <p>When the internal socio-technical security posture is weaker than the
competitors.</p>
      <p>When the baseline is lower than the internal socio-technical security
posture.</p>
      <p>When the baseline is higher than the internal socio-technical security
posture.
The SWOT is then converted to generic TOWS strategies for security. Note that
depending on the choice of baseline and CMM dimensions the specific strategy will look
different.</p>
    </sec>
    <sec id="sec-15">
      <title>Strategy</title>
    </sec>
    <sec id="sec-16">
      <title>WT Strategy (mini-mini)</title>
    </sec>
    <sec id="sec-17">
      <title>WO Strategy (mini-maxi)</title>
    </sec>
    <sec id="sec-18">
      <title>ST Strategy (maxi-mini)</title>
    </sec>
    <sec id="sec-19">
      <title>SO Strategy</title>
      <p>(maxi-maxi)</p>
      <p>Comment
Security strategy focusing decisions on minimize weakness and
threats. (This is probably the most common security strategy)
Security strategy minimizing weakness and focusing on security
related opportunities.</p>
      <p>Security strategy leveraging existing strength and focus on external
threats.</p>
      <p>Security strategy leveraging existing strength and focus on external
security related opportunities.</p>
      <p>CMMI
at:</p>
      <p>Institute
home page. [Online]
https://cmmiinstitute.com/
8. ISO/IEC, n.d. ISO/IEC 15504,21827, s.l.: s.n.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Berghaus</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Back</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <year>2016</year>
          .
          <article-title>Stages in Digital Business Transformation: Results of an Empirical Maturity Study</article-title>
          . s.l.,
          <source>MCIS</source>
          , p.
          <fpage>3</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>CMMI</given-names>
            <surname>Institute</surname>
          </string-name>
          ,
          <source>Available [Accessed 2 April</source>
          <year>2019</year>
          ].
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Doran</surname>
          </string-name>
          , G. T.,
          <year>1981</year>
          .
          <article-title>There's a S.M.A</article-title>
          .R.T.
          <article-title>Way to Write Management's Goals and Objectives</article-title>
          .
          <source>Management Review</source>
          ,
          <volume>70</volume>
          (
          <issue>11</issue>
          (AMA Forum)), pp.
          <fpage>35</fpage>
          -
          <lpage>36</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Drucker</surname>
            ,
            <given-names>P. F.</given-names>
          </string-name>
          ,
          <year>1973</year>
          ,
          <year>1974</year>
          . Management: Tasks, Responsibilities, Practices. New York(NU):
          <article-title>HarperCollins Publisers</article-title>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Humphrey</surname>
            ,
            <given-names>A. S.</given-names>
          </string-name>
          ,
          <year>2005</year>
          .
          <article-title>SWOT Analysis for Management Consulting</article-title>
          . SRI Alumni Association Newsletter, December, pp.
          <fpage>7</fpage>
          -
          <lpage>8</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Humphrey</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          et al.,
          <year>1987</year>
          .
          <article-title>A method for assessing the software engineering capability of contractors, s</article-title>
          .l.: Carnegie Mellon University.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7. ISACA,
          <year>2012</year>
          .
          <article-title>A Business Framework for the Governance and Management of Enterprise IT</article-title>
          . In: ROLLING MEADOWS: ISA, pp.
          <fpage>41</fpage>
          -
          <lpage>45</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          9.
          <string-name>
            <surname>Kerstetter</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <year>2017</year>
          . New York Times. [Online] Available at: https://mobile.nytimes.com/
          <year>2017</year>
          /03/13/technology/tech
          <article-title>- roundup-amazon-error-is-a-reminder-that-no-company-is-infallible</article-title>
          .
          <source>html [Accessed 3 April</source>
          <year>2019</year>
          ].
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          10.
          <string-name>
            <surname>Kowalski</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <year>1994</year>
          . IT Insecurity:
          <article-title>A Multi-disiplinary Inquiry</article-title>
          , Stockholm: s.n.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          11.
          <string-name>
            <surname>Nolan</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <year>1973</year>
          .
          <article-title>Managing the computer resource: A stage hypothesis</article-title>
          ..
          <source>Communication of the ACM</source>
          ,
          <volume>16</volume>
          (
          <issue>7</issue>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          12.
          <string-name>
            <surname>Sammut-Bonnici</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Galea</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <year>2014</year>
          .
          <article-title>SWOT analysis</article-title>
          . In: Wiley Encyclopedia of Management. s.l.:John Wiley &amp; Sons, Ltd..
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          13.
          <string-name>
            <surname>Scheiber</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <year>2017</year>
          .
          <article-title>How Uber usus psychological tricks to push drivers' buttons</article-title>
          . [Online] Available at: https://www.nytimes.com/interactive/2017/04/02/technology/uber-driverspsychological-tricks.
          <source>html [Accessed 3 April</source>
          <year>2019</year>
          ].
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          14.
          <string-name>
            <surname>Seebohm</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <year>2014</year>
          .
          <article-title>Collaborative Tools for Strategic Line Planning</article-title>
          . s.l., Concurrent Strategies.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          15.
          <string-name>
            <surname>Weihrich</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <year>1982</year>
          .
          <article-title>The TOWS Matrix a Tool for Situational Analysis</article-title>
          .
          <source>Long Rage Planning</source>
          ,
          <volume>15</volume>
          (
          <issue>2</issue>
          ), pp.
          <fpage>54</fpage>
          -
          <lpage>66</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          16.
          <string-name>
            <surname>Winby</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Albers Mohrman</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <year>2018</year>
          .
          <article-title>Digital Sociotechnical Systems Design</article-title>
          .
          <source>The Journal of Applied Behavioural Science</source>
          , Volume
          <volume>54</volume>
          (
          <issue>4</issue>
          ), pp.
          <fpage>399</fpage>
          -
          <lpage>423</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>