# US 12,603,755 B2 · Remote attestation with remediation > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,603,755 B2 - Document ID: US12603755B2 - Status: Granted - Kind: B2 - Application number: 18/624,575 - Filed: 2024-04-02 - Published: 2025-03-27 - Granted: 2026-04-14 - Earliest claimed: 2023-09-21 - Assignees: Denso Corporation - Applicants: Denso Corporation - Inventors: Ameer Kashani; Carlos Mora-Golding; Yasuharu Sugano; Tomonori Ikuse; Madoka Asai - Web page: https://patentgrep.com/patent/US12603755B2 ## CPC - H04L 9/008: {involving homomorphic encryption} - H04L 9/3236: {using cryptographic hash functions} - H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD} - H04L 9/3247: {involving digital signatures} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L 2209/84: Vehicles - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Systems, methods, and other embodiments described herein relate to remote attestation using a homomorphic hash. In one embodiment, a method includes identifying software components and associated metrics of the software components executing within a computing system of a vehicle according to a policy. The method includes constructing a tree according to the software components and partitions within the software components. The method includes storing, in leaf nodes of the tree, measurements of the metrics. The parent nodes define a hierarchical relationship between software components and the partitions. The method includes generating an incremental hash of the tree. The method includes providing the incremental hash as a secure representation of the software components. ## Claims ### Claim 1 A security system, comprising: one or more processors; a memory communicably coupled to the one or more processors and storing: a control module including instructions that, when executed by the one or more processors, cause the one or more processors to: identify software components and associated metrics of the software components executing within a computing system of a vehicle according to a policy; construct a tree according to the software components and partitions within the software components; store, in leaf nodes of the tree, measurements of the metrics, wherein parent nodes define a hierarchical relationship between software components and the partitions; generate an incremental hash of the tree; provide the incremental hash as a secure representation of the software components; and update the tree and the incremental hash by recomputing hashes at parent nodes of the tree associated with changes in the metrics and adapting the incremental hash according to the changes. ### Claim 2 (depends on 1) The security system of claim 1, wherein the instructions further include instructions to measure the metrics at defined times according to the policy, wherein the policy defines the partitions within the software components, a criticality of the software components, and the defined times for refreshing the metrics. ### Claim 3 (depends on 1) The security system of claim 1, wherein the instructions further include instructions to, responsive to receiving an attestation request, provide a root hash that is the incremental hash from the tree; and wherein the instructions further include instructions to communicate with a remote device to provide requested hashes of the parent nodes when the root hash fails to match a reference hash stored at the remote device, wherein the instructions to communicate the requested hashes of the parent nodes facilitate the remote device tracing an integrity failure in one of the software components. ### Claim 4 (depends on 3) The security system of claim 3, wherein the instructions further include instructions to mitigate the integrity failure from an attack according to a mitigation deployment received from the remote device, wherein the mitigation deployment is a control to the vehicle that causes the vehicle to perform one or more of restore the software components to a prior state using a system image and instantiate a failsafe mode within the vehicle. ### Claim 5 (depends on 1) The security system of claim 1, wherein the instructions to generate the incremental hash include instructions to iteratively combine hashes from the parent nodes until reaching a root node that includes a root hash by combining hashes from the parent nodes in the tree, wherein the tree is a Merkle tree, and wherein the incremental hash is a homomorphic hash. ### Claim 6 (depends on 1) The security system of claim 1, wherein the metrics are measurements of one or more of: static data and dynamic data within the vehicle as defined by the policy. ### Claim 7 (depends on 1) The security system of claim 1, wherein the instructions further include instructions to analyze characteristics of the vehicle according to a mitigation model when the vehicle is identified as being subject to an integrity failure to generate a prediction about whether additional vehicles and which vehicles may be impacted by an attack associated with the integrity failure. ### Claim 8 (depends on 1) The security system of claim 1, wherein the security system is embedded within a vehicle and performs attestation for a relying party using the incremental hash. ### Claim 9 A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to: identify software components and associated metrics of the software components executing within a computing system of a vehicle according to a policy; construct a tree according to the software components and partitions within the software components; store, in leaf nodes of the tree, measurements of the metrics, wherein parent nodes define a hierarchical relationship between software components and the partitions; generate an incremental hash of the tree; provide the incremental hash as a secure representation of the software components; and update the tree and the incremental hash by recomputing hashes at parent nodes of the tree associated with changes in the metrics and adapting the incremental hash according to the changes. ### Claim 10 (depends on 9) The non-transitory computer-readable medium of claim 9, wherein the instructions further include instructions to measure the metrics at defined times according to the policy, wherein the policy defines the partitions within the software components, a criticality of the software components, and the defined times for refreshing the metrics. ### Claim 11 (depends on 9) The non-transitory computer-readable medium of claim 9, wherein the instructions further include instructions to, responsive to receiving an attestation request, provide a root hash that is the incremental hash from the tree; and wherein the instructions further include instructions to communicate with a remote device to provide requested hashes of the parent nodes when the root hash fails to match a reference hash stored at the remote device, wherein the instructions to communicate the requested hashes of the parent nodes facilitate the remote device tracing an integrity failure in one of the software components. ### Claim 12 (depends on 11) The non-transitory computer-readable medium of claim 11, wherein the instructions further include instructions to mitigate the integrity failure from an attack according to a mitigation deployment received from the remote device, wherein the mitigation deployment is a control to the vehicle that causes the vehicle to perform one or more of restore the software components to a prior state using a system image and instantiate a failsafe mode within the vehicle. ### Claim 13 (depends on 9) The non-transitory computer-readable medium of claim 9, wherein the instructions to generate the incremental hash include instructions to iteratively combine hashes from the parent nodes until reaching a root node that includes a root hash by combining hashes from the parent nodes in the tree, wherein the tree is a Merkle tree, and wherein the incremental hash is a homomorphic hash. ### Claim 14 A method, comprising: identifying software components and associated metrics of the software components executing within a computing system of a vehicle according to a policy; constructing a tree according to the software components and partitions within the software components; storing, in leaf nodes of the tree, measurements of the metrics, wherein parent nodes define a hierarchical relationship between software components and the partitions; generating an incremental hash of the tree; providing the incremental hash as a secure representation of the software components; and updating the tree and the incremental hash by recomputing hashes at parent nodes of the tree associated with changes in the metrics and adapting the incremental hash according to the changes. ### Claim 15 (depends on 14) The method of claim 14, further comprising: measuring the metrics at defined times according to the policy, wherein the policy defines the partitions within the software components, a criticality of the software components, and the defined times for refreshing the metrics. ### Claim 16 (depends on 14) The method of claim 14, further comprising: responsive to receiving an attestation request, providing a root hash that is the incremental hash from the tree; and communicating with a remote device to provide requested hashes of the parent nodes when the root hash fails to match a reference hash stored at the remote device, wherein communicating the requested hashes of the parent nodes facilitates the remote device tracing an integrity failure in one of the software components. ### Claim 17 (depends on 16) The method of claim 16, further comprising: mitigating the integrity failure from an attack according to a mitigation deployment received from the remote device, wherein the mitigation deployment is a control to the vehicle that causes the vehicle to perform one or more of restore the software components to a prior state using a system image and instantiate a failsafe mode within the vehicle. ### Claim 18 (depends on 14) The method of claim 14, wherein generating the incremental hash includes iteratively combining hashes from the parent nodes until reaching a root node that includes a root hash by combining hashes from the parent nodes in the tree, wherein the tree is a Merkle tree, and wherein the incremental hash is a homomorphic hash. ### Claim 19 (depends on 14) The method of claim 14, wherein the metrics are measurements of one or more of: static data and dynamic data within the vehicle as defined by the policy. ### Claim 20 (depends on 14) The method of claim 14, further comprising: analyzing characteristics of the vehicle according to a mitigation model when the vehicle is identified as being subject to an integrity failure to generate a prediction about whether additional vehicles and which vehicles may be impacted by an attack associated with the integrity failure.