Z. Cliffe Schreuders 2929bdb322 feat: Add TEMPLATE_006 (Message Logs) and comprehensive template documentation
Created Template 006 for encrypted messaging app evidence (Signal/Wickr) showing ENTROPY handler-asset communications, plus comprehensive README documentation for the entire template system.

## New Files:

### TEMPLATE_AGENT_ID_006_message_logs.md
- **Evidence Type:** Signal/Wickr encrypted messaging app logs
- **Key Feature:** Handler uses subject's REAL NAME 8 times in operational comms
- **Direct Identity Confirmation:** Definitive proof of NPC as ENTROPY asset
- **Evidence Strength:** 75% alone → 99% combined with other templates
- **High Cooperation Potential:** 85% base (subject wants out, shows coercion)

**5 Message Threads Included:**
1. Initial Tasking - Handler assigns data theft, uses real name
2. Operational Concerns - Subject worried, handler reassures
3. Coordination with Cell - Payment confirmed, second asset mentioned
4. Internal ENTROPY Comms - Handler briefs cell leader, confirms recruitment method
5. Escalation and Pressure - Subject wants out, handler threatens and coerces

**What Makes This Template Unique:**
- Only template with direct real name confirmation via ENTROPY internal comms
- Shows subject is KNOWN ENTITY within ENTROPY organization
- Reveals handler's OPSEC failure (using real names)
- Documents coercion and victimization (subject tried to quit)
- Provides intelligence beyond subject: handler contact, cell structure, operations
- Creates moral complexity: perpetrator who is also victim

**Substitution Variables (17 total):**
- [SUBJECT_NAME], [SUBJECT_CODENAME], [HANDLER_CODENAME]
- [CELL_DESIGNATION], [OPERATION_NAME]
- [HANDLER_PHONE], [SUBJECT_PHONE]
- [TARGET_ORGANIZATION], [DATA_TYPE], [SYSTEM_NAME]
- [AMOUNT], [MEETING_LOCATION], [DEADLINE_DATE]
- [DATE_1] through [DATE_5], [TIME_1] through [TIME_5]
- [PRESSURE_DETAIL], [SUBJECT_CONCERN]
- [SECOND_ASSET_CODENAME], [CELL_LEADER_CODENAME]

**Gameplay Integration:**
- Discovery: RARE (server compromise or handler device seizure)
- Unlocks: Handler arrest, second asset ID, cell mapping
- Interrogation approaches: Overwhelming evidence (85%), Empathetic victim-focused (90%), Strategic flip (90%)
- Intelligence yield: Cell structure, handler contact, dead drops, payment methods

**Educational Value (CyBOK):**
- Encrypted messaging security & limitations
- OPSEC failures in operational communications
- Mobile device forensics
- Digital evidence authentication
- Insider threat psychology and coercion tactics
- Counterintelligence and asset flipping

### README.md (Comprehensive Template System Guide)
- **Purpose:** Complete documentation for using all 6 evidence templates
- **Sections:** Quick start, substitution guide, best practices, examples

**Key Content:**
- Quick Start Guide (4 steps: Choose templates → Gather values → Substitute → Deploy)
- Complete 6-template overview with summaries
- **Complete Substitution Variable Reference Table:**
  - Core Identity (3 variables - used in ALL templates)
  - ENTROPY Operational (7 variables)
  - Financial (4 variables)
  - Technical/System (3 variables)
  - Communication (3 variables)
  - Location (3 variables)
  - Temporal (5 variables)
  - Contextual (4 variables)
- Evidence Combination Strategies (5 strategic paths)
- Interrogation Approaches by Evidence Collected (clear unlocks)
- Best Practices (DO/DON'T lists)
- Rarity and Discovery Recommendations (progression table)
- Success Metrics and Gameplay Impact (evidence count → outcomes)
- Customization Examples (3 complete NPC scenarios with all substitutions)
- Educational Value Summary (CyBOK alignment)
- Quick Reference Checklist

**DO/DON'T Best Practices:**
✓ Replace ALL placeholders
✓ Keep values consistent across templates for same NPC
✓ Match timeline chronologically
✓ Consider cooperation potential
✗ Don't leave [BRACKETS] in final version
✗ Don't require 100% collection
✗ Don't over-punish coerced NPCs

## Updated Files:

### TEMPLATE_CATALOG.md
- Updated template count: 5 → 6
- Updated section title: "The Five Evidence Templates" → "The Six Evidence Templates"
- Added complete Template 006 entry with:
  - Full substitution variable list (17 variables)
  - Message thread summaries
  - Real name usage pattern analysis
  - 9 red flags documented
  - Evidence strength progression
  - Gameplay integration details
  - Forensic & legal assessment
  - Cross-references to other templates
  - Discovery scenarios and timing
- Updated Evidence Chain diagram to include Message Logs
- Updated Confidence Thresholds table: Added 6-template row (99.9% confidence, 95% cooperation)
- Added 2 new combination strategies:
  - "Real Name Confirmation + High Cooperation" (Templates 006 + 005 + 002 = 99%, 95% cooperation)
  - "Complete Cell Mapping" (Templates 006 + 004 + 002 + 003 = 99.9%, enables handler arrest)
- Added Template 006 to Discovery Placement Recommendations (Very Hard, Late investigation)
- Updated Expansion Opportunities: Renumbered future templates 007-011 (was 006-010)
- Updated Version History: Added v2.0 entry
- Updated Quick Reference Card: Added Template 006 with  NEW marker

## System Impact:

**Template System v2.0:**
- Total Templates: 6 (was 5)
- Total Substitution Variables: 32+ unique placeholders
- Evidence Chain: 6-step progression from suspicion → definitive proof
- Maximum Confidence: 99.9% (all 6 templates)
- Cooperation Range: 50% (1 template) → 95% (all 6 with empathetic approach)

**New Capabilities:**
- Direct real name confirmation via ENTROPY internal comms
- Handler identification and arrest enablement
- Cell structure mapping
- Second asset discovery at same organization
- Coercion documentation for cooperation agreements
- Highest cooperation potential (85-95%)

**Documentation Completeness:**
- Quick start guide for new users
- Complete variable reference (32+ variables documented)
- 5 evidence combination strategies
- 8 interrogation approach unlocks
- 3 complete NPC customization examples
- Educational value mapped to CyBOK

## Integration Notes:

**Template 006 Cross-References:**
- Corroborates Template 002 (payment amounts match message discussions)
- Corroborates Template 003 (data extraction dates align with tasking)
- Corroborates Template 004 (dead drop timing/location matches messages)
- Corroborates Template 005 (emotional arc: trapped, wants out)
- Connects to RECRUITMENT_001 (financial pressure methodology)
- Connects to TACTICAL_001 (if operation is infrastructure attack)
- Connects to LEVERAGE_001 (pressure detail as leverage point)

**Recommended Discovery:**
- Rarity: RARE (Very Hard)
- Timing: Late game (Mid-game for major operation rewards)
- Prerequisites: Server compromise OR handler device seizure
- Value: Very High (real name confirmation + handler intel + cell mapping)

All templates maintain narrative consistency, CyBOK educational alignment, and infinite reusability through [PLACEHOLDER] substitution system.
2025-11-19 17:43:15 +00:00
2025-05-16 10:42:42 +01:00
2025-11-16 10:20:00 +00:00
2025-11-14 19:47:54 +00:00

Break Escape: Cyber-Physical Security Learning Framework

Break Escape is an escape room-inspired games-based learning framework that simulates cyber-physical security challenges. Break Escape creates immersive experiences where learners engage with both physical and digital security mechanisms within narrative-driven scenarios explicitly mapped to the Cyber Security Body of Knowledge (CyBOK). The game is inspired by retro top-down games, dungeon crawlers, escape rooms, and cyber security challenges.

Note: Break Escape is currently in development. Please report any issues or feedback via GitHub.

Live Demo -- Early Beta Playtesting

You can try Break Escape directly from your browser by visiting: https://hacktivity.co.uk/break-escape-beta/scenario_select.html

Youll choose from scenarios, each offering its own set of puzzles and challenges, ranging from cryptography to physical security.

After playing, please fill out a short survey. Your insights will be instrumental in improving the game and understanding the benefits. https://forms.gle/kiVgNUBSHu2KjcJt8

Features

  • Immersive Learning Environment: Top-down 2D game environment accessible through web browsers
  • Cyber-Physical Security Challenges: Simulations of various security mechanisms:
    • Key-based locks (with physical keys and lockpicking mini-game)
    • PIN code systems
    • Password-protected interfaces
    • Biometric authentication (fingerprints that can be dusted and spoofed)
    • Bluetooth proximity detection
  • CyberChef Integration: Embedded cryptographic tools for encryption and data analysis
  • CyBOK Mapping: Each scenario is explicitly mapped to relevant Cyber Security Body of Knowledge areas
  • Multiple Scenarios: Various pre-built scenarios focusing on different security aspects:
    • "CEO Exfil Investigation" - Corporate espionage and data exfiltration
    • "Captain Meow's Disappearance" - Encoding and cryptography
    • "Encoding and Encryption Lab" - Basic cryptographic principles
    • "Asymmetric Encryption with RSA" - Public key cryptography
    • "Symmetric Encryption with AES" - Block ciphers and encryption modes
    • "Biometric Security Breach" - Fingerprint authentication

Technical Implementation

Break Escape is implemented using:

  • Phaser.js: Core game engine
  • JavaScript/HTML5: Front-end implementation
  • JSON: Scenario specification format

Installation

Break Escape is a web-based application and requires a web server to run. You can:

Option 1: Use the hosted version

Visit the live demo at https://hacktivity.co.uk/break-escape-beta/scenario_select.html

Option 2: Use Python's built-in HTTP server

  1. Clone the repository:

    git clone https://github.com/yourusername/break-escape.git
    cd break-escape
    
  2. Start a local web server:

    python3 -m http.server
    
  3. Open your web browser and navigate to:

    http://localhost:8000
    

Option 3: Deploy to a web server

  1. Upload all files to your web server directory
  2. Access through your domain

Usage

Start Break Escape:

  • Open Break Escape in your web browser
  • Choose a scenario based on your learning objectives or difficulty preference

Play the game:

  • When you start a scenario, you will be given a brief of the scenario.
  • You can navigate through the virtual environment using mouse clicks.
  • Interact with objects by clicking on them.
  • Collect items into your inventory to use later.
  • Solve puzzles and progress through rooms to complete the scenario.

After playing, please fill out a short survey. https://forms.gle/kiVgNUBSHu2KjcJt8

Game Controls

  • Mouse Click: Move character, interact with objects
  • Inventory: Click collected items to use them
  • Notes Panel: Access important information you've discovered
  • Bluetooth Scanner: Detect nearby Bluetooth devices (when available)
  • Biometrics Panel: View collected fingerprint samples (when available)

Scenario Design

Break Escape features a flexible JSON-based scenario specification format that enables educators to create custom scenarios without programming knowledge. The scenario structure includes:

  • Rooms with connections, objects, and optional locks
  • Objects with properties like takeable, readable, observations, and lock requirements
  • Special object types for fingerprint collection, cryptographic analysis, and more

For detailed information on creating your own scenarios, refer to README_scenario_design.md.

License

Break Escape is dual licensed:

  • AGPL (GNU Affero General Public License)
  • Open Government Licence

Acknowledgements

Break Escape was developed as an educational tool to address the "reflection gap" identified in many existing cyber security games by requiring players to actively apply security knowledge rather than merely encountering security terminology during gameplay.

The project integrates CyberChef, an open-source web application for encryption and data analysis, allowing learners to interact with genuine cryptographic tools within the game environment.

Special thanks to the Cyber Security Body of Knowledge (CyBOK) for providing the knowledge framework that Break Escape scenarios are mapped to.

This project is supported by a Cyber Security Body of Knowledge (CyBOK) resources around CyBOK 1.1 grant (2024-2025).


For questions, contributions, or more information, please open an issue on the project repository.

Description
No description provided
Readme 72 MiB
Languages
JavaScript 86.5%
Ink 7%
HTML 2.9%
CSS 2.5%
Ruby 0.9%
Other 0.2%