Skip to content

Range Builder Guide

Range Builders create and deploy cyber ranges using Crucible platform components. They design infrastructure, scenarios, and user experiences to deliver engaging material that meets training, exercise, or challenge objectives.

This guide provides step-by-step instructions for building complete cyber ranges using the Crucible stack—Alloy for team management, Caster for infrastructure deployment, Steamfitter for automated scenario events, and Player for exercise delivery.

Overview

As a Range Builder, you'll work with four primary Crucible applications:

  • Alloy: Event orchestration and team management
  • Caster: Infrastructure-as-code topology deployment
  • Steamfitter: Automated scenario injection and task execution
  • Player: User interface and exercise delivery

Prerequisites

Before building ranges, ensure you have:

  • Content Developer permissions in all Crucible applications
  • Access to Terraform modules and templates
  • Understanding of your target virtualization environment (VMware vSphere, Azure, or Proxmox)
  • Basic knowledge of cyber range concepts

Common Range Patterns

There are many ways to structure cyber ranges depending on your training goals, audience, and available resources. Here are some common patterns to consider:

  1. Basic Lab Environment

  2. Single team with individual workstations

  3. Pre-configured tools and documentation

  4. Self-paced learning objectives

  5. Red vs Blue Exercise

  6. Opposing teams with different objectives

  7. Automated inject schedule

  8. Real-time monitoring and scoring

  9. Incident Response Scenario

  10. Timeline-driven event progression

  11. Evidence discovery points

  12. Collaborative investigation tools

  13. Penetration Testing Lab

  14. Vulnerable target environment

  15. Progressive difficulty levels
  16. Documentation and reporting tools

Best Practices

  1. Infrastructure Design

  2. Use modular Terraform configurations

  3. Implement proper resource naming conventions
  4. Plan for scalability and resource limits

  5. Test destruction/cleanup procedures

  6. Scenario Development

  7. Start with simple manual tasks before automation

  8. Use clear, descriptive task names
  9. Create a clear timeline for all events and injects
  10. Test timing and dependencies thoroughly

  11. Provide meaningful feedback to participants

  12. User Experience

  13. Design intuitive navigation paths

  14. Provide clear instructions and objectives
  15. Test from participant perspective
  16. Plan for different skill levels

Support

For additional help join the community discussions.