Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a Security Misconfiguration?

A security misconfiguration is a setting that leaves a system exposed without any software flaw being involved: a default password, a debug endpoint, an over-permissive token, or storage left open.

Illustration for the cybersecurity term Security Misconfiguration
Home / Blog / Cybersecurity Terms / What Is a Security Misconfiguration?
17 November 2026

What Is a Security Misconfiguration?

What Is a Security Misconfiguration?

A security misconfiguration is a weakness created by how a system is set up rather than by a defect in its code. The software is patched, the vendor has done nothing wrong, and yet the system is exposed — because a default account was never removed, a debug interface stayed enabled, a permission was written with a wildcard, or storage was left readable. It is the category where the answer to “which vulnerability was exploited?” is “none”.

Why It Sits So High in the OWASP Top 10

The OWASP Top 10 ranks Security Misconfiguration at A05 in the 2021 edition, up from sixth place previously, and the supporting data showed roughly 90% of tested applications had at least one instance. The reason is structural: modern systems have an enormous number of settings, those settings change constantly, and almost all of them default to convenience. Every framework, container image, cloud service, SaaS tenant, and CI platform adds its own surface, and nobody owns the aggregate.

The Patterns That Recur

Two incidents illustrate the scale this reaches. In August 2021 researchers found that the default settings on Microsoft Power Apps portals made list data publicly readable, exposing around 38 million records across many organisations that had each configured their portal exactly as documented. In September 2023 a Microsoft AI research team published a dataset using an Azure shared access signature token that was scoped to an entire storage account with write permission, exposing roughly 38 TB of internal data including private keys and internal messages. Neither involved a vulnerability.

Why It Persists

Misconfiguration is not a knowledge problem. It persists because configuration drifts faster than it is reviewed. A production environment that was hardened at launch accumulates emergency changes, supplier access, and exceptions granted at midnight that were never reversed. Each change is individually reasonable; the aggregate is a system nobody has fully described.

Multiply that by the number of environments and the number of platforms and you have the real cause: configuration state has no owner, no version history, and no test. Everything else follows from that.

Making Settings Deliberate

  1. Define a baseline per platform. Use the CIS Benchmarks, vendor hardening guides, or NCSC device and cloud guidance as a starting point, then record your own deviations with reasons. A written baseline turns “is this right?” into a check rather than a debate.
  2. Build it rather than configure it. Golden images and infrastructure as code make the configuration reviewable and repeatable. See our note on Terraform security for how to keep that pipeline itself trustworthy.
  3. Scan before deployment. Policy checks against templates catch an open security group in a pull request, which is a far cheaper place to fix it than production.
  4. Detect drift continuously. Posture management for cloud, configuration management for servers, and SSPM for SaaS all exist to notice the setting that changed last Thursday.
  5. Remove rather than disable. Uninstalled components cannot be re-enabled by a later change or an attacker.
  6. Test from the outside. A scanner confirms a setting; an assessor shows what chaining three of them together achieves. System hardening and testing are complementary, not alternatives.

The UK Compliance View

Secure configuration is one of the five technical controls in Cyber Essentials, which means any British organisation holding that certification has already committed to removing default accounts, disabling unnecessary services, and applying least functionality. Under UK GDPR, a misconfiguration that exposes personal data is a breach like any other, and the ICO has repeatedly cited absent or inadequate configuration review in its enforcement reasoning. For operators within the NIS Regulations, configuration management is an explicit expectation rather than an implied one.

If you would like an outside view of what your settings currently allow, our infrastructure and architecture review services examine configuration against both a baseline and an attacker’s path through it.

FAQ – Frequently Asked Questions

Is Misconfiguration the Same as a Vulnerability?

They are different causes with similar consequences. A vulnerability is a defect in software that the supplier must fix and that typically receives a CVE identifier. A misconfiguration is a setting the operator chose, or accepted by default, that leaves the system exposed. Patching resolves the first; changing settings and preventing drift resolves the second, which is why vulnerability scanning alone leaves the larger gap.

Which Misconfigurations Should We Fix First?

Prioritise anything that removes authentication from internet-reachable systems: open storage, exposed management interfaces, default credentials, and databases listening publicly. Next come over-permissive identity policies, because they turn a minor foothold into a major incident. Missing headers and verbose errors matter, but they rarely cause a breach on their own and can wait behind the exposure issues.

How Do We Stop Configuration Drift?

Make the desired state machine-readable and enforce it. Define infrastructure in code, apply changes only through the pipeline, and use policy checks to reject non-compliant templates before deployment. Then run continuous posture checks to catch changes made outside that path, and treat every such change as an incident to investigate rather than a finding to tick off.

Do Cloud Providers Protect Us From Misconfiguration?

Only partly. Providers have improved defaults substantially, such as blocking public access on new storage buckets, and they supply tools that flag risky settings. Under the shared responsibility model, however, configuration of your resources remains your obligation, and the provider will not override a setting you deliberately chose. The defaults help new deployments; established estates still need review.

Related Terms

You May Be Interested In These

What Is a Blue Team?

Cybersecurity Terms

16 July 2021

What Is a Blue Team?

Read More
What Is OAuth 2.0?

Cybersecurity Terms

17 November 2026

What Is OAuth 2.0?

Read More
What Is the Security Policy Hierarchy?

Cybersecurity Terms

17 November 2026

What Is the Security Policy Hierarchy?

Read More