This is not limited to consumer transactions like banking apps, and deployment is never guaranteed to be the result of a rational decision-making process. I hav

This is not limited to consumer transactions like banking apps, and deployment is never guaranteed to be the result of a rational decision-making process. I have now had more than one employer who deployed remote attestation in a bring-your-own-device ecosystem. They do this because they are told by some vendor tutorial that it is more secure, but they end up disabling user devices by accident. My current IT department told me to buy a new phone if my current one couldn't pass a SafetyNet check. The problem is that if you are inside a project developing something like this, you can clearly visualize your expected use case, but it's impossible to know what other use cases will be contrived. Of course in this case, we have predicted a few major malfeasances and I think anyone supporting a project like this needs to know the harmful use cases and be responsible for developing with them in mind.