<!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>Software Application Security Test Strategy with Lean Canvas Design</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Padmaraj Nidagundi</string-name>
          <email>padmaraj.nidagundi@gmail.com</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Marina Uhanova</string-name>
          <email>marina.uhanova@rtu.lv</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Riga Technical University, Faculty of Computer science and Information technology</institution>
          ,
          <addr-line>Riga</addr-line>
          ,
          <country country="LV">Latvia.</country>
        </aff>
      </contrib-group>
      <fpage>50</fpage>
      <lpage>53</lpage>
      <abstract>
        <p>- Software security play key role to keep software application user's personal information safe from the hackers who breach defenses of the software and exploit weaknesses in it. In software development, most of the time companies give less priority for security while developing the software because of lack of skilled professional or less budget and time constraints. The software security testing main goal is to identify the all possible loopholes and weakness in the system before it starts using by the end customers. It is important to consider the security testing in each phase of the systems development life cycle (SDLC) and it needs to cover the confidentiality, integrity, authentication, availability, authorization and non-repudiation of the system. The making software error free with security issues, software test engineer need to have an effective strategy to mitigate security risks. This paper emphasizes on the possibilities of lean canvas design for the security test strategy building in the software testing process.</p>
      </abstract>
      <kwd-group>
        <kwd>security testing</kwd>
        <kwd>security test strategy</kwd>
        <kwd>lean canvas for security testing</kwd>
        <kwd>software testing</kwd>
        <kwd>test strategy</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>INTRODUCTION</p>
      <p>
        The growth of technology increases the Internet of things
(IoT), cloud, web software products complexity and increased
the possible threats to attackers from different endpoints with
the system. Every year small to reputed companies also faces
many type software security issues and these incidents directly
impacted on the business, brand reputation and customer trust
on the software products. In recent years’ companies are started
spending more time, resources and money to make security
testing as the number one Information technology (IT) priority
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. In the software security testing, different types of security
test need to be done before application reach to the intended end
user, such as vulnerability scanning, security scanning,
penetration testing, risk assessment, security auditing, ethical
hacking, posture assessment.
      </p>
      <p>
        Software security testing considered as a non-functional
testing, in this process software tester test the application and
make sure it is secured or not with different possible attacks [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
In this process, tester determines the data protection, leakage of
sensitive data with developed software for intended hardware.
Every year Open web application security project (OWASP)
doing possible research in the wide range and releasing the
possible risks with the software products. In last few years’ lean
      </p>
    </sec>
    <sec id="sec-2">
      <title>Copyright held by the author(s).</title>
      <p>
        canvas design is used for the building the strategy for the
number of different companies, this research article focus on
the developing the prototype and its possible utilization for the
software security testing [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>II.</p>
    </sec>
    <sec id="sec-3">
      <title>THE PROBLEM STATEMENT In software security testing quality assurance [10], [13] team faces many challenges. 50</title>
      <p>●</p>
      <p>Lack in developing security testing strategy in each
phase of SDLC.</p>
      <p>Not start security testing at the early stage of software
development.</p>
      <p>Not having the well-trained security tester in a team.
Not having appropriate security test tools for custom
developed software.</p>
      <p>Lack in building the security test planning and test
data.</p>
      <p>III.</p>
      <p>ANALYSIS OF SOFTWARE SECURITY TESTING IN SDLC</p>
      <p>AND LEAN CANVAS DESIGN</p>
      <p>
        In recent research by Harvard business school’s, 75% of all
start-ups fail survey done by the Shikhar Ghosh and noticeable
most of the start-ups are focused on the software as their
product. But rest 25% start-up companies are successful
because of the adaptation of the lean principles [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. In recent
years, lean canvas design is adopted by the companies to build
the strategy with the product, services, describe, design,
challenge, and pivot the business model. It is a one-page
lightweight document with blocks and appropriate title.
      </p>
      <p>
        Lean canvas is a tool to validate the ideas with more
creativity, experimentation [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Considering the lean canvas as
a base model our research for software security testing will help
us to address the many security test strategy and planning.
●
●
●
●
      </p>
      <p>Identify and design the more appropriate lean canvas
design prototype for security testing.</p>
      <p>Simplify the software security test strategy with SDLC.
Undertaking the lean principles for the design of the
software security testing compatible lean canvas.</p>
      <p>Identify and design software security testing metrics
and blocks on the lean board.</p>
      <p>A. Waterfall VS Agile approach</p>
      <p>The first time Alex Osterwalder and his co-author
introduced business model canvas in the year 2000. Onward it
started used by the number of startups to big companies to
manage the strategy. The business model canvas shows the
possible predefined blocks; those help to define the problem
and possible solution using the different channel blocks showed
on the one-page document. It helps make a clearer strategy for
the business problem. Lean canvas life cycle starts with the
ideas, build, product, measure, data, learn and each of the gives
valuable feedback continuously to next stage.</p>
      <p>
        In recent years, agile based software development is growing
with a number of projects it created new opportunity and
challenges for the software based product and it impacted on
the software security testing as well. Agile development focus
on the adaptive planning, early delivery, and constant
improvement [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]. In again development. Agile development
needs to start with risk analysis and it brings the new
requirements.
      </p>
      <p>It focuses on the more request product release.</p>
    </sec>
    <sec id="sec-4">
      <title>A number of dynamic features changes. Increasing business level risk when product backlogs changes.</title>
    </sec>
    <sec id="sec-5">
      <title>Technical risk with each new sprint.</title>
      <p>Validations risk with every code check in and
product release.</p>
      <p>In such situation, effective security test strategy will
help to tackle the situation and there is no slandered
strategy approach has been investigated that fit in agile
to overcome security testing issues.</p>
      <p>C. Approaching lean canvas design for security testing
strategy.</p>
      <p>
        Description: Software security testing is essential in each
stage of software development, in such situation test strategy
play key role to improve the software security in each stage [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ],
[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. According to OWASP 2017 there are a number of possible
threats injection, broken authentication and session
management, Cross-site Scripting (XSS), broken access
control, security misconfiguration, sensitive data exposure,
insufficient attack protection, cross-site request forgery
(CSRF), using components with known vulnerabilities and
under protected application programming interface (API).
      </p>
      <p>
        Prerequisites: What type of security test need to be done with
application and knowledge about security test tools to be used
with the application [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. According to the pentest-standard need
to consider in the test execution pre-engagement interactions,
intelligence gathering, threat modeling, vulnerability analysis,
exploitation, post exploitation and reporting.
      </p>
      <p>Complexity: Each application is unique and each code or user
story can bring new challenges to test engineer with technology
and technical point of view.</p>
      <p>Pro: Lean canvas will help to set a proper strategy with each
user story or developed code.</p>
      <p>Con: It will bring the limitation with in-depth analysis report
visualizing on the single page, to overcome we need to use
external hyperlinks from the board.</p>
      <p>Recommendation: With changing the scope of the software
application lean canvas design need to redesigned with a new
title for the existing blocks with descriptions.</p>
      <p>
        Example: Consider a web application testing with the
reconnaissance, configuration management, authentication
testing, session management, authorization testing, data input
validation, denial-of-service (optional) and web / API services
testing need to be done [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. In such situation, we can visualize
the all possible test strategy one single page.
      </p>
      <p>D. Discover of the security test metrics for lean canvas board</p>
      <p>Considering the lean principles, we will identify the more
proper roadmap for the design of the lean canvas.</p>
      <p>●
●
●</p>
      <p>Transport – Security test needs to wait until full
code or software module is ready.</p>
      <p>Inventory – Not fully developed code or module
according to business re-equipment not able
consider for the testing.</p>
      <p>Motion – Once part of code or module is already
tested then we can consider it re-testing only with
the full system.</p>
      <p>Waiting – Some time security test is interrelated to
each other in such situation it need to pre-planned
for the scope.</p>
      <p>Overproduction – It does not bring any value some
time testing component or code that not fulfill the
business requirement.</p>
      <p>Over processing – Poor system architecture or
selection of wrong security test tools will consume
more time.</p>
      <p>Defects – Identified security weakness of the
system or code, need to be fixed and such issues
need to be retested.</p>
      <p>Considering the lean principle for the lean canvas design we
extract several blocks &amp; test metrics and these we can use to
visualize the board. It is continuing process of finding the
correct metrics with the scope of the project.</p>
      <p>E. Approaching lean canvas prototype design for software
security testing</p>
      <p>
        Considering section 2 and 3 various input and possibilities
we draw a prototype lean canvas board with several sections
and related text fields on the single page [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>LEAN CANVAS DESIGN ADAPTION INVESTIGATION IN</p>
      <p>THE SECURITY TEST</p>
      <p>The study explains the new possibilities for usage of the
visualized lean canvas in the software security testing purpose
this single page template can impact on the security testing plan
and security test strategy and simplify the software test process.
Also, help to build the secured software product to the end
customers.</p>
      <p>To extend the prototype lean canvas design for the software
security testing, it is necessary to carry out the following
research activities to gather more information.</p>
      <p>●
●
●
●
●
●
●</p>
      <p>Need to carry out a detailed experiment in the software
security testing process for identifying the lean
metrics.</p>
      <p>Need to carry out a detailed experiment to how lean
canvas design best fit for security testing.</p>
      <p>Identified &amp; collected list existing security standards
and evaluate for the lean canvas design.</p>
      <p>Investigate possibilities more appropriate design for
the security testing using lean canvas visualization.
Need to develop algorithms to developing and
optimize the lean metrics.</p>
      <p>Need to develop an intelligent software that gathers
information from input and design a more appropriate
lean canvas design.</p>
      <p>Investigation needed about machine learning
possibilities to lean canvas design generation.</p>
      <p>The author wish is to increase the adoption on lean
canvas design in test process to improve the software
security testing strategy to simplify the complex process
and long documentation. Improving software testing
strategy process is continues ongoing research. The author
wishes this paper will generate more ideas, new aspect on
prototypes design and experiment on creating software test
strategy using lean canvas design.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>T.</given-names>
            <surname>Nakajima H. Ishikawa E. Tokunaga F. Stajano</surname>
          </string-name>
          , “
          <article-title>Technology challenges for building Internet-scale ubiquitous computing”.</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Yang</surname>
            <given-names>S</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liao</surname>
            <given-names>C</given-names>
          </string-name>
          , “
          <article-title>A study of critical success factors on software quality assurance of cloud networking devices”</article-title>
          ,
          <source>3rd International Conference on Systems and Informatics (ICSAI)</source>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Omotunde</surname>
            <given-names>H</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ibrahim</surname>
            <given-names>R</given-names>
          </string-name>
          , “
          <article-title>A Hybrid Threat Model for Software Security Requirement Specification”</article-title>
          ,
          <source>International Conference on Information Science and Security (ICISS)</source>
          ,
          <year>2016</year>
          pp
          <fpage>1</fpage>
          -
          <lpage>4</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <string-name>
            <surname>Wotawa</surname>
            <given-names>F</given-names>
          </string-name>
          , “
          <article-title>On the Automation of Security Testing”</article-title>
          ,
          <source>International Conference on Information Science and Security (ICISS)</source>
          ,
          <year>2016</year>
          pp
          <fpage>11</fpage>
          -
          <lpage>16</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Jain</surname>
            <given-names>M</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gopalani</surname>
            <given-names>D</given-names>
          </string-name>
          , “
          <article-title>Testing application security with aspects”</article-title>
          ,
          <source>International Conference on Electrical, Electronics, and Optimization Techniques (ICEEOT)</source>
          <year>2016</year>
          , pp
          <fpage>3161</fpage>
          -
          <lpage>3165</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Jiménez</surname>
            <given-names>R</given-names>
          </string-name>
          , “
          <article-title>Pentesting on web applications using ethical - hacking”</article-title>
          ,
          <source>IEEE 36th Central American and Panama Convention (CONCAPAN XXXVI)</source>
          ,
          <year>2016</year>
          , pp
          <fpage>1</fpage>
          -
          <lpage>6</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Vibhandik</surname>
            <given-names>R</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bose</surname>
            <given-names>A</given-names>
          </string-name>
          , “
          <article-title>Vulnerability assessment of web applications - a testing approach”</article-title>
          , Forth International Conference on e-Technologies and
          <article-title>Networks for Development (ICeND) 2015</article-title>
          , pp
          <fpage>1</fpage>
          -
          <lpage>6</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Steven</surname>
            <given-names>J</given-names>
          </string-name>
          , “
          <article-title>Threat Modeling - Perhaps It's Time”</article-title>
          ,
          <source>IEEE Security &amp; Privacy</source>
          ,
          <year>2010</year>
          , Volume
          <volume>8</volume>
          , Issue 3, pp
          <fpage>83</fpage>
          -
          <lpage>86</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>]</surname>
            <given-names>X.</given-names>
          </string-name>
          <string-name>
            <surname>Wang</surname>
          </string-name>
          , “
          <source>The Combination of Agile and Lean in Software Development: An Experience Report Analysis”, Agile Conference (AGILE)</source>
          ,
          <year>2011</year>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>9</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>D. G.</given-names>
            <surname>Rex</surname>
          </string-name>
          <string-name>
            <surname>Black</surname>
          </string-name>
          , Erik Van Veenendaal,
          <article-title>Foundations of software testing: ISTQB certification, 3rd Edition</article-title>
          . Cengage
          <string-name>
            <surname>Learning</surname>
            <given-names>EMEA</given-names>
          </string-name>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <surname>Nidagundi</surname>
            <given-names>P</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Novickis</surname>
            <given-names>L</given-names>
          </string-name>
          , “
          <article-title>New method for mobile application testing using lean canvas to improving the test strategy”</article-title>
          ,
          <source>Computer Sciences and Information Technologies (CSIT)</source>
          <year>2017</year>
          , pp
          <fpage>171</fpage>
          -
          <lpage>174</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>M.</given-names>
            <surname>Ide</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Amagai</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Aoyama</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Kikushima</surname>
          </string-name>
          , “
          <article-title>A Lean Design Methodology for Business Models</article-title>
          and Its Application to IoT Business Model Development,” in Agile Conference, AGILE,
          <year>2015</year>
          , pp.
          <fpage>107</fpage>
          -
          <lpage>111</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          <source>[13] World Quality Report 2016-2017</source>
          , Capgemini, Sogeti, and
          <string-name>
            <surname>HP</surname>
          </string-name>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>