|
| 1 | +--- |
| 2 | +title: 2nd International Workshop on Security and Risk in Identity Management (SeRIM 2026) |
| 3 | +subtitle: Call for Papers |
| 4 | +menubar: SeRIM2026 |
| 5 | +--- |
| 6 | + |
| 7 | +# Topics of Interest |
| 8 | +We encourage submissions on a range of topics related to the security and risk assessment applied to identity management, including but not limited to: |
| 9 | +- Case Studies in Secure Identity Management |
| 10 | +- Formal Verification of Identity Management Protocols |
| 11 | +- Risk Assessment Methodologies and Strategies |
| 12 | +- Security Metrics for Identity Systems |
| 13 | +- Specification Languages for Automated Analysis |
| 14 | +- Threat Modeling and Vulnerability Assessment |
| 15 | +- Tools for Security Analysis |
| 16 | + |
| 17 | +# Submission Guidelines |
| 18 | +Submitted manuscripts must present original research that does not substantially overlap with any previously published work or submissions under consideration by other venues. |
| 19 | + |
| 20 | +Submissions must be in English and provided in PDF format, following the IEEE conference proceedings format. They will be categorized into (page limits exclude references and well-marked appendices): |
| 21 | +- **Regular Papers**: full-length research papers (up to 10 pages). |
| 22 | +- **Short Papers**: research papers presenting preliminary results (up to 6 pages). |
| 23 | +- **Tool Papers**: description of tools or practical implementations (up to 4 pages). They will be presented in a Demo Session, where attendees can see live demonstrations of the tools. |
| 24 | + |
| 25 | +Submissions must be made through the [EasyChair conference management system](https://easychair.org/conferences/?conf=serim2026). |
| 26 | + |
| 27 | +Papers must be submitted in a form suitable for **anonymous review**: no author names or affiliations may appear on the title page, and papers should avoid revealing their identity in the text. Authors should also take care in not including acknowledgments that help identify them (e.g., funding information, names of colleagues who gave feedback on the paper). When referring to your previous work, do so in the third person, as though it were written by someone else. Any source code or other material (e.g., data sets) which requires hosting must use anonymous services. This explicitly excludes hosting on GitHub or Google Drive (which could leak reviewer identities). Instead, authors are encouraged to use services such as [Anonymous GitHub](https://anonymous.4open.science/). |
| 28 | + |
| 29 | +Failure to comply with the above requirements may result in rejection without review. |
| 30 | + |
| 31 | +Please note that at least one author of each accepted paper must register for the workshop and present the paper in person. |
| 32 | + |
| 33 | +# Workshop Proceedings |
| 34 | +All accepted papers (regular, short and tool) will be included in the workshop proceedings. Specifically, they will be published in a volume within IEEE Xplore, accompanying the main proceedings of IEEE EuroS&P 2026. |
| 35 | + |
| 36 | +# Important Dates |
| 37 | +{% include_relative includes/important-dates.md %} |
| 38 | + |
| 39 | +# Proactive Prevention of Harm |
| 40 | +We expect authors to carefully consider and address the potential harms associated with carrying out their research, as well as the potential negative consequences that could stem from publishing their work. Failure to adequately discuss such potential harms within the body of the submission may result in rejection of a submission, regardless of its quality and scientific value. |
| 41 | + |
| 42 | +# Open Science Expectations |
| 43 | +As for the main conference, our expectation for SeRIM is that researchers will maximize the scientific and community value of their work by making it as open as possible. This means that, by default, all of the code, data, and other materials (such as survey instruments) needed to reproduce your work described in an accepted paper will be released publicly under an open source license. Sometimes it is not possible to share work this openly, such as when it involves malware samples, data from human subjects that must be protected, or proprietary data obtained under agreement that precludes publishing the data itself. All submissions are encouraged to include a clear statement on Data Availability that explains how the artifacts needed to reproduce their work will be shared, or an explanation of why they will not be shared. If data reproducibility is required for significant contributions of the work and the authors do not explain reproducibility and/or share the artifacts, papers that fail to satisfy these commitments may be removed from the workshop. |
| 44 | + |
| 45 | +# AI Guidelines |
| 46 | +The use of AI-generated content (including but not limited to text, figures, images, and code) shall be disclosed in the acknowledgments section. At the time of submission, the acknowledgments do not count towards the page limit. The AI system used shall be identified, and specific sections of the article that use AI-generated content shall be identified and accompanied by a brief explanation regarding the level at which the AI system was used to generate the content. |
| 47 | + |
| 48 | +The use of AI systems for editing and grammar enhancement is common practice and, as such, is generally outside the intent of the above policy. In this case, disclosure as noted above is not required, but recommended. |
| 49 | + |
| 50 | +To uphold the highest standards of integrity and confidentiality, the use of generative AI for paper reviews is expressly prohibited. |
0 commit comments