<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
We are proud to chair next year's USEC 2017 conference in San Diego
after the successful EuroUSEC 2016 (during the security week). <br>
<br>
<div class="moz-text-html" lang="x-western">
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;">
<div style="font-family: Times New Roman; color: #000000;
font-size: 16px">
<div id="divRpF221586" style="direction: ltr;"><span
style="font-family: Arial; font-size: 30.6667px;">Usable
Security (USEC) Workshop </span></div>
<div>
<div style="direction:ltr; font-family:Tahoma;
color:#000000; font-size:10pt">
<div style="font-family:Times New Roman; color:#000000;
font-size:16px">
<div>
<div style="direction:ltr; font-family:Tahoma;
color:#000000; font-size:10pt">
<div style="font-family:Times New Roman;
color:#000000; font-size:16px">
<div>
<div style="direction:ltr; font-family:Tahoma;
color:#000000; font-size:10pt">
<div style="font-family:Times New Roman;
color:#000000; font-size:16px">
<div>
<div style="direction:ltr;
font-family:Tahoma; color:#000000;
font-size:10pt">
<div style="font-family:Times New Roman;
color:#000000; font-size:16px">
<div>
<div style="direction:ltr;
font-family:Tahoma; color:#000000;
font-size:10pt">
<div style="font-family:Times New
Roman; color:#000000;
font-size:16px">
<div>
<div>
<div style="direction:ltr;
font-family:Tahoma;
color:#000000;
font-size:10pt">
<div
style="font-family:Times
New Roman;
color:#000000;
font-size:16px">
<div>
<div
style="direction:ltr;
font-family:Tahoma;
color:#000000;
font-size:10pt">
<div
style="font-family:Times
New Roman;
color:#000000;
font-size:16px">
<div>
<div
style="direction:ltr;
font-family:Tahoma; color:#000000; font-size:10pt">
<div>
<div
style="font-family:Tahoma;
font-size:13px">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div
style="font-size:13px">
<div
style="font-family:Tahoma;
font-size:13px">
<h1 dir="ltr"
id="docs-internal-guid-e51a9e96-fa84-bb80-ab5f-d29376c30a21"
style="line-height:1.38;
margin-top:24pt; margin-bottom:6pt">
<span
style="font-size:30.6667px;
font-family:Arial; vertical-align:baseline">Call for Papers</span><span
style="font-size:26.6667px; font-family:Arial; font-weight:400;
vertical-align:baseline">
</span><span
style="font-size:26.6667px;
font-family:Arial; font-weight:400; vertical-align:baseline">
</span></h1>
<h2 dir="ltr"
style="line-height:1.697684210526316; margin-top:18pt;
margin-bottom:15pt">
<span
style="font-size:21.3333px;
font-family:Arial; font-weight:400; vertical-align:baseline">Paper
Submission
Deadline: 1
December 2016</span></h2>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:16px;
font-family:"Droid Sans"; color:rgb(46,46,46);
background-color:rgb(255,255,255);
vertical-align:baseline">One cannot have security and privacy without
considering
both the
technical and
human aspects
thereof. If
the user is
not given due
consideration
in the
development
process, the
system is
likely to
enable users
to protect
their privacy
and security
in the
Internet.
</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:16px;
font-family:"Droid Sans"; color:rgb(46,46,46);
background-color:rgb(255,255,255);
vertical-align:baseline">Usable security and security is more
complicated
than
traditional
usability.
This is
because
traditional
usability
principles
cannot always
be applied.
For example,
one of the
cornerstones
of usability
is that people
are given
feedback on
their actions,
and are helped
to recover
from errors.
In
authentication,
we obfuscate
password entry
(a usability
fail) and we
give people no
assistance to
recover from
errors.
Moreover,
security is
often not
related to the
actual
functionality
of the system,
so people
often see it
as a bolt-on,
and an
annoying
hurdle. These
and other
usability
challenges of
security are
the focus of
this workshop.</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:16px;
font-family:"Droid Sans"; color:rgb(46,46,46);
background-color:rgb(255,255,255);
vertical-align:baseline">We invite submissions on all aspects of human
factors
including
mental models,
adoption, and
usability in
the context of
security and
privacy. USEC
2017 aims to
bring together
researchers
already
engaged in
this
interdisciplinary
effort with
other computer
science
researchers in
areas such as
visualization,
artificial
intelligence,
machine
learning and
theoretical
computer
science as
well as
researchers
from other
domains such
as economics,
legal
scientists,
social
scientists,
and
psychology. We
particularly
encourage
collaborative
research from
authors in
multiple
disciplines.</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:16px;
font-family:"Droid Sans"; color:rgb(46,46,46);
background-color:rgb(255,255,255);
vertical-align:baseline">Topics include, but are not limited to:</span></p>
<ul
style="margin-top:0pt;
margin-bottom:0pt">
<li dir="ltr"
style="list-style-type:disc; font-size:16px; font-family:"Droid
Sans";
color:rgb(46,46,46);
background-color:rgb(255,255,255); vertical-align:baseline">
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:0pt">
<span
style="vertical-align:baseline">Human
factors
related to the
deployment of
the Internet
of Things (New
topic for
2017)</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc; font-size:16px; font-family:"Droid
Sans";
color:rgb(46,46,46);
background-color:rgb(255,255,255); vertical-align:baseline">
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:0pt">
<span
style="vertical-align:baseline">Usable
security /
privacy
evaluation of
existing
and/or
proposed
solutions.</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc; font-size:16px; font-family:"Droid
Sans";
color:rgb(46,46,46);
background-color:rgb(255,255,255); vertical-align:baseline">
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:0pt">
<span
style="vertical-align:baseline">Mental
models that
contribute to,
or complicate,
security or
privacy</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc; font-size:16px; font-family:"Droid
Sans";
color:rgb(46,46,46);
background-color:rgb(255,255,255); vertical-align:baseline">
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:0pt">
<span
style="vertical-align:baseline">Lessons
learned from
designing,
deploying,
managing or
evaluating
security and
privacy
technologies</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc; font-size:16px; font-family:"Droid
Sans";
color:rgb(46,46,46);
background-color:rgb(255,255,255); vertical-align:baseline">
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:0pt">
<span
style="vertical-align:baseline">Foundations
of usable
security and
privacy incl.
usable
security and
privacy
patterns</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc; font-size:16px; font-family:"Droid
Sans";
color:rgb(46,46,46);
background-color:rgb(255,255,255); vertical-align:baseline">
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="vertical-align:baseline">Ethical,
psychological,
sociological,
economic, and
legal aspects
of security
and privacy
technologies</span></p>
</li>
</ul>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:16px;
font-family:"Droid Sans"; color:rgb(46,46,46);
background-color:rgb(255,255,255);
vertical-align:baseline">We further encourage submissions that
contribute to
the research
community’s
knowledge
base:</span></p>
<ul
style="margin-top:0pt;
margin-bottom:0pt">
<li dir="ltr"
style="list-style-type:disc; font-size:16px; font-family:"Droid
Sans";
color:rgb(46,46,46);
background-color:rgb(255,255,255); vertical-align:baseline">
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:0pt">
<span
style="vertical-align:baseline">Reports
of replicating
previously
published
studies and
experiments</span></p>
</li>
<li dir="ltr"
style="list-style-type:disc; font-size:16px; font-family:"Droid
Sans";
color:rgb(46,46,46);
background-color:rgb(255,255,255); vertical-align:baseline">
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="vertical-align:baseline">Reports
of failed
usable
security
studies or
experiments,
with the focus
on the lessons
learned from
such
experience.</span></p>
</li>
</ul>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:16px;
font-family:"Droid Sans"; color:rgb(46,46,46);
background-color:rgb(255,255,255);
vertical-align:baseline">It is the aim of USEC to contribute to an
increase of
the scientific
quality of
research in
human factors
in security
and privacy.
To this end,
we encourage
the use of
replication
studies to
validate
research
findings. This
important and
often very
insightful
branch of
research is
sorely
underrepresented
in human
factors in
security and
privacy
research to
date. Papers
in these
categories
should be
clearly marked
as such and
will not be
judged against
regular
submissions on
novelty.
Rather, they
will be judged
based on
scientific
quality and
value to the
community. We
also encourage
reports of
failed
experiments,
since their
publication
will serve to
prevent others
falling into
the same
traps. </span></p>
<h3 dir="ltr"
style="line-height:1.697684210526316; margin-top:14pt;
margin-bottom:4pt">
<span
style="font-size:17.3333px;
font-family:Arial; vertical-align:baseline">Location and Important Dates</span></h3>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Paper submission: 1 December
2016 (11:59pm
PST) - see
note below on
CHI
submissions</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Notification: 21 January
2017</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Camera ready copy due: 31
January 2017</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Workshop: 26 February 2017
(co-located
with NDSS
2017)</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Location: Catamaran Resort
Hotel &
Spa in San
Diego,
California.</span></p>
<h3 dir="ltr"
style="line-height:1.697684210526316; margin-top:14pt;
margin-bottom:4pt">
<span
style="font-size:17.3333px;
font-family:Arial; vertical-align:baseline">Submission Instructions</span></h3>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Papers should be written in
English. Full
papers must be
no more than
10 pages total
(excluding
references and
appendices).
Papers must be
formatted for
US letter size
(not A4) paper
in a
two-column
layout, with
columns no
more than 9.25
inch high and
3.5 inch wide.
The text must
be in Times
font, 10-point
or larger,
with 11-point
or larger line
spacing.
Authors are
encouraged to
use the NDSS
provided
templates
(<a class="moz-txt-link-freetext" href="https://www.internetsociety.org/events/ndss-symposium/ndss-templates">https://www.internetsociety.org/events/ndss-symposium/ndss-templates</a>).</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">We also invite short papers
of up to 6
pages covering
work in
progress,
short
communications,
as well as
novel or
provocative
ideas. Short
papers will be
selected based
on their
potential to
spark
interesting
discussions
during the
workshop.</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Papers that contribute to
the research
community’s
knowledge base
such as
studies
replicating
previous
results can be
submitted as
full or short
papers.</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Submissions do not have to
be anonymized
for review.
Please clearly
refer to your
own related
work.</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Note: USEC would like to
accommodate
those who are
waiting to
hear back
about their
CHI 2017
submissions
but who would
like to also
submit their
work for
consideration
for USEC. The
CHI decision
notification
is expected to
be December
12, 2016.
Owing to the
overlapping
dates for both
conferences,
we have made
allowances *in
this instance
only* for
duplicate
submissions.
Please read
the following
information
carefully. You
may submit
work already
submitted to
the CHI
"Papers &
Notes" track
to USEC 2017
before you
receive your
acceptance
notification
from CHI,
provided that:
1. you clearly
indicate on
the manuscript
that the work
has been
submitted to
CHI 2017; 2.
you email the
PC chair
(<a class="moz-txt-link-abbreviated" href="mailto:usec2017@easychair.org">usec2017@easychair.org</a>)
at the time of
submission to
USEC; 3. you
inform the PC
chair
immediately
when you are
notified about
the status of
your CHI
submission.
Any work
accepted for
publication at
CHI will be
withdrawn from
consideration
for USEC 2017.</span></p>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">The proceedings will be
published by
the Internet
Society.</span></p>
<h3 dir="ltr"
style="line-height:1.697684210526316; margin-top:14pt;
margin-bottom:4pt">
<span
style="font-size:17.3333px;
font-family:Arial; vertical-align:baseline">Conference Website</span></h3>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline"><a class="moz-txt-link-freetext" href="http://www.karenrenaud.com/usec">http://www.karenrenaud.com/usec</a></span></p>
<h3 dir="ltr"
style="line-height:1.697684210526316; margin-top:14pt;
margin-bottom:4pt">
<span
style="font-size:17.3333px;
font-family:Arial; vertical-align:baseline">Program Chairs</span></h3>
<p dir="ltr"
style="line-height:1.697684210526316;
margin-top:0pt; margin-bottom:15pt">
<span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Melanie Volkamer, Karlstad
and Darmstadt</span><span
style="font-size:14.6667px; font-family:Arial; vertical-align:baseline"><br
class="kix-line-break">
</span><span
style="font-size:14.6667px;
font-family:Arial; vertical-align:baseline">Karen Renaud, Glasgow</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<pre class="moz-signature" cols="72">
</pre>
<br>
<pre class="moz-signature" cols="72">--
Dr. Melanie Volkamer
Head of Group
SecUSo- IT Security, Usability and Society
Center for Advanced Security Research Darmstadt
TU Darmstadt
Hochschulstrasse 10
D - 64289 Darmstadt
Phone: +49(0) 6151 16 5422
Fax: +49(0) 6151 16 4825
E-Mail: <a class="moz-txt-link-abbreviated" href="mailto:melanie.volkamer@cased.de">melanie.volkamer@cased.de</a>
Web: <a class="moz-txt-link-abbreviated" href="http://www.secuso.cased.de">www.secuso.cased.de</a>
</pre>
</body>
</html>