Key Takeaways
- Security misconfiguration is primarily a configuration problem rather than a coding flaw.
- OWASP ranked security misconfiguration second among web application security risks in 2025, reinforcing the need for secure baselines and continuous configuration checks.
- A fully patched system can still be misconfigured. Patches correct flaws in software. They do not change a legacy protocol that was left on an administrator account that was never disabled.
- Defaults, convenience, and drift cause most cases. Vendors often ship products with settings that favour fast setup, and administrators leave these default settings unchanged, fail to reverse temporary changes, or allow configurations to drift from the intended secure state over time.
- Fixing misconfigurations requires testing for application compatibility, a staged rollout, and a rollback path in case the fix causes disruptions.
- Detection has to be continuous. A configuration audit is accurate only on the day it runs. New systems, software changes, and manual edits keep reopening gaps.
What is Security Misconfiguration?
Security misconfiguration is an incorrect or insecure security setting on a device, operating system, application, or service that leaves it open to attack. NIST defines a misconfiguration as “an incorrect or suboptimal configuration of an information system or system component that may lead to vulnerabilities”.
A setting can go wrong in three ways:
- Missing. A protection exists but was never turned on, such as a firewall that is disabled or an account lockout rule that was never set.
- Left at the default. The vendor's default setting favours convenience over security, such as a built in administrator account that stays active or sample applications that stay installed.
- Set incorrectly. Someone changed a setting to fix a problem or meet a deadline and left it in an unsafe state, such as a file share opened to everyone.
Misconfigurations can appear in operating systems, servers, browsers, network devices, printers, databases, web applications, and cloud services. The problem is widespread. The OWASP Top 10:2025 ranks security misconfiguration second, up from fifth place, and reports that every application it tested had some form of misconfiguration. The weakness comes from how a system is set up, and not from the vendor code. That is why misconfigurations are found through a configuration audit against a baseline, and fixed by changing the setting.
This article focuses on endpoint, server, and web server misconfigurations that IT teams can assess and fix directly.
Why do security misconfigurations happen?
Most misconfigurations are ordinary decisions that were never revisited. The common causes are:
- Default settings. Software and devices often ship with predefined admin credentials that favours convenience over security. CISA notes that attackers can find many default credentials with a simple web search.
- Temporary changes that stay. Someone changed a setting to fix a problem or meet a deadline and left it in an unsafe state, say, an admin relaxes a firewall rule or enables a share to troubleshoot a problem and forgets to reverse it.
- Configuration drift. A system that met its baseline last quarter moves away from it through software updates, manual edits, and new deployments.
- Complexity. A single operating system has hundreds of security relevant settings, and no one remembers the safe value for each.
- Backward compatibility. Legacy protocols stay enabled because an old application still depends on them.
- Unclear ownership. When no team owns the secure state of a system, no one checks it.
What are examples of security misconfiguration?
The examples below focus on endpoints and servers, where an IT team controls the settings directly.
| Area | Example | Why is it risky? |
|---|---|---|
| Default credentials | 1. Built in administrator or guest account left active 2. Default passwords on devices, printers, and scanners | Default credentials can be found with a web search. CISA notes that printers and scanners may hold privileged domain accounts, so one compromised device can become a path into the domain. |
| Legacy protocols | SMBv1, Telnet, SNMPv1 and v2c, TFTP, enabled or exposed unnecessarily. | Older protocols can reveal system information, give unintended remote access, or let attackers spoof name lookups and capture credentials. |
| Accounts and passwords | Weak password policies, or missing controls against repeated login attempts, such as account lockout. | Credentials can be guessed quickly, and a missing account lockout policy allows unlimited brute force attempts. |
| Unnecessary ports or services | Firewall disabled, unnecessary services enabled, or ports such as 445 exposed beyond their intended network scope. | Services that were never meant to be reachable become open to other systems on the network. |
| Network shares | Shares and repositories open to more users than needed. | Sensitive data and stored credentials become easy to collect and copy out. |
| Operating system hardening | Data Execution Prevention or address space layout randomization turned off. | Memory protections that make exploitation harder are missing. |
| Browsers | Safe browsing disabled, plugins allowed to run without asking the user. | Browser based attacks becomes easier. |
| Linux hosts | Accounts with empty passwords, SELinux or AppArmor not enforced, insecure services such as Telnet running. | Local and remote access controls are weaker than intended. |
What is the difference between security misconfiguration and a vulnerability?
Both can lead to a compromise, but they have different causes and different fixes. A software vulnerability is a weakness in software or its implementation that an attacker can exploit. A security misconfiguration results from an insecure setting on a device, that leaves it open to attack. The terms overlap in standards. NIST generally treats misconfigurations as a type of vulnerability, while its SCAP validation program defines the two as separate things, with “vulnerability” limited to software flaws. IT teams use the separate meaning in practice, because the two are found and fixed differently:
| Security Misconfiguration | Software Vulnerability | |
|---|---|---|
| Definition | An incorrect or unsafe setting in a system, cloud environment, network, or application. | A broader weakness or flaw in software, hardware, architecture, or code logic |
| Root Cause | Human error, overlooked settings, default passwords, or failure to follow hardening guidelines. | Programming errors, buffer overflows, logic bugs, or insecure software design. |
| Where the weakness sits | The weakness is in how a system is set up. | The weakness is in the software or in how it was built. |
| Typical examples | SMBv1 is left enabled, a default administrator account stays active, or no account lockout rule is set. | A service has a buffer overflow, or an application is missing an input check. |
| How it is found | A configuration audit compares system settings against a baseline. | A vulnerability scan checks for known software weaknesses, including those associated with CVE identifiers. |
| Does a patch help? | Usually not, because the software has no flaw to correct. | Usually yes, once the vendor has released a patch. |
A vulnerability scan and a configuration audit answer different questions, and a complete vulnerability management program runs both. Scoring methods such as CVSS rate software flaws, so configuration findings need their own severity and exposure review.
What are the risks of security misconfiguration?
A misconfiguration rarely causes damage by itself. It gives an attacker lateral movement to move further. NSA and CISA reviewed their red team and blue team assessments, hunt activity, and incident response work, and published the ten most common cybersecurity misconfigurations in large organizations:
| NSA/CISA finding | What does it mean and why it matters? |
|---|---|
| Default configurations of software and applications | Software and devices retain vendor-supplied default credentials, permissions, or settings instead of being properly secured before deployment. Attackers can exploit known default credentials to gain unauthorized access. |
| Improper separation of user/administrator privilege | Regular user accounts or service accounts have more privileges than necessary, or administrators use privileged accounts for everyday activities. |
| Insufficient internal network monitoring | Network traffic and activity on individual systems are not monitored adequately. Suspicious connections, unauthorized access, and attackers moving between systems may go undetected. |
| Lack of network segmentation | User devices, production systems, and critical infrastructure are not adequately separated into different network segments. An attacker who compromises one system may be able to access other systems across the network. |
| Poor patch management | Patches are not regularly applied, or organizations continue using unsupported operating systems and outdated firmware. Known vulnerabilities remain unaddressed, giving attackers opportunities to exploit them. |
| Bypass of system access controls | Attackers exploit weaknesses in authentication mechanisms to access systems without following the expected login process. For example, stolen password hashes can be reused to authenticate through techniques such as pass-the-hash. |
| Weak or misconfigured multi-factor authentication (MFA) | MFA methods are implemented incorrectly or use verification methods that attackers can bypass. Phishing, fraudulent login approval requests, and SIM-swapping attacks can help attackers get around the additional authentication step. |
| Insufficient access control lists (ACLs) on network shares and services | Permissions on shared folders and network services are broadly assigned, allowing unauthorized users to access sensitive files, credentials, or administrative information. |
| Poor credential hygiene | Weak or easily guessed passwords and passwords stored in plain text make it easier for attackers to obtain valid credentials. These credentials can then be used to access systems and impersonate legitimate users. |
| Unrestricted code execution | Systems allow unverified programs, scripts, or macros to run without adequate restrictions. Attackers can exploit this to execute malicious code, establish access, and move further into the network. |
The advisory describes how several of these turn into real access:
- Default credentials. Printers and scanners often have privileged domain accounts loaded so users can scan to a shared drive. An attacker who signs in with a default password can use that account to move laterally.
- Legacy name resolution. When the Windows services like Link-Local Multicast Name Resolution (LLMNR) and NetBIOS Name Service (NBT-NS) are enabled, attackers can spoof lookups so computers send usernames and password hashes to a system the attacker controls. The hashes can then be cracked offline.
- Crackable passwords. CISA links easily cracked passwords to short length, under 15 characters, and predictable choices. In one assessment, a team cracked more than 80% of the passwords in an Active Directory in 12 hours.
- Open network shares. Attackers search shares for sensitive data and cleartext credentials, then copy the data out, often for extortion.
Attackers use whichever weakness is open, and often combine a configuration gap with a software flaw.
How to detect security misconfigurations
Finding misconfigurations is a repeatable audit, not a one time project. A practical sequence follows.
- Know what exists. An audit can only cover systems that are in the inventory, so unmanaged computers, servers, and devices need to be found first.
- Pick a baseline. A baseline is the agreed secure state for each system role. Most teams start from published benchmarks. CIS Benchmarks and DISA STIGs are common choices.
- Audit against the baseline on a schedule. Compare the live settings of every system with the baseline. Repeat the audit continuously, because drift reopens gaps between audits.
- Review exposed ports and services. A port audit lists which ports are open on each endpoint and which of them should not be.
- Check where each setting is enforced. Some settings are controlled by domain group policy and must be changed in the policy itself, as local changes may be overwritten.
How to fix and prevent security misconfigurations
NSA and CISA put this in plain terms: remove default credentials and harden configurations, disable unused services and add access controls, update regularly, and reduce, restrict, audit, and monitor administrative accounts. A fix still changes how a live system behaves, so the order of work matters.
- Rank the findings by severity and exposure. The same risk prioritization logic used for software vulnerabilities applies here. Internet facing systems, administrator accounts, and legacy protocols come first, and a critical setting on a server that handles sensitive data outranks a low severity setting on a spare laptop.
- Test the impact before changing anything. Disabling a legacy protocol can stop an old application from working, so check which applications depend on a setting first.
- Deploy in stages. Start with a small group of systems, confirm that nothing breaks, and then widen the rollout.
- Keep a rollback path. Record the original value before any change, so a change that causes an outage can be reversed quickly.
- Handle exceptions deliberately. Some systems cannot meet the baseline. Record the reason and the owner, and review each exception on a schedule so it does not stay open indefinitely.
- Verify the result. Rescan to confirm that the setting changed and the deviation is gone.
Prevention comes from the same baseline. Every new operating system image and server should be built from the hardened baseline, not from vendor defaults, with default accounts removed at build time. Continuous auditing then catches drift before it becomes an exposure.
How Vulnerability Manager Plus helps detect and fix security misconfigurations
ManageEngine Vulnerability Manager Plus includes security configuration management, which follows the same workflow described above for Windows and Linux systems: detect, assess impact, deploy the fix, handle failures, and manage exceptions.
- Detect deviations from a baseline. Vulnerability Manager Plus continuously monitors managed systems against predefined security configuration templates based on CIS and STIG benchmarks. The console lists each misconfiguration with its category, the number of affected systems, whether a fix is available, and whether the fix needs a reboot.
- Assess impact before deploying. Each fix shows its post deployment issues, so administrators can see what a change may affect before they push it.
- Deploy fixes at scale. An administrator selects the misconfigurations, defines target computers, and deploys the fix from the same console. Deploy Immediately reaches up to 200 computers at once, and the remaining computers receive the fix on their next refresh cycle.
- Handle failures and rollback. Computers where a fix failed are listed so the deployment can be started again. For Windows, revert scripts are available to roll a change back.
- Manage exceptions and web servers. A check can be added to the exceptions list so it is not reported for specific systems. Web server hardening detects default and insecure configurations on Apache, Tomcat, IIS, and nginx, and describes the cause, impact, and remediation for each.
Settings controlled by domain group policy cannot be overridden from the console, so Vulnerability Manager Plus points to manual resolution steps for those. The security misconfiguration catalog documents each detected misconfiguration with its description, severity, resolution steps, possible side effects, and reboot requirement, and the how to guide on detecting security misconfigurations shows the console steps. Software vulnerabilities and missing patches are handled alongside configuration findings, with patch management covering the patching side.
