Skip to content

HerrHozi/AS2Go

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

AS2Go (Attack Scenario To Go)

Module Type PowerShellGallery PowerShell License Maintenance

Author:          Holger Zimmermann | zimmermannn.holger@live.de
Current Version: 2026.5.21.1342
Last Update:     2026-05-21

AS2Go (Attack Scenario To Go) is a PowerShell-based Active Directory attack simulation and training framework designed for demos, workshops, security awareness sessions, and purple team exercises.

The project provides a controlled lab environment that demonstrates how attackers can move through an Active Directory infrastructure by following a realistic cyber kill chain — from initial access to full domain compromise.

AS2Go helps security professionals, consultants, and defenders better understand how common weaknesses in Active Directory can be abused in practice, while providing a safe and repeatable environment for learning and demonstrations.

It is designed for:

  • Security awareness and blue team training
  • Detection engineering and incident response exercises
  • Demonstrating Semperis Directory Services Protector (DSP), Microsoft Defender and Sentinel alert behavior
  • Repeatable SOC tabletop and hands-on lab sessions

Project Information

Important Notice

AS2Go is intended for educational use in isolated, authorized lab environments only.

Do not run this module in production or in any environment you do not own or explicitly control. You are responsible for legal, policy, and compliance requirements in your organization.

What AS2Go Demonstrates

attack-scenario-to-go-along-the-kill-chain_853x480_7s

AS2Go follows a realistic multi-phase attack chain to generate observable behavior for defenders. Depending on your setup and enabled phases, the simulation can include:

  • Initial account abuse and access attempts
  • Reconnaissance activities
  • Privilege escalation paths
  • Sensitive data access and exfiltration simulation
  • Domain compromise and persistence scenarios

The goal is not stealth, but visibility and learning.

Module Structure

  • Public/: Entry points and phase orchestrators
  • Core-Functions/: Internal helper and attack action functions
  • Tools/: External binaries or dependencies used in lab workflows
  • LabSetup/: Optional lab preparation scripts
  • CleanUp/: Runtime output and exported artifacts

Requirements

Platform

  • Windows lab environment
  • PowerShell 7.1 or higher
  • Active Directory test domain (recommended for full scenario)

PowerShell Modules

  • ActiveDirectory
  • GroupPolicy

External Tools (depending on phase)

  • Certify.exe
  • Mimikatz.exe
  • Rubeus.exe
  • NetSess.exe
  • PsExec.exe

Note: Tool availability and security controls in your lab influence which actions are executed successfully.

Installation

Requirements for the initial AS2Go lab configuration

  • Single-domain Active Directory environment
  • At least one Domain Controller (DC)
  • At least one domain-joined victim machine, such as a server or workstation
  • Initial configuration should preferably be executed on the victim machine
  • Administrative privileges are required
  • Enterprise Admin privileges are recommended for full configuration

Option 1: Import from local folder

Import-Module <PathToModule>\AS2Go.psd1 -Force

Option 2: Install from PSGallery

Install-Module -Name AS2Go -Scope AllUsers -Force
Import-Module AS2Go -Force

Quick Start

Start the demo workflow

Start-AS2GoDemo

Useful startup switches

# Setup the lab
Initialize-AS2GoLabConfiguration

# Run a Password Spray
Invoke-ASPhase04BruteForceAttack

# Phase Privilege Escalation
Invoke-ASPhase07PrivilegeEscalation

# Last phase Domain Compromise and Persistence
Invoke-ASPhase12DomainCompromisePersistence

# Troubleshooting friendly output
ASP12 -EnableLogging -SkipImages -SkipClearHost

Typical Training Flow

  1. Prepare a fresh lab snapshot.
  2. Start AS2Go and run one phase at a time.
  3. Observe telemetry in Defender/Sentinel/SIEM.
  4. Validate detections and enrich incident playbooks.
  5. Reset lab and repeat with different switches.

Public Commands (Examples)

  • Start-AS2GoDemo
  • Invoke-ASPhase04BruteForceAttack
  • Invoke-ASPhase06Reconnaissance
  • Invoke-ASPhase07PrivilegeEscalation
  • Invoke-ASPhase09ReconnaissancePriviledged
  • Invoke-ASPhase10AccessSensitiveData
  • Invoke-ASPhase11ExfiltrateSensitiveData
  • Invoke-ASPhase12DomainCompromisePersistence

Use Get-Help for command documentation:

Get-Help Start-AS2GoDemo -Full
Get-Help Invoke-ASPhase12DomainCompromisePersistence -Full

Logging and Artifacts

AS2Go can produce logs and temporary output files for review and cleanup.

  • Use -EnableLogging for verbose execution logging.
  • Review generated files in your configured cleanup/output folders.
  • Archive artifacts for training evidence and detection tuning history.

Recommended Safety Practices

  • Use isolated virtual networks only.
  • Use non-production accounts and data only.
  • Snapshot systems before each run.
  • Restrict internet egress in the lab if possible.
  • Document each run (phase, time, expected alerts, observed alerts).

Roadmap Ideas

  • Additional simulation profiles for different defender maturity levels
  • Built-in reporting templates for SOC training outcomes
  • Extended cloud/hybrid identity telemetry mappings

Contributing

Issues and pull requests are welcome. If you share improvements, include:

  • Lab assumptions
  • Reproduction steps
  • Expected vs. observed behavior
  • Sample logs/screenshots (sanitized)

Acknowledgments

Thanks to the security community and tool authors whose research and utilities support realistic defensive training labs.

About

AS2Go is an acronym for Attack Scenario To Go. AS2Go is written in PowerShell and goes along the cyber kill chain, with stops at Password Spray, Reconnaissance, Privilege Escalation, Sensitive Data Access & Exfiltration and Domain Compromise.

Resources

License

Stars

Watchers

Forks

Contributors