It's extremely likely that it's based on the verifiedBootHash from key attestation. Key attestation also might be getting extended to cover firmware attestation better.
Our Auditor app provides support for obtaining that both locally and via our https://attestation.app service.
See https://developer.android.com/training/articles/security-key-attestation… for information about key attestation.
It hasn't been updated for the latest revisions though. v3 already wasn't the latest. 5th generation Pixels launched with v4 attestation. So just bear in mind that already wasn't fully up-to-date/complete docs.
Can see we have the verified boot hash in the local (Auditor) and remote (https://attestation.app) verification output for Auditor. If they've expanded the information from key attestation, we'll be able to provide more. The verified device information section is from hardware.