Difference between revisions of "OWASP Security Shepherd"

From OWASP
Jump to: navigation, search
(Updating Project Status Banner)
(Wiki Restruture)
Line 1: Line 1:
<div style="width:100%;height:90px;border:0,margin:0;overflow: hidden;">[[File: lab_big.jpg|link=OWASP_Project_Stages#tab.3DLab_Projects]]</div>
+
=Main=
[[Image:Shepherd-Injection-Lesson.JPG|thumb|300px|right|Detailed vulnerability explainations]][[Image:Shepherd-Scoreboard.JPG|thumb|300px|right|Competitive Learning Environment]]
+
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div>
'''Security Shepherd''' is a computer based training application for web and mobile application security vulnerabilities. This project strives to herd the lost sheep of the technological world back to the safe and sound ways of secure practices. Security Shepherd can be deployed as a CTF (Capture the Flag) game or as an open floor educational server.
+
<div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:Lab_big.jpg|link=]]</div>
 +
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 +
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
  
== Overview ==
+
==OWASP Security Shepherd==
[[Image:Shepherd-CTF-Level-One.JPG|thumb|300px|right|Easy configuration to suit every use]]
 
Security Shepherd has been implemented with the aim of fostering and improving security awareness among a varied skill-set demographic. This project enables users to learn or to improve upon existing manual penetration testing skills. This is accomplished through lesson and challenge techniques. A lesson provides a user with a lot of help in completing that module, where a challenge puts what the user learned in the lesson to use. Utilizing the OWASP top ten as a challenge test bed, common security vulnerabilities can be explored and their impact on a system understood. The by-product of this challenge game is the acquired skill to harden a player's own environment from OWASP top ten security risks. The modules have been crafted to provide not only a challenge for a security novice, but security professionals as well.
 
  
Security Shepherd's vulnerabilities are not simulated, and are instead delivered through hardened real security vulnerabilities that can not be abused to compromise the application or its environment. Many of these levels include insufficient protections to these vulnerabilities, such as black list filters and poor security configuration.
+
OWASP Security Shepherd is a web and mobile application security training platform. Security Shepherd has been designed to foster and improve security awareness among a varied skill-set demographic. The aim of this project is to take any user, from AppSec novice to experienced engineer, and sharpen their penetration testing skillset to security expert status.
  
===CTF Mode===
+
==Description==
Security Shepherd can be morphed into a CTF server by an administrator with the click of a button. This presents users with one module at a time. They must complete their current level before they can continue. Administrators can also set a "Module Block" that prevents users from progressing past a certain level. It is also possible to run a CTF in a Tournament mode where a user can complete any module in any order they wish. When either of these modes are enabled, the scoreboard is then available. The scoreboard updates automatically and reflects the bonus points users achieve by completing a module first, second or third.
 
  
===User Management===
+
OWASP Security Shepherd project enables users to learn or to improve upon existing manual penetration testing skills. This is accomplished by presenting security risk concepts to users in lessons followed by challenges. A lesson provides a user with help in layman terms about a specific security risk, and help them exploit a text book version of the issue. Challenges include poor security mitigations to the security risk which have left room for user's to exploit.
Security Shepherd includes a user friendly method of creating many users at a time for administrators, as well as an optional open registry system. Users' activities are logged allowing an administrator to gather real time data on who is connected to Security Shepherd and what their module progress is. This data can be mined to gather information on who was online, at what time and how much time has been actively spent on a challenge.
 
  
===Topic Coverage===
+
Utilizing the OWASP top ten as a challenge test bed, common security vulnerabilities can be explored and their impact on a system understood. The by-product of this challenge game is the acquired skill to harden a player's own environment from OWASP top ten security risks. The modules have been crafted to provide not only a challenge for a security novice, but security professionals as well.
 +
 
 +
Security Shepherd's security risks are delivered through hardened real security vulnerabilities that can not be abused to compromise the application or its environment. Shepherd does not simulate security risks so that all and any attack vectors will work, ensuring a real world response.
 +
 
 +
Security Shepherd is highly configurable. System administrators can tune the project experience to present specific security risk topics or even specific Security Shepherd modules. The array of user and module configuration available allows Shepherd to be used by a single local user, by many in a competitive classroom environment or by hundreds in an online hacking competition.
 +
 
 +
==Layout Options==
 +
 
 +
An administrator user of Security Shepherd can change the layout in which the levels are presented to players. There are three options:
 +
 
 +
'''CTF Mode'''
 +
 
 +
When Shepherd has been deployed in the CTF mode, a user can only access one uncompleted module at a time. The first module presented to the user is the easiest in Security Shepherd, which has not been marked as closed by the administrator. The levels increase slowly in difficulty and jump from one topic to another. This layout is the recommended setting when using Security Shepherd for a competitive training scenario.
 +
 
 +
'''Open Floor'''
 +
 
 +
When Shepherd has been deployed in the Open Floor mode, a user can access any level that is marked as open by the admin. Modules are sorted into their Security Risk Categories, and the lessons are presented first. This layout is ideal for users wishing to explore security risks.
 +
 
 +
'''Tournament Mode'''
 +
 
 +
When Shepherd has been deployed in the Tournament Mode, a user can access any level that is marked as open by the admin. Modules are sorted into difficulty bands, from least to most difficult. This layout is ideal when Shepherd is being utilised as an open application security competition. 
 +
 
 +
 
 +
| valign="top"  style="padding-left:25px;width:350px;border-right: 1px dotted gray;padding-right:25px;" |
 +
 
 +
== What is Security Shepherd? ==
 +
 
 +
OWASP Security Shepherd provides:
 +
 
 +
* Teaching Tool for All Application Security
 +
* Web Application Pen Testing Training
 +
* Mobile Application Pen Testing Training
 +
* Safe Playground to Practise AppSec Techniques
 +
* Real Security Risk Examples
 +
 
 +
==Topic Coverage==
 
The Security Shepherd project covers the following web application security topics;
 
The Security Shepherd project covers the following web application security topics;
  
*[[Top_10_2010-A1|SQL Injection]]
+
*[[Top_10_2013-A1|SQL Injection]]
*[[Top_10_2010-A2|Cross Site Scripting]]
+
*[[Top_10_2013-A2|Broken Authentication and Session Management]]
*[[Top_10_2010-A3|Broken Authetication and Session Management]]
+
*[[Top_10_2013-A3|Cross Site Scripting]]
*[[Top_10_2010-A5|Cross Site Rrequest Forgery]]
+
*[[Top_10_2013-A4|Insecure Direct Object Reference]]
*[[Top_10_2010-A4|Insecure Direct Object Reference]]
+
*[[Top_10_2013-A6|Sensitive Data Exposure]]
*[[Top_10_2010-A7|Insecure Cryptographic Storage]]
+
*[[Top_10_2013-A7|Missing Function Level Access Control]]
*[[Top_10_2010-A8|Failure to Restrict URL Access]]
+
*[[Top_10_2013-A8|Cross Site Request Forgery]]
*[[Top_10_2010-A10|Unvalidated Redirects and Forwards]]
+
*[[Top 10 2013-A10|Unvalidated Redirects and Forwards]]
*[[Top_10_2010-A9|Insufficient Transport Layer Security]]
 
 
*[[Mobile_Top_10_2014-M2|Insecure Data Storage]]
 
*[[Mobile_Top_10_2014-M2|Insecure Data Storage]]
 +
*[[Mobile_Top_10_2014-M4|Unintended Data Leakage]]
 +
*[[Mobile_Top_10_2014-M5|Poor Authentication and Authorisation]]
 +
*[[Mobile_Top_10_2014-M6|Broken crypto]]
 
*[[Mobile_Top_10_2014-M7|Client Side Injection]]
 
*[[Mobile_Top_10_2014-M7|Client Side Injection]]
 
*[[Mobile_Top_10_2014-M10|Lack Of Binary Protections]]
 
*[[Mobile_Top_10_2014-M10|Lack Of Binary Protections]]
*[[Mobile_Top_10_2014-M4|Unintended Data Leakage]]
 
*[[Mobile_Top_10_2014-M6|Broken crypto]]
 
  
==Download==
 
  
You can download the Security Shepherd VM or Manual Installation Pack from [https://sourceforge.net/projects/owaspshepherd/files/ Source Forge].
+
== Related Projects ==
 +
 
 +
* [[OWASP_WebGoat_Project]]
 +
 
 +
==Licensing==
 +
The Security Shepherd project is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
 +
 
 +
The Security Shepherd project is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of  merchantability or fitness for a particular purpose.  See the GNU General Public License for more details. See http://www.gnu.org/licenses/ .
 +
 
 +
 
 +
| valign="top"  style="padding-left:25px;width:250px;" |
 +
 
 +
== Download ==
 +
 
 +
* [https://sourceforge.net/projects/owaspshepherd/files/ OWASP Security Shepherd SourceForge]
 +
 
 +
== Presentation ==
 +
 
 +
[https://www.youtube.com/watch?v=-brsnYrksAI AppSecEU 2014 Video]
 +
 
 +
[http://2014.appsec.eu/wp-content/uploads/2014/07/Sean.Duggan-OWASP-Security-Shepherd-Mobile-Web-Security-Awareness-and-Education.pdf AppSecEU 2014 Presentation]
 +
 
 +
== Project Leaders ==
 +
 
 +
Mark Denihan - mark.denihan@owasp.org
 +
 
 +
Sean Duggan  - sean.duggan@owasp.org
 +
 
 +
== Recent News and Events ==
 +
* [May 2015] Security Shepherd @ AppSecEU 2015 Project Summit
 +
* [May 2015] Shepherd v2.3 Released
 +
* [April 2015] Security Shepherd's platform was used to run the LATAM Tour 2015 Online CTF
 +
* [December 2015] Shepherd V2.2 Released
 +
 
 +
==Classifications==
 +
 
 +
  {| width="200" cellpadding="2"
 +
  |-
 +
  | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-labs-trans-85.png|100px|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Lab_Projects]]
 +
  | align="center" valign="top" width="50%"| [[File:Owasp-breakers-small.png|link=]] 
 +
  |-
 +
  | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=]]
 +
  |-
 +
  | colspan="2" align="center"  | [[File:Project_Type_Files_TOOL.jpg|link=]]
 +
  |}
 +
 
 +
|}
 +
 
 +
=FAQs=
 +
 
 +
; Q1 Can I Re-Skin Shepherd and then Train People With it?
 +
: A1 Yes! Shepherd plans to include this in-app in version 2.4
 +
 
 +
; Q2 Where can I access Security Shepherd?
 +
: A2 You can Download it and run it yourself, ask your lecturer to, and we tend to have a public environment available at https://owasp.securityshepherd.eu/ . It operates on a Research Network in ITB's Security Research Lab, so it can be in a state of flux.
 +
 
 +
= Acknowledgements =
 +
==Contributors==
 +
OWASP Security Shepherd is developed by a worldwide team of volunteers. The primary contributors to date have been:
 +
 
 +
* Mark Denihan
 +
* Sean Duggan
 +
* Ciaran Napier
 +
* Jason Flood
 +
* Patrick Hanily
 +
* Peter Dolan
 +
 
 +
The Security Shepherd template makes it extremely easy to add additional lessons. We are actively seeking developers to add new lessons as new web technologies emerge. If you are interested in volunteering for the project, or have a comment, question, or suggestion, please contact Mark.denihan@owasp.org
 +
 
 +
New levels or level ideas are wanted in the highest degree and there is development is in progress to fork the Security Shepherd platform into a CTF framework. If you wish to contribute a level or even an idea; contact Mark Denihan on mark.denihan@owasp.org. The aim of Security Shepherd's future development is to create a comprehensive platform for web and mobile application pen testing training / security risk education. Check out the project [http://bit.ly/securityShepherdGithub GitHub] and find some issues that you can help with right away.
 +
 
 +
To contribute right away, pull the source from [http://bit.ly/securityShepherdGithub GitHub]
 +
 
 +
==Other==
 +
Both the Security Shepherd Platform and the Mobile Shepherd aspects of this project were initially created as part of BSc degrees in the Dublin Institute of Technology. Thanks to DIT for allowing those projects to be donated to the OWASP community.
  
==Releases==
+
== Project Sponsors ==
  
Security Shepherd has been designed with expansion in mind. The application's underlying architecture is composed of a secure core application and database server that depicts how the application runs. There is also an exposed application and database service that runs all of the server side vulnerability examples. If these services are compromised, the core service can continue to run unaffected.
+
The OWASP Security Shepherd project would like to acknowledge and thank the generous support of our sponsors. Please be certain to visit their stall at the [http://bit.ly/AppSecEu2014|OWASP AppSec EU 2015] conference as well as follow them on [http://bit.ly/bccRiskAdvisory Twitter].  
  
Security Shepherd is written in Java and is compiled in a web application archive (WAR) and therefore can be run on any platform with a Java virtual machine and a web application server like Tomcat. To eliminate tedious environment configuration; there is a Security Shepherd Virtual Machine. This environment includes Tomcat/MySQL servers pre-loaded with Security Shepherd. For those that prefer the path of higher resistance or want to build a dedicated Security Shepherd server, a manual pack is available for download as well.
+
[[File:BccRiskAdvisoryLogo.jpg]]
  
 +
[[File:EdgescanLogo.jpg]]
 +
 +
=Setup Help=
 
===Security Shepherd v2.3 VM Setup:===
 
===Security Shepherd v2.3 VM Setup:===
 
To get a Security Shepherd VM ready to rock, follow these steps;
 
To get a Security Shepherd VM ready to rock, follow these steps;
Line 84: Line 193:
 
* Follow in application prompts for further configuration
 
* Follow in application prompts for further configuration
  
== Future Development ==
+
=Screenshots=
 
+
[[Image:Shepherd-Injection-Lesson.JPG|thumb|300px|left|Detailed vulnerability explainations]][[Image:Shepherd-Scoreboard.JPG|thumb|300px|left|Competitive Learning Environment]] [[Image:Shepherd-CTF-Level-One.JPG|thumb|300px|left|Easy configuration to suit every use]]
New levels or level ideas are wanted in the highest degree and there is development is in progress to fork the Security Shepherd platform into a CTF framework. If you wish to contribute a level or even an idea; contact Mark Denihan on mark.denihan@owasp.org.
 
 
 
The aim of Security Shepherd's future development is to create a comprehensive platform for web and mobile application pen testing training / security risk education.
 
Check out the project [https://www.owasp.org/index.php/Projects/OWASP_Security_Shepherd/Roadmap roadmap] and find some tasks that you can help with right away..
 
 
 
To contribute right away, pull the source from [http://bit.ly/securityShepherdGithub GitHub]
 
 
 
== Events with Security Shepherd ==
 
[[Image:Shepherd-CTF-In-Play.JPG|thumb|300px|right|Over 60 people playing the CTF at [[HackDub2012]]]]
 
 
 
The Security Shepherd application has been tried and tested across a number of Beta runs in venues like Facebook and the IRISScon CTF. Since these events Security Shepherd has been knocking on security doors trying to be recognized as the new platform for web application security training.
 
 
 
* Security Shepherd was used as the [[HackDub2012|OWASP Dublin Hackathon 2012]]
 
* Security Shepherd's platform was used be used to manage the [[AppSecIreland2012| OWASP Ireland AppSec 2012]] CTF in September 2012
 
* Security Shepherd's platform was used to administer the Traditional Style CTF at the IRISS security conference in October 2012 and 2013
 
* Security Shepherd's platform was used to deliver the Traditional Style CTF at the 2013 SOURCE Conference CTF in Facebook
 
* Security Shepherd's platform was used to govern the EU Tour 2013 and LATAM Tour 2013 Online CTF's
 
* Security Shepherd's platform was used to conduct the 2013 OWASP Global CTF
 
* Security Shepherd was used as the 2014 OWASP application security summer school CTF at the Faculty of Organization and Informatics in Varaždin
 
* Security Shepherd's platform was used to run the LATAM Tour 2015 Online CTF
 
 
 
== Project Contributors ==
 
 
 
The Security Shepherd project was founded and is ran by Mark Denihan. The mobile wing of Security Shepherd is lead by Sean Duggan. If you wish to contribute to the OWASP Security Shepherd project please contact at mark.denihan@owasp.org, as help in any regard of the application is very much appreciated.  Security Shepherd distributions are currently maintained on [http://bit.ly/shepherdSourceForge SourceForge]. The Security Shepherd template makes it extremely easy to add additional lessons. We are actively seeking developers to add new lessons as new web technologies emerge. If you are interested in volunteering for the project, or have a comment, question, or suggestion, please join the Security Shepherd [https://lists.owasp.org/mailman/listinfo/owasp_security_shepherd mailing list].
 
 
 
Both the Security Shepherd Platform and the Mobile Shepherd aspects of this project were initially created as part of BSc degrees in the Dublin Institute of Technology. Thanks to [http://www.dit.ie DIT] for allowing those projects to be donated to the OWASP community.
 
 
 
== Project Sponsors ==
 
 
 
The OWASP Security Shepherd project would like to acknowledge and thank the generous support of our sponsors. Please be certain to visit their stall at the [http://bit.ly/AppSecEu2014|OWASP AppSec EU 2014] conference as well as follow them on [http://bit.ly/bccRiskAdvisory Twitter].
 
[[File:BccRiskAdvisoryLogo.jpg]][[File:EdgescanLogo.jpg]]
 
 
 
[[Category:OWASP Project|Security Shepherd Project]]
 
[[Category:OWASP Download]]
 
[[Category:OWASP Tool]]
 
[[Category:OWASP Release Quality Tool]]
 
  
__NOTOC__
+
__NOTOC__ <headertabs />
  
[[Category:OWASP Project]]
+
[[Category:OWASP Project]]  [[Category:OWASP_Builders]] [[Category:OWASP_Breakers]]  [[Category:OWASP_Tool]]

Revision as of 09:09, 19 May 2015

OWASP Project Header.jpg
Lab big.jpg

OWASP Security Shepherd

OWASP Security Shepherd is a web and mobile application security training platform. Security Shepherd has been designed to foster and improve security awareness among a varied skill-set demographic. The aim of this project is to take any user, from AppSec novice to experienced engineer, and sharpen their penetration testing skillset to security expert status.

Description

OWASP Security Shepherd project enables users to learn or to improve upon existing manual penetration testing skills. This is accomplished by presenting security risk concepts to users in lessons followed by challenges. A lesson provides a user with help in layman terms about a specific security risk, and help them exploit a text book version of the issue. Challenges include poor security mitigations to the security risk which have left room for user's to exploit.

Utilizing the OWASP top ten as a challenge test bed, common security vulnerabilities can be explored and their impact on a system understood. The by-product of this challenge game is the acquired skill to harden a player's own environment from OWASP top ten security risks. The modules have been crafted to provide not only a challenge for a security novice, but security professionals as well.

Security Shepherd's security risks are delivered through hardened real security vulnerabilities that can not be abused to compromise the application or its environment. Shepherd does not simulate security risks so that all and any attack vectors will work, ensuring a real world response.

Security Shepherd is highly configurable. System administrators can tune the project experience to present specific security risk topics or even specific Security Shepherd modules. The array of user and module configuration available allows Shepherd to be used by a single local user, by many in a competitive classroom environment or by hundreds in an online hacking competition.

Layout Options

An administrator user of Security Shepherd can change the layout in which the levels are presented to players. There are three options:

CTF Mode

When Shepherd has been deployed in the CTF mode, a user can only access one uncompleted module at a time. The first module presented to the user is the easiest in Security Shepherd, which has not been marked as closed by the administrator. The levels increase slowly in difficulty and jump from one topic to another. This layout is the recommended setting when using Security Shepherd for a competitive training scenario.

Open Floor

When Shepherd has been deployed in the Open Floor mode, a user can access any level that is marked as open by the admin. Modules are sorted into their Security Risk Categories, and the lessons are presented first. This layout is ideal for users wishing to explore security risks.

Tournament Mode

When Shepherd has been deployed in the Tournament Mode, a user can access any level that is marked as open by the admin. Modules are sorted into difficulty bands, from least to most difficult. This layout is ideal when Shepherd is being utilised as an open application security competition.


What is Security Shepherd?

OWASP Security Shepherd provides:

  • Teaching Tool for All Application Security
  • Web Application Pen Testing Training
  • Mobile Application Pen Testing Training
  • Safe Playground to Practise AppSec Techniques
  • Real Security Risk Examples

Topic Coverage

The Security Shepherd project covers the following web application security topics;


Related Projects

Licensing

The Security Shepherd project is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

The Security Shepherd project is distributed in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose. See the GNU General Public License for more details. See http://www.gnu.org/licenses/ .


Download

Presentation

AppSecEU 2014 Video

AppSecEU 2014 Presentation

Project Leaders

Mark Denihan - mark.denihan@owasp.org

Sean Duggan - sean.duggan@owasp.org

Recent News and Events

  • [May 2015] Security Shepherd @ AppSecEU 2015 Project Summit
  • [May 2015] Shepherd v2.3 Released
  • [April 2015] Security Shepherd's platform was used to run the LATAM Tour 2015 Online CTF
  • [December 2015] Shepherd V2.2 Released

Classifications

Owasp-labs-trans-85.png Owasp-breakers-small.png
Owasp-builders-small.png
Project Type Files TOOL.jpg
Q1 Can I Re-Skin Shepherd and then Train People With it?
A1 Yes! Shepherd plans to include this in-app in version 2.4
Q2 Where can I access Security Shepherd?
A2 You can Download it and run it yourself, ask your lecturer to, and we tend to have a public environment available at https://owasp.securityshepherd.eu/ . It operates on a Research Network in ITB's Security Research Lab, so it can be in a state of flux.

Contributors

OWASP Security Shepherd is developed by a worldwide team of volunteers. The primary contributors to date have been:

  • Mark Denihan
  • Sean Duggan
  • Ciaran Napier
  • Jason Flood
  • Patrick Hanily
  • Peter Dolan

The Security Shepherd template makes it extremely easy to add additional lessons. We are actively seeking developers to add new lessons as new web technologies emerge. If you are interested in volunteering for the project, or have a comment, question, or suggestion, please contact Mark.denihan@owasp.org

New levels or level ideas are wanted in the highest degree and there is development is in progress to fork the Security Shepherd platform into a CTF framework. If you wish to contribute a level or even an idea; contact Mark Denihan on mark.denihan@owasp.org. The aim of Security Shepherd's future development is to create a comprehensive platform for web and mobile application pen testing training / security risk education. Check out the project GitHub and find some issues that you can help with right away.

To contribute right away, pull the source from GitHub

Other

Both the Security Shepherd Platform and the Mobile Shepherd aspects of this project were initially created as part of BSc degrees in the Dublin Institute of Technology. Thanks to DIT for allowing those projects to be donated to the OWASP community.

Project Sponsors

The OWASP Security Shepherd project would like to acknowledge and thank the generous support of our sponsors. Please be certain to visit their stall at the AppSec EU 2015 conference as well as follow them on Twitter.

BccRiskAdvisoryLogo.jpg

EdgescanLogo.jpg

Security Shepherd v2.3 VM Setup:

To get a Security Shepherd VM ready to rock, follow these steps;

Setting up your instance of Security Shepherd with the VM: In Steps!

  • Import the VM to your hyper visor (Eg: Virtual Box)
  • Make sure the VM has a bridged adapter (or a Host-Only adapter if you don't want anyone else to connect)
  • Boot the VM
  • Sign in with securityshepherd / owaspSecurityShepherd
  • Change the user password with the passwd command
  • In the VM, run "ifconfig" to find the IP address. Make note of this
  • On your host machine, open http://<VM IP Address>/
  • Sign in with admin / password
  • Change the admin password (cannot be password again)
  • Time to play!

Security Shepherd v2.3 Manual Pack:

The manual release is a single download, unrar, and follow the steps release.

  • Download the Security Shepherd Manual Pack
  • Install Apache Tomcat 7
  • Install MySql, using the default password (Contained in readme.txt) to skip future steps, if you prefer your own password go ahead and set-up MySql with that instead!
  • Extract the Security Shepherd Manual Pack
  • Copy the sql files extracted from the pack to the bin directory of MySql
  • Open MySql from the command line (eg: mySqlBinDirectory/mysql -u root -p )
  • Type the following commands to execute the Shepherd Manual Pack SQL files;

source core.sql source exposedSchema.sql

  • Open the webapps directory of your Tomcat instance
  • Delete any directories that are there already
  • Move the WAR file from the Shepherd Manual Pack into the webapps folder of Tomcat
  • Start Tomcat
  • Open the temp directory of Tomcat
  • If you chose the default when configuring MySql as your DB password, you are running MySql on the same machine as Tomcat and you are using port 3306 for MySql, you can skip this step. Otherwise, in the ROOT directory found in the temp folder, modify the /WEB-INF/coreDatabase.properties to point at your local DB with your MySql settings. Leave the Driver alone!
  • If you have more than one ROOT or Exposed folder in your temp folder, visit your Tomcat instance with your browser and then check the Tomcat logs for a line that reads "Servlet root =" to find which directory is the correct one to modify the MySql settings of.
  • Open your the root context of your Tomcat server (eg: http://127.0.0.1:8080/ )
  • Sign into Security Shepherd with the default admin credentials (admin / password)
  • Change the admin password
  • Follow in application prompts for further configuration
Detailed vulnerability explainations
Competitive Learning Environment
Easy configuration to suit every use