Please take our brief and anonymous Needs Survey to tell us about your experimentation needs.  Or you can contact us via our Contact page.

Apply for a summer internship with the SPHERE project. An internship lasts 8-10 weeks. You will work with us at USC-ISI in Marina del Rey, CA, or Northeastern University in Boston, MA. Below are three available opportunities, please view for more information and how to apply:
- SPHERE 2025 Internship INFRASTRUCTURE
- SPHERE 2025 Internship CPS
- SPHERE 2025 Internship IoT

Do you run a shared research infrastructure that has unique cybersecurity needs, not amenable to off-the-shelf solutions? Reach out to us to connect with top researchers who can collaborate with you on SPHERE to design custom solutions that meet your needs.

Do you run a shared research infrastructure, used by cybersecurity and privacy researchers? Would you like your resources to become temporarily or permanently part of SPHERE? Reach out to us, we'd love to explore opportunities like this.

Let us help you learn how to use SPHERE as part of your work. Reach out with your questions, comments, and feature requests via our Contacts page.

Teaching cybersecurity or privacy? Please try our education modules. There are homework assignments for undergraduate and graduate classes, demonstrations for K-12 students, and capture-the-flag exercises. Reach out to us with questions via our Contacts page. We love to support education with SPHERE!

Guidelines for using SPHERE

SPHERE is happy to support artifact evaluation for any conference that welcomes cybersecurity and privacy papers. Artifact evaluation committees (AECs) can use SPHERE to evaluate any artifact, even if it is unrelated to cybersecurity and privacy research.

There are three ways we can support AECs on SPHERE. AEC chairs should consider these and let us know which mode works best for their needs.

1. HotCRP integration

We have integrated SPHERE support into the HotCRP. You can install the code from https://github.com/STEELISI/hotcrp and follow the instructions from README. At most, one allocation per paper is allowed - the allocation may contain one or more resources (e.g., VMs), and they may be connected or not. All interaction with SPHERE is via the HotCRP interface. AE accounts are anonymous on SPHERE, even though they can be fully set up in the HotCRP.

2. SPHERE creates accounts for AEC chair

The AEC chair can ask artifact evaluators for their resource needs, collect them in a Google doc, and then share them with the SPHERE team. We will create the  accounts, allocate the needed resources, and put the information into the document. The AE accounts are anonymous.

3. Artifact evaluators creates their own accounts

Artifact evaluators can create their own accounts on SPHERE. If they want to remain anonymous to the SPHERE team they can use the following fake information during account creation:

First name: <CONF NAME>
Last name: Evaluator
Username: <CONFNAME>XYZ  (XYZ can be chosen by the evaluator so accounts are unique)
E-mail: <CONFNAME>[email protected]

For example an evaluator for NDSS 2025 could use the following information:

First name: NDSS2025
Last name: Evaluator
Username: ndss2025icecream
E-mail: [email protected] 

Archiving evaluated artifacts

SPHERE aims to increase reproducibility of cybersecurity and privacy research. We would like to archive the artifacts that were successfully evaluated, so that they can be reused by other researchers on SPHERE. Please email [email protected] when an artifact is ready to be archived.