ICANEWS

Engineering & Technology

Windows Batch-Script Framework Cuts Endpoint Security Configuration Time in Large-Scale Deployment Case

WSPA automated recurring Windows security configuration tasks without additional management agents, reducing reported per-endpoint execution time from more than

Researcher 이찬우 (Lee Chanwoo), from 아주대학교 정보통신대학원 사이버보안전공 (Cyber Security, Graduate School of Information and Communication Technology, Ajou University), designed a lightweight automation framework called Windows Security Policy Automation (WSPA) to address this operational problem.

The study focused specifically on environments where centralized management infrastructure or additional endpoint agents may be restricted. Rather than proposing a new Windows security mechanism, WSPA combines existing Windows commands, system-management functions, and batch scripts into a standardized sequence for applying approved security configurations.

The framework was subsequently deployed to more than 5,000 Windows 10 and Windows 11 endpoints. In the operational range reported in the study, the time required to apply the relevant security measures to a single endpoint fell from more than 30 minutes under the manual process to less than 5 minutes using WSPA.

A Lightweight Alternative for Constrained Environments

Windows security configuration can be automated using technologies such as Group Policy, PowerShell, Microsoft Endpoint Configuration Manager, and Microsoft security-baseline tools.

These approaches provide advantages in areas such as centralized management, scalability, complex automation, and asset administration. However, their use can depend on infrastructure or operational conditions such as Active Directory, management servers, endpoint agents, or script-execution policies.

The study does not argue that batch scripts are universally superior to these technologies.

Instead, WSPA was positioned as a complementary option for environments in which additional management infrastructure is limited.

Its design requirements included compatibility with Windows 10 and Windows 11, minimal external dependencies, administrative privilege checks, consistent policy execution, result verification, and maintainability.

WSPA therefore relies on native Windows commands and batch-script execution rather than a separate commercial program or additional endpoint agent.

How WSPA Works

The system was designed around four main components:

  • an administrative execution component,
  • an environment verification component,
  • security-policy modules,
  • and a result-output component.

Before applying any security configuration, WSPA checks whether the script has administrative privileges and verifies the Windows operating-system version.

If the required execution conditions are not satisfied, the security actions are not initiated.

Once those checks are completed, WSPA executes the security-policy modules sequentially and then outputs the results and stores logs for later verification.

The system architecture presented in the study separates security controls into functional modules so that policy changes can be managed without treating the entire script as a single undifferentiated procedure.

What Security Measures Are Automated?

The study identifies several categories of endpoint security controls handled by WSPA.

For account policies, the framework can apply settings related to password length, password complexity, and password-change cycles.

For remote access, it can restrict Remote Desktop and other remote-management functions.

For firewall configuration, it applies Microsoft Defender Firewall activation and profile-related settings.

For shared resources, it restricts default shared folders and unnecessary sharing.

For stored credentials, WSPA includes procedures for removing saved credentials.

For service management, the framework can disable unnecessary services, including Remote Registry.

It also applies registry-based Windows security policies as part of the automated sequence.

The study does not disclose the detailed commands or specific policy values used in the operational deployment. It states that these were omitted for security reasons and that actual policy values may differ depending on organizational requirements.

From Manual Configuration to Scripted Execution

WSPA was implemented as a batch script executed through Windows Command Prompt using native Windows administrative commands.

The basic workflow is:

administrative privilege check → Windows version check → sequential execution of security-policy modules → result output → log storage.

The goal was not merely to execute commands faster, but also to encode the order of recurring administrative tasks into a repeatable procedure.

Before large-scale deployment, the study reports that functional checks were conducted on Windows 10 and Windows 11 systems. These checks examined whether the commands executed successfully, whether the intended policies were applied, and whether the changes could interfere with existing business functions.

However, the exact Windows build numbers and the number of repeated functional tests were not recorded in the underlying material presented in the paper. The study therefore identifies this as a limitation for reproducibility.

More Than 5,000 Endpoints Deployed

After testing on trial endpoints, WSPA underwent technical review by relevant departments and was gradually introduced into the operational environment.

The review considered:

  • whether the intended security policies were applied,
  • compatibility with Windows 10 and Windows 11,
  • and possible effects on existing business functions.

The deployment path and specific policy values were not disclosed for security reasons.

The framework was ultimately deployed to more than 5,000 Windows 10 and Windows 11 endpoints.

During operation, policy changes were incorporated through script modification and subsequent review.

A critical distinction in the study is that the figure of more than 5,000 endpoints refers to the scale of deployment. It does not mean that the study collected 5,000 independent experimental measurements.

Reported Configuration Time Fell From Over 30 Minutes to Under 5 Minutes

The operational evaluation focused on four areas:

  • the time required to apply the same security measures to one endpoint,
  • the ability to verify results for individual security items,
  • the potential to standardize the procedure,
  • and the scale of actual deployment.

According to the reported operational ranges, manually applying the security measures to one endpoint required more than 30 minutes.

With WSPA, the process from script execution through completion of item-level result output required less than 5 minutes.

Using the boundary values alone, the study calculates the minimum time reduction as:

\[ \frac{30-5}{30}\times100 = 83.3\% \]

The paper therefore reports a minimum 83.3% reduction in execution time based on the boundary values.

This percentage refers specifically to the time required to perform the security-configuration procedure. It does not represent an 83.3% improvement in security effectiveness or an 83.3% reduction in security incidents.

Why the 83.3% Figure Should Be Interpreted Carefully

The time measurements were not collected through a controlled repeated experiment with a standardized set of identical machines.

Instead, the study used operational range values that had been recorded or confirmed during field use.

The manual figure of “more than 30 minutes” included both applying each security setting and confirming the result. The WSPA figure of “less than 5 minutes” covered the period from script execution to completion of item-level output.

Hardware specifications and detailed operating-system builds were not held constant across all endpoints.

For this reason, the study did not calculate or report a mean execution time, standard deviation, confidence interval, or statistical significance test.

The 83.3% figure is therefore a conservative arithmetic comparison based on the reported range boundaries, rather than a statistically estimated average treatment effect.

Standardizing Procedure, Not Demonstrating Fewer Security Incidents

Encoding the security procedure into a script can reduce variation in the sequence in which administrators perform repetitive tasks.

The study consequently identifies procedural standardization as one of WSPA's operational advantages.

However, it did not measure before-and-after values for actual configuration omission rates or policy-compliance rates.

Nor did it analyze whether WSPA reduced security incidents, successful attacks, or endpoint compromise.

Raw execution logs were not used to calculate overall success rates, failure rates, variance, or other large-sample quantitative performance measures.

The findings should therefore be interpreted as evidence of field applicability, procedural standardization, and reduced execution time, not as causal evidence that the framework directly improves security outcomes.

WSPA Is Not Presented as a Replacement for GPO, PowerShell, or MECM

The study explicitly limits the scope of its conclusions.

Group Policy, PowerShell, MECM, and Microsoft security-baseline tools offer capabilities that a Windows batch-script framework does not necessarily provide, particularly in centralized management and more complex automation scenarios.

WSPA was therefore not proposed as a universal replacement.

Its practical contribution lies in showing how native Windows commands can be modularized into a lightweight security-configuration framework when additional centralized infrastructure or endpoint agents are difficult to use.

The study's contribution is thus less about inventing new Windows commands than about systematizing existing controls into a repeatable operational process and documenting a large-scale field deployment.

Important Limitations Remain

The paper identifies several limitations that restrict how broadly the results can be interpreted.

First, detailed Windows build numbers and the number of repeated measurements were not provided.

Second, the study did not analyze raw execution-time values, averages, variance, failure rates, or policy-compliance rates.

Third, there was no controlled comparison group and no long-term dataset on security incidents, making it impossible to estimate a causal security effect.

Fourth, organizational security policies differ, limiting the external validity of a framework whose detailed policy values must be adapted to individual environments.

The deployment results should therefore be understood as a case-based operational evaluation, rather than a controlled experiment demonstrating statistically identified security improvements.

Future Work: Stronger Logs, Recovery, and Quantitative Validation

The study proposes several directions for further development.

Future evaluations could conduct repeated experiments by operating-system build and collect device-level success and failure logs, average execution time, standard deviation, confidence intervals, policy-compliance rates, and failure or disruption rates.

The framework itself could also be extended with:

  • digital signatures,
  • integrity verification,
  • recovery mechanisms after failed execution,
  • version control,
  • automated diagnosis and recovery,
  • and de-identified reporting functions.

The study additionally proposes mapping the framework against Microsoft security baselines to evaluate whether organizational policy settings remain aligned with current recommendations.

Such work would allow future versions of WSPA to move beyond a field deployment case toward more rigorous quantitative evaluation of reliability, policy compliance, and operational performance.

A Practical Case for Lightweight Endpoint Automation

The study shows that a relatively simple automation architecture based on native Windows commands and batch scripts can be deployed at substantial scale in an environment where more elaborate management infrastructure may be constrained.

Its strongest evidence concerns operational execution: the same categories of endpoint security measures that reportedly required more than 30 minutes per device when performed manually were completed in less than 5 minutes through WSPA in the reported field case.

At the same time, the paper carefully limits that result. More than 5,000 endpoints represent deployment scale rather than independent experimental samples, and the available evidence does not establish a reduction in security incidents or a statistically identified improvement in security effectiveness.

Within those boundaries, WSPA provides a documented example of how repetitive Windows endpoint-hardening procedures can be standardized and automated using only native operating-system capabilities in constrained operational environments.

Research Information

Original Study: Design and Operational Evaluation of a Windows Endpoint Security Automation Framework Using Batch Scripts
Original Korean Title: 「Windows 배치 스크립트 기반 단말 보안조치 자동화 체계의 설계와 운영 효과 분석」
Researcher: 이찬우 (Lee Chanwoo)
Affiliation: 아주대학교 정보통신대학원 사이버보안전공 (Cyber Security, Graduate School of Information and Communication Technology, Ajou University)

Key Findings

  • Windows Security Policy Automation (WSPA) was designed to automate recurring endpoint security configuration tasks using native Windows commands and batch scripts.
  • The framework was intended for environments where separate management servers or additional endpoint agents are restricted or difficult to introduce.
  • WSPA sequentially applies controls related to accounts, remote access, Microsoft Defender Firewall, shared folders, stored credentials, unnecessary services, and registry-based security settings.
  • Following functional review, WSPA was deployed to more than 5,000 Windows 10 and Windows 11 endpoints.
  • The reported time required to apply the same set of security measures to one endpoint decreased from more than 30 minutes manually to less than 5 minutes with WSPA, corresponding to a minimum reduction of 83.3% based on the boundary values.
  • The 5,000-plus deployment count is not equivalent to 5,000 independent experimental observations, and the study did not analyze raw-log-based success rates, variance, policy-compliance rates, or reductions in security incidents.