31st USENIX Security Symposium - August 10-12, 2022, Boston, MA, USA Sponsored by USENIX, the Advanced Computing Systems Association
←
→
Page content transcription
If your browser does not render page correctly, please read the page content below
Announcement and Call for Papers www.usenix.org/sec22/cfp
31st USENIX Security Symposium
August 10–12, 2022, Boston, MA, USA
Sponsored by USENIX, the Advanced Computing Systems Association
The USENIX Security Symposium brings together researchers, Winter Deadline
practitioners, system administrators, system programmers, • Refereed paper submissions due: Tuesday, February 1, 2022,
and others interested in the latest advances in the security 11:59 pm AoE
and privacy of computer systems and networks. The 31st
USENIX Security Symposium will be held August 10–12, 2022,
• Early reject notification: March 11, 2022
in Boston, MA. • Rebuttal Period: April 18–20, 2022
Important: The USENIX Security Symposium moved to multiple
• Notification to authors: May 2, 2022
submission deadlines in 2019 and included changes to the review • Final paper files due: June 14, 2022
process and submission policies. Detailed information is available
at USENIX Security Publication Model Changes. • Invited talk and panel proposals due: Tuesday, February 1, 2022
All researchers are encouraged to submit papers covering • Poster proposals due: Wednesday, July 6, 2022
novel and scientifically significant practical works in computer ° Notification to poster presenters: Wednesday, July 13, 2022
security. The Symposium will span three days with a technical Conference Organizers
program including refereed papers, invited talks, posters, panel
discussions, and Birds-of-a-Feather sessions. Co-located events Program Co-Chairs
will precede the Symposium on August 8 and 9. Kevin Butler, University of Florida
Kurt Thomas, Google
Important Dates
Program Committee
Summer Deadline Yousra Aafer, University of Waterloo
• Refereed paper submissions due: Tuesday, June 8, 2021, Ruba Abu-Salma, King’s College London
11:59 pm AoE Gunes Acar, Katholieke Universiteit Leuven
• Early reject notification: July 15, 2021 Sadia Afroz, International Computer Science Institute (ICSI), Avast
• Rebuttal Period: August 23–25, 2021 Devdatta Akhawe, Dropbox
• Notification to authors: September 3, 2021 Daniel Alexander Zappala, Brigham Young University
• Final paper files due: October 5, 2021 Ardalan Amiri Sani, University of California, Irvine
Olabode Anise, Google
Fall Deadline
Daniele Antonioli, EPFL, EURECOM
• Refereed paper submissions due: Tuesday, October 12, 2021, Maria Apostolaki, ETH Zurich
11:59 pm AoE
Elias Athanasopoulos, University of Cyprus
• Early reject notification: November 20, 2021 Davide Balzarotti, EURECOM
• Rebuttal Period: January 10–12, 2022 Tiffany Bao, Arizona State University
• Notification to authors: January 20, 2022 David Barrera, Carleton Univeristy
• Final paper files due: February 22, 2022 Adam Bates, University of Illinois at Urbana–Champaign
Lejla Batina, Radboud University
Lujo Bauer, Carnegie Mellon University
Rev. 09/28/21Jethro Beekman, Fortanix Earlence Fernandes, University of Wisconsin—Madison Antonio Bianchi, Purdue University Domenic Forte, University of Florida Battista Biggio, University of Cagliari Aurélien Francillon, EURECOM Leyla Bilge, NortonLifeLock Research Group Michael Franz, University of California, Irvine Vincent Bindschaedler, University of Florida Yanick Fratantonio, Cisco Talos Priyam Biswas, Intel David Freeman, Facebook Marina Blanton, University at Buffalo Aymeric Fromherz, Inria Erik-Oliver Blass, Airbus Patrick Gage Kelley, Google Tamara Bonaci, Northeastern University Eva Galperin, Electronic Frontier Foundation Joseph Bonneau, New York University Vinod Ganapathy, Indian Institute of Science (IISc) Glencora Borradaile, Oregon State University Christina Garman, Purdue University Marcus Botacin, Federal University of Paraná Carrie Gates, Bank of America Ioana Boureanu, University of Surrey Genevieve Gebhart, University of Washington Information School Nathan Burow, MIT Lincoln Laboratory Daniel Genkin, University of Michigan Joseph Calandrino, Federal Trade Commission Ryan Gerdes, Virginia Tech Stefano Calzavara, Università Ca’ Foscari Venezia Arthur Gervais, Imperial College London Yinzhi Cao, Johns Hopkins University Irene Giacomelli, Protocol Labs Srdjan Capkun, ETH Zurich Yossi Gilad, The Hebrew University of Jerusalem Alvaro Cardenas, University of California, Santa Cruz Neil Gong, Duke University Nicholas Carlini, Google Tyrone Grandison, The Data-Driven Institute Lorenzo Cavallaro, University College London Daniel Gruss, Graz University of Technology Z. Berkay Celik, Purdue University Guofei Gu, Texas A&M University Sang Kil Cha, Korea Advanced Institute of Science and Le Guan, University of Georgia Technology (KAIST) Shuang Hao, The University of Texas at Dallas Neha Chachra, Facebook Wajih Ul Hassan, University of Illinois at Urbana–Champaign Rahul Chatterjee, University of Wisconsin—Madison Christophe Hauser, USC/Information Sciences Institute Sze Yiu Chau, The Chinese University of Hong Kong Xiali Hei, University of Louisiana at Lafayette Kai Chen, Institute of Information Engineering, Chinese Academy Grant Hernandez, Qualcomm of Sciences Matthew Hicks, Virginia Tech Qi Alfred Chen, University of California, Irvine Ralph Holz, University of Twente Yizheng Chen, Columbia University Thorsten Holz, Ruhr University Bochum Sherman S. M. Chow, The Chinese University of Hong Kong Nick Hopper, University of Minnesota Amrita Roy Chowdhury, University of Wisconsin—Madison Diane Hosfelt, Apple Nicolas Christin, Carnegie Mellon University Syed Rafiul Hussain, The Pennsylvania State University Chitchanok Chuengsatiansup, The University of Adelaide Luca Invernizzi, Google Camille Cobb, Carnegie Mellon University Sotiris Ioannidis, Technical University of Crete Shaanan Cohney, Princeton University and University of Melbourne Cynthia Irvine, Naval Postgraduate School Andrea Continella, University of Twente Suman Jana, Columbia University Cas Cremers, CISPA Helmholtz Center for Information Security Ramya Jayaram Masti, Intel Bruno Crispo, University of Trento Yuseok Jeon, UNIST (Ulsan National Institute of Science Weidong Cui, Microsoft Research and Technology) Anupam Das, North Carolina State University Yier Jin, University of Florida Pubali Datta, University of Illinois at Urbana–Champaign Brent Byunghoon Kang, Korea Advanced Institute of Science Nathan Dautenhahn, Rice University and Technology (KAIST) Alexandra Dmitrienko, University of Wuerzburg Chris Kanich, University of Illinois at Chicago Adam Doupe, Arizona State University Apu Kapadia, Indiana University Bloomington Tudor Dumitras, University of Maryland Alexandros Kapravelos, North Carolina State University Zakir Durumeric, Stanford University Vasileios Kemerlis, Brown University Manuel Egele, Boston University Florian Kerschbaum, University of Waterloo Thomas Eisenbarth, University of Lübeck Taesoo Kim, Georgia Institute of Technology Mary Ellen Zurko, MIT Lincoln Laboratory Yongdae Kim, Korea Advanced Institute of Science and Mohamed Elsabagh, Kryptowire Technology (KAIST) Pardis Emami-Naeini, University of Washington Sam King, University of California, Davis and Bouncer Technologies William Enck, North Carolina State University Michel Kinsy, TAMU Roya Ensafi, University of Michigan Engin Kirda, Northeastern University Birhanu Eshete, University of Michigan Katharina Kohls, Radboud University Saba Eskandarian, The University of North Carolina at Chapel Hill Tadayoshi Kohno, University of Washington Sascha Fahl, CISPA Helmholtz Center for Information Security Kari Kostiainen, ETH Zurich Kassem Fawaz, University of Wisconsin—Madison Srikanth Krishnamurthy, University of California, Riverside Yunsi Fei, Northeastern University Joshua A Kroll, Naval Postgraduate School
Katharina Krombholz, CISPA Helmholtz Center for Paul Pearce, Georgia Institute of Technology, International
Information Security Computer Science Institute (ICSI)
Christopher Kruegel, University of California, Santa Barbara Giancarlo Pellegrino, CISPA Helmholtz Center for
Deepak Kumar, Stanford University Information Security
Anil Kurmus, IBM Research Europe Roberto Perdisci, University of Georgia and Georgia Institute
Andrea Lanzi, University of Milan of Technology
Pavel Laskov, University of Liechtenstein Radia Perlman, Dell EMC
Byoungyoung Lee, Seoul National University Peter Peterson, University of Minnesota
Kyu Hyung Lee, University of Georgia Fabio Pierazzi, King’s College London
Sangho Lee, Microsoft Research Christina Poepper, New York University Abu Dhabi
Wenke Lee, Georgia Institute of Technology Niels Provos, Stripe
Tancrède Lepoint, Google Amir Rahmati, Stony Brook University
Ada Lerner, Wellesley College Jeyavijayan Rajendran, Texas A&M University
Frank Li, Georgia Institute of Technology Sara Rampazzi, University of Florida
Qi Li, Tsinghua University Mariana Raykova, Google
Tianshi Li, Carnegie Mellon University Joel Reardon, University of Calgary
David Lie, University of Toronto Bradley Reaves, North Carolina State University
Zhiqiang Lin, Ohio State University Elissa Redmiles, Max Planck Institute for Software Systems
(MPI-SWS)
Martina Lindorfer, TU Wien
Michael K. Reiter, Duke University
Guyue Liu, Carnegie Mellon University
Konrad Rieck, Technische Universität Braunschweig
Kangjie Lu, University of Minnesota
William Robertson, Northeastern University
Wouter Lueks, EPFL
Franziska Roesner, University of Washington
Xiapu Luo, The Hong Kong Polytechnic University
Eyal Ronen, Tel Aviv University
Matteo Maffei, TU Wien
Stefanie Roos, TU Delft
Stefan Mangard, Graz University of Technology
Ahmad-Reza Sadeghi, Technische Universität Darmstadt
Mohammad Mannan, Concordia University
Brendan Saltaformaggio, Georgia Institute of Technology
Ivan Martinovic, Oxford University
Nitesh Saxena, University of Alabama at Birmingham
Michelle Mazurek, University of Maryland
Sebastian Schinzel, Münster University of Applied Sciences
Patrick McDaniel, The Pennsylvania State University
Michael Schwarz, CISPA Helmholtz Center for Information Security
Shagufta Mehnaz, Dartmouth College
Jörg Schwenk, Ruhr University Bochum
Aastha Mehta, University of British Columbia, Vancouver
Wendy Seltzer, W3C and Massachusetts Institute of Technology
Sarah Meiklejohn, University College London and Google
Johanna Sepulveda, Airbus
Marcela Melara, Intel Labs
Mahmood Sharif, Tel Aviv University and VMware
Nele Mentens, Leiden University and Katholieke Universiteit Leuven
Imani N. Sherman, University of Florida
Jiang Ming, The University of Texas at Arlington
Shweta Shinde, ETH Zurich
Ariana Mirian, University of California, San Diego
Fatemeh Shirazi, Web3 Foundation
Jelena Mirkovic, University of Southern California
Maliheh Shirvanian, Visa Research
Daniel Moghimi, University of California, San Diego
Yan Shoshitaishvili, Arizona State University
Esfandiar Mohammadi, University of Lübeck
Haya Shulman, Fraunhofer SIT
Mainack Mondal, Indian Institute of Technology, Kharagpur
Peter Snyder, Brave Browser
Soo-Jin Moon, Google
Sooel Son, Korea Advanced Institute of Science and
Veelasha Moonsamy, Ruhr University Bochum Technology (KAIST)
Thomas Moyer, University of North Carolina Chengyu Song, University of California, Riverside
Marius Muench, Vrije Universiteit Amsterdam Alessandro Sorniotti, IBM Research Europe
Takao Murakami, AIST Kyle Soska, University of Illinois at Urbana–Champaign
Toby Murray, University of Melbourne Michael Specter, Massachusetts Institute of Technology
Nick Nikiforakis, Stony Brook University Drew Springall, Auburn University
Anita Nikolich, University of Illinois at Urbana–Champaign Jessica Staddon, JPMorgan Chase
Shirin Nilizadeh, The University of Texas at Arlington Emily Stark, Google
Adam Oest, PayPal Angelos Stavrou, Virginia Tech
Hamed Okhravi, MIT Lincoln Laboratory Deian Stefan, University of California, San Diego
Melek Önen, EURECOM Ben Stock, CISPA Helmholtz Center for Information Security
Cristina Onete, University of Limoges/XLIM/CNRS 7252 Gianluca Stringhini, Boston University
Yossi Oren, Ben-Gurion University of the Negev Yixin Sun, University of Virginia
Rebekah Overdorf, EPFL Yuqiong Sun, Facebook
Miroslav Pajic, Duke University Qiang Tang, The University of Sydney
Dimitrios Papadopoulos, The Hong Kong University of Science Dave ( Jing) Tian, Purdue University
and Technology
Yuan Tian, University of Virginia
Bryan Parno, Carnegie Mellon University
Nils Ole Tippenhauer, CISPA Helmholtz Center for
Mathias Payer, EPFL Information SecurityAlin Tomescu, VMware Research Symposium Topics
Shruti Tople, Microsoft Research Refereed paper submissions are solicited in all areas relating
Santiago Torres-Arias, Purdue University to systems research in security and privacy, including but not
Florian Tramèr, Stanford University limited to:
Patrick Traynor, University of Florida
Carmela Troncoso, EPFL
• System security
° Operating systems security
Güliz Seray Tuncay, Google
Selcuk Uluagac, Florida International University ° Web security
Blase Ur, University of Chicago ° Mobile systems security
Anjo Vahldiek-Oberwagner, Intel Labs ° Distributed systems security
Michel van Eeten, Delft University of Technology ° Cloud computing security
Mayank Varia, Boston University • Network security
Ingrid Verbauwhede, Katholieke Universiteit Leuven ° Intrusion and anomaly detection and prevention
Luca Viganò, King’s College London ° Network infrastructure security
Hayawardh Vijayakumar, Samsung Research America ° Denial-of-service attacks and countermeasures
Bimal Viswanath, Virginia Tech ° Wireless security
Daniel Votipka, Tufts University
David Wagner, University of California, Berkeley
• Security analysis
° Malware analysis
Michael Waidner, Technische Universität Darmstadt
° Analysis of network and security protocols
Gang Wang, University of Illinois at Urbana–Champaign
Ting Wang, The Pennsylvania State University ° Attacks with novel insights, techniques, or results
XiaoFeng Wang, Indiana University Bloomington ° Forensics and diagnostics for security
Michael Weissbacher, Square, Inc. ° Automated security analysis of hardware designs and
implementation
Tara Whalen, Carleton University
Christian Wressnegger, Karlsruhe Institute of Technology (KIT) ° Automated security analysis of source code and binaries
Matthew Wright, Rochester Institute of Technology ° Program analysis
Eric Wustrow, University of Colorado Boulder • Machine learning security and privacy
Jason (Minhui) Xue, The University of Adelaide • Data-driven security and measurement studies
Daphne Yao, Virginia Tech ° Measurements of fraud, malware, spam
Yuval Yarom, The University of Adelaide and Data61 ° Measurements of human behavior and security
Tuba Yavuz, University of Florida • Privacy-enhancing technologies and anonymity
Yanfang (Fanny) Ye, Case Western Reserve University
Heng Yin, University of California, Riverside
• Usable security and privacy
Qiang Zeng, University of South Carolina
• Language-based security
Sarah Zennou, Airbus
• Hardware security
Fengwei Zhang, Southern University of Science and ° Secure computer architectures
Technology (SUSTech) ° Embedded systems security
Xiangyu Zhang, Purdue University ° Methods for detection of malicious or counterfeit
Yang Zhang, CISPA Helmholtz Center for Information Security hardware
Yuan Zhang, Fudan University ° Side channels
Wenting Zheng, Carnegie Mellon University • Research on surveillance and censorship
Yajin Zhou, Zhejiang University • Social issues and security
Haojin Zhu, Shanghai Jiao Tong University ° Research on computer security law and policy
Steering Committee ° Ethics of computer security research
Michael Bailey, University of Illinois at Urbana–Champaign ° Research on security education and training
Matt Blaze, University of Pennsylvania ° Information manipulation, misinformation, and
Dan Boneh, Stanford University disinformation
Srdjan Capkun, ETH Zurich ° Protecting and understanding at-risk users
William Enck, North Carolina State University ° Emerging threats, harassment, extremism, and
Kevin Fu, University of Michigan online abuse
Rachel Greenstadt, New York University • Applications of cryptography
Casey Henderson, USENIX Association ° Analysis of deployed cryptography and cryptographic
Nadia Heninger, University of California, San Diego protocols
Thorsten Holz, Ruhr-Universität Bochum ° Cryptographic implementation analysis
Engin Kirda, Northeastern University
° New cryptographic protocols with real-world
Tadayoshi Kohno, University of Washington applications
Thomas Ristenpart, Cornell Tech This topic list is not meant to be exhaustive; USENIX Security is
Franziska Roesner, University of Washington interested in all aspects of computing systems security and pri-
Patrick Traynor, University of Florida vacy. Papers without a clear application to security or privacy of
David Wagner, University of California, Berkeley computing systems, however, will be considered out of scope
and may be rejected without full review.Refereed Papers Lightning Talks
Papers that have been formally reviewed and accepted will Information about lightning talks will be available soon.
be presented during the Symposium and published in the
Birds-of-a-Feather Sessions (BoFs)
Symposium Proceedings. By submitting a paper, you agree
that at least one of the authors will attend the conference to Birds-of-a-Feather sessions (BoFs) will be held Tuesday,
present it. Alternative arrangements will be made if global Wednesday, and Thursday evenings. Birds-of-a-Feather
health concerns persist. If the conference registration fee will sessions are informal gatherings of persons interested in a
pose a hardship for the presenter of the accepted paper, particular topic. BoFs often feature a presentation or a demon-
please contact conference@usenix.org. stration followed by discussion, announcements, and the shar-
ing of strategies. BoFs can be scheduled on-site or in advance.
A major mission of the USENIX Association is to provide for the To schedule a BoF, please send an email to the USENIX Confer-
creation and dissemination of new knowledge. In keeping with ence Department at bofs@usenix.org with the title and a brief
this and as part of USENIX’s open access policy, the Proceed- description of the BoF; the name, title, affiliation, and email
ings will be available online for registered attendees before the address of the facilitator; and your preference of date and time.
Symposium and for everyone starting on the opening day of the
technical sessions. USENIX also allows authors to retain owner- Submission Policies
ship of the copyright in their works, requesting only that USENIX Important: The USENIX Security Symposium moved to multiple
be granted the right to be the first publisher of that work. See submission deadlines in 2019 and included changes to the review
our sample consent form at www.usenix.org/sample_consent_ process and submission policies. Detailed information is available
form.pdf for the complete terms of publication. at USENIX Security Publication Model Changes at www.usenix.org/
Go to Paper Submission Policies and Instructions page at www. conference/usenixsecurity22/publication-model-change.
usenix.org/conference/usenixsecurity22/submission-policies- USENIX Security ’22 submissions deadlines are as follows:
and-instructions for more information.
• Summer Deadline: Tuesday, June 8, 2021, 11:59 pm AoE
Artifact Evaluation • Fall Deadline: Tuesday, October 12, 2021, 11:59 pm AoE
The Call for Artifacts will be available soon. • Winter Deadline: Tuesday, February 1, 2022, 11:59 pm AoE
All papers that are accepted by the end of the winter submis-
Symposium Activities sion reviewing cycle (February–May 2022) will appear in the
Invited Talks, Panels, Poster Session, Lightning Talks, and BoFs proceedings for USENIX Security ’22. All submissions will be
In addition to the refereed papers and the keynote presenta- made online via their respective web forms, linked from the
tion, the technical program will include invited talks, panel USENIX Security ’22 Call for Papers web page: Summer Dead-
discussions, a poster session, and Birds-of-a-Feather sessions line, Fall Deadline, Winter Deadline. Do not email submissions.
(BoFs). You are invited to make suggestions regarding topics Submissions should be finished, complete papers, and we
or speakers in any of these sessions via email to the contacts may reject papers without review that have severe editorial
listed below or to the program co-chairs at sec22chairs@ problems (broken references, egregious spelling or grammar
usenix.org. errors, missing figures, etc.) or are submitted in violation of the
Submission Instructions outlined below.
Invited Talks and Panel Discussions
Invited talks and panel discussions will be held in parallel with All paper submissions, including Major Revisions, should be at
the refereed paper sessions. Please submit topic suggestions most 13 typeset pages, excluding bibliography and well-marked
and talk and panel proposals via email to sec22it@usenix.org appendices. These appendices may be included to assist
by February 1, 2022. reviewers who may have questions that fall outside the stated
contribution of the paper on which your work is to be evaluated
Poster Session or to provide details that would only be of interest to a small
Would you like to share a provocative opinion, an interesting minority of readers. There is no limit on the length of the bibli-
preliminary work, or a cool idea that will spark discussion at this ography and appendices but reviewers are not required to read
year’s USENIX Security Symposium? The poster session is the any appendices so the paper should be self-contained without
perfect venue to introduce such new or ongoing work. Poster them. Once accepted, papers must be reformatted to fit in 18
presenters will have the entirety of the evening reception to pages, including the bibliography and any appendices.
discuss their work, get exposure, and receive feedback from Papers should be typeset on U.S. letter-sized pages in two-
attendees. column format in 10-point Times Roman type on 12-point
To submit a poster, please submit a draft of your poster, in leading (single-spaced), in a text block 7” x 9” deep. Authors are
PDF (maximum size 36” by 48”), or a one-page abstract via encouraged to make use of USENIX’s LaTeX template and style
the poster session submission form, linked from the USENIX files available at www.usenix.org/paper-templates when pre-
Security ’22 Call for Papers web page, by July 6, 2022. Decisions paring your paper for submission. Failure to adhere to the page
will be made by July 13, 2022. Posters will not be included in the limit and formatting requirements can be grounds for rejection.
proceedings but may be made available online if circumstances Papers should not attempt to “squeeze space” by exploiting
permit. Poster submissions must include the authors’ names, underspecified formatting criteria (e.g., columns) or through
affiliations, and contact information. At least one author of manipulating other document properties (e.g., page layout,
each accepted poster must register for and attend the Sympo- spacing, fonts, figures and tables, headings). Papers that, in the
sium to present the poster. chair’s assessment, make use of these techniques to receive an
unfair advantage, will be rejected, even if they comply with the
above specifications.Please make sure your paper successfully returns from the • Authors should carefully review figures and appendices
PDF checker (visible upon PDF submission) and that document (especially survey instruments) to ensure affiliations are not
properties, such as font size and margins, can be verified via accidentally included.
PDF editing tools such as Adobe Acrobat. Papers where the • When referring to your previous work, do so in the third
chairs can not verify compliance with the CFP will be rejected. person, as though it were written by someone else. Only
blind the reference itself in the (unusual) case that a third-
Prepublication of Papers
person reference is infeasible.
Prepublication versions of papers accepted for USENIX Secu-
rity ’22 will be published and open and accessible to everyone • Authors may include links to websites that contain source
code, tools, or other supplemental material. Neither the
without restrictions on the following dates:
link in the paper nor the website itself should contain the
• Summer Deadline: Tuesday, November 9, 2021 authors’ names or affiliations.
• Fall Deadline: Tuesday, April 5, 2022 Papers that are not properly anonymized may be rejected
• Winter Deadline: TBD (final papers will be published with the without review.
full conference proceedings) While submitted papers must be anonymous, authors may
Embargo Requests choose to give talks about their work, post a preprint of the
Authors may request an embargo for their papers by the dead- paper online, disclose security vulnerabilities to vendors or the
line dates listed below. All embargoed papers will be released public, etc. during the review process.
on the first day of the conference, Wednesday, August 10, 2022. Facebook Internet Defense Prize
• Summer Deadline: Tuesday, November 2, 2021 The Internet Defense Prize recognizes and rewards research
• Fall Deadline: Tuesday, March 29, 2022 that meaningfully makes the internet more secure. Created in
• Winter Deadline: Tuesday, July 12, 2022 2014, the award is funded by Facebook and offered in partner-
ship with USENIX to celebrate contributions to the protection
Conflicts of Interest and defense of the internet. Successful recipients of the Inter-
The program co-chairs require cooperation from both authors net Defense Prize will provide a working prototype that demon-
and program committee members to prevent submissions strates significant contributions to the security of the internet,
from being evaluated by reviewers who have a conflict of particularly in the areas of prevention and defense. This award
interest. During the submission process, we will ask authors to is meant to recognize the direction of the research and not
identify members of the program committee with whom they necessarily its progress to date. The intent of the award is to
share a conflict of interest. This includes: (1) anyone who shares inspire researchers to focus on high-impact areas of research.
an institutional affiliation with an author at the time of submis-
You may submit your USENIX Security ’22 paper submission for
sion, (2) anyone who was the advisor or advisee of an author at
consideration for the Prize as part of the regular submission
any time in the past, (3) anyone the author has collaborated or
process. Find out more about the Internet Defense Prize at
published within the prior two years, (4) anyone who is serv-
www.internetdefenseprize.org.
ing as the sponsor or administrator of a grant that funds your
research, or (5) close personal friendships. For other forms Human Subjects and Ethical Considerations
of conflict, authors must contact the chairs and explain the Submissions that describe experiments on human subjects,
perceived conflict. that analyze data derived from human subjects (even anony-
Program committee members who are conflicts of interest with mized data), or that otherwise may put humans at risk should:
a paper, including program co-chairs, will be excluded from 1. Disclose whether the research received an approval or
both online and in-person evaluation and discussion of the waiver from each of the authors’ institutional ethics review
paper by default. boards (e.g., an IRB).
Early Rejection Notification 2. Discuss steps taken to ensure that participants and others
The review process will consist of several reviewing rounds. In who might have been affected by an experiment were
order to allow authors time to improve their work and submit treated ethically and with respect.
to other venues, authors of submissions for which there is a If the submission deals with vulnerabilities (e.g., software
consensus on rejection will be notified earlier. vulnerabilities in a given program or design weaknesses in a
hardware system), the authors need to discuss in detail the
Author Responses steps they have already taken or plan to take to address these
Authors of papers that have not been rejected early will have vulnerabilities (e.g., by disclosing vulnerabilities to the vendors).
an opportunity to respond to an initial round of reviews. We en- The same applies if the submission deals with personally
courage authors to focus on questions posed by reviewers and identifiable information (PII) or other kinds of sensitive data. If
significant factual corrections. Once reviews are released to a paper raises significant ethical and legal concerns, it might be
authors for rebuttal, we will not process requests to withdraw rejected based on these concerns.
the paper and the paper will be viewed as under submission
Contact the program co-chairs at sec22chairs@usenix.org if
until the end of the cycle.
you have any questions.
Anonymous Submission
The review process will be double-blind. Papers must be
submitted in a form suitable for anonymous review:
• The title page should not contain any author names or
affiliations.Reviews from Prior Submissions Note that under the changes to the USENIX Security publication
Drawn from the ACM CCS 2020 CFP, IEEE S&P 2021 model, papers that have received a decision of Major Revisions
For papers that were previously submitted to, and rejected from USENIX Security are still considered to be under review
from, another conference, authors are required to submit a for the following two review cycles after notification; authors
separate document containing the prior reviews along with a must formally withdraw their paper if they wish to submit to
description of how those reviews were addressed in the current another venue. See USENIX Security Publication Model Changes
version of the paper. Authors are only required to include re- at www.usenix.org/conference/usenixsecurity22/publication-
views from the last time the paper was submitted. This includes model-change for details. For submissions that received Reject
withdrawn papers (if reviews were received) as well as papers or Reject and Resubmit decisions from USENIX Security ’21,
whose last submission was at USENIX. Reviewers will be asked resubmissions must follow the rules laid out for when they can
to complete their reviews before reading the provided supple- be resubmitted (i.e., not in the next deadline for Reject and
mentary material to avoid being biased in formulating their own Resubmit, and not in the next two deadlines for Reject).
opinions; once their reviews are complete, however, reviewers Questions? Contact your program co-chairs, sec22chairs@
will be given the opportunity to provide additional comments usenix.org, or the USENIX office, submissionspolicy@usenix.org.
based on the submission history of the paper. Authors who try
The program committee and external reviewers are required to
to circumvent this rule (e.g., by changing the title of the paper
treat all submissions as confidential. However, the program co-
without significantly changing the contents) may have their
chairs or designated committee members may share submis-
papers rejected without further consideration, at the discretion
sions outside the program committee to allow chairs of other
of the PC chairs.
conferences to identify dual submissions.
Submission Instructions Papers that do not comply with the submission requirements,
All submissions will be made online via their respective web including length and anonymity, that do not comply with
forms. Do not email submissions. Submissions must be in PDF resubmission policies, or that do not have a clear application
format. LaTeX users can use the “pdflatex” command to convert to security or privacy may be rejected without review. Papers
a LaTeX document into PDF format. Please make sure your sub- accompanied by nondisclosure agreement forms will not be
mission can be opened using Adobe Reader. Please also make considered.
sure your submission, and all embedded figures, are intelligible Each accepted submission may be assigned a member of the
when printed in grayscale. program committee to act as its shepherd through the prepa-
For resubmissions of Major Revisions, authors must submit a ration of the final paper. The assigned member will act as a
separate PDF that includes the verbatim Major Revision criteria, conduit for feedback from the committee to the authors.
a list of changes to the paper, and a statement of how the All papers will be available online before the symposium. If your
changes address the review comments. While not required, accepted paper should not be published prior to the event,
authors are strongly encouraged to submit as part of the PDF a please notify production@usenix.org after you submit your
“PDF ‘diff’” to assist reviewers in identifying your modifications. final paper. See the Embargo Requests section for deadlines.
For papers that were previously submitted to, and rejected
from, another conference, the required document (see Reviews Specific questions about submissions may be sent to the
from Prior Submissions above) should be submitted as a PDF program co-chairs at sec22chairs@usenix.org. The chairs will
file using the “Prior Reviews” field in the submission forms, not respond to individual questions about the submission process
via an appendix. if contacted at least a week before the submission deadline.
All submissions will be judged on originality, relevance, cor-
rectness, and clarity. In addition to citing relevant published
work, authors should relate their submission to any other
relevant submissions of theirs in other venues that are under
review at the same time as their submission to the Symposium.
These citations to simultaneously submitted papers should be
anonymized; non-anonymous versions of these citations must,
however, be emailed to the program co-chairs at sec22chairs@
usenix.org. Simultaneous submission of the same work to
multiple venues, submission of previously published work, or
plagiarism constitutes dishonesty or fraud. Failure to point out
and explain overlap will be grounds for rejection. USENIX, like
other scientific and technical conferences and journals, prohib-
its these practices and may take action against authors who
have committed them. See the USENIX Conference Submissions
Policy at www.usenix.org/submissions-policy for details.You can also read
