Default configuration is the initial set of settings a system, application or device uses before a user or administrator changes them. It defines baseline behaviour, such as enabled features, access controls, logging, network exposure or password policies, and can create a security exposure if shipped with permissive settings.
What default configuration means in practice
Default configuration is not just a convenience setting, it is the baseline trust posture a product ships with. Because users often deploy before hardening, permissive defaults can become the real-world security state for exposed services, management interfaces, logging, and authentication.
That makes the concept important across systems, applications, and devices: if the initial state is weak, every deployment starts with exposure that must be actively reduced rather than accidentally inherited.
Why default settings are a security boundary
Many compromises begin with settings that were technically temporary but became permanent because no one changed them. Weak defaults can leave unnecessary ports open, allow broad management access, disable logging, or preserve legacy behaviour that an attacker can abuse before any custom hardening is applied.
This is why CISA Secure by Design matters here: it treats secure defaults as a product responsibility, not an afterthought. A product that ships safely by default reduces the chance that first use is also first exposure.
Where default configuration creates exposure
The biggest risk is not the existence of defaults, but the mismatch between a generic baseline and a real deployment. Network devices may ship with exposed administration services, cloud tools may enable broad permissions, and applications may retain verbose debugging or weak password policy settings that are acceptable in a lab but dangerous in production.
Default configuration becomes especially risky when it interacts with other weak assumptions, such as implicit trust on internal networks, shared admin access, or unmanaged internet exposure. Top 10 Network Security Misconfigurations is a useful reference point for how exposed management, permissive firewall rules, and weak device baselines turn configuration into a security control failure.
How organisations should think about baselines
Good configuration management starts by knowing what the product enables before any local changes are made. That means treating the shipped baseline as something to review, compare, and document, not as a safe starting point by default.
The practical question is whether the baseline matches the intended use case, the data sensitivity, and the exposure profile. OWASP Top 10 Proactive Controls is relevant because secure-by-default configuration is part of building security in from the start, rather than relying on later cleanup.
For cloud and infrastructure operators, the same logic applies to management planes and automation tools. AWS Systems Manager Security Guide shows how scoped access, logging, and constrained defaults matter when a platform can reach many hosts at once.
Risk and Threat Considerations
Default configuration is attractive to attackers because it often represents the path of least resistance. If a service ships permissive, uses common credentials or exposes admin functions before hardening, an attacker may not need a novel exploit, only discovery and basic abuse of the baseline state.
Failure mechanism: The organisation assumes the shipped state is acceptable, but the product is deployed without removing open access, weak policy, or unnecessary features. That creates a repeatable exposure pattern across many assets, especially when images, templates, or device profiles are cloned at scale.
Impact: The result can be unauthorised access, easier lateral movement, poor visibility, and faster compromise of the first foothold. In the worst cases, a default setting becomes a persistent control gap that survives patching because it is rooted in configuration rather than code.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
CIS Controls v8 and NIST SP 800-53 Rev 5 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.
| Framework | Control / Reference | Relevance |
|---|---|---|
| CIS Controls v8 | CIS-4 — Secure Configuration of Enterprise Assets and Software | Default configuration is the baseline secure-config problem this control addresses. |
| CIS-12 — Network Infrastructure Management | Default network settings can expose management services, ports, and trust boundaries. | |
| Recommendation — Harden shipped defaults before production use and maintain approved secure baselines. Review and restrict default network exposure on infrastructure and edge devices. | ||
| NIST SP 800-53 Rev 5 | CM-6 — Configuration Settings | Default settings are configuration settings that must be defined, reviewed, and enforced. |
| CM-2 — Baseline Configuration | Default configuration is the starting baseline that should be documented and controlled. | |
| Recommendation — Define, implement, and monitor approved configuration settings for systems and applications. Establish and maintain baseline configurations for each system and device type. | ||
| ISO/IEC 27001:2022 | A.8.9 — Configuration management | Default configuration falls under controlled configuration of technology assets. |
| Recommendation — Control and review configuration baselines before systems enter production. | ||
Practitioner Guidance
Governance implication: Treat secure defaults as a procurement and deployment requirement, not just an engineering preference. Teams should know which baseline settings are safe for production, which must be changed during rollout, and who owns that decision.
What to watch for: Pay close attention to products that require manual hardening before first use, especially if they expose network services, management interfaces, or broad permissions immediately after installation. If a platform depends on “remember to change it later,” the default configuration is already part of the risk.
Related resources from NHI Mgmt Group
- Why does a default Docker configuration create lateral movement risk in containerised environments?
- Is CVE-2019-5591 (Fortinet FortiOS Default Configuration) being exploited in the wild?
- How do you patch or mitigate CVE-2019-5591 (Fortinet FortiOS Default Configuration)?
- Default Encryption Configuration
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org