Common use of Technical Papers Clause in Contracts

Technical Papers. To receive a Final Event prize, a team must submit an acceptable technical paper to the HAS4 organizers describing their approach to winning the game, to include a description of the attack strategies and defensive measures employed during the Final Event. Final Event technical papers are due within 3 weeks of the conclusion of the Final Event (see Rules Section 9 for official dates/times). Formal technical write-ups must include enough detail to permit accurate stepwise understanding of the CTF challenge described. Write-ups should follow the format of typical CTF write-ups. As an example of acceptable write-up format please see (xxxxx://xxxxxx.xxx/cromulencellc/hackasat-finals-2022/tree/main/team_writeups). The write- ups should include a background description of the vulnerabilities discovered and a description of the techniques used to exploit and/or patch those vulnerabilities. Associated source code, dependencies and instructions for deploying the code to address these vulnerabilities shall also be provided. The HAS4 organizers will review write-ups and communicate acceptance to each entrant official. By making a submission to this prize contest, all participants (all members of the team) agree that no part of its submission includes any Trade Secret information, ideas, or products. All submissions to this prize contest are deemed non-proprietary. Since the United States Air Force and/or United States Space Force do not wish to receive or hold any submitted materials “in confidence” it is agreed that, with respect to the participant’s submission, no confidential or fiduciary relationship or obligation of secrecy is established between the U.S. Government, HAS4 organizers, and the participant, the participant’s team, or the company or institution the participant represents when submitting, or any other person or entity associated with any part of the participant’s submission. The United States Air Force and Space Force reserve the right to disqualify a participant whose actions are deemed to violate the spirit of the competition for any reason, including but not limited to, the violation of laws or regulations in the course of participation in the Challenge. The United States Air Force and Space Force do not authorize or consent to participants infringing on any U.S. patent or copyright while participating in the Challenge. Signature of Entrant Official Date Appendix A: Participant Eligibility Verification Form‌ To protect your privacy, and to avoid the breach of any Personally Identifiable Information (PII), this form and any attachments shall be transmitted by a secure method. You may either submit: a) via email to xxxxx@xxxxxxxx.xxx as a password protected PDF, with the password submitted over Discord (preferred), or b) by regular mail to the address listed here: AFRL/RIBA

Technical Papers. To receive a Final Event prize, a team must submit an acceptable technical paper to the HAS4 HAS3 organizers describing their approach to winning the game, to include a description of the attack strategies and defensive measures employed during the Final Event. Final Event technical papers are due within 3 weeks of the conclusion of the Final Event (see Rules Section 9 for official dates/times). Formal technical write-ups must include enough detail to permit accurate stepwise understanding of the CTF challenge described. Write-ups should follow the format of typical CTF write-ups. As an example of acceptable write-up format please see (xxxxx://xxxxxx.xxx/cromulencellc/hackasat-finals-2022/tree/main/team_writeupsxxxxx://xxxxxx.xxx/ctfs/write-ups-2015/tree/master/defcon-qualifier-ctf-2015/babys- first/babyecho). The write- write-ups should include a background description of the vulnerabilities discovered and a description of the techniques used to exploit and/or patch those vulnerabilities. Associated source code, dependencies and instructions for deploying the code to address these vulnerabilities shall also be provided. The HAS4 HAS3 organizers will review write-write- ups and communicate acceptance to each entrant official. By making a submission to this prize contest, all participants (all members of the team) agree that no part of its submission includes any Trade Secret information, ideas, or products. All submissions to this prize contest are deemed non-proprietary. Since the United States Air Force and/or United States Space Force do not wish to receive or hold any submitted materials “in confidence” it is agreed that, with respect to the participant’s submission, no confidential or fiduciary relationship or obligation of secrecy is established between the U.S. Government, HAS4 HAS3 organizers, and the participant, the participant’s team, or the company or institution the participant represents when submitting, or any other person or entity associated with any part of the participant’s submission. The United States Air Force and Space Force reserve the right to disqualify a participant whose actions are deemed to violate the spirit of the competition for any reason, including but not limited to, the violation of laws or regulations in the course of participation in the Challenge. The United States Air Force and Space Force do not authorize or consent to participants infringing on any U.S. patent or copyright while participating in the Challenge. Signature of Entrant Official Date Appendix A: Participant Eligibility Verification Form‌ To protect your privacy, and to avoid the breach of any Personally Identifiable Information (PII), please mail a hardcopy of this form and any attachments shall be transmitted by a secure method. You may either submit: a) via email to xxxxx@xxxxxxxx.xxx as a password protected PDF, with the password submitted over Discord (preferred), or b) by regular mail to the address listed heresupporting documentation to: AFRL/RIBARIBA Attn: HAS3 00 Xxxxxxxxxxx Xxxxxxx Rome, NY 13441

Technical Papers. To receive a Final Event prize, a team must submit an acceptable technical paper to the HAS4 HAS2 organizers describing their approach to winning the game, to include a description of the attack strategies and defensive measures employed during the Final Event. Final Event technical papers are due within 3 weeks of the conclusion of the Final Event (see Rules Section 9 for official dates/times). Formal technical write-ups must include enough detail to permit accurate stepwise understanding of the CTF challenge described. Write-ups should follow the format of typical CTF write-ups. As an example of acceptable write-up format please see (xxxxx://xxxxxx.xxx/cromulencellc/hackasat-finals-2022/tree/main/team_writeupsxxxxx://xxxxxx.xxx/ctfs/write-ups-2015/tree/master/defcon-qualifier-ctf-2015/babys- first/babyecho). The write- write-ups should include a background description of the vulnerabilities discovered and a description of the techniques used to exploit and/or patch those vulnerabilities. Associated source code, dependencies and instructions for deploying the code to address these vulnerabilities shall also be provided. The HAS4 HAS2 organizers will review write-write- ups and communicate acceptance to each entrant official. By making a submission to this prize contest, all participants (all members of the team) agree that no part of its submission includes any Trade Secret information, ideas, or products. All submissions to this prize contest are deemed non-proprietary. Since the United States Air Force and/or United States Space Force do not wish to receive or hold any submitted materials “in confidence” it is agreed that, with respect to the participant’s submission, no confidential or fiduciary relationship or obligation of secrecy is established between the U.S. Government, HAS4 HAS2 organizers, and the participant, the participant’s team, or the company or institution the participant represents when submitting, or any other person or entity associated with any part of the participant’s submission. The United States Air Force and Space Force reserve the right to disqualify a participant whose actions are deemed to violate the spirit of the competition for any reason, including but not limited to, the violation of laws or regulations in the course of participation in the Challenge. The United States Air Force and Space Force do not authorize or consent to participants infringing on any U.S. patent or copyright while participating in the Challenge. Signature of Entrant Official Date Appendix A: Participant Eligibility Verification Form‌ To protect your privacy, and to avoid the breach of any Personally Identifiable Information (PII), please mail a hardcopy of this form and any attachments shall be transmitted by a secure method. You may either submit: a) via email to xxxxx@xxxxxxxx.xxx as a password protected PDF, with the password submitted over Discord (preferred), or b) by regular mail to the address listed heresupporting documentation to: AFRL/RIBARIBA Attn: HAS2 00 Xxxxxxxxxxx Xxxxxxx Rome, NY 13441