USENIX Security Skills
A 12-skill depth pack for USENIX Security Symposium submissions: venue fit, HotCRP cycle submission, shepherding and author interaction, camera-ready, two-phase artifact evaluation, Open Science compliance, appendix strategy, review process, writing style, related work, experiments, and the two-cycle workflow. Grounded in USENIX Security '26/'27 pages checked on 2026-07-08.
Skills in this plugin
12- ▌ Usenixsec Workflow · brycewang-stanfordUse when planning a USENIX Security Symposium project end to end — choosing between the two annual cycles, mapping the registration-to-camera-ready calendar for a chosen cycle, sequencing artifact and ethics work early, and coordinating a team across the multi-deadline Big-Four calendar.
- ▌ Usenixsec Submission · brycewang-stanfordUse when finalizing a USENIX Security Symposium submission — the per-cycle HotCRP site, the registration deadline a week before the paper deadline, the 13-page body plus mandatory Ethical Considerations and Open Science appendices, double-blind sweeps, and the early-reject exposure of a weak upload.
- ▌ Usenixsec Experiments · brycewang-stanfordUse when designing or auditing the evaluation of a USENIX Security Symposium paper — building threat-model-faithful experiments, adaptive-attacker analysis for defenses, false-positive and vantage-point rigor for detection and measurement, ethical experimentation on live systems, and honest baselines.
- ▌ Usenixsec Camera Ready · brycewang-stanfordUse when preparing final papers for the USENIX Security Symposium after acceptance — de-anonymizing, keeping the Ethical Considerations and Open Science appendices current, clearing the mandatory Phase-1 artifact availability check before finals are due, and meeting USENIX's open-access publication and presentation obligations.
- ▌ Usenixsec Related Work · brycewang-stanfordUse when positioning a USENIX Security Symposium paper against prior work — covering the Big-Four security venues plus specialty conferences, handling concurrent submissions across the multi-cycle calendar, citing your own work double-blind, and using USENIX's open-access proceedings for verification.
- ▌ Usenixsec Supplementary · brycewang-stanfordUse when deciding what goes where in a USENIX Security Symposium paper — the 13-page body, the two mandatory one-page appendices (Ethical Considerations, Open Science), optional appendices after the references, and external artifacts — so nothing decision-critical lands where reviewers won't look.
- ▌ Usenixsec Writing Style · brycewang-stanfordUse when drafting or revising prose for a USENIX Security Symposium paper — threat-model-first structure, calibrated security claims, disclosure narrative woven into the text, 13-page discipline in the USENIX template, and the plain systems-security register this program committee rewards.
- ▌ Usenixsec Review Process · brycewang-stanfordUse when reasoning about how a USENIX Security Symposium cycle actually decides — early-reject notifications, multi-round reviewing, the retirement of Major Revision in favor of shepherd-approval acceptances, resubmission restrictions between cycles, and what each notification email means for planning.
- ▌ Usenixsec Author Response · brycewang-stanfordUse when reviews arrive from a USENIX Security Symposium cycle and the authors must respond — writing the rebuttal that survives online PC discussion, handling required ethics-content revisions flagged mid-review, and working with a shepherd after an "Accepted on Shepherd Approval" decision.
- ▌ Usenixsec Reproducibility · brycewang-stanfordUse when strengthening reproducibility for a USENIX Security Symposium paper — writing the mandatory Open Science appendix, deciding what can and cannot be shared (exploit code, vulnerable-device data, human-subjects material), and making measurement, attack, and defense results independently regenerable.
- ▌ Usenixsec Topic Selection · brycewang-stanfordUse when deciding whether a project belongs at the USENIX Security Symposium or a sibling venue — routing among USENIX Security, IEEE S&P, ACM CCS, NDSS, and specialty venues (PETS, SOUPS, RAID, WOOT), and confirming the work has the artifact/measurement/systems evidence USENIX Security rewards.
- ▌ Usenixsec Artifact Evaluation · brycewang-stanfordUse when packaging artifacts for USENIX Security Symposium evaluation — the mandatory Phase-1 availability check that acceptance is conditional on, the optional Phase-2 push for Artifacts Functional and Results Reproduced badges, and building security artifacts (exploits, scanners, datasets) that evaluators can run safely.