Anti-cloning

This use case describes an application in which the host device is required to enforce authentication; that is, refuse to accept an unauthorized peripheral. The design challenge here is to find a robust way to implement security across the entire system, because weak points in the design might allow circumvention of the enforcement mechanism.

One reason for providing a secure identity that the host must authenticate is to ensure that a device (peripheral, etc.) whose operational capabilities expire after a specified number of cycles or a certain date cannot be operated beyond its expiration point.

This application differs from the Board ID™ tracking use case in which a person performs the enforcement function. Also, it differs from a simple authentication scenario in which the device does not need to have a unique identity, but only has to prove to the host that it is authentic.