- Write-ups
- Enterprise Security Operations and Vulnerability Management Simulation

Enterprise Security Operations and Vulnerability Management Simulation
Security lab simulating an enterprise network with isolated VLANs, Active Directory, Windows/Linux endpoints, Wazuh SIEM/XDR, OpenVAS scanning, vulnerable web apps, and Ansible automation.
Contents
Contents
A hands-on cybersecurity homelab that simulates how a small enterprise is built, monitored, tested, and improved.
Project at a glance
This project is an enterprise-style security laboratory built on a single Proxmox VE hypervisor. It combines network segmentation, representative identity services, Windows and Linux endpoints, Wazuh SIEM/XDR, Greenbone/OpenVAS vulnerability management, vulnerable web applications, and Ansible automation.
Active Directory is included as the lab's simulated enterprise identity service, not as the sole focus of the project. It provides realistic users, computers, authentication, DNS, and policy relationships so that security operations can be tested in an environment that behaves more like a real organization.
The lab is designed to answer a practical question:
Can I identify a weakness, understand its risk, detect related activity, remediate the issue, and verify that the control works?
Rather than treating each platform as a standalone installation, the project focuses on the complete security operations lifecycle. Systems are configured, tested against authorized targets, monitored, investigated, hardened, and rescanned.
This project is a self-built enterprise-style cybersecurity laboratory designed to simulate how corporate infrastructure is secured, monitored, tested, and maintained.
Built on Proxmox VE, the environment integrates pfSense, Windows Active Directory, Windows and Linux endpoints, Wazuh SIEM/XDR, OpenVAS vulnerability assessment, and Ansible automation.
The primary objective is to understand how these technologies work together in a practical security operations environment—from identifying vulnerabilities and monitoring endpoint activity to investigating alerts, prioritizing risk, applying changes, and validating remediation.
The lab deliberately models the relationships found in a real organization: users access services, endpoints generate telemetry, infrastructure exposes attack surface, security teams investigate findings, and administrators apply and verify corrective actions. The goal is to study those interactions rather than simply install individual products.
01 — Enterprise Infrastructure & Network Architecture
The lab runs on a single Proxmox VE hypervisor and uses pfSense to provide routing and network isolation between the upstream network and the internal laboratory environment.
Network Overview
## Lab Infrastructure Configuration
```text
Component | Configuration
----------------------------|------------------------
Virtualization | Proxmox VE 9.2.21
Firewall / Router | pfSense
WAN | 192.168.254.119
LAN Gateway | 10.0.20.1
Internal Subnet | 10.0.20.0/24
Domain Controller | w25-server-1
Domain Controller IP | 10.0.20.3
Active Directory Domain | ad.securitylab.test
Wazuh Manager | 10.0.20.12
OpenVAS / Greenbone Scanner | 10.0.20.11
```Infrastructure Layers
- Network Security — pfSense controls routing, firewall policies, and access between the upstream network and internal lab systems.
- Identity & Access — Windows Server 2025 provides a representative Active Directory environment with centralized authentication, DNS, and Group Policy capabilities.
- Endpoint Infrastructure — Windows 11 workstations and Linux servers represent the organization's users, servers, and workloads.
- Security Operations — Wazuh provides centralized security monitoring, while OpenVAS identifies potential vulnerabilities across the environment.
- Automation — Ansible supports repeatable configuration management and remediation tasks.
The internal network is designed as a controlled security environment for testing, monitoring, and investigation.
02 — Enterprise Identity & Directory Services
The Windows environment uses the domain controller w25-server-1, running Windows Server 2025, to simulate the identity layer of a small enterprise.
Domain: ad.securitylab.test
Kerberos Realm: AD.SECURITYLAB.TEST
Active Directory provides a realistic directory model for managing user accounts, computer accounts, authentication, DNS, and organizational policies. It is one supporting component of the wider simulation, alongside networking, endpoints, applications, monitoring, vulnerability assessment, and automation.
The directory structure uses dedicated Organizational Units:
Lab-ServersLab-WorkstationsLab-UsersLab-Groups
Windows 11 workstations are integrated into the domain, while Linux servers are being configured for centralized authentication through Kerberos and SSSD.
This component provides realistic identity and endpoint relationships for studying authentication failures, administrative delegation, suspicious activity, and the effect of security events across the wider environment.
03 — Wazuh SIEM/XDR: Security Monitoring & Detection
Wazuh is the central security monitoring platform in this lab. Its purpose is to provide visibility across Windows and Linux systems and help investigate suspicious activity from a centralized interface.
Wazuh Manager: 10.0.20.12
What Wazuh monitors
Endpoint agents collect and forward configured security telemetry to the Wazuh Manager. Depending on the operating system and enabled modules, this can include:
- Windows Security Events — authentication successes and failures, account changes, privilege-related events, and other Windows security activity.
- Linux System Logs — authentication attempts, SSH activity, service events, and system messages.
- File Integrity Monitoring — changes to selected files and directories that may indicate unauthorized modifications.
- System Inventory — information about installed software, operating systems, and other inventory data.
- Security Configuration Assessment — checks against selected security configuration policies.
- Threat Detection — rule-based alerts generated from collected events and enabled security integrations.
The goal is to build visibility across the domain controller, workstations, and Linux application servers instead of investigating each endpoint independently.
Practical Wazuh use cases
Identity and Windows monitoring
Investigate failed logons, unusual authentication patterns, account creation, group membership changes, and other events relevant to identity and Windows security.
Linux authentication monitoring
Review SSH login failures, repeated authentication attempts, suspicious account activity, and changes to important system files.
Web application monitoring
Collect relevant application and system logs from Juice Shop and DVWA hosts. Correlate suspicious HTTP requests with operating-system events where the available telemetry supports that investigation.
Detection engineering
Develop and test custom rules, tune alert thresholds, and validate detections using controlled simulations. The objective is to understand which events are collected, what triggers an alert, and how to distinguish suspicious behavior from normal administration.
Wazuh investigation workflow
- · Observe Collect endpoint logs and security telemetry.
- · Detect Use Wazuh rules and configured security modules to identify potentially suspicious activity.
- · Investigate Review the alert, affected host, timestamps, event details, and related activity.
- · Correlate Compare relevant events across Windows, Linux, identity infrastructure, and application logs.
- · Respond Determine whether containment, account changes, configuration adjustments, or other corrective actions are appropriate.
- · Validate Repeat the controlled test or review subsequent telemetry to confirm that the issue has been addressed.
The emphasis is on the complete detection lifecycle—not simply generating alerts, but understanding why they occurred and what action should follow.
04 — OpenVAS / Greenbone: Vulnerability Assessment & Management
OpenVAS, within the Greenbone vulnerability management ecosystem, is used to assess systems for potential security weaknesses.
OpenVas Scanner: 10.0.20.12
Wazuh Manager: 10.0.20.11
The objective is to identify, validate, prioritize, and remediate vulnerabilities across the internal lab network.
How vulnerability assessment is used
Asset discovery and selection
Identify the intended scan targets, including Windows endpoints, Linux servers, and intentionally vulnerable applications.
Vulnerability scanning
Run appropriate authenticated or unauthenticated scans. Credentialed scans can provide deeper visibility into operating-system and installed-software weaknesses when the required credentials and permissions are configured correctly.
Finding analysis
Review reported vulnerabilities, affected services, available evidence, severity, and remediation guidance. Scanner findings should be validated rather than automatically assumed to represent exploitable weaknesses.
Risk prioritization
Prioritize findings using severity, exposure, asset importance, exploitability, and business context. Critical findings warrant prompt investigation, but the highest numerical score is not the only factor in remediation decisions.
Remediation
Apply security patches, update vulnerable packages, correct configurations, disable unnecessary services, or restrict network exposure as appropriate.
Rescanning
Repeat the assessment to verify whether the identified findings have been resolved or remain outstanding.
OpenVAS vulnerability management workflow
01 · Discover Identify assets and select systems within the authorized scan scope.
02 · Assess Scan for known vulnerabilities, exposed services, and potential configuration weaknesses.
03 · Prioritize Review severity, evidence, exposure, and the operational importance of affected systems.
04 · Remediate Patch software, harden configurations, or reduce unnecessary exposure.
05 · Verify Rescan the affected systems and compare the results with the original findings.
06 · Report Document resolved findings, outstanding risks, and recommended next actions.
This workflow demonstrates that vulnerability management is a continuous process, not a one-time scan or a list of severity scores.
05 — Connecting OpenVAS and Wazuh
The most valuable aspect of the lab is the relationship between vulnerability management and security monitoring.
OpenVAS and Wazuh serve different but complementary purposes:
## OpenVAS / Greenbone vs. Wazuh
```text
OpenVAS / Greenbone | Wazuh
--------------------------------------------|--------------------------------------------
Identifies potential vulnerabilities | Monitors endpoint security telemetry
Evaluates exposed services and known | Detects suspicious activity using configured
weaknesses | rules and integrations
Produces vulnerability assessment findings | Produces security alerts and investigation
| context
Supports remediation prioritization | Supports monitoring, detection, and
| investigation
Uses rescanning to verify remediation | Uses subsequent telemetry and controlled
| tests to evaluate detection
```A vulnerability finding does not automatically become a Wazuh alert. Each platform uses different data sources and detection mechanisms. Their results can be compared and correlated through shared asset information, timestamps, hostnames, and investigation records.
The integrated security operations lifecycle
Discover assets → Assess vulnerabilities → Prioritize risk → Apply remediation → Verify fixes → Monitor endpoints → Investigate alerts → Improve controls
This lifecycle connects preventive security activities with ongoing detection and response.
For example, if a scan identifies an outdated service on a Linux server, the finding can be investigated and prioritized. The service can then be patched or hardened, and OpenVAS can rescan the host to validate the change. Wazuh can provide additional visibility into relevant system events and help investigate suspicious activity involving that host.
The result is a more complete view of security posture: identifying weaknesses, correcting them, and monitoring the environment afterward.
06 — Controlled Security Testing & Detection Engineering
The lab includes intentionally vulnerable applications, enterprise identity services, and supporting infrastructure for authorized security testing. These scenarios are designed to represent activity that a security team might investigate across multiple systems, not only within Active Directory.
Identity and infrastructure scenarios
Potential scenarios include password spraying, Kerberoasting, privilege escalation, lateral movement, suspicious account changes, and unauthorized Group Policy modifications.
Each exercise focuses on three questions:
- What activity was generated?
- Which logs and telemetry captured it?
- Did the configured monitoring rules detect it accurately?
The aim is to evaluate detection coverage, identify telemetry gaps, and improve monitoring through controlled testing.
Web application security scenarios
The application security environment includes:
- OWASP Juice Shop
- Damn Vulnerable Web Application (DVWA)
These applications support controlled testing of SQL injection, cross-site scripting, command injection, insecure file uploads, broken access control, and authentication weaknesses.
Relevant application logs and endpoint telemetry can then be reviewed in Wazuh to investigate how application-layer activity appears in the wider system.
All attack simulations are conducted against the lab's authorized targets.
07 — Ansible & Remediation Automation
Ansible is incorporated as the automation layer for repeatable system administration and security remediation across the simulated environment.
Potential automation tasks include:
- Applying operating-system security updates
- Standardizing Linux configurations
- Disabling unnecessary services
- Deploying and configuring monitoring agents
- Applying approved hardening settings
- Performing repeatable remediation tasks across multiple hosts
Automation helps reduce manual effort and supports consistency across the Linux server fleet.
---
- name: Update System Packages safely across Ubuntu, RHEL, Fedora, and AlmaLinux
hosts: all
become: true
gather_facts: true
tasks:
# ==========================================
# DEBIAN / UBUNTU FLAVORS
# ==========================================
- name: Handle Debian/Ubuntu Updates
block:
- name: Update apt cache and upgrade all packages safely
ansible.builtin.apt:
update_cache: true
upgrade: dist
autoremove: true
purge: true
register: apt_update_result
- name: Check if a reboot is required (Debian/Ubuntu)
ansible.builtin.stat:
path: /var/run/reboot-required
register: debian_reboot_needed
when: ansible_os_family == "Debian"
# ==========================================
# REDHAT / RHEL / FEDORA / ALMA FLAVORS
# ==========================================
- name: Handle RedHat/Fedora/AlmaLinux Updates
block:
- name: Upgrade all packages via DNF (Modern RedHat ecosystem)
ansible.builtin.dnf:
name: "*"
state: latest
update_cache: true
register: dnf_update_result
# Best Practice: Uses local package tools to see if a reboot is actually needed
- name: Check if a reboot is required (RedHat ecosystem)
ansible.builtin.command: needs-restarting -r
register: redhat_reboot_needed
failed_when: false
changed_when: false
when: ansible_os_family == "RedHat"
# ==========================================
# CONDITIONAL REBOOT PHASE
# ==========================================
- name: Reboot the server safely if updates require it
ansible.builtin.reboot:
msg: "Reboot initiated by Ansible due to critical package updates"
reboot_timeout: 300
when: >
(ansible_os_family == "Debian" and debian_reboot_needed.stat.exists) or
(ansible_os_family == "RedHat" and redhat_reboot_needed.rc == 1)The sample operating-system update playbook demonstrates this approach by applying package updates across Debian- and Red Hat-based systems, checking whether a reboot is required, and rebooting only when necessary.
A future extension of the lab is to connect vulnerability findings to a controlled remediation workflow, with approval and verification steps before changes are considered complete.
08 — Project Outcomes & Skills Demonstrated
This project brings together infrastructure engineering and defensive cybersecurity in a practical, evolving environment.
Infrastructure & Networking
- Proxmox virtualization
- pfSense firewall configuration
- Network addressing, routing, and segmentation
Identity & Access Management
- Enterprise identity and Active Directory administration
- DNS and Kerberos troubleshooting
- Windows and Linux identity integration
- Group Policy and access-control concepts
Security Operations
- Wazuh agent deployment and centralized monitoring
- Windows and Linux log analysis
- Alert investigation and detection engineering
- Security telemetry correlation
Vulnerability Management
- OpenVAS / Greenbone scanning
- Finding validation and risk prioritization
- Patch remediation and configuration hardening
- Rescanning and remediation verification
Automation & Application Security
- Ansible configuration management
- Controlled web application security testing
- Repeatable testing and remediation workflows
Conclusion
This homelab is designed to demonstrate how enterprise security technologies can work together as a cohesive operational environment.
By integrating identity services, pfSense, Wazuh, OpenVAS, Linux infrastructure, vulnerable web applications, and Ansible, the project provides a practical foundation for exploring how enterprise systems operate together across security monitoring, vulnerability management, identity security, and remediation.
The central objective is to move beyond installing individual tools and simulate the complete security lifecycle:
Identify weaknesses. Understand the risk. Detect suspicious activity. Investigate the evidence. Remediate the problem. Verify the result.
As the environment evolves, additional detection rules, documented scan results, investigation reports, and automated remediation playbooks will provide measurable evidence of the lab's capabilities.



