Hardening meaning, in plain words

Hardening means switching off unused features and reviewing settings to harden defense. What the NIST glossary and OWASP A05:2021 say, and why it must be repeated.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Hardening means switching off features you do not use and reviewing settings to make the defense firm. The English word means making something hard. The NIST glossary gives the definition from SP 800-152: a process of fixing vulnerabilities and disabling non-essential services to reduce the points an attacker can use. The definition therefore has two parts: fixing known weaknesses and disabling services that are not essential. Both steps shrink what an attacker can use.

How does hardening work?

Think of locking up a house. You lock even the windows you do not use, and you board up a back door that you never open. The fewer places there are to get in, the fewer places there are to check.

Servers and sites are the same. In the initial state, features you do not use or parts meant for trials may be left in place. OWASP's A05:2021 describes a minimal platform with no unnecessary features, components, documentation, or samples. It says to remove unused features and frameworks or not to install them in the first place.

OWASP also gives an example in which a sample application was left on a production server. Configuration problems are collected on the page about security misconfiguration. The free URL check reads only what an outside visitor can see, so whether your internal settings are hardened is a matter for a consultation.

Why does hardening matter?

Attacks can enter through the weakness of a feature that nobody uses, including a sample or trial component that was never removed. If you stop what you do not use, there is less to fix and less to watch.

OWASP says that with a repeatable hardening process, another environment locked down in the same way can be set up quickly and easily. It also becomes easier to avoid drift between the settings of testing and production environments.

You do not do it once and finish. Every time you add a feature or update something, the settings change. For that reason, you write the work down so that it can be repeated in the same order. What to call a weakness that is found is explained in the vulnerability term page.

Related terms

Next step

Examples of configuration problems and how to fix them are on the security misconfiguration page. The free URL check shows only what is visible from outside. Listing what you do not use is the first step. To ask about reviewing your settings, contact us.

Frequently asked questions

Is hardening done once and finished?

Not finished. Settings change when you add or update features and components. OWASP says that a repeatable process lets you set up another environment in the same hardened state quickly.

How do I decide what to switch off?

OWASP points to a minimal configuration with no unnecessary features, components, documentation, or samples. Start by listing what you do not use and removing what you truly do not need.

Frequently asked questions

Is hardening done once and finished?

Not finished. Settings change when you add or update features and components. OWASP says that a repeatable process lets you set up another environment in the same hardened state quickly.

How do I decide what to switch off?

OWASP points to a minimal configuration with no unnecessary features, components, documentation, or samples. Start by listing what you do not use and removing what you truly do not need.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.