ACM Conference on Computer and Communications Security (CCS)

ACM Conference on Computer and Communications Security (CCS)

Conference positioning

ACM Conference on Computer and Communications Security (CCS) is a top computer-science conference venue for security, privacy, cryptography, software/systems security, web security, and measurement. It rewards a security paper with strong novelty, complete threat model, and reviewer-proof evaluation. Treat this skill as a fit / venue-selection / re-framing tool for conference submission strategy, not as a substitute for the current year's CFP, author kit, ethics policy, or submission portal.

Because CS conferences change deadlines, templates, page limits, review workflow, artifact rules, AI-use policy, and rebuttal formats every cycle, always verify the live official instructions before making a submission-ready recommendation. Start from the official source anchor recorded for this venue in ../../resources/conference-roster.md and ../../resources/official-source-map.md.

When to trigger

• The author names CCS / ACM Conference on Computer and Communications Security as the target venue.
• A manuscript in security needs a conference-fit read before being formatted or submitted.
• The paper must be re-framed from journal style or arXiv style into a selective CS conference narrative.
• The author needs an evidence-gap, anonymity, artifact, rebuttal, or re-routing diagnosis for this venue.

Scope & topic fit

• Core fit: security, privacy, cryptography, software/systems security, web security, and measurement.
• Best submissions make a precise contribution type visible: algorithm, theorem, system, dataset, benchmark, empirical finding, design artifact, tool, or socio-technical analysis.
• The paper should explain why the result matters to CCS's reviewers, not just why it is interesting to the authors' lab or product context.
• Position related work against the most recent conference-cycle papers in this venue and its closest siblings; stale comparisons are a common early-review weakness.
• If the contribution is interdisciplinary, state which part is CS research and which part is domain evidence.

Venue-specific calibration

• Reviewer lens: Read reviewers as adversarial-method reviewers. Threat model, ethics, disclosure, adaptive attacks, and reproducible evidence are central.
• Contribution hook to foreground: the venue-specific contribution bar.
• Scope vocabulary to use naturally in the abstract and introduction: security, privacy, cryptography, software/systems security, web security, and measurement.
• Distinctive fingerprint for reviewer calibration: security, privacy, cryptography, software, measurement, venue-specific, contribution, flagship, sigsac.
• Official anchor domain: www.sigsac.org. Quote annual rules only after opening that source and the current-year CFP/author kit.

Close-neighbor routing guardrail

• Route to CCS when the paper is a broad computer-security contribution with a clear threat model, attack/defense evidence, and systems or protocol relevance to the ACM security community.
• Compare IEEE S&P, USENIX Security, and NDSS carefully. The right venue depends on threat model, artifact/reproducibility posture, ethics constraints, and community scope.

What distinguishes this venue from its closest siblings