Do This and Nothing More (DTANM) is a framework to run exercise modules that teach defensive programming and the "adversarial mindset" without requiring participants to have any special security knowledge. Like most beginners, programming students usually focus on how to get a particular outcome to occur; they try to answer the question "how do I get the program to work?" and neglect (or completely ignore) the question "what could cause this program to fail?" DTANM tries to teach them to think about protecting against failure without requiring them to be security experts.
In the security world we often teach adversarial thinking through demonstrating and interacting with classic vulnerabilities that are common and easy enough for students to grasp. Things like buffer overflows, directory traversal, SQL injection, cross-site scripting (XSS), and the like. But in order for students to perform these attacks and remediate them, they need to understand those vulnerabilities, common exploits, and other security-specific information. And even if they get this far, security exercises are often solo efforts -- the student against a static, predetermined challenge. It's only adversarial insofar as students pretend it is adversarial. Security competitions can teach adversarial thinking, but these tend to require even more special security knowledge and greater practical expertise in order to be competitive. They're not the best for novices.
We wanted to create a scenario where students could learn about and practice adversarial thinking in addition to developing a "hacking mindset" -- while requiring as little special security knowledge as possible. In Security in Computing, Pfleeger, Pfleeger and Margulies say "Wheras most requirements say 'the system will do this,' security requirements add the phrase 'and nothing more.'" This got us thinking -- perhaps we can create scenarios where students adversarially test and debug each others' programs -- finding edge cases and situations where the program does not act as it should, but where they don't need special security knowledge.
In order to be a "fair fight," students need to be working on the same program. So, in DTANM competitions, teams are given the same copy of a base program and a description of what the base program is supposed to do. Of course, like pretty much all software, the base program does not actually 100% fulfill or obey the specification. The teams' job is to find ways that the program deviates from the specification. Once they find these "attack vectors", they submit them to the framework. Then, the DTNAM framework takes those vectors and forces every team's copy of the program to run on that input -- causing programs that are still "vulnerable" to the bug to fail, while improved programs will operate correctly. In order to determine conclusively if a behavior is correct, we also create a 'gold' version of the base program that works as close to the specification as possible. Students can determine whether their program meets the requirement by comparing their own program to the performance of 'gold'. (Of course, they can't have gold's sourcecode...)
Since every DTANM competition works essentially the same way, we decided to work on a framework that could support competitions using a variety of base programs, rather than a single, hard-coded program. That's what the DTANM Framework is -- a tool for running DTANM competitions in conjunction with a "program pack" (which are packaged separately). The rest of this document describes how to install and start a generic DTANM competition; specific instructions for each "program pack" are included in their own documentation.
- A publicly accessible web server
- A DTANM pack. (Find instructions on building your pack at https://github.com/UMDLARS/dtanm_pack, or contact the developers for pre-made packs.) Make sure you update the settings in the config.py file, including ADMIN_USER_EMAIL and ADMIN_USER_PASSWORD, which will be the credentials that you will sign in with to configure the web UI.
- A domain name, if you want to enable non-self-signed HTTPS
- Docker installed (how to install Docker)
For normal use, we recommend downloading prebuilt Docker images. These should be up to date with the master branch of this repo, and are tested for stability.
wget -O docker-compose.yml https://raw.githubusercontent.com/UMDLARS/dtanm/master/docker-compose-prebuilt.yml
ln -s $MY_PACK_LOCATION pack # Substitute your pack's location here
docker-compose up -dWe don't guarantee the stability of a competition run built from source. However, it should work fine to clone the repo and build your competition from source. This is particularly recommended if you want to modify any aspect of the framework.
git clone https://github.com/UMDLARS/dtanm.git
cd dtanm
ln -s $MY_PACK_LOCATION pack # Substitute your pack's location here
docker-compose up -d --build # Build and start the server- visit the URL on which you're hosting (http://localhost:5000, commonly, if you're not proxying the service) and use the admin panel to set up teams and users. This uses the ADMIN_USER_EMAIL and ADMIN_USER_PASSWORD that you set up in the prerequisites step. Make sure to change your password!
- Set up reverse proxy for HTTPS. We use nginx and letsencrypt, for example:
# as root, fresh debian install
apt update
apt install -y nginx certbot python-certbot-nginx
echo "
server {
listen 80 default_server;
listen [::]:80 default_server;
server_name YOUR.DOMAIN.NAME.HERE.edu;
location / {
proxy_pass http://localhost:5000;
proxy_set_header Host \$host;
}
}
" > /etc/nginx/sites-enabled/default # CAREFUL! This will overwrite all your existing nginx config!
certbot --nginx
service nginx restart- Scale the number of workers: Particularly on machines equipped with an SSD,
speed of scoring scales fairly well with the number of worker containers.
We've had good luck with 8, which is somewhere between 4-6x faster than just
having one. (There's no magic behind 8; it's just a nice round number. Other
values may be better for you, and we'd welcome some performance benchmarks!)
To scale the service, simply run
docker-compose up -d --scale worker=8, or your chosen scale of workers. (Only the worker thread needs to be scaled.) This can be run either in place of thedocker-compose up -ddocumented above, or at any point after that (including during the competition!); it acts declaratively and will not change any existing containers.
To disable the server, make sure you've saved/exported any data from the
competition that you don't want to lose, and run docker-compose down in
the dtanm directory. If you're running a proxy, you may also want to disable
that (e.g. sudo service nginx stop).
Email the devteam at [email protected] -- or better yet, join it by subscribing to our list.