Acceptance at USENIX Security starts a short, condition-laden runway: in the '26 cycles, final papers were due about six weeks after notification (Cycle 1: notified Dec 4, 2025, finals Jan 15, 2026; Cycle 2: notified May 14, 2026, finals Jun 11, 2026), and during that same window the mandatory artifact-availability check had to pass. The camera-ready is therefore not a formatting chore — part of the acceptance itself is still pending.
Under the '26 Open Science policy, acceptance is conditional on the artifact evaluation committee verifying, before finals are due, that the artifacts named in the paper's Open Science appendix are genuinely available — or that the appendix carries a justified explanation for withholding them. Plan the runway backwards from that:
| Week after notification | Camera-ready lane | Artifact lane |
|---|---|---|
| 1 | Ingest decision + shepherd requests | Move artifacts from anonymous mirror to permanent home |
| 2–3 | Apply required edits; shepherd sign-off | Submit availability materials; respond to AE contact |
| 4 | De-anonymize; final template pass | Availability verified (Phase-1 complete) |
| 5–6 | Upload finals + metadata; presenter forms | Decide on optional Phase-2 (Functional / Reproduced) |
Restore identity everywhere it was stripped, and keep the pieces consistent:
The two named appendices — "Ethical Considerations" and "Open Science" — remain in the final paper, updated: disclosure timelines that were "in progress" at submission should state their current status (vendor response, CVE assignment, patch release).
# Final-paper checks
pdftotext final.pdf - | grep -nEi 'anonym|under submission|double.blind' | head
pdftotext final.pdf - | grep -noE 'https?://[^ ]+' | sort -u > urls.txt
while read -r n url; do curl -sIL --max-time 10 "${url#*:}" -o /dev/null \
-w "%{http_code} ${url}\n"; done < <(tr ':' ' ' < urls.txt | head -40)
pdffonts final.pdf | awk 'NR>2 && $4!="yes"' # any non-embedded font lines = fix
Follow the current "Instructions for Presenters and Authors of Accepted Papers" page for the cycle — title formatting, copyright/consent forms, and slide or poster requirements are set there, not in the CFP.
USENIX publishes Security proceedings open access; papers (and later, talk recordings) are freely available on usenix.org. There is no article charge. The author-side obligations run through the conference instead: presentation at the symposium in Baltimore (Aug 12–14, 2026 for the '26 program) per the current presenter instructions. Registration mechanics, speaker-registration rules, and any remote-presentation allowance are per-year decisions — 待核实 against the instructions page for your cycle before booking anything.
Cycle-1 authors get a bonus decision: finals are locked ~7 months before the symposium, so plan whether to post an extended version (arXiv or tech report) in the gap, and make the proceedings version state clearly which version is canonical.
[Runway] notification → finals dates; days remaining
[Conditions open] shepherd sign-off / Phase-1 availability / forms
[De-anonymization] identity restored + artifact URLs swapped and re-tested
[Appendices] Ethical Considerations + Open Science updated to current status
[Presentation] presenter, registration status, travel constraints