T 2.133 Poorly defined responsibilities for patch and change management

Clear responsibilities should also be defined within the framework of patch and change management. In the event of situations where the responsibilities are not or improperly defined, significant disadvantages may occur. For example, undefined responsibilities may result in severe security gaps not being closed promptly, since no one wants to assume the responsibility for an emergency patch.

Poorly defined, overlapping, or unclear responsibilities in patch and change management decelerate the classification of the requests for change into categories and the assignment of priorities and therefore the desired distribution of the patches and changes (rollout). The premature approval of a change or patch without testing and without taking into consideration all (technical) aspects may have severe repercussions for security.

In extreme cases, poorly defined responsibilities may adversely affect the entire organisation or large parts of it. Disturbances during operation have repercussions on the availability; the confidentiality and/or integrity is affected adversely if security-relevant patches are not distributed.

Examples: