NSF’s Safe-OSE Grant for Safety, Security, and Privacy in Open-Source Ecosystems

*Who May Serve as PI:

For Institutions of Higher Education:

By the submission deadline, any PI, co-PI, or other Senior/Key Personnel must hold either:

<ul>
<li>a tenured or tenure-track position, or</li>
<li>a primary, full-time, paid appointment in a research or teaching position, or</li>
<li>a staff leadership role in an Open-Source Program Office or equivalent position</li>
</ul>

at a U.S.-based campus of an Institution of Higher Education (see above), with exceptions granted for family or medical leave, as determined by the submitting institution.

Individuals with primary appointments at overseas branch campuses of U.S. institutions of higher education are not eligible.Researchers from foreign academic institutions who contribute essential expertise to the project may participate as Senior/Key Personnel or collaborators but may not receive NSF support.

For all other eligible proposing organizations:

The PI must be an employee of the proposing organization who is normally resident in the US and must be acting as an employee of the proposing organization while performing PI responsibilities. The PI may perform the PI responsibilities while temporarily out of the U.S.

Individuals withprimaryappointments atnon-U.S.basednon-profit ornon-U.S.basedfor-profit organizations are not eligible.

Although most open-source products are software-based, it is important to note that Safe-OSE applies to any type of OSE, including those based on scientific methodologies, models, and processes; manufacturing processes and process specifications; materials formulations; programming languages and formats; hardware instruction sets; system designs or specifications; and data platforms. The goal of the Safe-OSE program is to catalyze meaningful improvements in the safety, security, and privacy of the targeted OSE that the OSE does not currently have the resources to undertake. Funds from this program should be directed toward efforts to enhance the safety, security, and privacy characteristics of the open-source product and its supply chain as well as to bolster the ecosystem’s capabilities for managing current and future risks, attacks, breaches, and responses.

*Who May Serve as PI:

For Institutions of Higher Education:

By the submission deadline, any PI, co-PI, or other Senior/Key Personnel must hold either:

<ul>
<li>a tenured or tenure-track position, or</li>
<li>a primary, full-time, paid appointment in a research or teaching position, or</li>
<li>a staff leadership role in an Open-Source Program Office or equivalent position</li>
</ul>

at a U.S.-based campus of an Institution of Higher Education (see above), with exceptions granted for family or medical leave, as determined by the submitting institution.

Individuals with primary appointments at overseas branch campuses of U.S. institutions of higher education are not eligible.Researchers from foreign academic institutions who contribute essential expertise to the project may participate as Senior/Key Personnel or collaborators but may not receive NSF support.

For all other eligible proposing organizations:

The PI must be an employee of the proposing organization who is normally resident in the US and must be acting as an employee of the proposing organization while performing PI responsibilities. The PI may perform the PI responsibilities while temporarily out of the U.S.

Individuals withprimaryappointments atnon-U.S.basednon-profit ornon-U.S.basedfor-profit organizations are not eligible.

Although most open-source products are software-based, it is important to note that Safe-OSE applies to any type of OSE, including those based on scientific methodologies, models, and processes; manufacturing processes and process specifications; materials formulations; programming languages and formats; hardware instruction sets; system designs or specifications; and data platforms. The goal of the Safe-OSE program is to catalyze meaningful improvements in the safety, security, and privacy of the targeted OSE that the OSE does not currently have the resources to undertake. Funds from this program should be directed toward efforts to enhance the safety, security, and privacy characteristics of the open-source product and its supply chain as well as to bolster the ecosystem’s capabilities for managing current and future risks, attacks, breaches, and responses.

*Who May Serve as PI:

For Institutions of Higher Education:

By the submission deadline, any PI, co-PI, or other Senior/Key Personnel must hold either:

<ul>
<li>a tenured or tenure-track position, or</li>
<li>a primary, full-time, paid appointment in a research or teaching position, or</li>
<li>a staff leadership role in an Open-Source Program Office or equivalent position</li>
</ul>

at a U.S.-based campus of an Institution of Higher Education (see above), with exceptions granted for family or medical leave, as determined by the submitting institution.

Individuals with primary appointments at overseas branch campuses of U.S. institutions of higher education are not eligible.Researchers from foreign academic institutions who contribute essential expertise to the project may participate as Senior/Key Personnel or collaborators but may not receive NSF support.

For all other eligible proposing organizations:

The PI must be an employee of the proposing organization who is normally resident in the US and must be acting as an employee of the proposing organization while performing PI responsibilities. The PI may perform the PI responsibilities while temporarily out of the U.S.

Individuals withprimaryappointments atnon-U.S.basednon-profit ornon-U.S.basedfor-profit organizations are not eligible.

Although most open-source products are software-based, it is important to note that Safe-OSE applies to any type of OSE, including those based on scientific methodologies, models, and processes; manufacturing processes and process specifications; materials formulations; programming languages and formats; hardware instruction sets; system designs or specifications; and data platforms. The goal of the Safe-OSE program is to catalyze meaningful improvements in the safety, security, and privacy of the targeted OSE that the OSE does not currently have the resources to undertake. Funds from this program should be directed toward efforts to enhance the safety, security, and privacy characteristics of the open-source product and its supply chain as well as to bolster the ecosystem’s capabilities for managing current and future risks, attacks, breaches, and responses.

*Who May Serve as PI:

For Institutions of Higher Education:

By the submission deadline, any PI, co-PI, or other Senior/Key Personnel must hold either:

<ul>
<li>a tenured or tenure-track position, or</li>
<li>a primary, full-time, paid appointment in a research or teaching position, or</li>
<li>a staff leadership role in an Open-Source Program Office or equivalent position</li>
</ul>

at a U.S.-based campus of an Institution of Higher Education (see above), with exceptions granted for family or medical leave, as determined by the submitting institution.

Individuals with primary appointments at overseas branch campuses of U.S. institutions of higher education are not eligible.Researchers from foreign academic institutions who contribute essential expertise to the project may participate as Senior/Key Personnel or collaborators but may not receive NSF support.

For all other eligible proposing organizations:

The PI must be an employee of the proposing organization who is normally resident in the US and must be acting as an employee of the proposing organization while performing PI responsibilities. The PI may perform the PI responsibilities while temporarily out of the U.S.

Individuals withprimaryappointments atnon-U.S.basednon-profit ornon-U.S.basedfor-profit organizations are not eligible.

Although most open-source products are software-based, it is important to note that Safe-OSE applies to any type of OSE, including those based on scientific methodologies, models, and processes; manufacturing processes and process specifications; materials formulations; programming languages and formats; hardware instruction sets; system designs or specifications; and data platforms. The goal of the Safe-OSE program is to catalyze meaningful improvements in the safety, security, and privacy of the targeted OSE that the OSE does not currently have the resources to undertake. Funds from this program should be directed toward efforts to enhance the safety, security, and privacy characteristics of the open-source product and its supply chain as well as to bolster the ecosystem’s capabilities for managing current and future risks, attacks, breaches, and responses.