Use Cases

Field scenarios, per-client-type applications, and additional options for our devices in authorized security testing

Physical Security Testing

Testing Hoteling Office Spaces

Hoteling and hot-desking environments present unique security challenges. Shared workstations with docking stations create opportunities for attackers to compromise systems through physical access. This use case demonstrates how security professionals test these environments to identify vulnerabilities.

Scenario Overview

Modern offices increasingly use hoteling (desk reservation) and hot-desking (first-come, first-served) arrangements where employees don't have assigned workstations. These spaces typically include:

  • Universal docking stations with USB ports
  • Shared monitors, keyboards, and peripherals
  • Network connectivity for temporary users
  • Minimal physical security monitoring

This environment creates attack vectors that security teams need to identify and remediate.

Testing Methodology

1

Initial Reconnaissance

Security testers identify hoteling stations throughout the facility. They document:

  • Docking station models and USB port availability
  • Physical security controls (cameras, badge readers)
  • Employee traffic patterns and desk usage frequency
  • IT support response procedures
2

Device Deployment

Authorized security testers deploy USB testing devices to available docking stations. These devices are configured to:

  • Remain dormant until activated by scheduled scripts
  • Log connection events and system information
  • Execute predefined test scenarios when laptops connect
  • Report findings back to the security team

⚠️ Authorization Required: This testing is only performed with explicit written authorization from organization leadership and legal counsel.

3

Automated Execution Script

USB devices run an "arming" script at configured intervals. The typical attack simulation sequence includes:

Windows Execution:
  • Step 1: Device emulates keyboard input to open Run dialog (Win + R)
  • Step 2: Types command to open PowerShell in hidden mode
  • Step 3: Executes reconnaissance commands to gather system information
  • Step 4: Attempts to establish callback connection to test server
macOS Execution:
  • Step 1: Device emulates keyboard to open Spotlight (Cmd + Space)
  • Step 2: Searches for and opens Terminal application
  • Step 3: Executes shell commands in hidden Terminal window
  • Step 4: Gathers system configuration and network information
4

Attack Options & Data Collection

Once access is established, the security testing team evaluates multiple threat scenarios:

Persistence Installation

Test whether attackers could install scripts that survive reboots and provide ongoing access:

  • Startup folder entries
  • Scheduled tasks / cron jobs
  • Registry modifications (Windows)
  • Launch agents/daemons (macOS)
Data Exfiltration

Assess the risk of sensitive information theft:

  • Browser saved passwords and cookies
  • Recently accessed documents
  • Clipboard contents and keystrokes
  • Network credentials and certificates
  • Email and chat application data
Manual Command Execution

Evaluate whether attackers could execute commands in real-time:

  • Remote shell access via reverse connection
  • Lateral movement to other network resources
  • Privilege escalation attempts
  • Network reconnaissance and scanning
Persistent Compromise Chain

Test whether multiple users become compromised over time:

  • Each new laptop connection provides potential access
  • Device remains functional, arousing no suspicion
  • Compromise spreads as employees rotate through hoteling stations
  • Single physical breach yields multiple system compromises

MITRE ATT&CK Mapping

This testing methodology maps to the following MITRE ATT&CK tactics and techniques:

Initial Access

  • T1200: Hardware Additions - USB device deployment to docking stations
  • T1091: Replication Through Removable Media - USB-based initial compromise

Execution

  • T1059.001: Command and Scripting Interpreter: PowerShell - Automated PowerShell execution
  • T1059.004: Command and Scripting Interpreter: Unix Shell - macOS Terminal command execution
  • T1053: Scheduled Task/Job - Timed script execution from USB device

Persistence

  • T1547: Boot or Logon Autostart Execution - Startup folder and registry modifications
  • T1053: Scheduled Task/Job - Persistent scheduled tasks and cron jobs
  • T1543: Create or Modify System Process - Service creation for persistence

Discovery

  • T1082: System Information Discovery - OS and system configuration gathering
  • T1016: System Network Configuration Discovery - Network enumeration
  • T1033: System Owner/User Discovery - Current user identification

Collection

  • T1005: Data from Local System - File and credential harvesting
  • T1056: Input Capture - Keylogging capabilities
  • T1113: Screen Capture - Screenshots and display monitoring
  • T1115: Clipboard Data - Clipboard content collection

Network Command and Control

  • T1071: Application Layer Protocol - HTTP/HTTPS C2 channels
  • T1573: Encrypted Channel - Encrypted C2 communications
  • T1132: Data Encoding - Obfuscated C2 traffic

Findings & Vulnerabilities Identified

🔴 Critical: Zero USB Port Protection

Testing revealed that 100% of hoteling stations accepted USB devices without any security controls, endpoint protection, or monitoring.

🟠 High: Lack of Physical Monitoring

Testers were able to deploy devices during business hours without being challenged or detected by security cameras.

🟠 High: No Device Inventory

IT department had no inventory of approved devices, making unauthorized USB devices indistinguishable from legitimate peripherals.

🟡 Medium: Inadequate User Training

Employees did not report suspicious USB devices, and most were unaware of physical security threats in hoteling environments.

Recommended Countermeasures

Technical Controls

  • USB device whitelisting and port controls
  • Endpoint Detection and Response (EDR) solutions
  • Network segmentation for hoteling areas
  • Device authentication for docking stations
  • Application whitelisting to prevent unauthorized execution

Administrative Controls

  • Regular physical security audits of hoteling areas
  • Approved device inventory and asset tagging
  • Security awareness training on physical threats
  • Incident reporting procedures for suspicious devices
  • Daily inspection protocols for shared workstations

Impact & Results

This testing engagement successfully demonstrated critical vulnerabilities in the client's hoteling environment:

12
Hoteling Stations Tested
35+
Systems Compromised
72hrs
Test Duration
0
Detections by Security Team

Following our findings, the organization implemented comprehensive USB security controls, updated their physical security policies, and conducted company-wide training. Follow-up testing six months later showed 100% reduction in vulnerability to this attack vector.

⚖️ Ethical Testing Standards

All testing described in this use case was performed under strict ethical guidelines:

  • Full written authorization from executive leadership and legal counsel
  • Clearly defined scope and rules of engagement
  • No actual data exfiltration or system damage
  • Immediate notification of critical findings
  • Secure disposal of test data upon project completion
  • Compliance with all applicable laws and regulations

Learn more about our Ethical Use Policy.

Security Awareness Testing

Ransomware Simulation & User Response Testing

Employee response to ransomware incidents is a critical component of organizational security. This use case demonstrates how security teams test user awareness, incident reporting procedures, and organizational response capabilities through controlled ransomware simulations using USB-deployed devices.

Scenario Overview

Ransomware attacks represent one of the most significant cybersecurity threats facing organizations today. Testing how employees and security teams respond to ransomware incidents is essential for:

  • Validating incident response procedures and workflows
  • Measuring employee awareness and reaction time
  • Identifying gaps in detection and response capabilities
  • Training security teams with realistic attack scenarios
  • Assessing communication channels during security incidents

This controlled simulation uses USB devices to trigger realistic ransomware notifications that appear to encrypt a user's system, while safely logging all employee actions and organizational responses for comprehensive security assessment.

Testing Methodology

1

Pre-Deployment Planning

Before initiating ransomware simulation testing, security teams conduct thorough preparation:

  • Obtain explicit written authorization from executive leadership and legal counsel
  • Coordinate with IT security team to ensure detection systems won't interfere with test
  • Define clear success metrics: reporting time, escalation procedures, containment actions
  • Prepare communication plan for post-test debriefing
  • Identify target user groups and systems for testing
  • Configure logging infrastructure to capture all user and system responses

⚠️ Critical Coordination: Unlike other penetration testing, ransomware simulations must be carefully coordinated to avoid causing panic, business disruption, or triggering unnecessary escalations to external parties (law enforcement, cyber insurance, media relations).

2

USB Device Configuration

Specialized USB devices are configured to deploy the ransomware simulation payload. These devices include:

  • Hardware-based keyboard emulation for credential-free execution
  • Onboard storage containing the simulation payload and logging components
  • Trigger mechanisms: time-based activation or manual triggering via physical button
  • Secure logging system to record all user interactions and timestamps
  • Fail-safe mechanisms to immediately halt simulation if critical errors occur
3

Physical Deployment & Activation

Authorized security testers deploy USB devices to target workstations using one of several approaches:

Deployment Methods:
  • Direct Installation: During non-business hours, testers connect devices to selected workstations in common areas, conference rooms, or specific departments being tested
  • Social Engineering Component: Devices may be placed as "found" USB drives in parking lots, break rooms, or reception areas to test whether employees connect unknown devices
  • Hoteling Integration: Devices integrated into docking stations or USB hubs in shared workspace environments
Activation Triggers:
  • Time-Delay: Device activates at predetermined time (e.g., 10:00 AM on Tuesday) to simulate business-hours attack
  • Connection-Based: Triggers when specific conditions are met (user logged in, network connected, specific time range)
  • Manual Trigger: Tester activates remotely or via physical button for precise timing control
4

Ransomware Simulation Execution

When activated, the USB device executes a carefully orchestrated sequence that simulates realistic ransomware behavior:

Execution Sequence:
  1. Silent Preparation (5-10 seconds):
    • Device emulates keyboard to open system command interface (PowerShell/Terminal)
    • Deploys simulation payload to temporary directory
    • Initializes logging system to capture all subsequent user actions
    • Takes screenshot of desktop before simulation begins (baseline)
  2. Visual Impact Display:
    • Displays full-screen ransomware notice mimicking real-world ransomware families (e.g., styled similar to WannaCry, REvil, LockBit)
    • Shows "encryption progress" bar advancing across files
    • Presents ransom message with payment instructions and countdown timer
    • Includes contact information and "unique infection ID" for tracking
  3. Interactive Elements:
    • Buttons to "decrypt files" (non-functional, logs clicks)
    • Payment instructions with Bitcoin wallet address (test wallet, no actual transactions)
    • Support chat interface (simulated, logs all messages user attempts to send)
    • File browser showing "encrypted" files (visual overlay only, no actual encryption)

🛡️ Safety Measures: No actual file encryption occurs. The simulation uses visual overlays and file system monitoring to create the appearance of encryption without modifying user data. All actions are fully reversible.

5

Comprehensive Logging & Data Collection

The USB device's logging system captures detailed information about user and organizational response:

User Action Logging

Every interaction with the simulation is recorded with precise timestamps:

  • Initial Response Time: How long until user takes first action (move mouse, press key, etc.)
  • Interaction Attempts: Clicks on buttons, attempts to close window, keyboard shortcuts tried
  • Communication Actions: Phone picked up, attempts to contact IT, discussions with nearby colleagues
  • Compliance Actions: Whether user follows/violates security policies (e.g., attempts payment, removes USB devices, shuts down system)
  • Screenshots: Periodic captures showing exactly what user sees during incident
Response Time Metrics

Critical timing data for incident response assessment:

  • T+0: Ransomware notice appears on screen
  • T+[X]: User first acknowledges incident (moves mouse, touches keyboard)
  • T+[Y]: User contacts IT/Security (phone call, email, helpdesk ticket)
  • T+[Z]: IT/Security team acknowledges report and begins investigation
  • T+[W]: Incident formally escalated to appropriate response team
  • T+[V]: System quarantined or disconnected from network
Behavioral Analysis

Detailed psychological and behavioral response patterns:

  • Panic Indicators: Rapid clicking, repeated identical actions, random keystrokes
  • Problem-Solving Attempts: Task Manager access, trying Alt+F4, attempting safe mode boot
  • Policy Compliance: Follows incident response procedures vs. attempts independent resolution
  • Information Gathering: Reads entire message vs. immediate reaction without reading
  • Social Response: Immediately alerts others vs. keeps incident private
Network & System Monitoring

Secondary monitoring systems track organizational response:

  • Network Activity: When/if workstation is isolated from network
  • Security Tool Detection: Whether EDR, SIEM, or other security tools detect the simulation
  • Help Desk Activity: Ticket creation time, priority assignment, routing to appropriate team
  • Executive Notification: If/when leadership is informed of potential ransomware incident
  • Communication Channels: Which communication methods are used (email, phone, Slack, emergency channels)
6

Correlation & Incident Response Validation

After the simulation, security teams correlate logged device data with information employees reported to validate incident response procedures:

Correlation Analysis:
  • Report Accuracy: Compare employee's description of incident with actual logged events
    • Did they accurately describe the ransomware message?
    • Did they note the time correctly?
    • Did they mention specific details (ransom amount, file types mentioned, etc.)?
  • Response Time Gaps: Identify delays in incident reporting chain
    • Employee saw message at T+0 but didn't report until T+15 minutes
    • Help desk received report at T+15 but didn't escalate until T+45 minutes
    • Security team notified at T+45 but didn't begin investigation until T+90 minutes
  • Procedure Compliance: Verify employees followed documented incident response procedures
    • Did they immediately disconnect from network as policy requires?
    • Did they use correct reporting channel (emergency hotline vs. regular help desk)?
    • Did they preserve evidence (not reboot, not remove USB devices)?
  • Training Effectiveness: Assess whether security awareness training prepared employees
    • Did they recognize it as ransomware?
    • Did they avoid clicking payment links or providing information?
    • Did they remember key steps from training?

MITRE ATT&CK Mapping

Ransomware simulation testing maps to the following MITRE ATT&CK tactics and techniques:

Initial Access

  • T1200: Hardware Additions - Physical USB device deployment
  • T1091: Replication Through Removable Media - USB-initiated compromise

Execution

  • T1204.002: User Execution: Malicious File - Automated execution via HID emulation
  • T1059.001: Command and Scripting Interpreter: PowerShell - Hidden PowerShell window execution
  • T1059.004: Command and Scripting Interpreter: Unix Shell - Terminal-based payload deployment

Discovery

  • T1082: System Information Discovery - System profiling before simulation
  • T1083: File and Directory Discovery - File enumeration for simulation display
  • T1057: Process Discovery - Running process identification

Collection

  • T1113: Screen Capture - Baseline and periodic screenshots
  • T1056.001: Input Capture: Keylogging - User interaction logging
  • T1119: Automated Collection - Comprehensive logging of all user actions

Impact

  • T1486: Data Encrypted for Impact - Simulated ransomware encryption display
  • T1491: Defacement - Full-screen ransomware notification
  • T1490: Inhibit System Recovery - Simulated system lockout (visual only)

Defense Evasion

  • T1564.003: Hide Artifacts: Hidden Window - Execution in hidden command windows
  • T1070.004: Indicator Removal: File Deletion - Cleanup of execution artifacts

Findings & Vulnerabilities Identified

🔴 Critical: Delayed Incident Reporting

Average time from infection to IT notification was 23 minutes. In real ransomware attacks, this delay allows malware to encrypt thousands of files and spread laterally across the network.

🔴 Critical: Inconsistent Procedure Following

Only 35% of affected employees followed documented incident response procedures. Most attempted to resolve the issue independently before contacting IT, potentially destroying forensic evidence.

🟠 High: Network Isolation Failures

In 78% of cases, infected workstations remained connected to the corporate network for 30+ minutes after ransomware notification appeared, allowing potential lateral movement.

🟠 High: Inaccurate Incident Reports

Employee descriptions of the incident contained significant inaccuracies (wrong times, incorrect ransom amounts, missing critical details), hampering effective incident response.

🟡 Medium: Security Tool Detection Gaps

Endpoint security solutions detected the simulation in only 40% of cases, revealing significant gaps in behavioral analysis and anomaly detection capabilities.

🟡 Medium: Communication Channel Confusion

Employees used multiple different channels to report incidents (email, Slack, phone, in-person), causing confusion and delays in coordinated response.

Recommended Countermeasures

Enhanced Training Programs

  • Quarterly ransomware response drills with realistic scenarios
  • Clear, simplified incident response procedures posted at workstations
  • Mandatory security awareness training emphasizing immediate reporting
  • Gamified training exercises with rewards for proper incident handling
  • Department-specific response playbooks tailored to different roles

Technical Improvements

  • Automated network isolation triggers for suspected ransomware activity
  • Enhanced EDR behavioral detection for file encryption patterns
  • Panic button software for immediate IT/Security notification
  • Improved USB device controls and execution prevention
  • Real-time SIEM correlation rules for ransomware indicators

Process & Communication

  • Single, clearly defined incident reporting channel (e.g., dedicated security hotline)
  • Incident response team on-call rotation with defined SLAs
  • Regular tabletop exercises involving cross-functional teams
  • Post-incident review process to continuously improve procedures
  • Executive communication templates for rapid escalation

Response Optimization

  • Pre-configured incident response scripts and automation
  • Network segmentation to limit ransomware spread
  • Immutable backup systems with offline copies
  • Ransomware-specific detection and response playbooks
  • Regular restoration testing to validate recovery capabilities

Impact & Results

This ransomware simulation testing provided invaluable insights into organizational readiness:

45
Employees Tested
23min
Average Report Time
35%
Followed Procedures
100%
Event Correlation Success

The detailed logging and correlation capabilities provided unprecedented visibility into actual employee behavior during security incidents. Following implementation of recommended countermeasures and enhanced training, follow-up testing six months later showed average reporting time reduced to 4 minutes, procedure compliance improved to 87%, and automated network isolation activated in 95% of cases.

⚖️ Ethical Testing Standards

Ransomware simulation testing requires heightened ethical considerations:

  • Executive approval with full understanding of realistic simulation nature
  • Zero actual file encryption or data modification - all effects are visual only
  • Immediate availability of security team to halt simulation if employee distress is observed
  • Mandatory post-test debriefing with all affected employees within 24 hours
  • Clear communication that this was a test, with educational session on lessons learned
  • Counseling resources available for employees who experienced significant stress
  • All logging data secured and deleted after analysis per data retention policies
  • Compliance with all employment laws and regulations regarding workplace monitoring

Learn more about our Ethical Use Policy.

Advanced Persistent Threat Simulation

Advanced Persistent Access via Combined Devices

Modern adversaries employ sophisticated multi-vector attack techniques combining physical network access with compromised endpoints. This use case demonstrates how security teams test organizational resilience against advanced persistent threats (APT) using coordinated LAN-connected command-and-control infrastructure paired with USB-deployed implants that establish covert communication channels for remote operation and data exfiltration.

Scenario Overview

Advanced persistent threat actors increasingly use multi-stage attacks that combine physical access to network infrastructure with endpoint compromise. This sophisticated approach enables:

  • Persistent command-and-control (C2) even when internet egress is blocked
  • Covert data exfiltration through physical network devices
  • Long-range communication via emerging wireless standards (WiFi HaLow/802.11ah)
  • Coordinated attacks across multiple compromised endpoints
  • Evasion of traditional network security monitoring
  • Resilient infrastructure surviving network segmentation and isolation

This testing methodology simulates a realistic APT scenario where attackers deploy both network-connected C2 infrastructure and endpoint implants that work in concert to maintain persistent access, enabling security teams to identify critical gaps in defense-in-depth strategies.

Testing Methodology

1

Infrastructure Architecture Planning

Before deployment, security testers design a comprehensive attack infrastructure that mimics real-world APT operations:

Component Architecture:
  • LAN C2 Nodes: Network-connected devices acting as command-and-control servers
    • Raspberry Pi or similar single-board computers
    • Configured with long-range WiFi HaLow (802.11ah) adapters for extended range (up to 1km)
    • Connected to legitimate network ports (conference rooms, network closets, unused desk jacks)
    • Run covert C2 server software accepting connections from USB implants
    • Dual communication: wired LAN for C2 traffic, WiFi HaLow for external operator control
  • USB Endpoint Implants: Devices deployed to target workstations
    • USB-based implants with network client capabilities
    • Programmed to beacon to LAN C2 nodes on local network
    • Execute remote commands from C2 infrastructure
    • Exfiltrate data through C2 channel to LAN nodes
  • External Operator Station: Remote control point for testers
    • Positioned within WiFi HaLow range (parking lot, nearby building, vehicle)
    • Connects to LAN C2 nodes via long-range wireless
    • Provides interface for commanding implants and retrieving exfiltrated data
2

LAN C2 Node Deployment

Security testers deploy network-connected C2 infrastructure to serve as the backbone for coordinated attacks:

Deployment Strategy:
  • Target Locations: Areas with accessible network ports and minimal supervision
    • Conference rooms and meeting spaces
    • Network closets and IDF/MDF rooms
    • Unused desk ports in hoteling areas
    • Break rooms and common areas with network jacks
    • Behind network-connected printers or copiers
  • Physical Concealment: Devices disguised to avoid detection
    • Housed in inconspicuous enclosures (power adapters, surge protectors)
    • No visible indicators (LEDs disabled or covered)
    • Positioned behind furniture or equipment
    • Labeled as legitimate IT equipment when possible
  • Network Configuration: C2 nodes configured for stealth and persistence
    • DHCP client to automatically obtain IP address
    • MAC address spoofing to mimic legitimate device types
    • Minimal network footprint (no broadcasts, limited traffic)
    • Listen-only mode until USB implants connect
    • Encrypted C2 traffic resembling legitimate protocols
WiFi HaLow Configuration:
  • Long-Range Wireless: 802.11ah provides superior range and penetration
    • Operates in sub-GHz frequencies (900MHz) with better building penetration
    • Range up to 1km line-of-sight, 300-500m through buildings
    • Low power consumption enables long-term operation
    • Less congested spectrum compared to 2.4/5GHz WiFi
  • Covert Communication: Wireless link designed to evade detection
    • Custom SSID resembling legitimate networks
    • Encrypted with WPA3 for confidentiality
    • Beacon interval adjusted to reduce visibility
    • Operator can connect from parking lot or nearby location
3

USB Implant Deployment to Endpoints

Following LAN C2 infrastructure deployment, USB implants are strategically placed on target workstations:

USB Implant Characteristics:
  • Hardware Capabilities:
    • Dual functionality: Keyboard emulation + network client
    • Onboard storage for payloads and collected data
    • Programmable microcontroller for autonomous operation
    • Low power consumption for long-term deployment
  • Initial Compromise Phase:
    • Emulates keyboard to execute initial payload
    • Establishes persistent implant on target system
    • Configures network client to beacon to LAN C2 nodes
    • Removes execution artifacts and enters dormant state
  • Beaconing Behavior:
    • Periodically attempts connection to C2 nodes on local network
    • Uses multiple protocols (HTTP, HTTPS, DNS) to find active C2
    • Employs jitter and random delays to evade pattern detection
    • Falls back to dormant state if no C2 available
4

C2 Channel Establishment & Command Execution

Once USB implants successfully beacon to LAN C2 nodes, a covert command-and-control channel is established:

C2 Connection Flow

Multi-stage connection establishment ensuring stealth and reliability:

  1. Initial Beacon: USB implant sends lightweight check-in to C2 node
    • Includes unique implant ID and basic system information
    • Establishes encryption keys for secure communication
    • Receives initial tasking or remains dormant
  2. Operator Connection: Security tester connects to C2 via WiFi HaLow
    • From remote location (parking lot, nearby building)
    • Accesses web interface or SSH to C2 node
    • Views list of active implants and their capabilities
    • Issues commands to specific implants or all simultaneously
  3. Command Relay: C2 forwards operator commands to implants
    • Implants poll C2 for new commands on schedule
    • Commands encrypted and delivered via established channel
    • Results returned to C2 and available to operator
Remote Command Capabilities

Once C2 is established, testers can execute various attack scenarios:

  • Reconnaissance:
    • System information gathering (OS, patches, installed software)
    • Network mapping from compromised endpoint perspective
    • User activity monitoring and credential harvesting
    • File system enumeration for sensitive data identification
  • Lateral Movement:
    • Network scanning for additional targets
    • Credential relay attacks using harvested credentials
    • SMB/RDP connection attempts to adjacent systems
    • Active Directory enumeration and privilege mapping
  • Persistence:
    • Multiple persistence mechanisms across systems
    • Scheduled tasks and services for reliable execution
    • Registry modifications and startup entries
    • Redundant implants for survivability
  • Interactive Shells:
    • Real-time command execution on compromised endpoints
    • PowerShell, cmd.exe, or bash access depending on OS
    • Script upload and execution capabilities
    • Tool deployment for advanced operations
Data Exfiltration

Sensitive data collection and exfiltration through covert channels:

  • Target Data Identification:
    • Automated searching for documents, spreadsheets, databases
    • Keyword-based filtering (confidential, proprietary, password)
    • Browser data: saved credentials, cookies, history
    • Email and communication application data
  • Exfiltration Path:
    1. Data collected by USB implant from compromised system
    2. Transmitted to LAN C2 node via internal network
    3. Stored on C2 node for operator retrieval
    4. Operator extracts data via WiFi HaLow connection from remote location
    5. Entire chain occurs within internal network, bypassing perimeter controls
  • Stealth Techniques:
    • Data compressed and encrypted before transmission
    • Throttled transfer rates to avoid bandwidth anomalies
    • Mimics legitimate internal network protocols
    • Transfers during high-traffic periods for additional obfuscation
Long-Range Remote Operation

WiFi HaLow enables extended-range operation from unexpected locations:

  • Operational Scenarios:
    • Operator positioned in vehicle in parking lot or nearby street
    • Connection from adjacent building or public space
    • Mobile operation allowing operator to move while maintaining access
    • Emergency extraction of data when physical access is detected
  • Operational Security:
    • No requirement for operator to remain inside target facility
    • Reduced risk of physical detection or confrontation
    • Ability to quickly disconnect and relocate if necessary
    • Long-term monitoring possible with minimal operator exposure
5

Persistence & Long-Term Access Testing

The distributed infrastructure enables testing of long-term persistent access scenarios:

Resilience Testing:
  • Network Segmentation Bypass:
    • C2 nodes placed in multiple network segments
    • Implants automatically find available C2 node in their segment
    • Maintains access even when network is partitioned
  • Incident Response Simulation:
    • Infrastructure remains operational during "containment" attempts
    • Tests effectiveness of network isolation procedures
    • Identifies how adversaries could maintain presence during IR activities
  • Detection Evasion:
    • C2 traffic occurs entirely within internal network
    • No internet egress required, bypassing perimeter monitoring
    • Mimics legitimate internal protocols and services
    • Encrypted communications prevent content inspection
  • Multi-Week Engagement:
    • Infrastructure can remain deployed for extended periods
    • Periodic operator access to demonstrate ongoing compromise
    • Validates that security monitoring would detect prolonged presence

MITRE ATT&CK Mapping

Advanced persistent access testing demonstrates a comprehensive multi-stage attack mapped to the following MITRE ATT&CK tactics and techniques:

Initial Access

  • T1200: Hardware Additions - Physical deployment of LAN C2 nodes and USB implants
  • T1091: Replication Through Removable Media - USB-based endpoint compromise
  • T1199: Trusted Relationship - Abuse of internal network trust

Execution

  • T1059.001: Command and Scripting Interpreter: PowerShell - Remote PowerShell execution
  • T1059.004: Command and Scripting Interpreter: Unix Shell - Bash/shell command execution
  • T1053: Scheduled Task/Job - Persistence mechanisms via scheduled execution
  • T1569: System Services - Service-based payload execution

Persistence

  • T1547: Boot or Logon Autostart Execution - Registry and startup folder modifications
  • T1543: Create or Modify System Process - System service creation
  • T1053: Scheduled Task/Job - Scheduled task persistence
  • T1136: Create Account - Backup access account creation

Privilege Escalation

  • T1068: Exploitation for Privilege Escalation - Privilege elevation attempts
  • T1134: Access Token Manipulation - Token theft and impersonation
  • T1078: Valid Accounts - Use of harvested credentials for elevation

Defense Evasion

  • T1027: Obfuscated Files or Information - Encrypted C2 communications
  • T1205: Traffic Signaling - Covert channel establishment
  • T1090: Proxy - Internal network as proxy for C2
  • T1070: Indicator Removal - Log clearing and artifact removal
  • T1599: Network Boundary Bridging - WiFi HaLow external bridge

Credential Access

  • T1003: OS Credential Dumping - Memory credential extraction
  • T1555: Credentials from Password Stores - Browser and application credential theft
  • T1056.001: Input Capture: Keylogging - Credential capture via keylogger

Discovery

  • T1087: Account Discovery - Local and domain account enumeration
  • T1018: Remote System Discovery - Network host discovery
  • T1046: Network Service Discovery - Port scanning and service enumeration
  • T1083: File and Directory Discovery - Sensitive file identification
  • T1482: Domain Trust Discovery - Active Directory reconnaissance

Lateral Movement

  • T1021.001: Remote Services: Remote Desktop Protocol - RDP lateral movement
  • T1021.002: Remote Services: SMB/Windows Admin Shares - SMB-based lateral movement
  • T1550: Use Alternate Authentication Material - Pass-the-hash attacks

Collection

  • T1005: Data from Local System - Local file collection
  • T1039: Data from Network Shared Drive - Network share enumeration
  • T1114: Email Collection - Email and communication data
  • T1113: Screen Capture - Screenshot collection
  • T1119: Automated Collection - Systematic data gathering

Command and Control

  • T1071.001: Application Layer Protocol: Web Protocols - HTTP/HTTPS C2 channel
  • T1071.004: Application Layer Protocol: DNS - DNS tunneling for C2
  • T1573: Encrypted Channel - End-to-end encrypted C2
  • T1090.001: Proxy: Internal Proxy - LAN nodes as internal C2 proxies
  • T1132: Data Encoding - Encoded C2 traffic
  • T1001: Data Obfuscation - Protocol mimicry

Exfiltration

  • T1041: Exfiltration Over C2 Channel - Data exfil via established C2
  • T1030: Data Transfer Size Limits - Throttled exfiltration
  • T1048: Exfiltration Over Alternative Protocol - Multi-protocol exfiltration
  • T1020: Automated Exfiltration - Scheduled data exfiltration
  • T1537: Transfer Data to Cloud Account - Alternative exfil paths

Impact

  • T1565: Data Manipulation - Potential for data modification
  • T1490: Inhibit System Recovery - Backup system interference capability

Findings & Vulnerabilities Identified

🔴 Critical: Internal Network Assumed Trusted

Organizations had minimal internal network traffic monitoring, operating under assumption that internal communications are inherently trustworthy. C2 traffic between implants and LAN nodes went completely undetected.

🔴 Critical: Physical Port Security Nonexistent

Network ports in public areas had no authentication (802.1X) or monitoring. Attackers could connect C2 infrastructure to legitimate network without any security validation or detection.

🔴 Critical: Persistent Access Survived Incident Response

When one implant was detected and remediated, remaining infrastructure maintained operational access. Distributed C2 architecture provided resilience against partial discovery and containment attempts.

🟠 High: No Wireless Spectrum Monitoring

WiFi HaLow communications (900MHz sub-GHz band) went completely undetected. Organizations had no capability to detect or monitor wireless communications outside traditional 2.4/5GHz WiFi bands.

🟠 High: Data Exfiltration via Internal Channels

All data exfiltration occurred through internal network channels, completely bypassing perimeter DLP, web proxies, and firewall monitoring. Gigabytes of sensitive data successfully extracted without alerting security tools.

🟠 High: Network Device Inventory Gaps

IT departments had no comprehensive inventory of network-connected devices. Unauthorized C2 nodes blended in with legitimate equipment and were never questioned or investigated.

🟡 Medium: Limited USB Device Logging

USB device connections were not centrally logged or monitored. Implant deployments occurred without generating alerts or investigation triggers, allowing widespread compromise.

🟡 Medium: Inadequate Physical Security Inspections

Physical security rounds did not include inspection of network ports, equipment closets, or hidden areas. C2 nodes remained undetected for entire engagement duration (4+ weeks).

Recommended Countermeasures

Network Access Controls

  • Implement 802.1X port authentication for all network jacks
  • Network Access Control (NAC) with device profiling and posture assessment
  • Automatic quarantine for unknown or non-compliant devices
  • MAC address allowlisting for network-attached devices
  • Port security policies disabling unused network jacks
  • VLAN segmentation isolating guest/unmanaged devices

Wireless Security Monitoring

  • Wireless Intrusion Detection Systems (WIDS) covering all bands including sub-GHz
  • Spectrum analysis tools for detecting unauthorized wireless devices
  • Regular RF sweeps of sensitive areas and network closets
  • Faraday shielding for critical areas requiring zero wireless
  • Wireless policy enforcement and rogue AP detection

Internal Network Monitoring

  • Deploy internal network traffic analysis (NTA) solutions
  • East-west traffic inspection, not just north-south
  • Anomaly detection for unusual internal communication patterns
  • Encrypted traffic analysis (ETA) for detecting C2 in encrypted channels
  • Baseline legitimate internal protocols and flag deviations
  • Behavioral analytics for endpoints and network devices

Endpoint Protection

  • Advanced EDR with behavioral detection and response
  • USB device control policies with whitelisting
  • Application whitelisting preventing unauthorized execution
  • PowerShell logging and monitoring for suspicious activity
  • Kernel-level protections against HID attack vectors
  • Network connection monitoring from endpoints

Physical Security

  • Regular physical security audits of network infrastructure
  • Inventory and asset tagging for all network-connected devices
  • Locked enclosures for network equipment and patch panels
  • Security camera coverage of network closets and equipment rooms
  • Port security dongles or physical locks for unused network jacks
  • Tamper-evident seals on critical infrastructure

Detection & Response

  • SIEM correlation rules for C2 behavioral indicators
  • Threat hunting program focusing on internal threats
  • Network flow analysis for C2 communication patterns
  • Deception technology (honeypots) on internal networks
  • Regular purple team exercises simulating APT scenarios
  • Incident response playbooks for suspected internal compromise

Impact & Results

This advanced persistent threat simulation revealed critical gaps in defense-in-depth strategies:

3
LAN C2 Nodes Deployed
18
USB Implants Deployed
28 days
Persistent Access Duration
0
Detections by Security Team

The combination of LAN-connected C2 infrastructure and USB implants created a sophisticated attack platform that evaded all existing security controls. Data exfiltration totaling 12GB occurred entirely through internal channels without detection. Following engagement, the organization implemented comprehensive network access controls (802.1X), deployed internal traffic monitoring, established a device inventory system, and created an APT-focused threat hunting program. Follow-up red team assessment one year later resulted in early detection and containment of similar attack infrastructure.

⚖️ Ethical Testing Standards

Advanced persistent threat simulation requires exceptional operational security and ethics:

  • Executive-level authorization with full technical briefing on capabilities and risks
  • Legal review ensuring compliance with all applicable laws and regulations
  • Clearly defined scope including authorized network segments and data types
  • No actual exfiltration of truly sensitive data (test data used for demonstrations)
  • Daily check-ins with designated security stakeholder to prevent actual incidents
  • Emergency cutoff procedures if real threat actors detected during engagement
  • All deployed infrastructure tracked with removal verification at engagement conclusion
  • Comprehensive documentation enabling organization to detect similar real-world attacks
  • Post-engagement purple team session demonstrating detection and response improvements

Learn more about our Ethical Use Policy.

Consulting Delivery

Consulting Engagements, Run by One Expert

Consulting teams are constrained by senior pentester time: every site visit, every travel day, and every engagement depends on scarce specialist availability. This use case shows how a security firm structures engagements so a specialist arms the devices beforehand, any available employee performs the on-site connection, and the expert controls and reports the engagement remotely.

Scenario Overview

A consulting firm wants to deliver meaningful computer and network testing to more clients without scaling its senior staff. The engagement model works in three roles:

  • The expert loads the test plan onto the devices before anyone travels and reviews the results afterwards
  • The visitor is chosen by availability, not skill: a field technician, a junior, whoever is free. They only connect devices to target computers and network ports
  • The devices hold the method and run it the same way every time, so results do not depend on who visited

The visitor needs no laptop or tools: a phone is enough. Devices are armed per engagement and reused, and one expert can run several engagements in parallel.

Testing Methodology

1

Arming by the Expert

Before anyone travels, the security expert loads the test plan onto the devices for this specific engagement. The plan defines which prepared tests launch, which network checks run, and what the survey collects. Arming is the expert's job before anyone travels. Everything after runs without them on site.

2

On-Site Connection by Any Available Person

The visitor's entire task is physical: connect the USB device to the target computers and the network device to LAN ports. Because the visitor needs no laptop, no tooling and no specialist knowledge, scheduling depends on availability instead of expert calendars.

⚠️ Authorization Required: Engagements are only performed with explicit written authorization from the client organization, defining scope, systems and time windows.

3

Live Expert Control

Once a device is connected on site, the expert reaches it remotely and runs any command on the target computer, with output returned in real time. In the room, control works from a phone over the device's own hotspot; remotely, paired devices relay commands through the fleet. The expert works live exactly where the test plan needs human judgment.

4

Collection and Merged Client Report

All deployed devices sync their logs to one collector. The USB device's computer findings and the network device's LAN findings merge into a single site report: executive summary, severity per event, timeline, plain-language findings and MITRE ATT&CK mapping. The expert reviews and delivers it remotely. Expert time goes to arming and review only.

MITRE ATT&CK Mapping

The automated test plans map to the following MITRE ATT&CK tactics and techniques:

Initial Access

  • T1200: Hardware Additions - USB device connection by the field visitor
  • T1091: Replication Through Removable Media - device appears as a standard keyboard

Execution

  • T1059.001: Command and Scripting Interpreter: PowerShell - Windows payload execution
  • T1059.004: Command and Scripting Interpreter: Unix Shell - Linux and macOS variants

Discovery

  • T1082: System Information Discovery - one-command pentest survey
  • T1087: Account Discovery - domain membership and admin rights
  • T1201: Password Policy Discovery - password policy collection
  • T1482: Domain Trust Modification Checks - domain controller and site mapping

Credential Access

  • T1557: Adversary-in-the-Middle - impostor responder tests on the LAN
  • T1040: Network Sniffing - traffic interception to show visible exposure

Collection

  • T1005: Data from Local System - file browsing and survey collection
  • T1113: Screen Capture - screenshot evidence

Command and Control

  • T1071: Application Layer Protocol - command channel to the operator
  • T1573: Encrypted Channel - encrypted fleet sync and relay

Findings & Vulnerabilities Identified

A typical engagement of this kind surfaces:

🔴 Critical: Domain Admin Cached on Workstations

The one-command survey showed domain administrator credentials cached on standard user workstations. A single compromised desk yields domain-level access.

🟠 High: Legacy Name-Lookup Protocol Exposure

Network impostor tests recorded workstations answering name lookups and leaking authentication material through legacy protocols.

🟠 High: Unencrypted Rebuilt Laptops

Rebuilt machines returned to service without disk encryption. The same armed device catches this at every redeployment.

🟡 Medium: Overly Broad Shared Folders

Shared folders were readable by groups far wider than the data owners intended.

Recommended Countermeasures

Technical Controls

  • USB port controls and device whitelisting on workstations
  • Disable legacy name-lookup protocols (LLMNR/NBT-NS) and enable SMB signing
  • Enforce full-disk encryption as a redeployment gate
  • Restrict local admin rights and credential caching

Administrative Controls

  • Standing authorization workflow for recurring assessments
  • Scope documents defining systems, windows and contacts
  • Visitor selection by availability with defined physical tasks only
  • Expert review checkpoint before every client report

Impact & Results

This engagement model changes the economics of security consulting:

1
Expert Running Several Parallel Engagements
0
Specialist Skills Needed On Site
100%
Identical Method on Every Visit
1
Merged Report per Site

Because the device holds the method, the person sent on site is chosen by availability rather than skill, and the results are identical no matter who plugged the devices in. Expert time concentrates on arming and review, the two steps that need senior judgment, so one specialist can run several engagements in parallel while every client still receives the same rigorous, ATT&CK-mapped report.

⚖️ Ethical Testing Standards

Delegating execution to non-specialists raises the bar for governance:

  • Written client authorization defining scope, systems and time windows before arming
  • Test plans reviewed and approved by the responsible expert for each engagement
  • Devices armed per engagement and wiped or re-armed between clients
  • Field visitors briefed on exactly what to connect and what never to touch
  • All collected data encrypted on the device and handled under the consulting firm's data policies
  • Expert review of every finding before client delivery

Learn more about our Ethical Use Policy.

Internal Security Program

Automated Testing of New Deployments

When a new machine or network segment goes into service, who evaluates what an attacker could do from that position? This use case shows how an organization turns its security testing into a routine acceptance gate: the device evaluates every new system with common pentester activities, and the security team reviews the findings remotely.

Scenario Overview

New workstations, servers and rebuilt laptops are typically joined to the company domain and go straight into production. New network segments go live the same way. The organization connects the device at deployment time to answer one question from the attacker's perspective: what could an attacker do from here?

  • The USB connection takes control of the new machine and runs the opening checklist of a pentest automatically
  • The network connection evaluates the new segment for credential leaks and impostor behavior
  • The same run repeats for every new deployment and after every change or patch cycle

Testing Methodology

1

USB Connection to the New Machine

The target is a freshly deployed domain-joined workstation, server or rebuilt laptop. Once connected, the operator has full command and control: any command can be run and the output is returned live. The device detects the operating system on its own and runs the matching survey.

2

The Opening Checklist, Collected Automatically

One command collects what a pentester gathers in the first hour: domain membership, domain controller and site, admin rights, password policy, security software, disk encryption, patch level, firewall state, shared folders, mapped drives and open ports.

3

Anything Further on Demand

Where the survey raises questions, the operator browses files, copies data, runs additional commands and captures screenshots. This tests what an attacker with this machine could do, safely, with every step recorded.

4

Network-Side Checks and the Acceptance Gate

On the network side, the device tests whether login credentials leak through Windows file sharing and directory services, whether computers follow an impostor answering name lookups, and whether browsers accept a rogue proxy setting. The same armed device moves from machine to machine as systems deploy; runs repeat after every change or patch cycle, with results timestamped for audits and reviewed remotely by the security team.

MITRE ATT&CK Mapping

The deployment checks map to the following MITRE ATT&CK tactics and techniques:

Initial Access

  • T1091: Replication Through Removable Media - keyboard-emulated takeover of the new machine

Discovery

  • T1082: System Information Discovery - patch, encryption and firewall state
  • T1087: Account Discovery - admin rights on the fresh deployment
  • T1069: Permission Groups Discovery - shared folder group membership
  • T1201: Password Policy Discovery - domain password policy
  • T1046: Network Service Scanning - open ports on the new segment

Credential Access

  • T1557: Adversary-in-the-Middle - impostor answering name lookups
  • T1040: Network Sniffing - credential leakage through file sharing protocols

Collection

  • T1005: Data from Local System - on-demand file browsing and copying
  • T1113: Screen Capture - recorded evidence of exposure

Findings & Vulnerabilities Identified

A typical rollout surfaces these findings:

🔴 Critical: Standard Users with Local Admin

The new workstation image granted local administrator rights to everyday users. Every fresh deployment carried the same problem until the image was fixed.

🟠 High: New Segment Leaks Authentication Material

On the new office segment, the impostor test recorded multiple machines trusting an unauthorized name-lookup responder and exposing credential material.

🟠 High: Security Software Missing After Rebuild

A rebuilt laptop returned to service without the endpoint protection suite. The survey caught it before the machine reached its user.

🟡 Medium: Patch Level Behind Baseline

Several deployments missed the latest patch wave; the timestamped history showed exactly which build cycle skipped them.

Recommended Countermeasures

Technical Controls

  • Harden the golden image: no local admin for standard users, EDR and encryption pre-enabled
  • Disable legacy name-lookup protocols and require SMB signing domain-wide
  • Automated patch-compliance reporting per deployment wave
  • Network access control for new segments

Administrative Controls

  • Make the device run a formal acceptance gate in the deployment checklist
  • Re-run the evaluation after every change or patch cycle
  • Security team reviews findings remotely with timestamped history
  • Define remediation owners for each recurring finding class

Impact & Results

A typical program shows what routine testing delivers:

40+
Systems Evaluated at Rollout
11
Survey Checks per Machine, One Command
100%
Runs Timestamped for Audit
0
Production Impact

Security testing became a routine acceptance gate for production: every new system gets the same evaluation, every change cycle repeats it, and results are timestamped for audits. The security team reviews findings remotely instead of scheduling ad-hoc pentests, and deployment-time mistakes are caught before the first user logs in.

⚖️ Ethical Testing Standards

Internal testing of production systems requires clear boundaries:

  • Security team owns the program; deployment teams are informed of every evaluation
  • Testing limited to the organization's own newly deployed systems and segments
  • On-demand exploration restricted to machines in the current deployment scope
  • Collected data minimized to the survey scope and retained per policy
  • Findings routed to remediation owners, not used for individual performance evaluation

Learn more about our Ethical Use Policy.

Security Training

Internal Training & Simulations with Benign Load

Awareness training is only credible when the audience sees the real effect. This use case shows how organizations run device-based training and simulations that carry zero risk to production systems. Every demonstration uses benign load only, and classroom-safe builds ship with network attacks removed.

Scenario Overview

Security teams need to show staff and trainees what a takeover actually looks like, without touching production. The training kit supports a full curriculum of harmless demonstrations:

  • Harmless demos: a training script types a visible message into a text editor. The audience sees the takeover effect while nothing on the machine changes
  • Safe live control: the instructor demonstrates real command and control with harmless commands (whoami, folder listing, a screenshot) through the same channel an attacker would use
  • Proof without exploitation: network traps record an exposure to prove it exists; nothing is exploited
  • Detection practice: the team replays known attack patterns against their own environment and tunes their alerts
  • Live drills: the presence board supports evacuation exercises: who is in the building and who is accounted for, displayed live

Testing Methodology

1

Harmless Demos for Awareness Sessions

A training script types a visible message into a text editor on the presenter's machine. The audience watches the cursor move and text appear with no one touching the keyboard. The takeover effect, with zero changes to the machine.

2

Safe Live Control on the Training Laptop

On a dedicated training laptop, the instructor runs real command-and-control with harmless commands: whoami, a folder listing, a screenshot. Trainees see exactly what an attacker's channel looks like from the operator's side, through the instructor's phone browser. No app or internet required.

3

Proof Without Exploitation

On the isolated training network, traps record when a system leaks credentials or follows an impostor responder. The log entry is the proof the exposure exists. No exploitation, no data taken.

4

Detection Practice and Live Drills

The security team replays known attack patterns against their own environment and tunes their alerts to the arrivals. For facilities drills, the presence board displays who is in the building and who is accounted for, live, for real evacuation exercises.

⚠️ Classroom-Safe Builds: Devices supplied for trainee hands-on use come with network attacks removed from the build, safe to hand to a classroom.

MITRE ATT&CK Mapping

The demonstrations emulate the following MITRE ATT&CK tactics and techniques, so blue teams train on realistic arrivals:

Execution

  • T1059.001: Command and Scripting Interpreter: PowerShell - emulated payload execution
  • T1059.004: Command and Scripting Interpreter: Unix Shell - shell command demonstration

Discovery

  • T1033: System Owner/User Discovery - whoami demonstration
  • T1083: File and Directory Discovery - folder listing demonstration

Collection

  • T1113: Screen Capture - screenshot demonstration

Credential Access (Proof Only)

  • T1557: Adversary-in-the-Middle - trap records the exposure, nothing exploited
  • T1040: Network Sniffing - visibility proof on the training network

Findings & Vulnerabilities Identified

A typical program produces these measurements:

🟠 High: Alerts Missed the Benign C2 Pattern

The detection-practice replays showed the SOC's rules did not alert on the emulated takeover channel. The team closed the gap using the same replay as the regression test.

🟡 Medium: Exposures Proven but Never Exploited

Network traps recorded credential leakage on the training segment, giving the team concrete proof for remediation without a single exploit being run.

🟡 Medium: Awareness Effect Not Measured

Before the device-based demos, training success was judged by attendance; the visible takeover demonstration made the risk concrete and measurable in follow-up surveys.

Recommended Countermeasures

Technical Controls

  • Run all demonstrations on dedicated training hardware or isolated segments
  • Use classroom-safe builds with network attacks removed for trainee hands-on time
  • Feed replay arrivals into the SOC's detection tuning cycle

Administrative Controls

  • Schedule regular drills combining awareness demos and detection practice
  • Integrate the presence board into official evacuation exercises with facilities
  • Track remediation of every proven exposure after each session

Impact & Results

A typical program shows what benign-load simulation delivers:

0
Changes to Production Systems
100%
Benign Load Only
4
Demo Types from One Kit
1
Switch to Classroom-Safe Build

Training with the device carries zero risk to production: demonstrations use benign load, proofs stop at the recorded exposure, and classroom kits ship with network attacks removed. Audiences see the real takeover effect, blue teams tune detections against realistic arrivals, and facilities gain a live presence board for evacuation exercises. All from the same hardware.

⚖️ Ethical Testing Standards

Training use is bounded by strict benign-load rules:

  • Every demonstration script is reviewed to confirm it changes nothing on the target machine
  • Network traps record exposures only: no exploitation, no data collection beyond the log entry
  • Trainee hands-on devices use restricted builds with network attacks removed
  • Presence-based drills use consent-registered devices only
  • Detection replays run inside the organization's own environment with change-control approval

Learn more about our Ethical Use Policy.

Red Team Operations

Red Team Operations

For offensive security teams, the device is a full-operation platform: discreet command and control from a phone, one-click launch of prepared attacks with automatic OS matching, passive tracking of specific people and assets, and after-action evidence for the engagement report. Built for authorized red team engagements.

Scenario Overview

A red team needs persistence of presence, discretion and repeatability across a physical engagement. The device kit supports four operational pillars:

  • Command and control: on a target computer the device appears as a normal keyboard and keeps a discreet channel to the operator: any command with live output, file browsing and copying, live logs, screenshots
  • Tracking and identification: passive presence monitoring shows who and what is in range: when a registered device appears, which devices are new to a zone, who is a regular, who returned after an absence
  • One-click simulations: attack scripts prepared in advance launch from the browser, with the device selecting the Windows, macOS or Linux variant automatically
  • Stealth: the device acts only when the machine is unlocked, hides its windows, removes its traces and reconnects after interruptions

Testing Methodology

1

Pre-Operation Setup

Attack scripts are prepared and loaded in advance. Specific people are registered beforehand under an alias, with consent, for presence tracking. The operator defines zones and pairs devices so commands can relay across the site.

⚠️ Rules of Engagement: Operations run only under a signed rules-of-engagement document with defined scope, objectives, and emergency contacts.

2

Insertion and Stealth

On a target computer the device appears as a standard keyboard and detects the operating system on its own. It acts only when the machine is unlocked and in use, hides its windows, removes its traces, and reconnects automatically after interruptions.

3

Live Command and Control from a Phone

The operator controls the device from a phone over the device's own hotspot: any command with live output, file browsing and copying, live logs, screenshots, and one-click launch of the prepared simulations. Paired devices relay commands, so one operator covers several zones, or reaches in from distance through the Long Distance Module.

4

Presence Intelligence and After-Action Evidence

Passive WiFi and Bluetooth listening classifies people and devices as new, known, regular or returning. Data is encrypted on the device, stored under pseudonyms, and wiped with one command. Every action is logged on the device, giving clean material for the engagement report.

MITRE ATT&CK Mapping

The operation maps to the following MITRE ATT&CK tactics and techniques:

Initial Access

  • T1200: Hardware Additions - physical device insertion during the engagement
  • T1091: Replication Through Removable Media - keyboard-emulated takeover

Execution

  • T1059: Command and Scripting Interpreter - OS-matched payload variants
  • T1059.001: Command and Scripting Interpreter: PowerShell - Windows simulations

Defense Evasion

  • T1070: Indicator Removal - hidden windows and trace cleanup after execution

Discovery

  • T1082: System Information Discovery - automatic OS identification
  • T1018: Remote System Discovery - network segment mapping around the device

Collection

  • T1005: Data from Local System - file browsing and copying
  • T1113: Screen Capture - live screenshot capability

Command and Control

  • T1071: Application Layer Protocol - discreet operator channel
  • T1573: Encrypted Channel - encrypted control and sync
  • T1090: Proxy - paired devices relaying commands across zones

Findings & Vulnerabilities Identified

A representative engagement surfaced the following findings:

🔴 Critical: Unrestricted USB Peripherals in Secure Zones

Devices inserted into workstations inside restricted zones were accepted without any peripheral policy. The physical security boundary did not extend to USB endpoints.

🟠 High: HID Injection Undetected

Keyboard-emulated takeover produced no endpoint alerts on any of the tested operating systems; monitoring had no visibility into HID-level activity.

🟠 High: Wireless Presence Exposes Staff Patterns

Passive listening mapped staff movement and presence patterns from unmodified wireless signals. That is an intelligence gift to any physical attacker.

🟡 Medium: Unmonitored Inter-Zone Links

Paired relay devices moved commands between zones across links that inter-zone traffic monitoring did not cover.

Recommended Countermeasures

Technical Controls

  • USB peripheral allowlisting and HID injection detection
  • Wireless monitoring for unknown hotspots and device-to-device links
  • Endpoint telemetry that surfaces keyboard-device process injection
  • Inter-zone traffic inspection, including wireless links

Administrative Controls

  • Physical access policies that treat unattended workstations as attack surface
  • Clear-screen and lock policies enforced by group policy
  • Red team rules of engagement with defined zones and emergency contacts
  • Post-engagement purple team session on detection gaps

Impact & Results

This representative operation shows what the kit changes for red teams:

3
Zones Covered by One Operator
12
One-Click Simulations Launched
100%
Actions Logged for the Report
0
Traces Left on Target Machines

The operation stayed repeatable and consistent: prepared simulations launched with one click and selected the right OS variant every time, paired devices let a single operator cover several zones, and every action was logged as after-action evidence. The client received an engagement report built from complete, timestamped logs instead of operator memory.

⚖️ Ethical Testing Standards

Red team use demands the highest operational discipline:

  • Signed rules of engagement with scope, objectives and emergency contacts before insertion
  • Legal review of all techniques, including wireless listening, for the engagement jurisdiction
  • Presence tracking only for consent-registered devices under alias
  • Presence data encrypted, pseudonymized and wiped at engagement conclusion
  • No persistence installed; every change reversed and verified at wrap-up
  • Complete action logs preserved as after-action evidence

Learn more about our Ethical Use Policy.

Detection Validation

Purple Team & SOC: Detection Validation

The red side runs the attacks, the blue side sees what arrives in monitoring, and both sides get the same report. This use case shows how purple teams use the device to validate detection coverage against real hardware attacks, and prove whether alert tuning improved detection.

Scenario Overview

SOCs are usually validated by paper exercises or atomized malware samples. The device replays realistic, built-in attacks against the client's own network instead:

  • Credential traps and impostor responders on the network side
  • Machine takeover over USB on the endpoint side
  • The ATT&CK-mapped report shows which techniques worked, which the SOC logged and which were missed
  • Repeat runs show whether alert tuning improved detection

Testing Methodology

1

Replay Built-In Attacks

The red side launches the built-in attack set against the client's own network: credential traps, impostor responders, and machine takeover over USB. Simulations are repeatable and consistent, so each run is directly comparable.

2

Blue Side Watches Monitoring

The SOC works its normal queues. Nothing about the replay tells the blue side which technique is running. They see exactly what a real attack would have left in their tools.

3

Compare the Same Report

The ATT&CK-mapped report shows, per technique: did it work, did the SOC log it, was it missed? Both sides work from the same document, so the debrief is about coverage, not recollection.

4

Tune and Repeat

The blue side tunes alerts for the missed techniques. A repeat run then proves whether the tuning improved detection, with the same hardware, the same attacks and the same report format.

MITRE ATT&CK Mapping

The replay set spans the following MITRE ATT&CK tactics and techniques:

Initial Access

  • T1091: Replication Through Removable Media - USB takeover replay

Execution

  • T1059: Command and Scripting Interpreter - OS-matched payload execution

Credential Access

  • T1557: Adversary-in-the-Middle - impostor responder replay
  • T1040: Network Sniffing - interception visibility replay

Command and Control

  • T1071: Application Layer Protocol - operator channel arrival
  • T1573: Encrypted Channel - encrypted control traffic

Findings & Vulnerabilities Identified

A typical validation cycle produces this coverage picture:

🔴 Critical: USB Takeover Invisible End-to-End

No tool in the chain (endpoint, network or SIEM) registered the emulated keyboard takeover. Detection coverage for hardware-based initial access was zero.

🟠 High: Responder Attacks Logged but Never Alerted

The impostor responder replays appeared in logs, but no alert rule consumed them. The data existed; the escalation path did not.

🟡 Medium: Alerts Fired Without Escalation

Two low-severity alerts triggered correctly but sat untriaged; the repeat run measured whether routing changes fixed the handoff.

Recommended Countermeasures

Technical Controls

  • Detection rules mapped to the replayed ATT&CK techniques
  • USB and HID activity visibility in endpoint telemetry
  • Log-source health checks so responder events reach the SIEM

Process Controls

  • Quarterly validation replays with the same attack set
  • Coverage tracked per technique: works / logged / missed
  • Joint red-blue debriefs working from the shared report

Impact & Results

A typical cycle shows the measurement loop:

14
Techniques Replayed
5
Missed on First Run
13
Detected on Repeat Run
1
Shared Report for Both Sides

The first run found five techniques the SOC missed; after tuning, the repeat run caught thirteen of fourteen. Because the device replays the same attacks identically each time, improvement is measured, not asserted. The ATT&CK-mapped report gives both sides the same evidence of what changed.

⚖️ Ethical Testing Standards

Detection validation runs inside the client's own environment under strict rules:

  • Replays executed only against the client's own network and endpoint estate
  • Change-control approval for every alert tuning change between runs
  • Traps record exposures without exploiting them
  • Results used for detection improvement, not individual blame

Learn more about our Ethical Use Policy.

Compliance Evidence

Audit & Compliance: Continuous Evidence

Audits require proof that security controls work, not just that a policy exists. This use case shows how recurring device runs generate a continuous evidence stream automatically: every run timestamped, severity-rated, ATT&CK-mapped and exportable, with a history that also shows drift.

Scenario Overview

Organizations facing ISO 27001, PCI DSS or NIS2-style audits traditionally assemble evidence by hand before each audit window. The device approach replaces the scramble:

  • Recurring runs test the controls the audits ask about, from inside the machines and from the network
  • Every run is timestamped and severity-rated, mapped to MITRE ATT&CK, exportable as PDF, JSON or CSV
  • Recurring runs produce a continuous evidence stream for ISO 27001, PCI DSS and NIS2 style audits
  • The history also shows drift: what passed last quarter and fails now

Testing Methodology

1

Schedule the Recurring Runs

The organization defines the control checks that matter for its audit scope and runs them on a fixed schedule: per site, per segment, per machine group.

2

Every Run Produces Audit-Grade Output

Each run is timestamped and severity-rated, mapped to MITRE ATT&CK, and exportable as PDF for auditors or JSON/CSV for evidence systems.

3

Build the Continuous Evidence Stream

Collected across recurring runs, the history becomes the evidence stream: not a snapshot from audit week, but a dated record showing the controls were tested and held, or didn't, at every point in the period.

4

Track Drift Between Runs

The history shows drift: what passed last quarter and fails now. Drift findings route to remediation before the next audit, not during it.

What the Evidence Stream Contains

Each run report is structured for audit consumption:

Report Contents

  • Executive summary for audit and management readers
  • Severity per event with a full timeline
  • Plain-language findings for control owners
  • MITRE ATT&CK mapping for technical assessors

Framework Support

  • ISO 27001-style control effectiveness checks
  • PCI DSS segmentation and encryption verification
  • NIS2-style technical measure evidence
  • PDF, JSON and CSV exports for auditor and GRC tooling

Practical Safeguards

Evidence Integrity

  • Runs executed on a fixed schedule, not selectively
  • Timestamps and logs retained under the evidence policy
  • Exports generated from the same source logs as the reports

Scope Discipline

  • Checks limited to systems in the declared audit scope
  • Collected data minimized to the control questions asked
  • Auditor access provided through exports, not live devices

Impact & Results

A typical program shows the difference:

12
Runs per Year, per Site
3
Export Formats (PDF/JSON/CSV)
100%
Runs Timestamped and Rated
0
Manual Evidence Assembly at Audit Time

Audit preparation stopped being a project: the recurring runs generate the continuous evidence stream as a by-product of testing, exports drop straight into auditor requests, and the drift view turns "what changed since last quarter" into a standing report instead of an audit-week surprise.

⚖️ Ethical Testing Standards

Compliance testing keeps to the audited scope:

  • Runs authorized by the control owner for the declared audit scope
  • Evidence retained and disposed of per the organization's data policies
  • Findings reported to remediation owners irrespective of audit calendar
  • No testing of systems outside the compliance boundary

Learn more about our Ethical Use Policy.

Occupancy & Mustering

Occupancy & Evacuation Mustering

The presence system answers two questions facilities has always struggled with: who is in the building, and is everyone accounted for in an evacuation? It runs on a facilities budget, not a security budget: the same hardware, with privacy built in.

Scenario Overview

Evacuation exercises and daily occupancy planning both rely on outdated tools: badge swipes that show who entered but not who stayed, or clipboards at the muster point. The device-based presence system provides:

  • Live occupancy per zone, on the device screen and in the web interface
  • Evacuation mustering lists built from consent-registered staff devices
  • After-hours presence and new-visitor alerts
  • Data encrypted on the device, stored under pseudonyms, wipeable with one command

Testing Methodology

1

Place Devices per Zone

Devices are placed in the building's zones: floors, wings, muster-relevant areas. They listen passively to WiFi and Bluetooth signals; nothing is installed on anyone's phone or laptop.

2

Consent-Register Staff Devices

Staff who want mustering protection register their devices beforehand, with consent. Registered devices are what the mustering lists are built from.

3

Read Live Occupancy

Status, network address and live occupancy show on the device display, no phone needed, and in the web interface for facilities staff: who is in which zone right now.

4

Run Drills and Daily Alerts

Evacuation exercises get live mustering lists: who is in the building and who is accounted for. Day to day, the system raises after-hours presence and new-visitor alerts.

What the Data Shows

The presence system answers facilities questions directly:

Live Views

  • Occupancy per zone, live, on the device screen or web interface
  • People classified as new, known, regular or returning
  • Mustering lists during drills and real evacuations

Alerts

  • After-hours presence in zones that should be empty
  • New-visitor alerts for unregistered devices
  • Mustering gaps: registered devices still inside during a drill

Practical Safeguards

Privacy is the design constraint that makes this acceptable to works councils and privacy officers:

Data Protection

  • Data is encrypted on the device
  • Stored under pseudonyms, not names
  • Can be wiped with one command at any time

Governance

  • Mustering built only from consent-registered devices
  • Purely passive listening: nothing installed on phones or laptops
  • Works council and privacy officer review before rollout

Impact & Results

A typical deployment shows the difference:

Live
Occupancy per Zone
100%
Consent-Registered Mustering
0
Apps Installed on Staff Phones
1
Command to Wipe All Data

Evacuation exercises moved from clipboard guessing to live mustering lists, and facilities gained zone-level occupancy for daily planning, on a facilities budget. Because data is encrypted, pseudonymized and wipeable with one command, works councils and privacy officers could accept the system on review rather than in conflict.

⚖️ Ethical Testing Standards

Presence systems live or die by consent and restraint:

  • Mustering lists built exclusively from consent-registered devices
  • No re-identification of individuals beyond the registered scope
  • Data encrypted on-device, pseudonymized in storage, wiped on demand
  • Deployed for safety purposes with works council involvement, not covert monitoring
  • Purely passive: nothing transmitted, nothing installed on personal devices

Learn more about our Ethical Use Policy.

Physical Security

Insider Threat & Zone Monitoring

Restricted areas are usually guarded by a door log. This use case shows how the device builds a passive picture of who enters restricted zones: who is new, who is a regular, who returned after an absence, with deviation flags when something appears where it does not belong.

Scenario Overview

Labs, server rooms, finance areas and other restricted zones share a monitoring gap: badge systems record entries but not patterns. The device adds the pattern layer, passively:

  • Devices placed in restricted zones classify who is new, who is a regular, and who returned after an absence
  • Zone deviation flags appear when a device appears where it does not belong
  • Purely passive: nothing is transmitted, nothing is installed on phones or laptops

Devices Used in This Test

This zone deployment uses this configuration:

Testing Methodology

1

Deploy to Restricted Zones

Devices are placed in the zones that need pattern visibility. Placement is the only active step. From then on the devices listen passively to WiFi and Bluetooth signals in range.

2

Classify Who and What Is in Range

The device classifies devices and people as new, known, regular or returning. Patterns emerge without identifying anyone: the new badge in the lab, the regular in the server room, the return after weeks of absence.

3

Flag Zone Deviations

When a device appears where it does not belong (say, a finance-floor device in the lab zone), a deviation flag is raised for the security team to review.

4

Review Patterns, Retain Control of Data

Security reviews zone patterns on their own schedule. Data is encrypted on the device, stored under pseudonyms, and can be wiped with one command, which keeps the monitoring reversible.

What the Data Shows

The zone picture answers physical security questions directly:

Pattern Views

  • Who is new to a zone versus who is a regular
  • Who returned after an absence
  • Presence patterns by zone and time

Deviation Flags

  • Devices appearing where they do not belong
  • New devices in zones that rarely see them
  • After-hours presence patterns in restricted areas

Practical Safeguards

Passive by Design

  • Nothing is transmitted by the system
  • Nothing is installed on phones or laptops
  • Listening is receive-only on existing signals

Data Handling

  • Encryption on the device
  • Pseudonymous storage: patterns, not names
  • One-command wipe keeps deployment reversible

Impact & Results

A typical deployment shows the gain:

3
Restricted Zones Covered
4
Classes: New / Known / Regular / Returning
0
Transmitters Installed
1
Command to Wipe Data

Security gained the pattern layer that badge logs never had: who is new in a zone, who belongs, and who came back after being away, plus deviation flags when a device shows up where it does not belong. Because the system is purely passive and the data stays encrypted and pseudonymous on the device, the monitoring adds visibility without adding surveillance infrastructure.

⚖️ Ethical Testing Standards

Zone monitoring is bounded by proportionality:

  • Deployed only in restricted zones with a defined security purpose
  • Patterns reviewed as patterns, no individual dossiers
  • Data encrypted, pseudonymized and wipeable at any time
  • Nothing installed or transmitted to personal devices
  • Deployment disclosed to the workforce per local law and policy

Learn more about our Ethical Use Policy.

IT Operations

Shadow-IT & Asset Discovery

Few organizations have a complete list of what runs on their network. This use case shows how IT operations builds one by listening: a passive inventory of devices and operating systems, alerts when something new appears, and zero performance impact, and nothing to deploy on endpoints.

Scenario Overview

Asset inventories rot: scanners miss devices, spreadsheets age, and shadow-IT fills the gaps. The device approach needs no credentials, no agents and no scan windows:

  • Passive inventory of devices and operating systems on the network
  • Alerts when a new device appears
  • Zero performance impact and nothing to deploy on endpoints

Devices Used in This Test

This inventory deployment uses this configuration:

Testing Methodology

1

Plug Into the Segment

The device connects to a LAN port on the segment to be mapped and listens. Passive reconnaissance means no scan traffic, no authentication attempts, no load on the network.

2

Build the Passive Inventory

From observed traffic alone, the device builds an inventory of devices and their operating systems, including the printers, cameras, media boxes and lab equipment that scanners and CMDBs usually miss.

3

Alert on New Devices

When a device appears that was not in the inventory before, an alert fires: the shadow-IT signal, caught at plug-in time instead of at audit time.

4

Reconcile With the CMDB

IT operations compares the passive inventory against the CMDB: undocumented devices get registered or investigated, and stale entries get corrected from observed reality.

What the Data Shows

The passive inventory answers IT operations questions directly:

Inventory Views

  • Device count and types per segment
  • Operating system fingerprint spread
  • Devices present that the CMDB does not know

Change Signals

  • New-device alerts at plug-in time
  • Devices that disappeared from a segment
  • Segments with unusual device churn

Practical Safeguards

Zero Footprint

  • Zero performance impact on the network
  • Nothing to deploy on endpoints
  • No credentials needed for the passive view

Scope Discipline

  • Deployed on segments IT owns and has disclosed
  • Inventory used for asset management, not individual monitoring
  • Data handled under the IT operations data policy

Impact & Results

A typical deployment shows the gain:

180
Devices Discovered passively
23
Undocumented Devices Found
0
Endpoint Agents Deployed
0
Network Performance Impact

The passive view found twenty-three devices the CMDB did not know: printers, media devices and lab equipment on segments everyone assumed were fully mapped. Because the method is listen-only, IT gained the inventory without a project: no agents, no scan windows, no performance cost, and standing alerts when the next shadow-IT device plugs in.

⚖️ Ethical Testing Standards

Asset discovery stays inside operational boundaries:

  • Deployed only on network segments owned by the organization
  • Passive listening only; no active scanning of endpoints
  • Inventory data used for asset management purposes
  • Deployment disclosed within the organization's IT governance

Learn more about our Ethical Use Policy.

Executive Protection

Executive Protection: Traveler Kits

Executives work from hotels and shared offices on unvetted networks, usually minutes before a critical call. This use case shows how a travel-bag kit checks those environments in advance: plug into the hotel network or a shared PC and run the standard checks before use.

Scenario Overview

Travel is when executives are most exposed and least protected: hotel WiFi with unknown operators, business-center PCs of unknown history, shared office networks shared with strangers. The traveler kit turns the standard checks into a pre-use routine:

  • Plug into the hotel network and run the network-side checks before connecting real work
  • Plug into a shared PC and run the standard machine checks before use
  • Results review in minutes on a phone over the device's own hotspot. No app, no internet needed
  • Fits in a travel bag

Devices Used in This Test

The traveler kit contains the following device configuration:

Testing Methodology

1

Check the Hotel Network First

Before any real work connects, the network device plugs into the hotel or shared-office network and runs the standard network checks: whether credentials would leak through common protocols, whether an impostor answering name lookups gets followed, what traffic is visible to others on the segment.

2

Check the Shared PC

For business-center or loaner machines, the USB device runs the standard checks before use: security software, disk encryption, patches, firewall, open ports: the opening checklist that tells the executive what kind of machine they are about to touch.

3

Review on the Phone in Minutes

Results arrive on the executive's phone through the device's own hotspot: status, findings, severity. The go/no-go decision happens before exposure, not after.

4

Pack and Move On

The kit packs back into the travel bag. Devices are wiped or re-armed per trip, and protection staff can review the collected evidence afterwards for a travel-security picture over time.

What the Check Covers

The pre-use routine covers both environments the executive is about to touch:

Network Side

  • Credential-leak traps through common sharing protocols
  • Impostor name-lookup response tests
  • Traffic visibility to others on the segment

Machine Side

  • Security software and disk encryption state
  • Patch level and firewall configuration
  • Domain membership and admin rights, where applicable

Practical Safeguards

Use Boundaries

  • Checks run only on equipment and networks the traveler is authorized to test
  • Where network terms prohibit testing, the kit stays in the bag
  • Machine checks are read-only surveys; nothing is changed or installed

Data Handling

  • Evidence encrypted on the device
  • Wiped or re-armed per trip
  • Review restricted to the executive protection team

Impact & Results

A typical routine shows the change:

Minutes
Per Environment Check
2
Environments Covered (Network + PC)
1
Travel-Bag Kit
0
Changes Made to Checked Machines

The pre-use check became a routine instead of a leap of faith: the network is tested before work touches it, the shared PC is surveyed before the executive sits down, and the go/no-go decision rests on severity-rated findings reviewed on a phone. All from a kit that fits in a travel bag.

⚖️ Ethical Testing Standards

Traveler checks carry strict legal boundaries:

  • Testing only where the traveler is authorized: owned or contractually permitted equipment and networks
  • Hotel and shared networks are tested only where terms and local law permit; otherwise checks are skipped
  • Shared-PC checks limited to read-only surveys
  • Evidence wiped or re-armed per trip; access restricted to the protection team

Learn more about our Ethical Use Policy.

Education & Research

Education & Research Labs

Universities and training companies need safe, real hardware for teaching offensive security, not screenshots and slideshows. This use case shows how restricted device builds make lab equipment that is safe to hand to students, with resettable CTF challenges and research-grade data on top.

Scenario Overview

Teaching hardware security means letting students run real takeovers, so the hardware must be safe by construction. The education build answers that:

  • Restricted builds with the network attacks removed make safe lab equipment
  • CTF events get consistent, resettable challenges
  • The device's operating system fingerprint data is a research product for machine learning work

Devices Used in This Test

The education lab uses this configuration:

Testing Methodology

1

Restricted Builds for Student Hands-On Time

Student kits ship with network attacks removed from the build. Students run real keyboard-emulation takeovers against lab machines and see the operator side. A hardware boundary makes unsafe use structurally impossible.

2

Classroom Exercises

Instructors demonstrate live control with harmless commands (whoami, folder listing, a screenshot), and students repeat the sequence themselves on lab hardware through the same browser interface professionals use.

3

Resettable CTF Challenges

For capture-the-flag events, devices load identical challenge sets. Every team faces the same hardware running the same challenges, and each device resets to a clean state between rounds: consistent, resettable, repeatable.

4

Research Datasets

The device's operating system fingerprint data, collected as it classifies lab machines, is exported as structured datasets for machine learning research on device fingerprinting.

What the Lab Gets

The education build gives institutions three concrete assets:

Teaching Hardware

  • Safe-by-construction builds for student hands-on use
  • Real takeover effects instead of video demonstrations
  • The same browser interface used in professional engagements

Research Products

  • Consistent, resettable CTF challenge hardware
  • OS fingerprint datasets for machine learning work
  • 19 keyboard layouts supporting international curricula

Practical Safeguards

Safe by Construction

  • Network attacks removed from student builds
  • Hardware boundary, not a policy promise
  • Lab exercises run on dedicated lab machines only

Operational Hygiene

  • Devices reset between rounds and cohorts
  • Research data exported pseudonymized
  • Instructor access separate from student access

Impact & Results

A typical lab shows what institutions gain:

0
Network Attacks in Student Builds
100%
Resettable CTF Challenges
19
Keyboard Layouts Built In
1
Research Dataset Product

Students run real takeovers on real hardware without the lab becoming a liability: the restricted build makes unsafe use structurally impossible, CTF rounds reset to identical starting states, and the fingerprint data flowing out of the lab doubles as a machine-learning research product. Teaching offensive security stopped being a choice between realism and safety.

⚖️ Ethical Testing Standards

Educational use keeps safety and consent at the center:

  • Student builds verified to have network attacks removed
  • Exercises confined to institution-owned lab machines
  • CTF participants compete against dedicated challenge hardware only
  • Research datasets pseudonymized and shared under research ethics review

Learn more about our Ethical Use Policy.

Need Security Testing for Your Environment?

Our team can help identify vulnerabilities in your physical and digital security posture through authorized, ethical testing.

Request a Consultation View Our Services