Skip to content

About

Building infrastructure for the Orion Project

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

2 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 

Repository files navigation

ORION — Infrastructure Deployment & Provisioning

FOR EDUCATIONAL AND AUTHORIZED CYBERSECURITY TRAINING PURPOSES ONLY

1. Project Overview

Orion Infrastructure Deployment & Provisioning is an infrastructure automation project developed as part of the Orion cybersecurity training initiative.

Its purpose is to automatically deploy and configure a complete simulated hospital IT infrastructure starting from two basic machines:

  • One Windows Server instance.
  • One Linux server instance.

Through two automation scripts, the project provisions the infrastructure, deploys the required services, configures network segmentation, initializes the Active Directory environment, and prepares centralized security monitoring.

The resulting infrastructure reproduces the architecture of a hospital information system, providing a realistic environment for cybersecurity exercises, defensive security training, incident response simulations, and SIEM-based investigations.

The deployment is designed to minimize manual configuration and ensure that the training environment can be reproduced consistently.

2. Project Objectives

The main objectives are:

  • Automate the deployment of a complete simulated hospital infrastructure.
  • Provision and populate an Active Directory environment.
  • Deploy containerized applications and supporting databases.
  • Deploy a containerized ELK monitoring stack.
  • Configure centralized log collection and forwarding.
  • Implement network segmentation and firewall policies.
  • Deploy endpoint and infrastructure monitoring agents.
  • Provide a reproducible environment for cybersecurity exercises.
  • Reduce the time required to rebuild the training infrastructure.

3. Infrastructure Architecture

The deployment relies on two primary hosts, each responsible for a different part of the infrastructure.

3.1 Windows Server

The Windows Server acts as the foundation for the identity and directory services.

It hosts:

  • Active Directory Domain Services.
  • The simulated hospital domain.
  • Organizational Units (OUs).
  • User accounts and groups.
  • Exercise-related directory objects.
  • Winlogbeat for Windows event collection.

The Active Directory environment is automatically populated with the objects and accounts required by the Orion exercise.

Winlogbeat collects Windows event logs and forwards them to the centralized ELK stack hosted on the Linux infrastructure.

3.2 Linux Server

The Linux server hosts the containerized hospital infrastructure and centralized monitoring services.

It includes:

  • Containerized ELK stack.
  • Containerized OpenEMR.
  • Containerized Kimai.
  • Associated application databases.
  • Firewall and network segmentation rules.
  • Filebeat for host-side and application log collection.

The Linux server acts as the main application and monitoring platform.

4. Deployed Services

4.1 Centralized Monitoring — ELK Stack

The project deploys a containerized ELK stack to centralize and analyze logs generated throughout the simulated infrastructure.

The stack provides the foundation for:

  • Log ingestion.
  • Log storage and indexing.
  • Event investigation.
  • Infrastructure monitoring.
  • Security event analysis.
  • Exercise-related detection and correlation.

The stack is preconfigured to receive telemetry from the Linux and Windows environments.

4.2 OpenEMR

OpenEMR is deployed as a containerized application with its associated database.

It represents the hospital's Electronic Medical Record (EMR) platform.

Within the Orion exercise, it serves as a simulated healthcare application and generates application-level telemetry for security monitoring.

4.3 Kimai

Kimai is deployed as a containerized application with its associated database.

It represents an administrative and time-tracking platform within the simulated hospital infrastructure.

Its application activity contributes to the overall synthetic activity generated during the exercise.

4.4 Databases

The databases required by OpenEMR and Kimai are deployed alongside their respective applications.

This ensures that the applications operate within a self-contained environment and that their data persistence requirements are handled by the deployment.

4.5 Firewall and Network Segmentation

The deployment includes firewall configuration designed to control communication between infrastructure components.

One of the main objectives is to isolate the DMZ from the internal network as much as possible.

The firewall rules establish controlled communication paths between the application environment, internal services, and monitoring infrastructure.

This segmentation helps reproduce the security boundaries commonly found in enterprise and healthcare environments.

4.6 Filebeat — Linux Log Collection

Filebeat is deployed on the Linux host to collect logs generated by the containerized applications and the host environment.

It forwards the collected events to the preconfigured ELK stack.

This provides centralized visibility into application and infrastructure activity.

4.7 Winlogbeat — Windows Log Collection

Winlogbeat is configured on the Windows Server to collect Windows event logs.

Its purpose is to forward relevant Windows telemetry to the ELK stack.

This enables centralized investigation of:

  • Windows authentication events.
  • Active Directory-related events.
  • System events.
  • Security events.
  • Other configured Windows event channels.

5. Automation Scripts

The project consists of two main deployment scripts.

5.1 build_AD.ps1

Platform: Windows Server
Language: PowerShell
Purpose: Active Directory provisioning and Windows log collection setup.

This script automatically builds and configures the Active Directory environment required by the Orion exercise.

Its responsibilities include:

  • Initial Active Directory provisioning.
  • Domain configuration.
  • Organizational Unit creation.
  • User and group provisioning.
  • Creation of exercise-related directory objects.
  • Configuration of the simulated hospital identity environment.
  • Winlogbeat deployment and configuration.

The script transforms a basic Windows Server installation into the directory services platform required by the exercise.

It also prepares Windows event collection to ensure that relevant system and security telemetry is forwarded to the centralized monitoring infrastructure.

5.2 build_containers.sh

Platform: Linux
Language: Shell / Bash
Purpose: Application infrastructure, monitoring deployment, and network configuration.

This script automatically deploys and configures the containerized infrastructure hosted on the Linux server.

Its responsibilities include:

  • Deployment of the containerized ELK stack.
  • Deployment of OpenEMR.
  • Deployment of Kimai.
  • Deployment and configuration of application databases.
  • Configuration of container networking.
  • Application of firewall rules.
  • Network segmentation and DMZ isolation.
  • Filebeat deployment and configuration.
  • Configuration of log forwarding to the ELK stack.

The script transforms a basic Linux installation into the application and monitoring platform of the simulated hospital.

6. Log Collection Architecture

A major objective of the deployment is to provide centralized visibility across the entire simulated infrastructure.

Two collection mechanisms are deployed.

Source Collector Destination
Windows Server Winlogbeat ELK Stack
Active Directory Winlogbeat ELK Stack
Linux Host Filebeat ELK Stack
OpenEMR Filebeat ELK Stack
Kimai Filebeat ELK Stack
Container infrastructure Filebeat ELK Stack

This architecture enables the SOC training environment to correlate events from different operating systems, applications, and infrastructure components.

The resulting telemetry supports realistic security monitoring and incident investigation scenarios.

7. Deployment Model

The deployment follows a two-stage provisioning process.

Stage 1 — Windows Infrastructure

The Windows Server is initialized and configured using build_AD.ps1.

This stage establishes the Active Directory environment and prepares Windows event collection.

Stage 2 — Linux Infrastructure

The Linux server is initialized and configured using build_containers.sh.

This stage deploys the containerized applications, ELK stack, firewall configuration, and Linux log collection.

Final Result

The two environments operate together as a simulated hospital information system, with centralized logging and monitoring.

8. Security Considerations

Because this infrastructure reproduces a healthcare environment, deployment must follow strict security principles.

The infrastructure is intended exclusively for controlled cybersecurity exercises.

Recommended safeguards include:

  • Use dedicated virtual machines or isolated laboratory hosts.
  • Use synthetic identities and test data.
  • Never populate the environment with real patient information.
  • Restrict access to management interfaces.
  • Review firewall rules before exposing any service.
  • Protect Active Directory administrative credentials.
  • Ensure that the ELK stack is accessible only through authorized network paths.
  • Keep container images and dependencies updated.
  • Avoid direct exposure of the training infrastructure to the public Internet.

The deployment must not be considered a production-ready hospital infrastructure without a separate security assessment and hardening process.

9. Educational Disclaimer

FOR EDUCATIONAL PURPOSES ONLY

This project is part of the Orion cybersecurity training initiative.

It is developed exclusively for educational, academic, research, and authorized cybersecurity training purposes.

Its objective is to provide a reproducible simulated hospital infrastructure for defensive security exercises, monitoring validation, and incident response training.

Users must ensure that:

  • They have authorization to deploy and operate the infrastructure.
  • All deployed systems belong to the designated training environment.
  • No real patient data or unauthorized personal information is used.
  • Firewall and network configurations are reviewed before deployment.
  • All activities comply with applicable laws and institutional policies.

The authors and contributors do not encourage or support unauthorized deployment or use.

The authors and contributors disclaim responsibility for unauthorized or unlawful use, to the extent permitted by applicable law.

10. License

This project is distributed under the MIT License.

Copyright (c) 2026 Christophe SUBLET, Grenoble INP - Esisar, UGA, CyberSkills@UGA

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

See the LICENSE file for the complete license text.

11. Project Attribution

Project: Orion
Component: Infrastructure Deployment & Provisioning
Category: Infrastructure Automation / Cybersecurity Training
Windows Automation: PowerShell
Linux Automation: Bash
Containerization: Docker
Monitoring: Elasticsearch / Logstash / Kibana / Beats
Applications: OpenEMR / Kimai
Directory Services: Active Directory
License: MIT


ORION — INFRASTRUCTURE DEPLOYMENT & PROVISIONING

Automating the deployment of a realistic hospital infrastructure for cybersecurity training, defensive monitoring, and incident response exercises.

FOR EDUCATIONAL AND AUTHORIZED CYBERSECURITY TRAINING PURPOSES ONLY.

About

Building infrastructure for the Orion Project

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages