Code of Conduct
All participants (competitors, organizers, volunteers) are expected to behave professionally at all times throughout the duration of the competition. This means to treat others with dignity and respect, and to foster an open and welcoming environment for all involved. Anyone found to be violating this stipulation will be penalized at the discretion of the competition organizers.
All network traffic during the competition is being captured and logged. Do not enter any personal credentials unless you are comfortable with sharing it with the world.
All university and local/state/federal government rules apply and ultimately supersede the regulations listed
No alcohol or substance use will be tolerated, including smoking (the University at Buffalo is a smoke-free campus).
You are free to come and go from the competition room as you please so long as it is not for outside assistance regarding competition matters. What happens in the competition room stays in the competition room (until the event is over, then by all means talk about and review whatever you wish!)
Service Uptime: 40% of blue team scores will be determined by the uptime of various services within their network and configuration of new services and system, via inject request. These services include Ping (1), Ping (A), AD, HTTP, FTP, and IMAP. Teams will all have access to a scoreboard, which will show which services are currently “up” (meaning reachable and usable) and which are “down” (unreachable and/or unusable). Scoring engine checks occur in a synchronous fashion – each service will be checked once every 60 seconds. Misconfigurations and not following best practices will mostly likely result in loss of point. This is determined based on Red Team gaining access.
Injects: 40% of blue team scores will be determined by the successful and quality completion of the tasks they are given by the white team throughout the competition. Completeness counts, as does quality. It is expected that any injects that are written will be typed in a professional and report/documentation format. Anything you submit inject-wise should be something that you would feel comfortable submitting to your boss at work.
Incident Reports: 20% of blue team’s will be determined by the successful and quality reporting of any incidents that occurred during the competition. It is expected that any incident reports written will be typed in a professional and report/documentation format. The same rules apply that apply to Injects apply to Incident Reports .
The University at Buffalo owns all infrastructure – this includes hardware, software, the hypervisor/VM’s, etc. Treat it with respect and take due care to not cause any damage outside the scope of the competition.
You are not authorized to revert any VM’s to a previous snapshot or template, or create your own snapshots or templates. Doing so will result in a significant white team penalty. You may purchase this service from the white team during the competition, however (more information on that will be provided). The white team purchase will inform you of any penalties to your budget at the time of the request.
All software used by blue teams in the competition must be free and open source (FOSS) and publicly available to anyone. No personal use or commercial trial software will be allowed.
There is to be no “pre-staging” of scripts or software prior to the start of the competition (i.e. creating a .zip archive and hiding it on Dropbox). All scripts and software must be publicly available and free for any competitor. The exceptions to this rule are scripts that are written during the competition inside of virtual machines and scripts written on paper.
You may not touch another team’s infrastructure (either physical or virtual). Doing so will result in immediate disqualification for your team. If it isn’t your team’s – don’t touch it!
There is no attacking in this competition, but certain injects may have you using tools such as nmap. You must only use these tools on your own team’s network. Any activity that could be construed as reconnaissance or attacking against another team, the University, or an outside entity will result in immediate disqualification for your team.
You are allowed to collaborate with teams participating in the competition. Reason being, most industry professionals need to do this to be successful. Teams will still be individual scored even when a joint effort is made.
You may NOT block entire subnet ranges in your Firewall Rules – you can only block specific IP addresses and you must have proof that they are malicious if you do so.
You will have access to Internet on your host machines during the competition to use for looking up reference material. You may only use free and publicly available resources (i.e. no paid support forums).
On the subject of Internet on your host machines – you may not use the host machine Internet for anything unrelated to the competition. This means no Facebook, Reddit, Twitter, etc. (unless specifically allowed by the white team for the purpose of an inject).
Any and all paper-based reference materials (cheat sheets, books, printed PDF’s, etc.) are allowed and encouraged. You may also write scripts beforehand and print them on paper to bring with you.
No electronic media will be allowed in the competition, namely USB drives, external hard drives, CD’s/DVD’s/BD’s etc.