# How to customize security baselines for Azure VMs and ARC servers?

x-oss.com · November 18, 2026

> Automanage simplifies compliance by automating the enforcement of security baselines across Azure VMs and Azure Arc-enabled servers, yet organizations...

## Applying Azure Automanage Best Practices

Automanage simplifies compliance by automating the enforcement of security baselines across Azure VMs and Azure Arc-enabled servers, yet organizations often struggle with tailoring these defaults to specific regulatory requirements. To customize effectively, leverage the built-in CIS benchmarks that now include native auditing for Linux workloads, ensuring comprehensive coverage without manual intervention. For Windows environments, utilize the machine best practices profile which aligns with Microsoft’s hardened security defaults, particularly relevant as newer server versions like Windows Server 2025 introduce stricter policies that may challenge existing migration strategies. By integrating these profiles, platform teams can automate routine patching and configuration checks, significantly reducing the operational overhead associated with frequent system restarts through hotpatching capabilities. This approach allows enterprise IT teams to maintain rigorous security postures while minimizing disruption to critical business applications.

**Also worth reading:** [What methods do sysadmins use to update security baselines?](https://x-oss.com/knowledge/what_methods_do_sysadmins_use_to_update_security_baselines.php) · [Is there a free PowerShell tool to assess Azure SQL Database security?](https://x-oss.com/knowledge/is_there_a_free_powershell_tool_to_assess_azure_sql_database_security.php) · [How to manage CVE monitoring without dedicating all day to security alerts?](https://x-oss.com/knowledge/how_to_manage_cve_monitoring_without_dedicating_all_day_to_security_alerts.php)

For cross-cloud object-storage scenarios typical in B2B SaaS platforms, extending these baselines to Arc servers ensures consistent governance across hybrid environments. Customize the baseline by modifying the assigned profile to exclude specific non-compliant settings that are safe for your unique workload architecture, such as certain network firewall rules or legacy service accounts. This selective customization prevents over-provisioning while maintaining audit readiness for major updates released at events like Microsoft Ignite. By focusing on high-impact controls and leveraging automated remediation, teams can achieve a balanced security posture that supports both innovation and compliance. This methodical application of best practices ensures that security remains robust without stifling the agility required for modern data-plane operations across diverse cloud infrastructures.

## Configuring Native CIS Benchmark Auditing

Configuring native CIS benchmark auditing for Azure VMs and Azure Arc-enabled servers requires a strategic approach to customize security baselines effectively. Microsoft has introduced native support for CIS benchmarks, particularly for Linux workloads, allowing platform teams to align their infrastructure with industry-standard security practices without relying on third-party tools. For Azure Arc-enabled servers, the integration extends this capability to hybrid environments, ensuring consistent policy enforcement across on-premises and cloud resources. To customize these baselines, administrators should leverage Azure Policy definitions that map directly to CIS controls, enabling granular adjustments based on specific organizational requirements. This native integration simplifies compliance reporting and reduces the operational overhead associated with maintaining external auditing solutions. By utilizing Azure Automanage Machine Best Practices, teams can automate the application of these benchmarks, ensuring that security configurations remain up-to-date with minimal manual intervention. This automation is crucial for maintaining a robust security posture in dynamic cloud environments where manual updates are prone to errors and delays.

The customization process also benefits from recent advancements in patch management and server hardening. With hotpatching available for Windows Server, organizations can apply critical security updates without the disruptive restarts that traditionally hindered continuous operations. This feature, combined with the general availability of Azure Automanage, streamlines the deployment of best practices across diverse workloads. Platform teams managing cross-cloud object-storage solutions can further enhance their security posture by integrating these native auditing capabilities with their existing SaaS data-plane architectures. The upcoming Windows Server 2025 preview introduces hardened security by default, which may pose migration barriers for existing environments but ultimately strengthens the overall security framework. By adopting these native tools, enterprises can achieve a more resilient and compliant infrastructure, ensuring that their security baselines are both customizable and robust against evolving threats. This holistic approach supports the needs of B2B cross-cloud object-storage environments, providing a unified method for managing security across hybrid and multi-cloud deployments.

## Implementing Hotpatching For Windows Servers

Hotpatching enables critical security updates to be applied without requiring a full system restart, significantly reducing downtime windows for enterprise environments. This capability is particularly valuable for maintaining high availability in Azure Virtual Machines and Azure Arc-enabled servers, where continuous operation is paramount. By leveraging the native hotpatch feature introduced in recent Windows Server versions, administrators can apply patches directly to the running kernel, ensuring that security baselines remain current without disrupting active workloads. This approach aligns with the broader trend of minimizing maintenance overhead while enhancing system resilience across hybrid cloud deployments.

To customize security baselines effectively, teams should integrate Azure Automanage Machine Best Practices with existing CIS benchmark auditing tools. This integration allows for automated compliance checks that adapt to both Azure VMs and Arc servers, ensuring consistent policy enforcement regardless of the underlying infrastructure. By combining native auditing capabilities with automated best practices, organizations can streamline their patching strategies and reduce the manual effort associated with baseline management. This unified approach not only simplifies compliance but also strengthens the overall security posture of cross-cloud environments, providing a robust framework for ongoing security maintenance and threat mitigation.

## Managing Linux Security Compliance

Platform teams operating across Azure VMs and ARC servers must leverage the newly introduced native CIS benchmark auditing capabilities to establish robust security baselines. This integration allows for automated compliance checks directly within the Azure portal, eliminating the need for external scanning tools. By configuring Azure Automanage Machine Best Practices, organizations can enforce standardized configurations that align with industry standards without manual intervention. This approach ensures consistent security postures across hybrid environments, reducing the complexity of managing diverse infrastructure. Teams can define custom policies that trigger alerts when deviations occur, enabling proactive remediation before vulnerabilities are exploited. The seamless integration of these tools simplifies the compliance workflow, allowing IT administrators to focus on strategic initiatives rather than routine audits.

Customizing these baselines requires careful alignment with specific organizational requirements while maintaining strict adherence to CIS guidelines. Platform teams should utilize Azure Policy definitions to tailor security controls for each workload type, ensuring that critical services remain protected without compromising performance. Regularly updating these configurations based on emerging threats and regulatory changes is essential for maintaining a resilient security posture. By adopting this automated approach, enterprises can achieve continuous compliance, reducing the risk of non-compliance penalties and enhancing overall data protection. This strategy not only streamlines security management but also provides a scalable framework for future expansions into new cloud regions or on-premises deployments.

## Handling Default Hardening Changes

Customizing security baselines for Azure VMs and ARC servers requires a strategic approach to balance compliance mandates with operational stability. Enterprise IT teams must leverage Azure Automanage Machine Best Practices, which now offers general availability for automated configuration management. This tool simplifies the initial setup by applying recommended security settings automatically, reducing the manual overhead traditionally associated with hardening. However, organizations often find the default configurations too restrictive for specific workload requirements. To address this, platform teams should integrate custom scripts or Azure Policy definitions that tailor the baseline to their unique infrastructure needs. This ensures that critical services remain functional while maintaining a robust security posture. The recent introduction of native CIS benchmark auditing for Linux in Azure further streamlines this process, allowing teams to verify compliance without extensive manual intervention. By combining automated best practices with targeted policy overrides, administrators can achieve a nuanced security configuration that respects both regulatory standards and technical necessities.

For ARC servers, the challenge lies in extending these Azure-native controls to hybrid environments seamlessly. Teams must ensure that the same security policies applied to cloud VMs are consistently enforced across on-premises or edge locations. This involves configuring Azure Policy initiatives that recognize ARC-connected machines and applying equivalent hardening rules. Additionally, with Windows Server 2028 preview highlighting hardened security by default, migration barriers may arise for existing environments. To mitigate potential disruptions, IT leaders should adopt hotpatching capabilities for Windows Server, allowing updates without frequent restarts. This approach minimizes downtime during security updates, ensuring continuous availability. By unifying governance across cloud and hybrid deployments, organizations can maintain a consistent security baseline. This unified strategy not only enhances compliance but also simplifies ongoing maintenance, providing a scalable framework for managing security across diverse infrastructure landscapes effectively.

## Security Baseline Configuration Methods

| Method | Azure VMs | ARC Servers |
| --- | --- | --- |
| Native Policy | Azure Policy | Azure Policy |
| Compliance | Azure Defender | Azure Defender |
| Automation | Automanage | Automanage |
| Auditing | CIS Benchmarks | CIS Benchmarks |

Enterprise IT teams now leverage native Azure Policy and Defender for unified compliance across hybrid environments. With Automanage automating best practices and hotpatching reducing downtime, organizations can enforce strict security baselines without disruptive restarts. This integrated approach simplifies auditing for both cloud and on-premises assets, ensuring consistent protection while addressing the migration challenges posed by hardened default configurations in modern Windows Server versions.

## Quick answers

### How does Azure Automanage simplify baseline configuration?

It automatically applies Microsoft-recommended best practices to reduce manual configuration effort.

### Can I audit CIS benchmarks on Linux VMs?

Yes, Azure now provides native auditing capabilities for Linux security benchmarks.

### Does hotpatching affect security baseline compliance?

Hotpatching allows updates without restarts, maintaining compliance without service interruption.

### What happens if my server lacks default hardening?

Newer Windows Server versions enforce strict defaults that may block legacy migrations.

Canonical: https://x-oss.com/knowledge/how_to_customize_security_baselines_for_azure_vms_and_arc_servers.php
Markdown: https://x-oss.com/knowledge/how_to_customize_security_baselines_for_azure_vms_and_arc_servers.php/index.md
