sdmay22-07 • Hackerville

This theme uses "root" links to dependencies and assets (CSS, JS, images, etc.). Place all theme files and directories at the root of your web server for this page to render as intended.

Senior Design Team sdmay22-07 • Hackerville

Introduction

Hello! This is the team website for sdmay22-07, the 7-person group working on Hackerville alongside our faculty advisor, Doug Jacobson.

Team Members & Roles

Andrew Groebe - Software Tester & Developer

Brady Heath - Client Communicator & Developer

Emily Hohneke - Team Organizer & Developer

Adam LaRocque - Lead Client Communicator & Developer

Isabel Maymir - Client Communicator & Developer

Liz Memmini - Team Organizer & Developer

Andrew Sandor - Software Tester & Developer

What is Hackerville?

Hackerville is a fictitious village where the cyber family and their friends live. The village has numerous bad people that want to do harm to the family using the internet. The idea is that we can use hackerville.org to provide hands-on activities to allow students to experience cyber security attacks and defenses. www.hackerville.org is the primary hosting site for the web infrastructure and will contain tools to help teach cyber security. In addition it also will host all of the web sites (good and bad) that support teaching cyber security like citybank.com.hackverville.org. For example we can use citybank.com.hackerville.org and fake-citybank.com.hackerville.org to have students experience different types of authentication and authentication attacks, phishing attacks, etc. Students / users can take on various roles in hackerville based on exercise. In some cases they will be a member of the cyber family, a friends of the family, a good person, or a bad person. They can also become citizens of hackerville and interact with each other along with interacting with the predefined roles.

Technology

While the majority of our technical implementation will begin next semester, we currently have a solid idea of the technical architechture of Hackerville. First and foremost, our website will utilize WordPress where it makes sense to do so. This includes static pages that do not need much interactivity or custom content. For more complex pages, we will create our own HTML pages that will be served from Apache on our backend server. LDAP will be used for our user authentication and authorization, and our frontend will interact with this backend service. Lastly, we plan to utilize automated testing heavily, such as shell scripts and Selenium for testing our functionality.