Depending on which areas of BACS are affected, incorrect configurations can impair operational processes, allow prohibited physical access to protected areas, and cause harm to systems, buildings, and people.

Consider the following examples:

These hazards are particularly relevant for BACS when a lack of opportunities to conduct corresponding testing makes it impossible to detect a faulty configuration before going live. This can also occur in the event of a faulty update or a faulty update process that renders a BACS unusable.