Skip to main content

PDF CFPCall for Papers

Deadline: June 23 June 28 (23:59:59 Anywhere on Earth)
Notification: August 19 August 25, with early reject notifications tentatively sent by July 25
Final Papers Due: October 16

Program Chair: Heng Yin, UC Riverside
Program Co-Chair: Gabriela Ciocarlie, The University of Texas at San Antonio
Artifacts Evaluation Co-Chair: Martina Lindorfer, TU Wien
Artifacts Evaluation Co-Chair: Gianluca Stringhini, Boston University

We solicit papers offering novel contributions in any aspect of applied security. Papers are encouraged on results that have been demonstrated to be useful for improving information systems security and that address lessons learned from the actual application, especially those related to our hard topic theme — Deployable and Impactful Security. Submitted papers must not substantially overlap papers that have been published or that are simultaneously submitted to a journal or a conference with proceedings.

ACSAC encourages authors of accepted papers to submit software and data artifacts and make them publicly available to the entire community. While authors can choose to submit artifacts after the papers get accepted, they are encouraged to submit artifacts early, immediately after their papers advance to the second round. Good artifacts will contribute positively to the paper evaluation.

If human subjects are involved in the submission, authors need to discuss in the paper how the ethical concerns are addressed. If an impactful vulnerability is reported in the paper, the author should discuss their plan for responsible disclosure. The chairs will contact the authors in case of major concerns and may reject a submission if ethical concerns are not sufficiently addressed.

(printable call for papers)

What format should the paper be in?

Please ensure that your submission is a PDF file of a maximum of 10 2-column pages, excluding well-marked references and appendices limited to 5 pages. Submissions must be generated using the 2-column ACM acmart template available at, using the [sigconf, anonymous] options. Submissions should not use older ACM templates (e.g., sig-alternate). Committee members are not required to read the appendices. All submissions must be anonymous (i.e., papers should not contain author names or affiliations, or obvious citations). In the rare case that citing previous work in the 3rd person is impossible, blind the reference and notify the Program Chairs.

Both of these constraints (page limit and anonymity) are hard constraints. Submissions not meeting these guidelines risk rejection without consideration of their merits.

What should I propose a paper on?

If you are developing practical solutions to problems relating to protecting commercial enterprises' or countries' information infrastructures, consider submitting your work to the Annual Computer Security Applications Conference. We are especially interested in submissions that address the application of security technology, the implementation of systems, and lessons learned. Special consideration will be given to papers that discuss system implementation, deployment, and lessons learned.

What makes a good ACSAC paper?

We've gone through the papers submitted in recent years, and have collected a set of characteristics of good ACSAC papers. These should be read by anyone considering submitting a paper.

Do you have any other advice regarding writing papers?

Yes, they are enumerated here. This advice covers presentation, copyright issues, alternate places at ACSAC for your submission, and restrictions on submissions.

What awards are given for papers?

Accepted papers will be judged by the program committee and two papers will be given a Distinguished Paper Award at the conference.

Who is on the Program Committee?

The list of program committee members may be found here.

How do I submit a paper?

How do I get more information?

For additional information regarding papers, please contact the Program Chair.