CCS: Computer and Communications Security



Past:   Proceedings on DBLP

Future:  Post a CFP for 2025 or later   |   Invite the Organizers Email


All CFPs on WikiCFP

Event When Where Deadline
CCS 2024 ACM Conference on Computer and Communications Security 2024 - first deadline
Oct 14, 2024 - Oct 18, 2024 Salt Lake City, U.S.A. Jan 28, 2024
CCS 2023 30th ACM Conference on Computer and Communications Security
Nov 26, 2023 - Nov 30, 2023 Copenhagen, Denmark May 4, 2023
CCS 2021 ACM CCS 2021 : ACM Conference on Computer and Communications Security (1st Cycle)
Nov 14, 2021 - Nov 19, 2021 Seoul, South Korea Jan 20, 2021
CCS 2019 26th ACM Conference on Computer and Communications Security
Nov 11, 2019 - Nov 15, 2019 London Feb 5, 2019
CCS 2017 The ACM Conference on Computer and Communications Security (CCS)
Oct 30, 2017 - Nov 3, 2017 Dallas, USA May 19, 2017
CCS 2016 23rd ACM Conference on Computer and Communications Security
Oct 24, 2016 - Oct 28, 2016 Vienna, Austria TBD
CCS 2015 22nd ACM Conference on Computer and Communications Security
Oct 12, 2015 - Oct 16, 2015 Denver, Colorado, US May 15, 2015
CCS 2013 ACM Conference on Computer and Communications Security
Nov 4, 2013 - Nov 8, 2013 Berlin, Germany May 8, 2013
CCS 2012 ACM Conference on Computer and Communications Security
Oct 16, 2012 - Oct 18, 2012 Raleigh, NC May 4, 2012
CCS 2011 ACM Conference on Computer and Communications Security
Oct 17, 2011 - Oct 21, 2011 Chicago, IL May 6, 2011
CCS 2010 17th ACM Conference on Computer and Communications Security
Oct 4, 2010 - Oct 8, 2010 Chicago, IL Apr 17, 2010
CCS 2009 16th ACM Conference on Computer and Communications Security
Nov 9, 2009 - Nov 13, 2009 Chicago, IL Apr 20, 2009
CCS 2008 15th ACM Conference on Computer and Communications Security 2008
Nov 3, 2008 - Nov 7, 2008 Alexandria, VA, USA Apr 14, 2008
CCS 2007 14th ACM Conference on Computer and Communications Security 2007
Oct 29, 2007 - Nov 2, 2007 Alexandria, VA, USA May 8, 2007

Present CFP : 2024

Call for papers

The 31th ACM Conference on Computer and Communications Security (CCS) seeks submissions presenting novel contributions related to all real-world aspects of computer security and privacy. Theoretical papers must make a convincing case for the relevance of their results to practice. Authors are encouraged to write the abstract and introduction of their paper in a way that makes the results accessible and compelling to a general computer-security researcher. In particular, authors should bear in mind that anyone on the program committee may be asked to review any paper.

CCS has two review cycles in 2024. For each submission, one of the following decisions will be made:

Accept: Papers in this category will be accepted for publication in the proceedings and presentation at the conference, possibly after making minor changes with the oversight of a shepherd.
Minor revision: Papers in this category are considered to be promising but need some minor additional work (e.g., minor experiments, proofs to minor lemmas). Authors will be given the opportunity to resubmit such papers, with appropriate revisions, in which case they should clearly explain in a separate note how the revisions address the comments of the reviewers. The revised paper will then be re-evaluated, and either accepted or rejected.
Reject: Papers in this category are declined for inclusion in the conference. Papers rejected from the first review cycle may not be submitted again (even in revised form) to the second review cycle.

Authors of each accepted paper must ensure that at least one author registers for the conference, and that their paper is presented in-person at the conference if at all possible.
Paper Submission Information

All submissions must be received by 11:59 PM AoE (UTC-12) on the day of the corresponding deadline. Submitted papers must not substantially overlap with papers that have been published or accepted for publication, or that are simultaneously in submission to a journal, conference, or workshop with published proceedings. All submissions should be properly anonymized; papers not properly anonymized may be rejected without review.

All submitted papers will be evaluated based on their merits, particularly their importance to practical aspects of computer and communications security and privacy, novelty, quality of execution, and presentation. For papers that might raise ethical concerns, authors are expected to convince reviewers that proper procedures (such as IRB approval or responsible disclosure) have been followed, and due diligence has been made to minimize potential harm.

Submitted papers may be rejected for being out of scope, at the discretion of the PC chairs. Authors who have questions about whether their paper is in scope are encouraged to ask the PC chairs in advance. No modifications to the author list on a paper may be made after submission.
Paper Format

Submissions must be a PDF file in double-column ACM format, no more than 12 pages long, excluding the bibliography, well-marked appendices, and supplementary material. Note that reviewers are not required to read the appendices or any supplementary material. Authors should not change the font or the margins of the ACM format. Submissions not following the required format may be rejected without review.
Providing Artifacts at Submission Time

Submissions whose claimed contributions rely on artifacts (e.g., code, models, data sets) are expected to make these accessible to the reviewers, unless there are good reasons not to, in which case these reasons must be mentioned in the submission. Submissions whose claimed contributions do not rely on artifacts do not need to submit artifacts. An anonymous link to a resource on the web is acceptable, provided the contents in the resource are also anonymized.
Optional Artifact Evaluation

A published scientific paper consists of a constellation of artifacts that extend beyond the document itself: software, hardware, evaluation data and documentation, raw survey results, mechanized proofs, models, test suites, benchmarks, and so on. To emphasize the importance of such artifacts, the benefits to the authors and the community as a whole, and promote the reproducibility of experimental results, ACM CCS will, for the second time, introduce an optional artifact evaluation (AE) process, inspired by similar efforts at several other conferences. All authors of accepted papers (including shepherd approved and minor revisions) are encouraged to submit artifacts for AE. Each artifact submitted will be reviewed by the Artifact Evaluation Committee (AEC); a special call for artifacts will follow.
Conference Tracks

Like last year, the ACM CCS Conference features a multi-track format. Each track operates as a separate mini-conference, with its own Track Chairs and Track Program Committee. The overall process is managed by the Program Chairs (David Lie and Engin Kirda). At the time of submission, authors must select one track, which should be the most relevant to the topic of the paper. We understand that some papers might span multiple topics. In specific cases, PC members might be asked to provide reviews for papers outside their track, in an effort to provide the best possible reviews to the authors. The chairs may decide to move a paper to another track.

This is the list of tracks and their Track Chairs:
Program Co-Chairs

David Lie (University of Toronto)
Engin Kirda (Northeastern University)

Track Chairs

Software Security
Yuan Tian (UCLA)
Web Security
Jason Polakis (University of Illinois, Chicago)
Network Security
Aanjhan Ranganathan (Northeastern University)
Formal Methods and Programming Languages
Catalin Hritcu (MPI SP)
Hardware, Side Channels, and Cyber Physical Systems
Yinqian Zhang (Southern University of Science and Technology)
Applied Cryptography
Melek Onen (Institut Eurecom)
Katerina Mitrokotsa (University of St. Gallen)
Machine Learning and Security
Reza Shokri (University of Singapore)
Murat Kantarcioglu (UT Dallas)
Security Usability and Measurement
Blase Ur (University of Chicago)
Gianluca Stringhini (Boston University)
Blockchain and Distributed Systems
Stefanie Roos (TU Delft)
Privacy and Anonymity
Wouter Loueks (CISPA)

Conflicts of Interest

The conference requires cooperation from both authors and program-committee members to ensure a fair review process. For this purpose, authors must report all program-committee members who, in their opinion, have a conflict of interest and therefore may not be able to provide an unbiased review. Mandatory declared conflicts of interest include current or former doctoral advisor/advisee, members of the same institution, close family members, and recent co-authors (within the past 2 years). For any other declared conflict, authors are required to explain the nature of the conflict, which will be reviewed by the Program Chairs and the Track Chairs. The chairs reserve the right to request further explanation and can remove non-mandatory conflicts at their discretion.

Track Chairs are allowed to submit papers, and those papers will be handled by the Program Chairs. They are only allowed to submit two papers in their own track, and any number in other tracks.

Program-committee members who have a genuine conflict of interest with a paper, including the Program Chairs and the Track Chairs, will be excluded from evaluation and discussion of that paper. When a Track Program Chair has a conflict, the paper will be handled by the Program Chairs. When a Program Chairs is conflicted, the other Co-Chair will be responsible for managing that paper. When both Program Chairs are in conflict, a committee member will be appointed to handle the paper. Program Chairs are not allowed to be authors or co-authors of any submissions.
Policy for Peer-Review Integrity

All SIGSAC sponsored conferences and workshops are required to follow ACM policies against harassment activities ( and ACM Code of Ethics and Professional Conduct ( Also all authors, PC members and non-PC reviewers are required to follow ACM Publications Policies ( Particularly, we require all reviewers to uphold the integrity of the peer review process and avoid conflict of interest of any form (e.g., reviewer collusion ring). Those who violate these policies will be penalized according to ACM policies ( If you would like to report a violation, please contact program chairs of your conferences/workshops or SIGSAC officers. We are committed to protecting the confidentiality of your communication.
Important Dates
First Review Cycle

Paper submission deadline: January 28th, 2024
Second Review Cycle

Paper submission deadline: April 14th, 2024 (tentative)

Related Resources

Ei/Scopus-ACAI 2024   2024 7th International Conference on Algorithms, Computing and Artificial Intelligence(ACAI 2024)
ACM ICDSP 2025   ACM--2025 9th International Conference on Digital Signal Processing (ICDSP 2025)
CCS 2024   ACM Conference on Computer and Communications Security 2024 - second deadline
IEEE-Ei/Scopus-ACEPE 2024   2024 IEEE Asia Conference on Advances in Electrical and Power Engineering (ACEPE 2024) -Ei Compendex
Ei/Scopus-CISDS 2024   2024 3rd International Conference on Communications, Information System and Data Science (CISDS 2024)
IEEE-Ei/Scopus-SGGEA 2024   2024 Asia Conference on Smart Grid, Green Energy and Applications (SGGEA 2024) -EI Compendex
EI/Scopus-PRDM 2024   2024 5th International Conference on Pattern Recognition and Data Mining(PRDM 2024)
SIGMETRICS 2025   The 2025 ACM SIGMETRICS conference (Winter Deadline)
Sensors journal 2024   Special Issue on Energy-Efficient Communication Networks and Systems: 2nd Eition
CCGrid 2025   The 25th IEEE/ACM international Symposium on Cluster, Cloud and Internet Computing