Call for Papers
Overview
The 34th 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 2027. 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 revise such papers for inclusion in the same cycle, 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.
Submission Policies and Instructions
Executive Summary
All papers must adhere to the following rules (outlined more verbosely below). Papers found in violation of any of these requirements will be desk-rejected without review.
By registration deadline
- All papers MUST be registered in the respective HotCRP instance one week before the submission deadline, including the definitive title, the definitive abstract, the definitive track, and the definitive track justification.
- Abstracts and titles MUST NOT be changed after the abstract registration deadline, on the HotCRP metadata.
- Because abstracts and titles are used to match papers with reviewers, abstracts and titles MUST NOT be changed in the final submitted PDF. They MAY be adjusted in the camera-ready version upon acceptance.
- A track MUST be selected and MUST NOT be changed after the registration deadline.
- All papers MUST provide a track justification (non-empty, not dubious) by the registration deadline. The track justification MUST NOT be changed after the registration deadline.
By submission deadline
- The list of authors MAY be changed after registration but CANNOT be changed after the submission deadline. In particular, NO author can be added once papers are accepted. The order of authors MAY be changed for the camera-ready version upon acceptance.
- All papers MUST discuss Open Science. This MUST be in a separate appendix called “Open Science” (placed after the 12-page main content and the bibliography) that clearly lists where the artifacts necessary for evaluating the contributions of their submission are located. These artifacts MUST be made available at most 3 days after the time of submission, or their lack of availability should be explained by the submission deadline. In case there is no artifact, this should be stated in this section.
- All papers with online artifacts MUST provide the URL of the anonymous artifact website by submission deadline in both the paper and HotCRP.
- All papers with potential ethical concerns MUST have a discussion of research ethics. This MUST be in a separate appendix called “Ethical Considerations” (placed after the 12-page main content and the bibliography). In case of doubts on whether your paper has potential ethical concerns, add an appendix “Ethical Considerations”.
- All papers MUST NOT reveal the identity of the authors (e.g., names, self-references with “we”, funding acknowledgements, deanonymizing GitHub repositories).
- All papers MUST comply with the unaltered ACM LaTeX template. Any attempts to remove whitespace (e.g., negative vspaces, savetrees, titlesec, removing author blocks, etc.) or change the formatting defaults (e.g., fonts) are strictly forbidden. The Computing Classification System (CCS) information, such as concepts, keywords, or copyrights management information, DOI, ISBN, ACM reference format, must be retained, without any alteration, except keyword update.
- All authors MUST provide their ORCIDs through the profile page on HotCRP by the submission deadline.
- All authors MUST acknowledge the submission terms on HotCRP by the submission deadline.
- Authors MUST NOT submit more than seven papers per cycle.
By online artifacts uploading deadline
- For Cycle B, CCS will pilot a 3-day grace period for artifacts provided through anonymous hosting services. After the artifact uploading deadline (May 2nd AoE), artifacts MUST be available at the provided URL and authors MUST NOT change the artifacts after the artifact uploading deadline.
Other
- At least one author of each accepted paper MUST register for and commit to attending the conference.
- The chairs retain the right to desk-reject any submissions which attempt to disrupt the reviewing process (e.g., attempting prompt injections or crashing PDF viewers with malicious PDFs).
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 should avoid revealing authors’ identity in the text. When referring to their previous work, authors are required to cite their papers in the third person, without identifying themselves. In the unusual case in which a third-person reference is infeasible, authors can blind the reference itself. Papers not properly anonymized may be rejected without review. Authors may submit up to a maximum of 7 papers at each cycle.
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. Note that CCS does not accept SoK or survey papers.
Submissions must be a PDF file in double-column ACM format using “sigconf” 2-column 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. The CCS information, such as concepts, keywords, or rights management information (e.g., DOI and ISBN), must be retained. The teaser figure is optional. Please refer to the sample-sigconf.tex and sample-sigconf.pdf in the ACM package (also mirrored here) for the instructions. In order to clarify what is optional and what must be retained, we provide a minimal sample-ccs2026.tex file and the corresponding sample-ccs2026.pdf file, obtained by compiling the ACM package. It contains the information that MUST be retained. Submissions not following the required format may be rejected without review.
Submitted papers may be rejected for being out of scope, at the discretion of the Program Chairs. Authors who have questions about whether their paper is in scope are encouraged to ask the Program Chairs in advance. No modifications to the author list on a paper may be made after submission.
Ethical Considerations
Authors are expected to consider the ethical implications and potential societal impact of their work. Papers that raise ethical concerns, such as those involving human subjects, user data, or real-world vulnerability analysis, must include a dedicated “Ethical Considerations” section. This section should discuss the balance of risks vs. benefits and the steps taken to minimize potential harm (e.g., responsible disclosure, data anonymization). Note that institutional (IRB/ERB) approval is neither strictly necessary nor always sufficient to demonstrate ethical conduct; we expect authors to reason about the ethics of their work beyond ensuring institutional compliance. For detailed guidance on community standards, we follow the USENIX Security ’26 Ethics Policy. This section does not count toward the page limit and must be placed after the 12-page main content and bibliography.
Open Science Policy
This edition of ACM CCS adopts an Open Science policy to strengthen the transparency, reproducibility, and long-term impact of published research. Authors are expected to share the artifacts underlying their results (such as code, datasets, models, scripts, and documentation) whenever legally, ethically, and practically possible.
Each submitted paper must include an “Open Science” appendix that:
- Enumerates all artifacts needed to evaluate the paper’s core contributions (e.g., code, datasets, models, configuration files, scripts, documentation, benchmarks).
- Clearly describes how the program committee can access each artifact during double-blind review (including anonymous URLs or credentials, where applicable).
- Explicitly justifies any artifact that cannot be shared (e.g., due to licensing restrictions, responsible disclosure concerns, safety or privacy of study subjects, or deployment risks if adversarial methods are released prematurely). When full sharing is not possible, authors are encouraged to provide partial, synthetic, or redacted artifacts that still allow reviewers to assess the methodology.
- In case no artifact is needed to evaluate the paper’s core contributions, the authors should state it explicitly.
Artifacts listed in the Open Science appendix are considered part of the submission and will be used in the review process. If a claimed contribution depends on an artifact that is not available and not convincingly justified, reviewers may judge that the contribution cannot be adequately evaluated, which can negatively affect the final decision. The Open Science appendix is treated as an appendix and does not count toward the 12-page limit.
Providing Artifacts at Submission Time
Artifacts are required for submissions whose contributions fundamentally rely on an implementation, experimental evaluation, system, tool, or dataset. This includes, but is not limited to, papers that:
- Introduce a new system, library, or tool.
- Present experimental results derived from an implementation.
- Propose a new benchmark, dataset, or data collection methodology.
If reviewers determine that a central contribution cannot be properly evaluated without accessing artifacts that are neither provided nor convincingly justified in the Open Science appendix, the paper may be rejected.
All artifacts will be treated with the same strict confidentiality as the manuscript. Access is restricted to the assigned PC members, who may use artifacts only for the purpose of evaluating the paper. Any unauthorized use, sharing, or downloading for personal or professional purposes constitutes a serious ethical violation and may result in removal from the PC and additional sanctions.
To preserve anonymity in the double-blind review process:
- Authors should host artifacts on anonymous hosting services (e.g., anonymous.4open.science) that do not expose identifying access logs and do not allow authors to track or fingerprint individual visitors. Make sure the files remain available for the whole duration of the evaluation process and are not updated after upload.
- Authors must not use self-managed or easily modifiable hosting solutions (such as personal websites, Google Sites, Google Drive, wikis, cloud buckets, or similar services) that allow them to dynamically update content or embed tracking mechanisms.
- Authors are discouraged from using general-purpose platforms like Zenodo, Figshare, or non-anonymized GitHub repositories as their default choice, since their typical use does not provide sufficient anonymization for double-blind review.
- Anonymous URLs should be included directly in the submitted paper, for example in the Open Science appendix, not entered separately into the submission system.
For large artifacts that cannot feasibly be hosted anonymously (e.g., datasets larger than 1 GB), authors may provide a representative subset sufficient to verify the methodology and core claims. In these cases, the Open Science appendix must explain why the full artifact cannot be shared anonymously and describe how the subset preserves the integrity and representativeness of the evaluation.
New for Cycle B: As CCS values artifacts, a 3-day grace period will be granted for artifacts provided through an anonymous website (e.g., anonymous.4open.science).
- After May 2nd AoE, papers with empty or dubious artifacts at the provided URL will be desk-rejected. Similarly, any update after the artifact deadline will lead to desk rejection.
- The grace period applies to material submitted through the URL provided in the HotCRP form. Supplementary material provided through HotCRP cannot be updated within the grace period.
- The artifacts MUST correspond to figures, experiments, and results provided in the submitted paper. The paper cannot be updated after the submission deadline even if a discrepancy between the paper and the artifacts is discovered.
After acceptance, authors are encouraged to de-anonymize or replace the anonymous links with stable, citable repositories, consistent with the Open Science policy above, and to register their artifacts for optional Artifact Evaluation.
Optional Artifact Evaluation
Beyond basic availability, ACM CCS offers an optional Artifact Evaluation (AE) process to recognize artifacts that are functional and support the reproducibility of the paper’s results.
Authors of accepted papers (including shepherd-approved and minor-revision papers) will have the option to submit their artifacts to the AE Committee for in-depth evaluation. The AEC will assess, as applicable:
- Whether the artifact is functional.
- Whether the artifact supports reproducing, within reasonable effort, the key results or claims in the paper.
A separate call for artifacts will be issued after paper acceptance, detailing submission instructions, evaluation criteria, and timelines. Artifacts that successfully pass AE may receive a corresponding recognition in the conference proceedings and on the paper’s web page.
Policy on the Use of Generative AI and LLMs
ACM CCS follows the ACM Policy on Authorship regarding the use of generative AI tools. Authors and reviewers must adhere to the following guidelines when using Large Language Models (LLMs) and other generative AI tools.
1. Guidelines for Authors
The use of generative AI tools to assist in preparing submissions is permitted, provided that human authors retain full responsibility for the accuracy, originality, and integrity of the work. Generative AI tools cannot be listed as authors.
Hallucinations, Fabrication, and Falsification
Authors must carefully verify that all AI-generated content is accurate and supported by evidence. Submissions that contain hallucinated citations, falsified or fabricated data, experiments, or results, or other invented claims presented as fact may be desk rejected.
Mandatory Disclosure of Generative AI Usage
In accordance with ACM’s authorship policy, all uses of generative AI tools must be disclosed.
If AI tools were used only for minor editorial improvements, a brief statement in the Acknowledgements Section is sufficient.
If AI tools were used to generate or substantially rewrite substantive content, authors must include a dedicated “Generative AI Usage” section placed after the 12-page main content and the bibliography.
2. Guidelines for Reviewers
To protect the integrity and confidentiality of the peer-review process, reviewers must not upload any part of a submitted manuscript to public generative AI tools or LLM services.
Reviewers who choose to use AI tools to assist in drafting their reviews may do so only if they refrain from including any content from the submission itself.
Violations of this policy are treated as serious breaches of confidentiality and may result in removal from the Program Committee and additional ACM sanctions.
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. At the time of submission, authors must select one track, which should be the most relevant to the topic of the paper.
Program Co-Chairs
TBD
Track Chairs
TBD
Track Justification Statement
Each submission must include a brief statement in the appropriate section of HotCRP addressing:
- Track selection justification: Why is your selected track the best match for your work?
For work spanning multiple tracks, simply choose the best fit and briefly explain your reasoning, and mention any fitting alternative tracks in your statement.
Special Note for Machine Learning Papers
Categorization of ML-Related Papers
ML for Security and Privacy Problems: If ML is used to solve a security or privacy issue, submit the paper to the track that better aligns with the primary field of the problem being addressed, not the “Security and Privacy of ML” track.
Security and Privacy of Machine Learning: If your work directly addresses the security or privacy of ML itself, the Security and Privacy of Machine Learning track is the right fit.
All papers submitted to this track must provide a threat model that clearly articulates the envisioned attackers, threat surfaces, generality, and practicality of the attack. If the authors believe they still fit the track without the need for a threat model, they need to explicitly justify this in the Track Justification Statement.
Purely theoretical ML works without actionable security insights are out of scope, as are papers focusing on generic ML properties that lack clear security implications.
Conflicts of Interest
The conference requires cooperation from both authors and program committee members to ensure a fair review process. 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.
Track Chairs are not allowed to submit papers to their own track, but may submit papers to other tracks, subject to the overall limit of 7 papers per cycle.
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.
Policy for Peer-Review Integrity
All SIGSAC sponsored conferences and workshops are required to follow ACM policies against harassment activities and the ACM Code of Ethics and Professional Conduct. All authors, PC members, and non-PC reviewers are also required to follow ACM Publications Policies.
We require all reviewers to uphold the integrity of the peer review process and avoid any form of conflict of interest. Those who violate these policies will be penalized according to ACM policies. If you would like to report a violation, please contact the Program Chairs of the conference or the SIGSAC officers.
Withdrawal Policy
Withdrawal of a paper is prohibited at any point prior to the official notification of the final decision being sent to the authors. By submitting a full paper, authors commit to seeing the submission for that cycle through the full review process.
Important Dates
TBD
Community Standards & Anti-Harassment
ACM CCS is committed to promoting diversity and inclusion in our community. If you have suggestions, concerns, or complaints related to biases or sexual harassment, we encourage you to reach out to the Program Chairs. We are committed to protecting the anonymity of such reports and helping to address your concerns.
We encourage authors to be mindful of not using language or examples that further the marginalization, stereotyping, or erasure of any group of people, especially historically under-represented groups in computing.
Agreements
By submitting your article to an ACM Publication, you are hereby acknowledging that you and your co-authors are subject to all ACM Publications Policies, including ACM’s Publications Policy on Research Involving Human Participants and Subjects. Alleged violations of this policy or any ACM Publications Policy will be investigated by ACM and may result in a full retraction of your paper, in addition to other potential penalties, as per ACM Publications Policy.
Please ensure that you and your co-authors obtain an ORCID ID, so you can complete the publishing process for your accepted paper. ACM has been involved in ORCID from the start and we have recently made a commitment to collect ORCID IDs from all of our published authors. We are committed to improve author discoverability, ensure proper attribution and contribute to ongoing community efforts around name normalization; your ORCID ID will help in these efforts.
Open Access Publishing Model for 2026 ACM Conferences
Starting January 1, 2026, ACM will fully transition to Open Access. All ACM publications, including those from ACM-sponsored conferences, will be 100% Open Access.
Authors from institutions not participating in ACM Open will need to pay an APC to publish their papers, unless they qualify for a financial or discretionary waiver.
Thanks to a temporary ACM subsidy for 2026, the APC will be as follows:
- $250 APC for ACM/SIG members
- $350 for non-members
This temporary subsidized pricing will apply to all conferences scheduled for 2026.