- Security '12 Home
- Registration Information
- Registration Discounts
- At a Glance
- Technical Sessions
- Hotel & Travel Information
- Poster Session
- Rump Session
- Birds-of-a-Feather Sessions
- For Participants
- Help Promote
- Call for Papers
- Past Proceedings
How and Where to Submit Refereed Papers
Important: Note that some past USENIX Security Symposiums have had different anonymity policies and page limits.
Papers are due by Thursday, February 16, 2012, at 11:59 p.m. PST (firm deadline). All submissions will be made online via the Web form. Submissions should be finished, complete papers.
Paper submissions should at most 13 typeset pages, excluding bibliography and well-marked appendices. There is no limit on the length of the bibliography and appendices, but reviewers are not required to read them. Once accepted, papers must be reformatted to fit in 16 pages, including bibliography and any appendices. The submission must be formatted in 2 columns, using 10 point Times Roman type on 12 point leading, in a text block of 6.5" by 9", on 8.5"x11" (letter-sized) paper. If you wish, please make use of this LaTeX file and style file when preparing your paper for submission.
Paper submissions must be submitted in a form suitable for anonymous review: no author names or affiliations may appear on the title page, and authors should avoid revealing their identity in the text. When referring to your previous work, do so in the third person, as though it were written by someone else. Only blind the reference itself in the (unusual) case that a third-person reference is infeasible. Contact the program chair at firstname.lastname@example.org if you have any questions.
Papers that do not comply with the submission requirements, including length and anonymity, may be rejected without review.
Submissions must be in PDF format. LaTeX users can use the "pdflatex" command to convert a LaTeX document into PDF format. Please make sure your submission can be opened using Adobe Reader. Please also make sure your submission, and all embedded figures, are intelligible when printed in grayscale.
All submissions will be judged on originality, relevance, correctness, 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 chair at email@example.com. Simultaneous submission of the same work to multiple venues, submission of previously published work, or plagiarism constitutes dishonesty or fraud. USENIX, like other scientific and technical conferences and journals, prohibits these practices and may take action against authors who have committed them. See the USENIX Conference Submissions Policy for details. Questions? Contact your program chair, firstname.lastname@example.org, or the USENIX office, email@example.com.
Papers accompanied by nondisclosure agreement forms will not be considered. Accepted submissions will be treated as confidential prior to publication on the USENIX Security '12 Web site; rejected submissions will be permanently treated as confidential.
Authors will be notified of acceptance by Tuesday, April 24, 2012. The final paper due date is Tuesday, June 19, 2012 (firm deadline). Each accepted submission may be assigned a member of the program committee to act as its shepherd through the preparation of the final paper. The assigned member will act as a conduit for feedback from the committee to the authors.
All papers will by default be available online to registered attendees before the symposium. If your accepted paper should not be published prior to the event, please notify firstname.lastname@example.org. The papers will be available online to everyone beginning on the first day of the symposium, August 8, 2012.
Specific questions about submissions may be sent to the program chair at email@example.com.