<!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>Usable Security Versus Secure Usability: an Assessment of Attributes Interaction</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Oleksandr Gordieiev</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vyacheslav Kharchenko</string-name>
          <email>V.Kharchenko@csn.khai.edu</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kate Vereshchak</string-name>
          <email>vereshchak@gmail.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Banking University</institution>
          ,
          <addr-line>1 Andriivska Street, Kyiv</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Luxoft</institution>
          ,
          <addr-line>10/14 Radisheva Street, Kyiv</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>National Aerospace University «KhAI»</institution>
          ,
          <addr-line>17 Chkalova Street, Kharkiv</addr-line>
          ,
          <country country="UA">Ukraine</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Attributes of information systems quality described in standard ISO/IEC25010 (2010) are analyzed. Some of them are contradictory, dependent and competing. One of the most competing characteristics are usability and security (U&amp;S). The article considers two main aspects of U&amp;S interaction called “usable security” and “secure usability”. The technique of qualitative assessment of the U&amp;S interaction based on analysis of subcharacteristics and metrics is suggested. An example of the technique application to assess U&amp;S interaction for university web-site is discussed.</p>
      </abstract>
      <kwd-group>
        <kwd />
        <kwd>Usability and security interaction</kwd>
        <kwd>usable security</kwd>
        <kwd>secure usability ISO/IEC25010</kwd>
        <kwd>ISO/IEC25023</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1.1</p>
    </sec>
    <sec id="sec-2">
      <title>Introduction</title>
      <sec id="sec-2-1">
        <title>Motivation</title>
        <p>
          Information systems are characterized by a set of characteristics/attributes that are
defined by international standards. The standard ISO/IEC 25010 «System and
software quality model» [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] defines the following 10 characteristics of information
systems: functional suitability, performance efficiency, compatibility, usability,
reliability, security, maintainability, portability. Such nomenclature was formed in
result their evolution during about 60 years [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. Certain characteristics
(subcharacteristics) of information systems interact at each other. I.e. there are
situations when strengthening (weakening) of one of the characteristics requires or
generates strengthening (weakening) of another or even a group of information
systems. In the article we will consider a couple of the most important, mutually
influence and competitive characteristics – usability and security (U&amp;S).
1.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>State of Art</title>
        <p>
          First of all, we need give of description for U&amp;S attributes. Usability – degree to
which a product or system can be used by specified users to achieve specified goals
with effectiveness, efficiency and satisfaction in a specified context of use [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ].
Security - degree to which a product or system protects information and data so that
persons or other products or systems have the degree of data access appropriate to
their types and levels of authorization [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. Information systems must have of Usability
and Security characteristics, because they must be comfortable in use and secure
simultaneously. Depending on field of information systems application, levels of
U&amp;S requirements and characteristic values are not the same. In most cases,
information systems are more usable, including at the expense of security, or more
secure at the expense their usability.
        </p>
        <p>Problems of U&amp;S characteristics interaction are well known, researched and
presented in materials of conferences, in articles and books. Analysis of works in this
field gave us possibility make some conclusions and divide of accessible works on
following groups in some fields:</p>
        <p>
           most part of works are about concrete problems in U&amp;S field and mechanisms
for their solutions [
          <xref ref-type="bibr" rid="ref3 ref4 ref5 ref6 ref7">3, 4, 5, 6, 7</xref>
          ]. In particular, in [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ] are viewed alphanumeric
passwords problems and are presented ways for their decision;
        </p>
        <p>
           following group of works about general conceptual questions in the U&amp;S field
[
          <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
          ];
        </p>
        <p>
           part of works about problems and peculiarities of U&amp;S interaction on required
levels [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ], on processed levels [
          <xref ref-type="bibr" rid="ref10">10, 11</xref>
          ] and on model levels (including UML models)
[12];
        </p>
        <p>
           small group includes works about U&amp;S problems for mobile applications
[13,14];
 separate works about analysis of literature in U&amp;S problems field [15];
 some articles about U&amp;S characteristics evolution. Authors of such works
represent the evolution and interaction of usability and security characteristics [
          <xref ref-type="bibr" rid="ref2">16, 2</xref>
          ].
1.3
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>Goal and Structure</title>
        <p>Preliminary analysis of works in U&amp;S field permitted to make the following
conclusions and determine goal of the paper:</p>
        <p>
           firstly, characteristics of U&amp;S which described in last program engineering
standards [
          <xref ref-type="bibr" rid="ref1">1, 17, 18</xref>
          ] are one from other results of 40 years evolution [
          <xref ref-type="bibr" rid="ref2">2, 16</xref>
          ]. They
represented as complex characteristics with set of depended subcharacteristics;
 secondly, analysis of U&amp;S subcharacteristics and metrics did not conduct in
existing works [
          <xref ref-type="bibr" rid="ref10 ref3 ref4 ref5 ref6 ref7 ref8 ref9">3-16</xref>
          ], which describe problems interaction of U&amp;S characteristics;
 thirdly, separate subdivision was organized at National Institute of Standards
and Technology (NIST) of USA [20], which solves tasks of U&amp;S interaction.
However, well known works describe, first of all, influence of Usability on Security
and did not take into account aspects of influence on level of their subcharacteristics.
        </p>
        <p>Thus, goal of article is determination, analysis and assessment of U&amp;S interaction
on subcharacteristics and metrics levels.</p>
        <p>The paper has the following structure. Main second section contains:
 description of "Usable security" and "Secure usability" interaction problem;
 analysis of U&amp;S interaction on subcharacteristics level and variants U&amp;S
subcharacteristics interaction;</p>
        <p> analysis of U&amp;S interaction on metrics level.</p>
        <p>The third section analyses and assesses U&amp;S interaction for university web-site and
the fourth section concludes and describes directions of the future research.
2
2.1</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Usability and Security</title>
      <sec id="sec-3-1">
        <title>Two Sides of the Same Coin</title>
        <p>Exist of two possible aspects of research and development (i.e. two sides of the same
coin): usable security and secure usability. Let’s consider in more details what are the
differences between these two aspects.</p>
      </sec>
      <sec id="sec-3-2">
        <title>Usable Security</title>
        <p>First aspect gives an answer on a question: how to develop functions secure access to
resources such, in order to ensure acceptable/necessary level of usability of user
interfaces. In order to link of U&amp;S characteristics in the usable security aspect was
more understandable, we need represent example of such an interaction. Very often
procedure of registration on web-site requires from users to confirm their presence
near personal computer. It needs to exclude automatic registration on the Internet. As
a rule, web-site offers to users input data for CAPTCHA
(Completely Automated Public Turing test to tell Computers and Humans Apart)
[20]. In majority of cases, the CAPTCHA is information, which automatic generator
on picture of web-page and which necessary input to textbox. Sometimes users have
problems with input of information from CAPTCHA (i.e. have problem with Public
Turing test), because information which is represented on picture periodically cannot
be discernible. (Fig. 1). Defect of such technique of identification can provoke
discomfort for user. For solution of such problem user necessary, periodically
manually reload the picture of CAPTCHA waiting for recognizable information. User
can wait long time of appearance recognizable information. User can also delay or
cancel, for example, web-site registration procedure. This is an example, when
«complex» security kills usability – (cSkU) Information systems developers necessary
take into account such aspect, when they make project of user interfaces. We have to
exclude situation, when high level of security «kills» the usability.</p>
        <p>It should be noted, that subdivision at National Institute of Standards and
Technology (NIST) of USA researches such U&amp;S problems [19].</p>
      </sec>
      <sec id="sec-3-3">
        <title>Secure Usability</title>
        <p>Second aspect has relationships with development of user interfaces thus, in order to
ensure necessary level of information security. Lets describe an example of such
interaction between usability and security. Public Turing test can be maximum simple
and represents one checkbox element, which necessary will set up in significance
«check» (Fig. 2). From usability position such variant of Public Turing test is more
better than his variant on Fig 1. But from security position such variant (Fig. 2) is
more worse, because as against previous variant (Fig. 1) such variant is more simply
pass (by software bots) during automatic registration without user. In other words, in
such a context there is another competition. This is situation, when «simple» usability
“kills” security – sUkS).</p>
      </sec>
      <sec id="sec-3-4">
        <title>General</title>
        <p>Thus, U&amp;S characteristics really have interconnection in the form of two aspects and
formally differences can be described through «castle» of objective function and
limitations.</p>
        <p> in first case it is necessary to ensure the required level of usability (Ureq), at
that maximize of security (Smax), i.e. S →max, U ≥ Ureq;</p>
        <p> in second case it is necessary ensure the required level of security (Sreq), at
that maximize of usability (Umax), i.e. . U→ max, S ≥ Sreq.</p>
        <p>We pay attention, that U&amp;S characteristics and their sub characteristics described
in article as their interpretation in group of standards ISO 25000.</p>
      </sec>
      <sec id="sec-3-5">
        <title>Attributes of Security and Usability</title>
        <p>Examined positions can be represented out in detail as:</p>
        <p>
           security – is combination of following subcharacteristics [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]: confidentiality,
integrity, non-repudiation, accountability and authenticity
        </p>
        <p>
          S = {Conf, Integr, N-rep, Acc, Aut};
 usability – is combination of following subcharacteristics [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]: appropriateness
recognizability, learnability, operability, user error protection, user interface
aesthetics, accessibility.
        </p>
        <p>U = {AppRec, Learn, Oper, UEP, UIA, Acs}.
2.3</p>
      </sec>
      <sec id="sec-3-6">
        <title>U&amp;S Subcharacteristics Interaction Analysis</title>
        <p>
          We will consider interaction between U&amp;S subcharacteristics. For that we will
describe more detail formulations their subcharacteristics [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ], which represented in
table 1.
degree еto which a product or system can be used
by specified users to achieve specified goals with
effectiveness, efficiency and satisfaction in a
specified context of use
degree to which users can recognize whether a
product or system is appropriate for their needs
degree to which a product or system can be used
by specified users to achieve specified goals of
learning to use the product or system with
effectiveness, efficiency, freedom from risk and
satisfaction in a specified context of use
degree to which a product or system has attributes
that make it easy to operate and control
degree to which a system protects users against
making errors
degree to which a user interface enables pleasing
and satisfying interaction for the user
degree to which a product or system can be used
by people with the widest range of characteristics
2.3
2.4
2.5
        </p>
        <p>Security</p>
        <sec id="sec-3-6-1">
          <title>Confidentiality</title>
        </sec>
        <sec id="sec-3-6-2">
          <title>Integrity</title>
        </sec>
        <sec id="sec-3-6-3">
          <title>Non-repudiation</title>
        </sec>
        <sec id="sec-3-6-4">
          <title>Accountability</title>
        </sec>
        <sec id="sec-3-6-5">
          <title>Authenticity</title>
          <p>and capabilities to achieve a specified goal in a
specified context of use
NOTE 1 The range of capabilities includes
disabilities associated with age.</p>
          <p>NOTE 2 Accessibility for people with disabilities
can be specified or measured either as the extent
to which a product or system can be used by
users with specified disabilities to achieve
specified goals with effectiveness, efficiency,
freedom from risk and satisfaction in a specified
context of use, or by the presence of product
properties that support accessibility.
degree to which a product or system protects
information and data so that persons or other
products or
systems have the degree of data access
appropriate to their types and levels of
authorization
degree to which a product or system ensures that
data are accessible only to those authorized to
have access
degree to which a system, product or component
prevents unauthorized access to, or modification
of, computer programs or data
degree to which actions or events can be proven
to have taken place, so that the events or actions
cannot be repudiated later
degree to which the actions of an entity can be
traced uniquely to the entity
degree to which the identity of a subject or
resource can be proved to be the one claimed</p>
          <p>We have received set of variants of U&amp;S subcharacteristics interaction because of
U&amp;S subcharacteristics analysis. Set of variants of U&amp;S subcharacteristics represents
table 2.</p>
          <p>We will comment received variants. First of all, we will set the numeration as two
numbers (from table 2), which includes the first number as usability characteristic and
the second number as security characteristic:</p>
          <p> 1-1. Appropriateness recognizability subcharacteristic has interaction with
confidentiality subcharacteristic. It is obvious, because before ensuring
`Confidentiality`, user must, for example, see text boxes for input confidential
information and inputted such information;</p>
          <p> 1-2, 1-3, 1-4, 1-5. In authors opinion, such variants of interaction between
U&amp;S characteristics are possible, but they require additional research for set up more
exact of interaction type;
1 Arepcporgonpirziaabteilnietyss ↑↑/↓↓ ? ? ?
2 Learnability ↑↓ – – –
3 Operability ↑↑/↓↓ ↑↑/↓↓ ↑↑/↓↓ ↑↑/↓↓
4 Uprsoetreecrtrioonr ↑↑/↓↓ ↑↑/↓↓ ↑↑/↓↓ ↑↑/↓↓
5 Uaessetrhienttiecrsface ↑↑/↓↓ ? ? ?
6 Accessibility ↑↓ ↑↓ ↑↓ ↑↓
– - interaction is absent;
↑↑ - increase of level of one characteristic incurring to increase of
level of other characteristic;</p>
          <p>↑↓ - increase of level of one characteristic incurring to decrease of
level of other characteristic;</p>
          <p>↓↓ - decrease of level of one characteristic incurring to decrease of
level of other characteristic;</p>
          <p>? - interaction is exist, but type of interaction to set very difficult
(exist necessity of additional research)
 2-1. Such variant of interaction between subcharacteristics Learnability and
Confidentiality exists, because if user receives more information abaut
Confidentiality, than the level will be lower. Thus, if level of Learnability will
increase, level of Confidentiality will decrease. And vice versa, if level of
Learnability will decrease, level of Confidentiality will increase;</p>
          <p> 2-2, 2-3, 2-4, 2-5. In authors opinion, such variants of interaction between
subcharacteristics are absent;</p>
          <p> 3-1, 3-2, 3-3, 3-4, 3-5. Such variants of interaction between subcharacteristics
of Operability and Confidentiality, Integrity, Non-repudiation, Accountability,
Authenticity exist, because of increase of Operability level leads to increase in such
subcharacteristics, and vice versa, because of decrease of Operability level leads to
decrease such subcharacteristics;</p>
          <p> 4-1, 4-2, 4-3, 4-4, 4-5. Variants of interaction between User error protection
and Confidentiality, Integrity, Non-repudiation, Accountability, Authenticity exist,
because decrease of count of user errors incurring to increase of level of
characteristics Confidentiality, Integrity, Non-repudiation, Accountability and
Authenticity, but increase of count of user errors incurring to decrease their level;
y
t
i
c
i
t
n
e
h
t
u</p>
          <p>A
5
?
–
↑↑/↓↓
↑↑/↓↓
?
↑↓
 5-1. User`s interface aesthetics subcharacteristic has interaction with
Confidentiality subcharacteristic, because, when user works with information systems
interface, which has attractive design and well tidy colors, user has esthetical
satisfaction, consequently, he can see textboxes for input confidential information and
input her;</p>
          <p> 5-2, 5-3, 5-4, 5-5. In authors opinion, such variants of interaction between
U&amp;S subcharacteristics are possible, but require additional research for set up more
exact of interaction type;</p>
          <p> 6-1, 6-2, 6-3, 6-4, 6-5. In this variants if the level of Accessibility
characteristic will increase then levels of all subcharacteristics of security
characteristic will decrease and vice versa, if level of Accessibility characteristic will
decrease then levels of all subcharacteristics of security characteristic will increase. It
is obvious, because of ensuring of Accessibility characteristic in information systems
for people with disabilities in user`s interfaces it is necessary to do coordinal redesign
of user interfaces. As a rule, such redesign of interfaces, on the one hand, lighten of
interaction with software for people with disabilities, on the other hand, it is source of
level decrease for all subcharacteristics of security characteristic.
2.4</p>
        </sec>
      </sec>
      <sec id="sec-3-7">
        <title>U&amp;S Metrics Analysis</title>
        <p>We will analyze of U&amp;S metrics. For that, first of all, we will represent short
description of metrics and primitives (table 3).</p>
        <sec id="sec-3-7-1">
          <title>Demonstration capability</title>
        </sec>
        <sec id="sec-3-7-2">
          <title>Completeness</title>
          <p>of user
documentation
and/or help
facility</p>
        </sec>
        <sec id="sec-3-7-3">
          <title>Message clarity</title>
        </sec>
        <sec id="sec-3-7-4">
          <title>Customizing possibility</title>
        </sec>
        <sec id="sec-3-7-5">
          <title>Input validity checking</title>
        </sec>
        <sec id="sec-3-7-6">
          <title>Avoidance of incorrect operation</title>
        </sec>
        <sec id="sec-3-7-7">
          <title>Appearance customizability of user interface</title>
        </sec>
        <sec id="sec-3-7-8">
          <title>Physical</title>
          <p>accessibility</p>
          <p>A = number of
operations that behave
inconsistently
B= total number of
operations that behave
similarly
How easily can A = number of messages
messages from a that are understood
system be easily
understood ? B = total number of
implemented messages
How many A=Number of
functions and implemented functions
operational which can be customised
procedures during operation
can a user B=Number of functions
customize for his requiring the
convenience? customization capability
What proportion A = Number of input
of input items items checked for valid
provide checking data
for valid data. B = Number of input
items which need
checking for valid data
How many A = number of functions
functions have implemented to
incorrect avoid critical or serious
operation malfunctions being
avoidance caused by incorrect
capability. operation</p>
          <p>B = total number of
incorrect operation
patterns
A=Number of types of
interface elements that
can be customised.</p>
          <p>B=Total number of types
of interface Elements
A = number of functions
accessible by the
disabled person.</p>
          <p>B = total number of
functions implemented
What proportion
of user interface
elements can be
customised in
appearance.</p>
          <p>What proportion
of
functions can a
user with a
physical
handicap access
How controllable A= Number of detected</p>
        </sec>
        <sec id="sec-3-7-9">
          <title>Usability/ Operability</title>
        </sec>
        <sec id="sec-3-7-10">
          <title>Usability/ User error protection</title>
        </sec>
        <sec id="sec-3-7-11">
          <title>Usability/ User interface aesthetics measures</title>
        </sec>
        <sec id="sec-3-7-12">
          <title>Usability/ Accessibility measures</title>
        </sec>
        <sec id="sec-3-7-13">
          <title>Security/</title>
          <p>controllability</p>
        </sec>
        <sec id="sec-3-7-14">
          <title>Security/ Integrity</title>
        </sec>
        <sec id="sec-3-7-15">
          <title>Security/ Nonrepudiation</title>
        </sec>
        <sec id="sec-3-7-16">
          <title>Security/ Accountability</title>
        </sec>
        <sec id="sec-3-7-17">
          <title>Security/ Authenticity</title>
          <p>Results of U&amp;S metrics descriptions analysis gave us possibility to set up variants
of their interaction (table 4).</p>
          <p>If we compare data from table 2 and 4 we can see, that sets of variants of
interaction of U&amp;S subcharacteristics and their metrics do not identical, but very
similar. Some interactions were changed in the subcharacteristics context. In table 4
such changes were marked be the grey background. Such result is obvious, because
U&amp;S metrics interact with subcharacteristics</p>
          <p>Security subcharacteristics
2.1 Confidentiality
2.2 Integrity
2.3 Non-repudiation
2.4 Accountability
2.5 Authenticity
s
d
o
h
t
e
m
n
o
i
t
a
c
i
t
n
e
h
t
u</p>
          <p>A
?
?
↑↑/↓↓
↑↑/↓↓
↑↑/↓↓
↑↑/↓↓
↑↑/↓↓
?
↑↓
We will represent simple example of U&amp;S interaction. First of all, worth noting, that
metrics U&amp;S equal to subsubcharacteristics (i.e. U&amp;S subcharacteristics of second
level). In this case, with usage of calculated significances, from U&amp;S metrics, in
author’s opinion, it is possible to do quantitative analysis of U&amp;S interaction. We will
do such analysis for separate subcharacteristics of U&amp;S characteristics. For example,
we will consider interaction of Operability and Confidentiality subcharacteristics on
basis of such interaction with metrics. For that see table. 3, which includes the
description of metrics and required primitives for calculation. Object of our research
will be web-site of Banking University (http://ubs.edu.ua/en/), which is on the stage
of the development. We will calculate metrics of significances for web-site before
making changes in this web-site (i.e. before testing). Results of calculation
represented in table. 5.
We have considered two basic aspects of U&amp;S interaction: usable security and secure
usability. Differences in such aspects were analyzed by use of practical examples.</p>
          <p>This work includes results of analysis of U&amp;S interaction on the level of
subcharacteristics and metrics. Results of such research give possibility to define the
set of variants of the interaction of U&amp;S subcharacteristics and metrics. Such variants
of interaction of subcharacteristics and metrics are not identical, but are very similar.</p>
          <p>In future authors are planning to make complete quantitative analysis of interaction
of U&amp;S subcharacteristics on the base of calculated metrics values. Authors suppose,
that such analysis must confirm that variants of interaction of U&amp;S subcharacteristics
assessment will be correct. Also we plan to analyze interaction between U&amp;S
characteristics of information systems and another once, for example, safety.</p>
          <p>Practical results of such assessment are improving of requirements foundation for
U&amp;S and other characteristics and correcting of design decisions.
11. Shamal Faily, John Lyle, Ivan Fléchais, Andrew Simpson. Usability and Security by
Design: A Case Study in Research and Development. Proc. of the NDSS Workshop on
Usable Security, At San Diego, CA, USA,
(http://eprints.bournemouth.ac.uk/22053/1/flfs15.pdf) (2015)
12. Paul DiGioia, Paul Douris. Social Navigation as a Model for Usable Security. In. proc.
of Symposium On Usable Privacy and Security (SOUPS), July 6-8, Pittsburgh, PA, USA,
pp. 101-108 (2005)
13. William Melicher, Darya Kurilova, Sean M. Segreti, Pranshu Kalvani, Richard Shay,
Blase Ur, Lujo Bauer, Nicolas Christin, Lorrie Faith Cranor, Michelle L. Mazurek.
Usability and Security of Text Passwords on Mobile Devices. In. proc. of the CHI
Conference on Human Factors in Computing Systems (CHI '16), Santa Clara, California,
USA, pp. 527-539 (2016)
14. Catalin Boja, Mihai Doinea. Usability vs. Security in mobile applications. Proc. of the IE
2013 International Conference, pp.138-142 (2013)
15. Ugochi Oluwatosin Nwokedi, Beverly Amunga Onyimbo, Babak Bashari Rad. Usability
and Security in User Interface Design: A Systematic Literature Review. International
Journal of Information Technology and Computer Science (IJITCS), Vol. 8, pp. 72-80
(2016)
16. Oleksandr Gordieiev, Vyacheslav Kharchenko and Mario Fusani. Evolution of software
quality models: usability, security and greenness issues. In proc. of the 19-th International
Conference on Computers (part of CSCC 15), July 16-20, Zakynthos Island, Greece, p.
519-523 (2015)
17. ISO/IEC 25023: Systems and software engineering – Systems and software Quality
Requirements and Evaluation (SQuaRE) – Measurement of system and software
product quality, ISO/IEC JTC1/SC7/WG6 (2011)
18. ISO/IEC 25030: Software engineering – Software product Quality Requirements and</p>
          <p>Evaluation (SQuaRE) – Quality requirements, ISO/IEC (2007)
19. Usability of security team at National institute of standards and Technology
(http://csrc.nist.gov/security-usability/HTML/about.html).
20. Completely Automated Public Turing test to tell Computers and Humans Apart,
CAPCHA (http://www.captcha.net/).</p>
        </sec>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. ISO/IEC 25010:
          <article-title>Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models</article-title>
          ,
          <source>ISO/IEC JTC1/SC7/WG6</source>
          , (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>Oleksandr</given-names>
            <surname>Gordieiev</surname>
          </string-name>
          .
          <article-title>Evolution of software Quality Models in Context of the Standard ISO 25010</article-title>
          .
          <source>In. proc. Dependability on Complex Systems DepCoS - RELCOMEX (DepCOS)</source>
          , June 30 - July 4,
          <string-name>
            <surname>Brunow</surname>
          </string-name>
          , Poland. - pp.
          <fpage>223</fpage>
          -
          <lpage>233</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>C. Shoba</given-names>
            <surname>Bindu</surname>
          </string-name>
          .
          <article-title>Secure Usable Authentication Using Strong Pass text Passwords</article-title>
          .
          <source>Computer Network and Information Security</source>
          , Vol.
          <volume>3</volume>
          ,
          <issue>2015</issue>
          , pp.
          <fpage>57</fpage>
          -
          <lpage>64</lpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Suliman</surname>
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Alsuhibany</surname>
          </string-name>
          .
          <article-title>A benchmark for designing usable and secure text-based captchas</article-title>
          .
          <source>International Journal of Network Security &amp; Its Applications (IJNSA)</source>
          , Vol.
          <volume>8</volume>
          , No.
          <issue>4</issue>
          , pp.
          <fpage>41</fpage>
          -
          <lpage>54</lpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>Julie</given-names>
            <surname>Thorpe</surname>
          </string-name>
          , Paul C. van Oorschot.
          <article-title>Graphical Dictionaries and the Memorable Space of Graphical Passwords</article-title>
          .
          <source>In. proc. of the 13th USENIX Security Symposium, August</source>
          <volume>9</volume>
          -13, San Diego, CA, USA, pp.
          <fpage>10</fpage>
          -
          <lpage>26</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Khalid</surname>
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Al-Sarayreh</surname>
          </string-name>
          ,
          <article-title>Lina A</article-title>
          .
          <string-name>
            <surname>Hasan</surname>
            ,
            <given-names>Khaled</given-names>
          </string-name>
          <string-name>
            <surname>Almakadmeh</surname>
          </string-name>
          .
          <article-title>A Trade-Off Model of Software Requirements for Balancing Between Security and Usability Issues</article-title>
          .
          <source>International Review on Computers and Software</source>
          , Vol.
          <volume>10</volume>
          (
          <issue>12</issue>
          ), pp.
          <fpage>1157</fpage>
          -
          <lpage>1168</lpage>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <article-title>7. Evaluating the accessibility, usability and security of Hospitals websites: An exploratory study</article-title>
          .
          <source>In proc. International conference on Cloud System and Big Data</source>
          Engineering (Confluence-2017), at Noida, Uttar Pradesh, India, (https://www.researchgate.net/publication/ 313841977_Evaluating_
          <article-title>the_accessibility_usability_and_security_of_Hospitals_websites _</article-title>
          <source>An_exploratory_study)</source>
          (
          <year>2017</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>Butler</given-names>
            <surname>Lampson</surname>
          </string-name>
          .
          <article-title>Privacy and Security Usable Security: How to Get It</article-title>
          .
          <source>Communications of the ACM</source>
          , Vol.
          <volume>52</volume>
          , no.
          <issue>11</issue>
          , pp.
          <fpage>25</fpage>
          -
          <lpage>27</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Bryan</surname>
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Payne</surname>
            ,
            <given-names>W. Keith</given-names>
          </string-name>
          <string-name>
            <surname>Edwards</surname>
          </string-name>
          .
          <article-title>A Brief Introduction to Usable Security</article-title>
          .
          <source>IEEE Internet Computing</source>
          , Vol.
          <volume>12</volume>
          , pp.
          <fpage>13</fpage>
          -
          <lpage>21</lpage>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Ivan</surname>
            <given-names>Flechais</given-names>
          </string-name>
          , Cecilia Mascolo,
          <string-name>
            <given-names>M. Angela</given-names>
            <surname>Sasse</surname>
          </string-name>
          .
          <article-title>Integrating security and usability into the requirements and design process</article-title>
          .
          <source>International Journal of Electronic Security and Digital Forensics</source>
          , Vol.
          <volume>1</volume>
          , pp.
          <fpage>12</fpage>
          -
          <lpage>26</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>