Secure Defaults
Systems should adopt secure defaults, ensuring the most restrictive, leastprivilege settings are enabled to minimize vulnerabilities from the start.
3 slides · 1 min read · Domain 3
When designing a system to be secure by default, its initial configuration should employ the strongest practice security settings, even if this creates some inconvenience for users.
Security and usability are typically assessed together, through both risk analysis and usability testing, to ensure that necessary protections remain in place while supporting business objectives.
Security professionals have a responsibility to advocate for secure defaults, regardless of whether they are working for a vendor or representing a customer.
Secure-by-default design is critical because many users never change initial settings, leaving weak defaults in place indefinitely. Systems that ship with permission configurations often become immediate targets for attackers, as they can be exploited before administrators harden them. Default configurations should enforce principles like least privilege, strong authentication, and encrypted communications. While there may be pressure to replace security to simplify onboarding or reduce costs, these tradeoffs must be weighed carefully.
Proper documentation, user education, and support can mitigate usability concerns without compromising foundational safeguards that protect organizations and their customers.