IScorE Now Online!

Leave a reply
IScorE, our CDC scoring application, is now online!
During the setup phase there are a few things on IScorE that you need to pay attention to:
  • Your flags. You will find a link to download them.  You must place these on your servers in the spots specified in the Rules Doc.
  • Dave and Susie’s passwords.  These are located on your dashboard under your team’s information.
  • User Social Security numbers.  These are located near the passwords.  You must use these SSNs when creating users in the Payroll app.
  • Service status.  Check to see if our scanner picks up your services so that you get points!  The scanner scans every 10 minutes during setup, and every 5 minutes during the attack phase.
  • Team information.  Feel free to upload a picture, it will display next to your team on the scoreboard.
Here’s the link: https://iscore.iseage.org/  Use the same credentials that you use to login to RDP and vCenter.
IScorE is relatively new (just over a year old!) compared to our CDCs.  It is still under active development, and as the lead developer of the project I love getting feedback.  If you have any problems with IScorE, encounter something that is confusing, or have ideas for new features, pleaselet us know!  You can email all the developers at iscore@iastate.edu or talk to me personally.

NTP Server Now Available

Leave a reply

Is the white team running an NTP server available to the blue teams to use? This would help us coordinate our logs, events and activities with white teams records of events.

Yes! An NTP server is now available at time.cdc.net, or 199.100.16.100 (the proxy server).

On Windows, right-click the clock, choose “Adjust date/time”, then click on the “Internet Time” tab.

On *nix systems, install ntpdate to easily synchronize with our server:

ntpdate time.cdc.net

You can also install an NTP daemon to sync automatically upon startup. See the documentation associated with your distro for more information.

Can you provide KMS information so we can keep our Windows Servers from locking up in three days?

ISU does not have a KMS server that licenses Windows Server installs. The ISOs we provided for 2008 R2 will be good for 30 days without entering a key. Just to verify this, I accessed your two active Windows VMs (RDP and your DC rebuild); both report that they are set to 30-day expiration. In the event that those do start complaining sooner, you can always re-arm as well using: slmgr.vbs /rearm

Shell Server Test Script now available!

Leave a reply

The script to test your shell server is now available from inside the ISEAGE network at http://blue.cdc.net/compile_test.sh

You can grab and run this easily via command line (assuming you’ve set up your network interface properly):

wget http://blue.cdc.net/compile_test.sh
chmod +x compile_test.sh
./compile_test.sh

Please note the difference between the java runtime (java) and java compiler (javac), as you will need both to function correctly!

The script automatically generates and deletes source files to run its tests. If you’d prefer to use these files for troubleshooting, simply set the PRESERVE variable near the beginning of the script to 1.

If you’d like to examine it on your local machine, it is also available here: compile_test.sh_.txt Remove the “_.txt” ending before running it.

Can we use a non-Windows solution to act as a Domain Controller?

You can try using another system to emulate a Windows DC if you wish. Please understand that there is a risk for you to do this. We have only tested our service scanner against a Windows AD, so if there is some quirk with your non-windows based solution that causes the service scanner not to register it, that will be something you will be responsible for.

As mentioned in the Scenario, your system will not only need to be able to bind via LDAP, but also need to issue Kerberos tickets in tandem.

Again, even if it works in your testing but not with our scanner, it’s on you to fix.

Can we replace the payroll application with a completely different software solution?

No.

Replacing the payroll application with another existing solution or scratching it and writing it from the ground up are not viable options for the purposes of this competition. Keep in mind we are trying to emulate a real IT department at a real company. Realistically you would not be able to come in a re-write all the company’s web apps. Even moving them to other existing solutions is not a trivial task, particularly for a payroll application.