Call for Papers
We solicit research and experience papers on a broad range of topics relating to secure systems development. Examples of topics in scope include the development of libraries, tools, or processes to produce systems resilient to certain attacks; formal foundations that underpin a language, tool, or testing strategy to improve security; techniques that drastically improve the scalability of security solutions for practical deployment; and experience, designs, or applications showing how to apply cryptographic techniques effectively to secure systems.
SecDev also seeks hands-on and interactive tutorials on security-focused processes, frameworks, languages, and tools. The goal is to share knowledge on the experience, art, and science of secure systems development.
NEW THIS YEAR!
We welcome submissions of Systematization of Knowledge (SoK) papers that evaluate, organize, and contextualize existing knowledge. Submissions must include the prefix “SoK: ” in the title.
SecDev also has calls for other types of contributions, such as posters, tool demos, and practitioner abstracts. Information on these solicitations is available on the SecDev website (TBA).
Areas of Interest
Areas of interest include (but are not limited to):
- Security/resiliency-focused system designs (HW/SW/architecture)
- Tools and methodology for secure code development
- Risk management and testing strategies to improve security
- Security engineering processes, from requirements to maintenance
- Security benchmarks and reproducibility studies
- Comparative experimental evaluation
- From research to practice – gaps and transitions
- Programming languages, development tools, and ecosystems supporting security
- Static program analysis for software security
- Dynamic analysis and runtime approaches for software security
- Automation of programming, deployment, and maintenance tasks for security
- Software ecosystem and software supply chain security
- Distributed systems design and implementation for security
- Privacy by design
- Human-centered design for systems security
- Formal verification and other high-assurance methods for security
- Code reviews, red teams, and other human-centered assurance
Mandatory In-Person Attendance
SecDev 2026 is an in-person conference. Authors of all accepted papers and tutorials are expected to register for and attend the conference in person. If this is likely to be a problem, please do not submit.
Submission Details
Submission site: TBA
Submissions must use the ACM Proceedings style.
Submissions must be one of three categories:
1. Research Papers
Long (up to 10 pages) or Short (up to 6 pages), excluding references and appendices.
These should present well-argued new work, evidence, or ideas.
SoK papers are allowed (title must begin with “SoK:”).
Exceptional vision position papers will also be considered.
2. Experience Papers
Long (up to 10 pages) or Short (up to 6 pages), excluding references and appendices.
These should report experience applying tools or methodology in a non-trivial setting, including lessons learned and both positive/negative findings.
Authors of accepted research or experience papers will present their work at the conference. Papers will appear in the formal proceedings (TBA).
Double-Blind Review
SecDev uses a light-weight double-blind review process.
Papers must:
- Omit author names and institutional affiliations
- Reference related author work in the third person
- Preserve anonymity without weakening the submission unnecessarily
More information will be provided (TBA).
3. Tutorial Proposals
Up to 2 pages, covering:
(a) topic
(b) tutorial format, including hands-on components
(c) expected audience and learning outcomes
(d) previous tutorials/talks by the proposers (if any)
Titles must be prefixed with “Tutorial:”
Tutorial proposals do not need to be anonymized.
Accepted tutorials will be 90 or 180 minutes and include hands-on elements. A two-page abstract may appear in the proceedings. Tutorials occur on the first day of the conference.
At least one author must register and present. Tutorial presenter registration is free.
AI-Based Tool Use Policy
For authors
- Use of AI-based tools (e.g., ChatGPT, Copilot) must be disclosed in the acknowledgments.
- Verbatim AI-generated text must be identified with tool + prompt.
- Substantial paraphrasing with AI tools must also be disclosed.
- If AI tools were used only for stylistic edits, note which sections and what instructions were applied.
For reviewers
- Reviewers must not use AI tools to write or edit reviews.
- Submitted papers or review drafts must not be uploaded to AI tools.
- Reviewers must self-certify that AI tools were not used.
Important Dates (All TBD)
- Paper and tutorial submission deadline: TBD
- Author notification: TBD
- Camera-ready deadline: TBD
- Conference dates: TBD