Patching can be viewed as a configuration modification and therefore subject to the organization's configuration management program and methods. What might also be an aspect of patching in terms of configuration management? Question $7$ options: $1)$ Patching doesn't need to be performed as a distinct effort; patching can go through the normal change request process like all other modifications $2)$ Any patches suggested$/$required by vendors to maintain compliance with service contracts must be made immediately, regardless of internal process restrictions. $3)$ Any patches suggested by third parties should never be considered as they may invalidate service contracts$/$warranties and negatively affect the organization's security posture. $4)$ The configuration$/$change management committee$/$board might grant blanket approval for patches $($at a certain impact level$)$ without need to go through the formal change process.