NECCDC Rules

NECCDC subscribes to the National CCDC Rules, which all teams must follow.

https://www.nationalccdc.org/rules.html

National Rules Amendments

2. Team Composition

• Team rosters must be submitted before published deadlines, and all team members must meet all stated eligibility requirements.
• Any changes to the team rosters can be made before the NECCDC Qualifier event, and must be communicated with Nationals and NECCDL (contact@neccdl.org) at least 24 hours in advance of the competition.
• During the NECCDC Regional, any eight (8) members from the submitted roster can compete on day 1 and a different set of eight (8) on day 2.
  • This change between day 1 and 2 of the NECCDC Regional does not need to be communicated.
  • There are to be no substitutions or additions during the competition day without explicit permission from the competition director.

4. Competition Conduct

n. Containerizing scored applications is allowed by NECCDC. Keep in mind before migrating, the Orange team will check existing business logic inside the application.

5. Internet Usage

f. Competitor Code Repositories

1. Teams must submit their repositories one week before each competition through a form shared by the League.
2. Once an ongoing competition ends, teams can update their repository. (i.e. updatable between Qualifiers and Regionals)
3. Using GIT is preferred for submitting resources. Repositories should be moved to read-only or archived during the freeze period.

Beta Test

1. Teams are allowed to download artifacts they generate (scan, inventory, etc.) from systems.
2. Existing files (ex. config file) or images cannot be downloaded/extracted.
3. Screenshots are allowed, and note taking is encouraged.
4. System redeployments are not permitted.