About This File
===============================================================================
WinIDS v4.1 Deployment Framework - Standalone Sensor Install Guide
Copyright © 2026 WinSnort.com | Michael Steele
===============================================================================OPERATIONAL OVERVIEW
This package contains a specialized deployment framework for the Windows Intrusion Detection System (WinIDS). It is engineered for high-performance installations on Windows 10/11 and Windows Server (2016-2025) 64-bit.
-------------------------------------------------------------------------------
PHASE I: PRE-DEPLOYMENT SPECIFICATIONS
-------------------------------------------------------------------------------
* Target Environment : Optimized for clean OS installations. * Archive Integrity : Extract all package contents to a dedicated directory. * Archive Security : w1nsn03t.c0m-------------------------------------------------------------------------------
PHASE II: STANDALONE SENSOR DEPLOYMENT
-------------------------------------------------------------------------------
Locate the config.conf file in the local extraction directory on the Host.
Open it with a text editor (such as Notepad) and configure the following variables:
$TempDir = "" # Path for temporary installation/download files (e.g., "D:\files") $WinIDSRoot = "" # Primary home directory for WinIDS installation (e.g., "D:\home") $Oinkcode = "" # Your 40-character Snort.org Oinkcode for rule updates $SensorName = "" # A unique name for this Host Sensor (e.g., "HostName") $EnableAllRules = $true # Set to $false to disable rule testing and high-volume logging $EnableRestorePoint = $true # Set to $false to skip System Restore point creation $SnortUser = "snort" # Master Host ALERT Database Username $SnortPass = "l0gg3r" # Master Host ALERT Database Password $RootUser = "root" # Master Host (Root) MySQL/PostgreSQL Database Username $RootPass = "d1ngd0ng" # Master Host (Root) MySQL/PostgreSQL Database PasswordSave all changes to config.conf and close the editor.
Right-click Installer.exe and select "Run as Administrator" to begin the installation.
-------------------------------------------------------------------------------
PHASE III: PARAMETER CONFIGURATION
-------------------------------------------------------------------------------
SECURITY RECOMMENDATIONS
The Username and password values above are defaults. For production environments, it is strongly advised to update these credentials to enhance network security but if there is any doubt, leave them as is.
DATABASE Roles
The SnortUser/Pass credentials are used by Barnyard2 to authenticate with the ALERT database. These credentials also facilitate the connection between remote nodes and the Master Host across the LAN/WAN.
The RootUser/Pass credentials are administrative and used for command-line database management post-installation and also used for the Database manager utility.
DOCUMENTATION
Use caution when modifying default settings. Ensure all changes are recorded for future administrative reference.
DEPLOYMENT DURATION ESTIMATES
Completion times vary based on the selected database engine and host operating system. The following estimates are based on standard network throughput and hardware resource availability. Workstation standalone or node deployments generally complete in ~15 minutes. Server host deployments generally complete in ~40 minutes. Performance is directly influenced by available system resources and network bandwidth.
RECOVERY AND RESILIENCY LOGIC
The WinIDS framework is designed with automated resume capability. In the event of a package acquisition failure, you will need to manually download the required asset to your defined $TempDir and re-initialize the installer. The framework will automatically detect the local file and resume the deployment. Do not terminate the installer during active system modifications or registry updates to prevent system corruption.
SYSTEM RESTORE OPERATIONS
In workstation environments, when EnableRestorePoint is active, the installer generates a system restore point prior to setup. This process initializes the required snapshot services, clears existing restore points, and creates a fresh baseline snapshot before cycling the services back to manual. This specific sequence ensures the "first-run" pre-installation snapshot remains protected from automatic purging.
If a valid "first-run" snapshot is already present—often the result of a previous removal via the RestorePoint utility—the installer will bypass the creation step to preserve the original baseline for the new installation.
SYSTEM RECOVERY PROCESS
The RestorePoint utility relies on the initial "first-run" snapshot to execute a rollback. If this snapshot is detected, the utility will revert the system to its original pre-installation state. However, if the snapshot is missing, the process will automatically terminate to prevent system instability.
Without a valid snapshot, a clean rollback cannot be performed. In this scenario, you must manually resolve the conflict, restore from a full system backup, or initiate a fresh installation. Note that while the recovery process leaves $WinIDSRoot and $TempDir untouched, performing a new installation will permanently delete all data within the $WinIDSRoot directory.
DATA INTEGRITY
The System Restore feature is intended for configuration recovery and is not a replacement for a comprehensive backup solution. System Restore services are set to manual and toggled as needed. Windows Restore Points are transient and may be purged during routine maintenance cycles if those services are running.
ENVIRONMENTAL CONSTRAINTS & BEST PRACTICES
Server Deployments: Since Windows Server architectures do not natively support System Restore points, this feature is automatically bypassed during Server OS deployments.
PULLEDPORK RULE MAINTENANCE
The original PulledPork by Shirkdog is housed within a sophisticated wrapper, accessible via the WinSnort Start Menu. While the utility is designed for "out-of-the-box" functionality with no manual configuration required, the wrapper offers a highly verbose interface with integrated system checks. Every update attempt is documented in the PulledPork log folder. To maintain system stability, the utility automatically rolls back to the last known-good rule set if an update fails.
The Rule Updater includes a built-in scheduler with configurable intervals ranging from 15 to 60 minutes. It supports automated retention of successful updates and SMTP email notifications. While "Silent Mode" is available for remote or unmanaged sensors, the updater will default to a verbose display if launched manually from the desktop while in "Silent Mode". If executed in silent mode without SMTP, the system continues to capture errors and failures within the local log files.
-------------------------------------------------------------------------------
PHASE IV: POST-DEPLOYMENT MANAGEMENT
-------------------------------------------------------------------------------
Upon successful completion, the WinIDS Management Suite will be accessible via Start Menu > WinSnort. Core utilities include:
* WinIDS Console : Real-time telemetry, event monitoring, and analysis. * Rules Updater : PulledPork-driven rule-set synchronization. * System Restore : System Restore Point (SRP) Utility (Workstation Only). * Database Utility : Database maintenance utility.Although a system reboot is not strictly mandatory, it is recommended to ensure all environment variables are refreshed. Please note that the WinSnort Start Menu group may not appear in the Start Menu until a system restart has been completed.
===============================================================================
TECHNICAL DOCUMENTATION & SUPPORT: http://winsnort.com===============================================================================