Each team will be provided with a problem scenario and a nonfunctional programmatic solution in either Java or C#. The solution will contain multiple coding errors to be corrected.

The team will be evaluated on the corrections implemented, providing the correct answer to the problem scenario, the time it takes for the program to execute, and the time it took the team to submit their corrections from the start of their scheduled 30 minute window.

Each team will bring their own device to attempt this challenge, any tools the team anticipates a need for should be downloaded in advance of the event. Upon arrival at the ASU Building located at 32 Commerce St, each team will be provided with a site to register a user for. The team will then execute various Cybersecurity challenge scenarios. When the team succeeds in a scenario, a flag will be provided, and the team will submit the flag for points. Example categories for this challenge include: Forensics, Website Exploitation, and Cryptography.

The team will be evaluated on the points awarded. The judging representative will annotate the score for the team at the end of their scheduled 120 minute window.

Each team will be provided two different computer with similar hardware and network cabling. Both systems will have Windows Operating Systems installed and identical hardware configurations. The team will be required to troubleshoot and fix system problems in order to network both computers and share a file from the desktop on System 2 to the desktop on System 1 and vice versa. Knowledge of ethernet cabling, Windows IPv4 configuration, Ad Hoc networking, Windows Network Profiles and Windows Firewall are advantageous. Teams will be evaluated based on their ability to have both systems communicating to one another and successfully sharing a file on each of the computers in a 30 minute time period.

Server Hardening is the process of securing a system by reducing its vulnerabilities. Some security measures and policies are specific to the server's role in an organization, but there are some configuration settings that should be done no matter what the server will be doing.

Using best practices, each team will be evaluated on how many tasks they have completed using an evaluator provided checklist. This checklist outlines tasks that would normally be done by a System Administrator to prepare a system for use.

Working knowledge of a Windows Server Operating System, along with the ability to use a Remote Desktop Service or Terminal Service to a Windows Server is encouraged. Teams will have 90 mins to complete this event.

Each team will choose a Smart City, Smart Base, Smart Campus problem, then create a prototype mobile application to address the chosen problem, and finally pitch the problem and prototype solution to a panel of judges. The application can be written in any language. The pitch presentation must state the following; team name, team members names, team member demographics, brief description of the application, major aspects/capabilities of the application, language application is written in, biggest technical challenge, and the resolution to the technical challenge. The presentation cannot exceed 5 minutes in length and must include screenshots of the application or a video driving through the application. Presentations must be posted to your assigned Google Drive by 4PM on Monday, August 27th. Every team member does NOT have to participate in the presentation delivered to the judges. Teams will be evaluated on creativity, innovation, and presentation of the application.

Teams will be evaluated on creativity, innovation, and presentation of the application.