Windows Automation Playbook
Slide 1 of 12
SimpleSense.io · Michael Krawczyk
Windows Automation
Playbook
An iterative approach to building consistency, scalability, and security across Windows infrastructure — from 72,454 vulnerabilities to a structured, measurable framework.
12
Slides
72,454
Vulns at Start
93%
Patch Compliance
5
Core Pillars
01 Project Overview Introduction
01
Inherited Unmanaged Console
02
Established Security Baselines
03
Prioritized Critical Remediation
04
Developed Remediation Scripts
05
Validated Automation Results
02 Windows Automation Architecture
🗂
Scalable Group Structures
DxeDot S1 Deployment · Siem Log Shipper · Vulnerability Management · CX Compliance
📋
Centralized Script Repository
CVE-2021-26875 · CVE-2022-24474 · CVE-2022-37986 · CVE-2022-41058
⚙️
Automated Remediation Workflows
Peer Review → First Review & Approval → Controlled Testing
📊
Consistent Policy Enforcement
Total Remediation Totals — Down 109, Down 29, Down 6282…
03 IaC & Provisioning Infrastructure
1
Automated Group Provisioning
Automated assignment of agents and clients to the correct group hierarchy.
2
Security Baselines & Windows Patching
Standardized patch policies and CIS-aligned security configurations across all systems.
3
Version Control
Script changes tracked with peer review and approval gates before deployment.
4
Controlled Provisioning
Scheduled, role-based execution ensuring consistent and predictable deployment outcomes.
04 Automated Group Provisioning Configuration
🏢 Client Level
Habitat PatchMatic
Habitat MS Safety Scans
Habitat Local Administrators Group Monitor
Habitat Windows Backup
Habitat Windows Registry
Red Flag
✅ Production — Vuln Scanning and Maint.
☐ Onboarding — Vuln Scanning
📍 Location Level
Dallas Data Center · LocationID: 678
Habitat Wifi Scanner
Default: eDot Contract Client · eDot Custom Patching
☐ Exclude From Vul Scanning
☐ Update Java
✅ Remove Java
☐ Vuln Scanning
🤖 Agent Level
Dallas Data Center / 11L2258
Idle Time: Active
eDot Vulnerability Management
Do not remove JAVA
☐ Exclude From Vul Scanning
Custom Patching
Patch Management
05 Configuration Enforcement Implementation
📁 Provisioning
Established the folder hierarchy and logical group structure. Each group tier inherits the correct baseline policies and script schedules.
⚙️ Implementation
Built on that foundation by using fixed schedules and role-based hierarchy. Scripts are targeted precisely using group inheritance and subgroup inclusion.
📂 Script Repository — 28 Scripts
📁 vulnerability-mitigation /
📁 CVE Remediations /
🔧 Microsoft
🔧 No Reboot Required CVE Remediations
🔧 Third party applications
📁 eDot Generally Useful
📁 FSRM Crypto/Ransomware Protection
📁 Examples / Zabbix/Grafana
📁 _00 - Old Scripts
06 Windows Patching Compliance
93%
Overall Compliance
225
Daytime Patching
332
Pending Reboot
13
WSUS Enabled
Severity Compliance
100%
Critical
98%
Important
99%
Moderate
100%
Low
96%
Unspecified
CVSS Compliance
100%
High
100%
Medium
97%
Low
07 Established a Secure Baseline Vulnerability Management
72,454
Starting Vulnerabilities
March 2024 Patch Progress
Total (excl. Offline >30d)1995
% of Online Devices Patched68%
Installed1302
Missing649
Offline >30 Days139
End of Life OS11
Grand Total2323
January 2025 Patch Status
Grand Total2435
Jan Online Devices Patched93%
🔴Starting Point: 72,454 Vulnerabilities Identified. The environment lacked documented standards or structure.
Immediate stabilization was critical. No existing remediation processes or baseline policies were in place.
🪟Windows Patching was baselined together to ensure stable, accurate vulnerability data going forward.
📋
Multi-client vulnerability data (7/9/2024):
Chicago Sinak · DuPage Senior · Friedman Seating · Robber Inc
Total vulns spanned Critical / High / Medium / Low / Unknown
08 Script Lifecycle & Version Control Process
📋
Step 1
Define Requirements
💻
Step 2
Develop & Document
👥
Step 3
Peer Review & Approval
🧪
Step 4
Controlled Testing
🔒
Step 5
Critical Software Validation
Step 6
Final Review & Approval
🚀
Step 7
Staggered Deployment
📡
Step 8
Post-Deployment Monitoring
09 Controlled Provisioning Automation
🕐
Fixed-Schedule Execution Provisioning scripts run on fixed schedules to ensure consistent execution across all endpoints.
🔒
CIS-Compliant Automation Automation maintains CIS-compliant configurations across all maintenance-phase systems.
// Scheduled Script Example — Microsoft CVE Remediations
CVE-2023-28260 .NET DLL Hijacking 17:30:22 Mon, Wed, Fri
CVE-2022-41058 W7 Denial… 18:00:00 Daily
CVE-2022-37986 Elevation of P… 08:15:00 Weekly
Schedule Options
● Once ○ Minute ○ Hourly ○ Daily ○ Weekly ○ Monthly
10 Cybersecurity Considerations Analysis
🔍 Identified data integrity issues in ASIO vulnerability scans producing inaccurate results.
🔄 Cross-validated ASIO findings with Automate console data and manual checks for accuracy.
📈 Analyzed 60-day trending drift (Sept–Oct baselines) to assess true client security posture.
Vulnerability Trend · Jan → Nov (Sum by Severity)
Jan
Feb
Jul
Aug
Sep
Oct
Nov
Unknown
Low
Medium
High
Critical
11 Collaboration and Coordination Cross-Team
1
Identified scanner drift and data discrepancies between ASIO and Automate.
2
Initiated cross-team communication to validate and correct results.
3
Documented findings and escalations to ensure visibility and accountability.
4
Turned isolation into structured collaboration through transparency and follow-up.
12 Outcomes & Challenges Results
🏚️
Inherited an outdated RMM console and inconsistent ASIO scan data, requiring complete overhaul and manual validation.
💪
Operated with minimal direction and vendor support, driving progress independently through self-audits and persistence.
🤖
Developed structured remediation processes, automating validated fixes and improving data integrity across all clients.
🏆
Transformed a disorganized, failing program into a consistent, measurable vulnerability management framework.