Hacking-Lab Challenge Development Procedures
This article is created for challenge developers of Hacking-Lab who want to integrate a docker challenges into HL.
HL Challenge Development Overview
https://www.hacking-lab.com/blog/become-a-challenge-developer#main
idocker Challenges
https://www.hacking-lab.com/blog/idocker-challenge-developer#main
rdocker Challenges
https://www.hacking-lab.com/blog/rdocker-challenge-developer#main
HL Docker Templates
https://www.hacking-lab.com/blog/docker-template-generator-for-challenge-developers#main
Challenge Development
Information about HL components
Datacenter
ESXi
Storage
Git
Networking, Reverse Shells
Whitelisting of Client IP’s after HL Login (before services can be reached)
Admin VPN, Client Setup
Issuing HL server certificates (or client certificates)
Challenge Deployment
Creation of a challenge in a tenant
Creation of a challenge globally
Sharing challenges from tentant to global
Sharing challenge from global to tenant
Vulnerable Servers
VM
idocker, rdocker, multi-docker challenges
Deployment in Azure
Shared dockers (like Timesketch)
Challenge Development
FAQ for solving common problems
Requirements for the challenge description (for the user)
Level
Category
Task
Steps
How to write the solution do
Docker Development
Docker Templates
s6, flag deployments (FILE vs. ENV)
Resource Editor (Challenge Editor)
Docker Development Guidelines (file permission, archives, …)
use of HL docker images
use of non-HL docker images, Ubuntu, others
Docker Generator
LiveCD
Building the LiveCD (CI/CD) pipeline
VPN for CTF Players
Reverse Shells
HL App Usage
Create, Delete, Archive Events
Assign Users or Teams to events
Public, Private, Voucher Access Codes
How to create a global leaderboard
How to create stats and customer reports
Support
Discord
Jira Tickets
External Challenge Creators
NOC (No Objection Certificate)
Not copying challenges from the internet
Procedure Guideline
From the idea to the implementation
NDA (Non Disclosure Agreement)