Skip to content
Log in DE Arrange a meeting

Knowledge · Security management

Defining protection goals and distinguishing them from measures

Protection goals describe the intended security state. How they differ from measures, how to word them verifiably, and what an effectiveness check shows.

Updated: · MOVETOS

A protection goal describes which security state is to be reached or maintained. It makes the identified protection need concrete and forms the basis for selecting and assessing suitable security measures.

Distinguishing protection goal and measure

A measure is what is done or installed. A protection goal describes what it is done for.

Installing a camera is a measure. Detecting dangerous visitor movements in time so that countermeasures can be initiated is a protection goal. Only by separating the two can different measures be compared by how well they achieve the goal.

Examples from practice

AreaProtection goal
EventDetect dangerous visitor movements in time and respond to them effectively
Critical infrastructure (KRITIS)Maintain security-relevant functions even if the primary supply fails
CorporatePrevent unauthorised vehicle access in line with the defined security requirements
MunicipalityInform visitors reliably about dangers, even during disruptions

These are examples of wording. How a protection goal reads in a specific case follows from the identified protection need of the event or facility concerned.

Wording goals concretely and verifiably

Protection goals should be worded as concretely and verifiably as possible. This includes suitable criteria for

  • the required function,
  • responsiveness and
  • proof of effectiveness.

Which criteria apply in detail must be determined professionally for the respective deployment. This also covers test criteria, responsibilities and assumptions about possible failures. Blanket values do not replace this.

More on this: Turning protection goals into security requirements.

Installed does not mean effective

A security measure does not fulfil its purpose merely by being installed. What matters is whether it actually works under the intended operating and fault conditions: during live operation, when parts of the technology fail, and with the people who are meant to operate it.

More on this: Ordered does not mean implemented: verifying security measures.

Security concept and effectiveness check

A security concept describes what is planned. The effectiveness check shows whether the intended protective effect is actually achieved. The two belong together: without a verifiable protection goal there is no yardstick for the check.

More on this: From security concept to working event operations.

Checklist: is the protection goal usable?

  • The protection goal describes a state or an effect, not a particular device.
  • It is linked to the identified protection need.
  • Function and responsiveness are described with criteria.
  • Assumptions about operating and fault conditions, including failures, are defined.
  • Responsibilities are named.
  • It is determined how effectiveness is proven.

Conclusion

A protection goal names the intended security state, not the measure. It is usable if it can be checked whether it is achieved under real operating and fault conditions.

Note: research status 19 November 2026. General orientation; the statements have not been checked against the original regulations. Laws, ordinances and standards (such as the German state assembly-venue ordinances, the KRITIS Umbrella Act, the Occupational Safety and Health Act, DIN ISO 31000) are binding only within their respective scope; standards are not automatically legally mandatory. Not every event is subject to the assembly-venue regulations. Not legal advice. No function, response time or certification of MOVETOS OPS is promised.

Read on

Events, companies or critical infrastructure: we will show you how MOVETOS OPS does this in practice.