Glossary
Secure configuration
Definition
Secure configuration means setting up software and devices to reduce unnecessary access and avoid unsafe defaults.
It means choosing and maintaining settings that restrict unnecessary functions and access. It complements patching rather than replacing it.
A customer may include “Secure configuration” 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.
Secure configuration is the choice and maintenance of settings that reduce a system's exposure. It can include disabling unused services, restricting administration, changing default credentials and limiting data sharing. The right settings depend on the system and the work it supports.
It differs from patching. A fully updated application can still expose information through a public sharing setting or an unnecessarily powerful account. Conversely, careful settings do not fix a software vulnerability that needs an update.
Consider a small business buying a network device. Before use, its administrator could restrict the management interface, set individual credentials where supported and disable features that the business does not need. Leaving factory defaults untouched may expose more functions than intended.
Configuration is ongoing work. New features, troubleshooting changes and supplier updates can alter settings over time. A documented baseline gives the administrator something to compare against, but exceptions need review rather than silent acceptance. Maintain a documented baseline and compare actual settings against it after changes. Review exceptions and correct drift; an installation checklist only shows what someone checked at that time. A checklist completed during installation says little about the state of the system a year later.