In computer security applications, to check the integrity of a specific data/program binary, a cryptographic hash function is normally deployed to generate a digest and compare it with a reference digest.
When a remote device proves the integrity of the code and data residing on the platform to a verifying party, it is called remote attestation.
Looking into different remote attestation schemes, I remarked that some of them use a checksum on the memory content to generate the attestation value. In contrast, others propose using a cryptographic hash function.
I personally was expecting that a cryptographic hash function is the goto function when integrity is demanded, especially when the system security is in goal.
"Software-based attestation schemes aim at proving the integrity of code and data residing on a platform to a verifying party." reference
An example of the most common software-based remote attestation scheme is SWATT, which conducts a checksum on the memory content in a pseud-random traversal.
What makes the use of the checksum more common than a cryptographic function for such a security mechanism?