What is endpoint hardening?
Endpoint hardening is the practice of reducing vulnerabilities in individual devices (laptops, desktops, servers, mobile phones) by disabling unnecessary services, closing unused ports, removing default configurations, and enforcing strict security controls.
The work involves both removal (disabling unused services, deleting unnecessary applications) and reinforcement (patching promptly, enforcing strong authentication, encrypting data, configuring firewalls, establishing baseline configurations).
Consider how exposed a device can become when it is left in an unmanaged or inherited configuration. For example, if Remote Desktop is enabled without network restrictions, PowerShell is unrestricted, legacy authentication protocols are still active, and local administrator accounts share weak or reused passwords, each of those settings becomes a potential backdoor. Whether a given device carries these settings depends on how it was imaged, configured, and managed.
Hardening reduces these entry points before attackers find them.
The goal is straightforward: shrink the attack surface. Make lateral movement harder. Reduce the number of exploitable vulnerabilities on each device.
Why is endpoint hardening important?
- Breach timelines are collapsing. Average eCrime breakout time dropped to 29 minutes in 2025, down from 48 minutes in 2024 and 98 minutes in 2021, according to the CrowdStrike 2026 Global Threat Report. That's not time for a security team to detect, investigate, and respond. It's time for attackers to own your infrastructure. Hardened endpoints slow that down. Detection systems can catch attacks sooner when the attacker can't simply move laterally using unnecessary services or default configurations.
- The financial stakes are real. The IBM 2025 Cost of a Data Breach Report put the global average cost of a breach at $4.44 million, down from $4.88 million in 2024, a decline IBM attributes largely to faster detection and containment. Organizations that used AI and automation extensively across their security operations saved an average of $1.9 million per breach and shortened the breach lifecycle by an average of 80 days. Hardening complements that speed by reducing how many incidents succeed in the first place.
- Regulatory frameworks expect it. The NIS2 Directive in Europe requires essential and important entities to adopt cybersecurity risk-management measures that include basic cyber hygiene practices, vulnerability handling, access control, and cryptography policies, with fines of up to 10 million euros or 2% of global annual turnover, whichever is higher, for essential entities. Endpoint hardening supports many of these measures. HIPAA, PCI-DSS, FedRAMP, NIST 800-171, and ISO 27001 also contain requirements that hardening helps meet. Cyber insurance underwriters now ask directly: do you enforce MFA? Are LAPS deployed? Is BitLocker enabled? Is endpoint detection running? A single "no" can affect coverage.
- Known vulnerabilities are still a leading attack vector. Many breaches don't require zero-days. Verizon's 2026 Data Breach Investigations Report found that exploitation of vulnerabilities was the most common way attackers gained initial access, at 31% of breaches. Attackers often exploit known vulnerabilities that patches would have fixed, or leverage services and features that serve no business purpose but remain enabled. Attackers don't need sophistication when outdated software, default credentials, and unnecessary administrative tools are sitting accessible.
10 core best practices of endpoint hardening
Endpoint hardening isn't a single control. It's a layered approach. Here are the practices that matter most:
- Establish secure configuration baselines
- Disable unnecessary services, ports, and applications
- Enforce least privilege and remove unnecessary admin rights
- Configure host firewalls and restrict remote access
- Automate operating system and application patching
- Enforce strong authentication and MFA
- Enable disk encryption and manage recovery keys
- Configure Windows attack surface reduction rules
- Control which applications can run
- Monitor configurations and remediate drift
1. Establish secure configuration baselines.
A security baseline is a tested, documented configuration that applies recommended security settings in a single policy. Instead of manually configuring dozens of settings on thousands of devices, baselines do it systematically.
Microsoft provides pre-configured security baselines for Windows 10, Windows 11, Microsoft Edge, Defender for Endpoint, and Office. These baselines are based on expert knowledge from Microsoft, partners, and customers analyzing thousands of group policy settings.
The CIS Benchmarks (published by the Center for Internet Security) are another industry standard. The Windows 11 benchmark includes hundreds of recommended settings, so most teams start with a prioritized subset, validate it in a pilot group, and expand from there.
2. Disable unnecessary services, ports, and applications.
Every running service, open port, and installed application is something you have to patch, monitor, and defend. If a feature has no business purpose, removing it shrinks the attack surface.
Best practice approach:
- Inventory what is running and listening on each device class, and use audit data to confirm what is actually used before turning anything off.
- Disable legacy protocols and services with no business need, such as SMBv1, LLMNR, and unused remote administration services.
- Remove unauthorized, end-of-life, and bundled applications, and uninstall prohibited software automatically so it does not return.
- Test changes on a pilot group first, because some line-of-business applications depend on services that look unused.
Document any exceptions and review them regularly so temporary exemptions don't become permanent gaps.
3. Enforce least privilege and remove unnecessary admin rights.
Standing local administrator rights let malware and attackers install software, disable security tools, and move across the network. To enforce least privilege, give users the access their role requires and nothing more.
Best practice approach:
- Remove users from the local Administrators group by default.
- Use separate admin accounts for administrative tasks, and keep them away from email and web browsing.
- Deploy Windows LAPS (or an equivalent) so every device has a unique, regularly rotated local administrator password.
- Grant just-in-time, application-specific elevation for tasks that genuinely need it.
- Review privileged group membership on a regular schedule.
4. Configure host firewalls and restrict remote access.
A host-based firewall protects each device even when it leaves the corporate network. Remote access services such as Remote Desktop are useful but are also a common target when exposed without restrictions.
Best practice approach:
- Enable the host firewall on all network profiles, deny inbound traffic by default, and allow only the exceptions you need.
- Disable Remote Desktop and other remote administration services where they are not needed. Where they are needed, limit access to a VPN or jump host and require network level authentication and MFA.
- Block inbound SMB, WinRM, and similar management ports from untrusted networks.
- Apply equivalent firewall settings on macOS and Linux devices, and log blocked connections for review.
Push these settings centrally with configuration management so every device receives the same rules.
5. Automate operating system and application patching.
Unpatched vulnerabilities are the entry point in a significant portion of breaches. But manual patching doesn't scale. Automated patch management closes known vulnerabilities faster and more consistently.
Patching works best alongside the ability to identify and remediate endpoint vulnerabilities, so you can fix what attackers are most likely to exploit first.
An illustrative rollout approach (adjust the timing to your exploitation risk and business requirements):
- Split devices into rings: Pilot (IT staff), Early Adopters, Broad (everyone).
- For example, deploy security patches to the Pilot ring after a short deferral (such as 3 to 7 days), then to broader rings (such as 7 to 14 days). These timelines are examples, not fixed rules.
- Fast-track critical or actively exploited vulnerabilities through an emergency policy, and shorten or skip deferrals when exploitation risk is high.
- Use software inventory tools to track what's running and what versions are current.
- Handle feature updates (major OS version upgrades) differently from security patches. Many organizations defer them for a period (for example, 90 to 120 days) so compatibility issues surface, but the right window depends on your applications, support lifecycle, and security requirements.
Modern patch management tools integrate with centralized device management platforms, making this process automated and observable. The result: fewer vulnerable days between vulnerability disclosure and patching.
6. Enforce strong authentication and MFA.
MFA is one of the most effective account protection controls available. Microsoft research, cited in its identity management guidance, shows that MFA can block more than 99.2% of account compromise attacks. With MFA, a stolen password alone is not enough to sign in. Attackers can still target MFA through phishing and session theft, which is why phishing-resistant methods matter.
For human users, mandate MFA for:
- All cloud applications.
- Remote access and VPN connections.
- Administrative accounts without exception.
Phishing-resistant MFA options are now expected:
- FIDO2 security keys and passkeys.
- Windows Hello for Business.
- Certificate-based authentication.
Legacy authentication protocols should be blocked globally. If users can't use modern authentication, that's a sign the application needs updating or retiring.
Implement via Conditional Access policies so MFA enforcement is tied to context (device compliance, sign-in risk, network location).
Secure workload identities separately. Service accounts, scripts, and automation are a different problem from human sign-ins. Workload identities such as managed identities and service principals do not use interactive MFA, because there is no person to answer a prompt. Microsoft recommends migrating user-based service accounts to workload identities. Then secure them in other ways:
- Use managed identities where possible so no credentials are stored in code or configuration.
- Prefer certificates or federated credentials over client secrets, and rotate or retire secrets you cannot avoid.
- Assign least-privilege roles and review them regularly.
- Monitor workload identity sign-ins, and restrict where they can authenticate from (for example, with Conditional Access for workload identities, where your licensing supports it).
7. Enable disk encryption and manage recovery keys.
An unencrypted laptop turns a lost or stolen device into a potential data breach. If a device is lost, stolen, or seized, encryption is the last line of defense.
BitLocker (Windows) and FileVault (macOS) encrypt the entire drive so data remains inaccessible without the encryption key or the user's credentials.
Deployment approach, by operating system:
- Windows: BitLocker management requires a supported edition such as Pro, Enterprise, or Education. Silent, no-prompt encryption generally depends on prerequisites such as UEFI firmware, a TPM, and the right policy settings. Devices that don't meet them may need user input, such as a PIN or password.
- macOS: FileVault is typically enabled through a configuration profile delivered by an MDM. Because it ties encryption to user accounts, enablement usually happens when a user signs in and is generally not fully silent. Manage FileVault encryption and recovery keys centrally so lost passwords don't become lost data.
- Escrow recovery keys to a central store such as Active Directory, Microsoft Entra ID, or your endpoint management platform, and restrict who can retrieve them.
- Report on encryption status to find devices that are not yet protected.
NIS2 expects policies on cryptography and, where appropriate, encryption, which makes encryption at rest a common baseline expectation. BitLocker and FileVault are built into the operating systems, so there is usually no separate encryption license, subject to the edition requirements above.
The performance impact is typically minimal on modern hardware. Older drives may see slight slowdowns, but this is acceptable compared to the breach risk.
8. Configure Windows attack surface reduction rules.
Attack surface reduction (ASR) rules are a set of Microsoft Defender controls that block risky behaviors attackers rely on, before they execute. Instead of only detecting malware after it runs, ASR rules block specific techniques, which reduces the chances of those techniques succeeding.
Examples:
- Block Office applications from creating child processes (reduces the risk of macro attacks).
- Block executable content from email clients and webmail (reduces the risk of email-borne malware).
- Block Win32 API calls from Office macros.
- Block credential stealing from the LSASS process.
ASR rules require Microsoft Defender Antivirus as the primary AV with real-time protection enabled, and some rules also depend on cloud-delivered protection. Advanced reporting depends on your licensing.
Deployment:
- Configure attack surface reduction rules through your device management platform.
- Start in audit mode to identify false positives.
- Monitor blocked events for legitimate workflows.
- Switch to block mode after a validation period (1-2 weeks minimum).
ASR rules punch above their weight because they target behaviors shared by whole classes of attacks (macro malware, email-borne executables, credential theft from memory) rather than individual signatures. Both the Microsoft security baselines and the CIS Benchmarks include recommended ASR settings.
9. Control which applications can run.
Application control restricts which software can execute on endpoints: approved applications are allowed to run, and others are blocked by policy. This reduces the risk of unauthorized software and malware running on a device, although no single control stops every threat, so it should sit alongside patching, EDR, and the other practices in this guide. Windows Defender Application Control (WDAC), now documented by Microsoft as App Control for Business, is the modern approach, while AppLocker remains available as the legacy alternative for older environments.
Implementation approach:
- Start with a baseline that allows Microsoft-signed binaries, your managed applications, and blocks everything else.
- Deploy in audit mode to identify legitimate applications that would be blocked.
- Adjust the policy accordingly, then enforce.
- Update the policy as new applications are deployed.
Application control does add friction for end-users (new software needs approval), so management and communication are critical. The security benefit often outweighs the operational overhead, particularly in high-security environments.
10. Monitor configurations and remediate drift.
Hardening isn't a one-time project. Configurations drift over time due to patches, updates, user changes, or misconfiguration. Continuous monitoring helps ensure baselines stay in place.
Key controls:
- Enable PowerShell Script Block Logging (Event 4104) and Module Logging (Event 4103).
- Deploy comprehensive host-based logging and behavioral monitoring.
- Enable audit logging for account logon, logon/logoff, object access, and privilege use events.
- Forward logs to a centralized SIEM for correlation and analysis.
Security Configuration Assessment (SCA) tools compare current configurations against baselines and flag deviations. This enables two approaches:
- Automated remediation: the tool automatically fixes drift.
- Manual review: the tool alerts administrators to manual configuration changes that need investigation.
Without logging and monitoring, you have no visibility into whether hardening controls are still in place or whether an attacker has disabled them.
Harden every endpoint from one console. Deploy security baselines, automate patching, and enforce encryption across Windows, macOS, Linux, and mobile with Endpoint Central.

Common endpoint hardening challenges and solutions
1. Resource constraints.
IT teams are overloaded. Hardening feels like "one more thing."
Solution: start small and automate. Security baselines do the heavy lifting with a single policy applying many settings at once. Deploy via centralized device management so manual configuration is unnecessary. Begin with your Pilot ring (IT staff and high-risk users), prove value, then expand. Automation can substantially reduce the effort compared with manual approaches.
2. Visibility gaps.
You can't secure what you can't see. Many organizations don't have a complete inventory of endpoints, especially in BYOD or remote work environments.
Solution: use Unified Endpoint Management (UEM) to inventory devices, track compliance, and report on hardening status. Build reports that show which devices have baselines applied, which are out of compliance, and which need remediation.
3. Configuration drift.
Hardening works great for the first week. Then patches are applied, users disable settings, or other policies override your configurations.
Solution: deploy continuous monitoring and automated remediation. Tools that continuously scan configurations against baselines and either auto-remediate drift or alert for manual review keep hardening in place. Make this part of governance: review exceptions monthly, document approved deviations, and remediate unauthorized drift immediately.
4. User impact.
Some hardening measures (application whitelisting, restricted PowerShell, BitLocker setup) create friction for end-users.
Solution: communicate first. Explain why hardening matters. Test in Pilot ring and gather feedback. Adjust policies if legitimate workflows are blocked. Deploy in phases so users adapt gradually. For critical controls (MFA, BitLocker), the security benefit outweighs short-term friction.
Endpoint hardening standards and compliance
Hardening isn't just security. It's compliance. Nearly every major framework asks the same underlying question in different language: can you prove your devices are securely configured, patched on schedule, access-controlled, and monitored for change? Hardening is how you generate that proof. Auditors don't accept "we take security seriously" as evidence; they want baseline documentation, patch SLAs, and drift reports. A mature hardening program produces all of that as a byproduct, which means the same work satisfies both your security team and your auditors. Here's how the major frameworks map to it.
| Framework | What it requires | How hardening supports it |
|---|---|---|
| HIPAA (Healthcare) | Protection of patient data (PHI). | Encryption, MFA, and access control support the technical safeguards for protecting PHI. |
| PCI-DSS (Payment cards) | Protection of cardholder data. | Patch management, firewall rules, and access control reduce breach risk and support audit readiness. |
| NIS2 (Europe) | Article 21 requires cybersecurity risk-management measures, including basic cyber hygiene practices, vulnerability handling, access control, and cryptography policies. | Endpoint hardening supports many of these measures. |
| FedRAMP (US Federal) | Strict endpoint security and configuration management. | Secure boot, logging, and EDR deployment commonly contribute to FedRAMP authorization. |
| NIST 800-171 and CMMC (US Defense) | Secure configuration, patch management, access control, and continuous monitoring. | Endpoint hardening aligns with both frameworks. |
| ISO 27001 (International) | Security baselines, patch management, access control, and continuous improvement. | Endpoint hardening helps demonstrate control over security configuration. |
For every framework, hardening isn't the whole answer. But it's the foundation. Without hardened endpoints, meeting compliance requirements is much harder.
How Endpoint Central supports endpoint hardening
Every practice above is achievable manually on one machine. The problem is 10,000 machines across different operating systems, locations, and user groups. That's the scale problem, and it's the one you can't harden your way out of by hand. This is where Endpoint Central comes in: it helps you automate the core hardening practices across your entire fleet from a single console.
1. Group Policy and security baselines.
Deploy security baselines and GPOs centrally to thousands of devices simultaneously. Endpoint Central supports both Windows Group Policy Objects and cloud-native policies for modern, cloud-managed devices. Push baselines to pilot rings first, validate, then expand.
2. Patch management.
Automate patching across all endpoints with configurable deployment rings. Define SLAs that match your risk appetite (for example, critical patches in 7 days and standard patches in 14 days), schedule deployments to minimize business disruption, and monitor compliance in real-time. Endpoint Central integrates patch management with device compliance, so devices that are out of compliance for patches can be flagged and remediated.
3. Mobile device management (MDM).
Harden mobile devices (iOS, Android) alongside desktops and servers with MDM. Deploy security baselines, enforce passcode and encryption policies, restrict application installation, and apply compliance policies across device types from a single console.
4. Compliance monitoring.
Track hardening status across your entire fleet. Run compliance scans, compare actual configurations against baselines, identify drift, and generate audit-ready reports. Know exactly which devices are compliant and which are at risk.
5. Remote management.
Execute hardening actions remotely: apply security patches, deploy configuration updates, lock or wipe devices, and remediate incidents without requiring on-site access.
6. Application control and whitelisting.
Deploy application whitelists and blacklists centrally. Restrict execution to approved applications and block unauthorized software across your entire fleet.
7. Reporting and alerting.
Generate compliance reports for audits, security reviews, and executive leadership. Set up alerts for non-compliant devices, configuration changes, and security events.
With Endpoint Central, endpoint hardening scales from dozens to tens of thousands of devices without proportional increases in IT overhead. A commissioned Forrester Total Economic Impact study of Endpoint Central found a 442% return on investment, and customers report saving up to 95% of the time previously spent on manual patch management, which is how hardening at scale becomes an operational program supported by automation.
Deploy baselines, automate patching, and prove compliance across your entire fleet. Start hardening at scale with ManageEngine Endpoint Central today.

