To maintain a wall of separation between paper review and the artifacts, authors will be given the option to submit their artifacts only after their papers have been accepted for publication at ACM CCS.
Now that the reviewing process for ACM CCS is finalized, the AE will take place and authors of accepted papers can submit an artifact for review.
By the artifact submission deadline, authors can submit their artifacts, Artifact Appendix, and other supporting information via the submission form, which will be available starting October 20.
Authors define the contents of their artifact submission. For example, software, hardware, data sets, survey results, test suites, mechanized (but not paper) proofs, access to special hardware, and so on.
Authors choose which badges their artifact should be evaluated towards, we will use the same process as USENIX Security.
In general, good artifacts are expected to be: consistent with the paper, as complete as possible, well documented, and easy to (re)use. The AEC will read the paper and then judge if the artifact meets the criteria for each of the requested badges.
Each artifact submission will be reviewed by at least two AEC members. The review is single-blind and strictly confidential. All AEC members are instructed to treat the artifact confidential during or after completing evaluation, nor retain any part of it after evaluation.
Thus, you are free to include models, data files, proprietary binaries, exploits under embargo, etc., in your artifact. Since we anticipate small glitches with installation and use, reviewers may communicate with authors for the period November 1-17 to help resolve glitches while preserving reviewer anonymity.
Please make sure that at least one of the authors is reachable to answer questions in a timely manner.
The AEC will then complete its evaluation and notify the authors of the outcome several days before ACM CCS takes place.