Principles of Security and Trust is a broad forum related to all theoretical and foundational aspects of security and trust.
We seek submissions on the foundations of information security, privacy, and trust, relevant for computer science and different application disciplines. Case studies that reflect the strengths and limitations of existing foundations, methods, and their supporting tools are also welcome, as are more exploratory presentations on open questions.
Areas of interest include:
|Confidentiality||Covert channels||Crypto foundations|
|Cyber-physical systems security||Database security||Distributed systems security|
|Security and privacy economics||Hardware security||Information flow|
|Integrity||Languages for security||Malicious code|
|Mobile security and privacy||Models and policies||Privacy and privacy-preserving systems|
|Provenance||Reputation and trust||Resource usage|
|Risk assessment||Security architectures||Security protocols|
|Trust management||Usable security and privacy||Usage control|
|Web security and privacy|
Call for Papers
Important dates and submission instructions
The review process of POST 2019 is double-blind, with a rebuttal phase.
Authors are asked to omit their names, institutions, and other directly identifying information; refer to their prior work in the third person, just as to prior work by others; and not to include acknowledgements that might identify them.
POST 2019 solicits four types of contributions: regular research papers, systematization of knowledge papers, position papers and tool demonstration papers.
Regular research papers
POST allows regular research paper submissions of at most 20 pages (excluding bibliography). Additional material intended for reviewers but not for publication in the final version—for example, details of proofs—may be placed in a clearly marked appendix that is not included in the page limit. POST reviewers are at liberty to ignore appendices and papers must be understandable without them.
Systematization of knowledge (SoK) papers
SoK papers evaluate, systematize, and contextualize existing knowledge. Suitable papers are those that provide an important new viewpoint on established research areas, challenge long-held beliefs in such an area with compelling evidence, or present a comprehensive new taxonomy of such an area. Survey papers without such insights are not appropriate. Submissions should be distinguished by the prefix “SoK:” in the title. They will be reviewed by the PC and held to the same standards as traditional research papers, except instead of emphasizing novel research contributions the emphasis will be on value to the community.
The page limit is as for regular research papers – 20 pages (excluding the bibliography).
Position papers that present a well justified stance on a fundamental but possibly controversial question. For example: “Privacy should trump security in all cases” (or the other way around), “Cryptocurrencies should be outlawed because… / encouraged because …”, “Why we should/should not research internet-based voting”. A position paper can also propose new directions for foundational research without having worked out all technical details. Position papers will be selected based on originality, likelihood of stimulating insightful discussion at the conference, and technical merit.
Position papers may be no longer than 10 pages (excluding bibliography) and their titles must start with the words “Position Paper:”.
Tool demonstration papers
Submissions of tool demonstration papers should consist of two parts:
The first part, at most 6 pages, should describe the tool presented and provide information that illustrates the maturity and robustness of the tool (this part will be included in the proceedings). If available, the URL of the tool should be provided in the appropriate form field when submitting your paper. This field can only been seen by PC chairs, and hence, it does not have to be anonymized. Of course, authors may also include anonymized URLs directly in their submission. The title of the submission should start with the words “Tool Demonstration:”.
The second part should be either (i) a video of the demonstration, max 15 minutes, which sketches the planned demo talk; a URL to the video should be sent to the program chairs separately at the time of submission, or (ii) an appendix of at most 6 pages, which should explain how the demonstration will be carried out and what it will show, including screen dumps and examples. (This part will not be included in the proceedings, but will be evaluated.)