Glossary

Security by default

secure by default secure-by-default

Definition

Security by default gives a product protective initial settings, so customers do not have to discover and enable every safeguard themselves.

Security by design shapes how a product is built. Security by default concerns the protective settings a customer receives before making changes.

A customer may include “Security by default” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

Security by default means the standard starting configuration favours protection. A customer should not need specialist knowledge simply to discover that an important safeguard is switched off. Examples include restricted initial sharing permissions and requiring suitable authentication for sensitive access.

It complements security by design. Design concerns how the product is built; defaults concern the state in which it reaches the customer. Neither term proves that a product is safe for every purpose or correctly configured for a particular business.

For example, a small consultancy adopting a document service could reasonably expect new workspaces to be private until sharing is deliberately enabled. Making every uploaded file public and relying on the customer to find a setting would place the protective work on the customer.

Defaults still need to be reviewed against business needs. Check the initial settings for access, sharing, authentication, logging and recovery; note which stronger controls require an upgrade and how risky changes are explained. Administrators may change defaults, integrations may introduce new permissions and product updates may alter behaviour. A protective starting point is valuable, but it still needs ownership over time.

Sources