SOUPS
  2010

July 14-16, 2010
Redmond, WA

SOUPS Home

Call for participation

Registration

Program

Venue

Organization

Symposium On Usable Privacy and Security

CALL FOR PAPERS, POSTERS, AND PROPOSALS

[plain text] [PDF]

The 2010 Symposium on Usable Privacy and Security (SOUPS) will bring together an interdisciplinary group of researchers and practitioners in human computer interaction, security, and privacy. The program will feature technical papers, a poster session, panels and invited talks, discussion sessions, and in-depth sessions (workshops and tutorials). This year SOUPS will be held in Redmond, WA.

See important dates below.

TECHNICAL PAPERS

We invite authors to submit original papers describing research or experience in all areas of usable privacy and security. Topics include, but are not limited to:

  • innovative security or privacy functionality and design,
  • new applications of existing models or technology,
  • field studies of security or privacy technology,
  • usability evaluations of new or existing security or privacy features,
  • security testing of new or existing usability features,
  • longitudinal studies of deployed security or privacy features,
  • the impact of organizational policy or procurement decisions, and
  • lessons learned from the deployment and use of usable privacy and security features.

All submissions must relate to both usability and either security or privacy. Papers on security or privacy applications that do not address usability or human factors will not be considered.

Papers need to describe the purpose and goals of the work completed to date, cite related work, show how the work effectively integrates usability and security or privacy, and clearly indicate the innovative aspects of the work or lessons learned as well as the contribution of the work to the field.

Submitted papers must not significantly overlap papers that have been published or that are simultaneously submitted to a peer-reviewed venue or publication. With the exception of publicly available prior work that is documented in your related work section, any overlap between your submitted paper and other work either under submission or previously published must be documented in a clearly-marked explanatory note at the front of the paper. State precisely how the two works differ in their goals, any use of shared experiments or data sources, and the unique contributions. If the other work is under submission elsewhere, the program committee may ask to review that work to evaluate the overlap. Please note that program committees frequently share information about papers under review and reviewers usually work on multiple conferences simultaneously. As technical reports are not peer reviewed they are exempt from this rule. You may also release pre-prints of your accepted work to the public at the time of your discretion.

Accepted papers will appear in the ACM Digital Library as part of the ACM International Conference Proceedings Series. The technical papers committee will select an accepted paper to receive the SOUPS 2010 best paper award.

New this year, authors have the option to attach to their paper supplemental appendices containing study materials (e.g. surveys) that would not otherwise fit within the body of the paper. These appendices may be included to assist reviewers who may have questions that fall outside the stated contribution of your paper, on which your work is to be evaluated. The body of your paper must still be self contained and provide sufficient detail to elucidate your study methodology and results, as reviewers are neither required nor expected to read supplemental appendices. Accepted papers will be published online with their supplemental appendices included.

Papers must use the SOUPS formatting template (available for MS Word or LaTeX) and be up to 12 pages in length, exclusive of the bibliography and any supplemental appendices described above. Submissions must be no more than 20 pages including bibliography and appendices. If your supplemental materials exceed this page limit, you may upload a separate external appendix file with these materials. The external appendix file need not conform to the SOUPS formatting template. In that case, make sure you mention the external appendix in the body of your paper and describe its contents. For the body of your paper, brevity is appreciated, as evidenced by the fact that many papers in prior years have been well under this limit. All submissions must be in PDF format and should not be blinded. In addition, you must cut and paste an abstract of no more than 300 words onto the submission form.

Submit your paper using the electronic submissions page for the SOUPS 2010 conference (http://cups.cs.cmu.edu/soups/2010/submit.html). A successful submission will display a web page confirming it, and a confirmation email is sent to the corresponding author. Please make sure you receive that confirmation email when you submit, and follow the directions in that email if you require any follow up.

Technical paper submissions will close at 5 PM, US Pacific time, the evening of Friday, March 5. This is a hard deadline! Authors will be notified of technical paper acceptance by April 30, and camera ready final versions of technical papers are due June 12.

Authors are encouraged to review: Common Pitfalls in Writing about Security and Privacy Human Subjects Experiments, and How to Avoid Them.

SOUPS policy on submissions by program co-chairs: A submission may be authored or co-authored by a SOUPS program co-chair so long as the other co-chair has no conflicts with any of the authors. In this event, the paper will be submitted directly to the unconflicted co-chair by the submission deadline. The unconflicted chair will select a minimum of three other program committee members or other experts as reviewers. After each reviewer has submitted a review, their collective reviews, and any further comments they may have, will be shared amongst themselves such that each may remain anonymous in the discussion if they so choose. The unconflicted program chair may be entrusted with removing reviewers' names and forwarding the reviewers' comments to provide anonymity if no technological solution is available. After all reviews and comments have been shared, the paper will be accepted if, and only if, no less than three fourths of those participating in the process (the 3+ reviewers and the unconflicted co-chair) agree that the paper would have been accepted had the program chair not been an author.

POSTERS

We seek poster abstracts describing recent or ongoing research or experience in all areas of usable privacy and security. Submissions should use the SOUPS poster template [MS Word] [LaTeX] and be at most two pages. Accepted poster abstracts will be distributed to symposium participants and made available on the symposium web site. Please follow the final submission formatting instructions when preparing your poster abstract to avoid the need to revise poster abstracts after acceptance decisions are made. In addition, SOUPS will include a poster session in which authors will exhibit their posters. Note, poster abstracts should be formatted like short papers, not like posters. Authors of accepted posters will be sent information about how to prepare and format posters for the conference.

Submit your poster using the electronic submissions page. A successful submission will display a web page confirming it, and a confirmation email is sent to the corresponding author. Please make sure you receive that confirmation email when you submit, and follow the directions in that email if you require any follow up.

We also welcome authors of recent papers (2009 to 2010) on usable privacy and security to present your work at the SOUPS poster session. Please submit the title and abstract of your conference paper, full citation, and a link to the published version.

Submissions will close at 5pm, US Pacific time, the evening of May 28.

DISCUSSION SESSIONS

SOUPS will feature parallel, moderated breakout sessions (similar to Birds of a feather sessions) in which symposium participants will discuss a topic related to usable privacy and security. These sessions may include a brief introduction to the topic by the moderator, but otherwise will not include formal presentations. Discussion session topics may include, but are not limited to, definitions or metrics, design critiques, research agendas, or frameworks for collaborative research. We seek proposals for discussion session topics. Proposals must include a one paragraph statement of the topic to be discussed and a one paragraph bio of each proposer that describes their experience or interest in the topic. Optionally, proposers may submit up to two pages of background material that can be distributed to participants and posted on the SOUPS website. Authors of accepted proposals will be expected to moderate their discussion session and provide a brief report on their session for posting on the SOUPS web site after the symposium.

Proposals for discussion sessions should be submitted via email to sessions AT cups DOT cs DOT cmu DOT edu

Submissions will close at 5pm, US Pacific time, the evening of May 28.

IN-DEPTH SESSIONS (WORKSHOPS AND TUTORIALS)

We are soliciting proposals for a small number of in-depth sessions on usable security and privacy. These sessions could run either a half or full day, and could be lecture-oriented (tutorial) or a group-oriented session designed to widely share experience (workshop). To get a better idea, please see the following examples of previous workshop and tutorial descriptions:

Examples of Previous Workshops:

Examples of Previous Tutorials:

Proposals should include the following:

  • Title
  • Leader(s) (including pertinent biographical information)
  • Format (tutorial or workshop)
  • Description
  • Duration (half or full day)
  • Target audience
  • (Workshops only) Goals and highlights of the call for participation.

In-depth sessions will be open to all SOUPS attendees. They will generate materials that will be made available on the SOUPS website (tutorial notes, workshop presentations and a report/summary). Workshops will have their own CFP for presentations, abstracts, or short papers, which will be published by February 15.

Send in-depth session proposals to sessions AT cups DOT cs DOT cmu DOT edu by January 12.

PANELS

SOUPS is seeking proposals for panels. A good panel focuses on an issue of current concern, and has a strong and clear point of contention in the topic, in the questions, and in the panelist points of view. Full proposals should contain a title, description of the topic, and suggested panelists (with pertinent biographical information). We encourage panels structured as debates rather than just a series of short talks. We are also interested in ideas for panels you would like to see on the program, even if you do not wish to be a panel organizer.

Send suggestions or proposals for panels to sessions AT cups DOT cs DOT cmu DOT edu by January 12.

INVITED TALKS

We're looking for ideas for invited speakers. Please suggest a speaker you would like to hear from, or have heard recently with something provocative or visionary to say on the topic of usable security and privacy.

Send suggestions for invited speakers to sessions AT cups DOT cs DOT cmu DOT edu by January 12.

IMPORTANT DATES

Early registration deadline - June 5
Conference - July 14-16

Technical papers
Submission deadline - March 5, 5 pm US Pacific time (hard deadline!)
Notification of paper acceptance - April 30
Camera ready papers due - June 12

Posters and discussion sessions
Submission deadline - May 28
Notification of acceptance - June 3

In-depth sessions (tutorials and workshops)
In-depth session proposal submission deadline - January 12
Notification of in-depth session proposal acceptance - January 25
Workshop paper submission deadline - May 8, Extended to May 17
Notification of workshop paper acceptance - June 3
Camera ready papers due - June 12

Panels and invited talks
Panel proposal submission deadline - January 12
Speaker suggestion submission deadline - January 12

 

SOUPS 2010 is sponsored by Carnegie Mellon CyLab and Microsoft.