The signing process doesn't, but Microsoft reserve the right to revoke the binary's hash if it's used to attack other systems. Implementations that don't verify

The signing process doesn't, but Microsoft reserve the right to revoke the binary's hash if it's used to attack other systems. Implementations that don't verify drivers are going to be fairly easy to circumvent into use as an arbitrary bootloader for unsigned or compromised content, and if the blackhats do so then revocation is a likely outcome. There's no explicit list of required implementation policies. People are free to implement whatever policy they want, based on their perceptions of the risk of revocation.