ASIACCS 2018 Call for Papers
We invite submissions from academia, government, and industry presenting novel research on all theoretical and practical aspects of computer and network security. Areas of interest for ASIACCS 2018 include, but are not limited to:
- Access control
- Accounting and audit
- Applied cryptography
- Big data security and privacy
- Blockchain and alternatives
- Cloud computing security
- Computer forensics
- Cyber-physical system security
- Data and application security
- Embedded systems security
- Formal methods for security
- Hardware-based security and applications
- IoT security and privacy
- Key management
- Malware and botnets
- Mobile computing security
- Network security
- Operating system security
- Practical post-quantum security
- Privacy-enhancing technology
- Runtime attacks and defenses
- Secure computation
- Security architectures
- Security of critical infrastructures
- Security metrics
- Software security
- Threat modeling
- Trusted computing
- Usable security and privacy
- Web security
- Wireless security and privacy
Technical papers submitted for ASIACCS are to be written in English. Papers must be at most 12 pages including bibliography. However, a maximum of 3 additional pages can be used for well-marked appendices. Note that appendices cannot exceed 3 pages even if the main text is less than 12 pages. Submissions must follow the new ACM conference template, which has been updated for 2017 (Use sigconf style). Submissions should not use older ACM formats or non-standard formatting. Submissions must be in Portable Document Format (.pdf). Authors should devote special care that fonts, images, tables and figures comply with common standards and do not generate problems for reviewers.
Submissions not meeting the formatting requirements risk rejection without consideration of their merits.
Double and Concurrent Submissions
Submissions to ASIACCS 2018 must not substantially overlap with papers that are published or simultaneously submitted to other venues (including journals or conferences/workshops). Double-submission will result in immediate rejection. Detected violations may be reported to other conference chairs and journal editors.
ASIACCS requires double-blind reviewing process. All submissions should be appropriately anonymized. Author names and affiliations should not appear in the paper. The authors should avoid obvious self-references and should appropriately blind them if used. The list of authors cannot be changed after the acceptance decision is made unless approved by the Program Chairs.
The authors should take care of clarifying any potential ethical and legal concerns to their results, highly critical vulnerabilities or exploits, etc. The authors should provide evidence that they have thoroughly considered such issues.
The Program Committee reserves the right to reject a submission if insufficient evidence was presented that ethical or relevant legal concerns were appropriately addressed.
Conflicts of Interest
The program chairs require cooperation from both authors and program committee members to prevent submissions from being evaluated by reviewers who may have a conflict of interest. During the submission, authors should identify members of the program committee with whom they have a conflict of interest. Conflict of interest includes but not limited to: advisors and advisees (at any time in the past); authors and PC members who share an institutional relationship; professional collaborations (regardless of whether they resulted in a publication) that occurred in the past 2 years; line-of-management relationship, grant program manager, close personal relationships.
Authors are not allowed to declare conflicts of interest in order to prevent submissions from being reviewed by selected PC members. However, authors can contact the program chairs and provide convincing arguments if they have certain concerns about the fair judgement of their submissions. PC members, including chairs that have a conflict of interest with a paper, will be entirely excluded from the evaluation of that paper.
Submission Site and Contact
The following link is for paper submission: https://asiaccs18.hotcrp.com/
Please read the above submission instructions before submitting the paper. If you have any questions, please contact: firstname.lastname@example.org.
Camera-Ready and Conference Presentation
If a paper is accepted, the author list in submission cannot be changed when preparing the camera-ready version. Authors of accepted papers must also guarantee that their papers will be presented at the conference. At least one author of the paper must be registered at the appropriate full conference rate.
Early Rejection and Appeals
(Drawn from IEEE S&P 2016 CFP)
There will be no conventional rebuttal process. Papers that receive substantially negative initial reviews will be rejected early. The authors of early-rejected papers, and only such papers, will receive a copy of their initial reviews. Authors who substantively disagree with the reviews can appeal to the PC chairs. Authors’ appeals must clearly and explicitly identify concrete disagreements with factual statements in the initial reviews that should be adjudicated by a special arbitration reviewer who may be recruited by the PC chairs. Appealing a submission that was rejected early will keep it under consideration, and it cannot be withdrawn or resubmitted elsewhere until the final notification of acceptance or rejection.
For inquiries on conference venue and logistics, please contact general chairs:
- Jong Kim, Pohang University of Science and Technology (POSTECH), Korea -<email@example.com>
- Gail-Joon Ahn, Arizona State University, USA and Samsung Electronics, Korea – <firstname.lastname@example.org>
- Seungjoo Kim, Korea University, Korea – <email@example.com>
For inquiries on technical program, please contact program chairs:
- Yongdae Kim, Korea Advanced Institute of Science & Technology (KAIST), Korea – <firstname.lastname@example.org>
- Javier Lopez, University of Malaga, Spain – <email@example.com>
- Taesoo Kim, Georgia Tech, USA – <firstname.lastname@example.org>