This article will examine the methods employed by the Heimdal Agent to identify and resolve issues affecting its operation, and how the self-healing mechanism functions.
Heimdal.MonitorService
This independent service monitors the operational status of other Heimdal services every 60 seconds. If any service is found not running, the Heimdal.MonitorService will automatically restart it. Additionally, it checks the digital signatures of all services to confirm they haven’t been tampered with by malicious entities.
Self-Update Mechanism
Operating as a standalone service, the self-update mechanism ensures stability by not being affected by issues in other services. For instance, if the HeimdalClientHost service encounters a problem post-update and crashes, the self-update service remains unaffected.
HeimdalSecurityServiceMonitor
Upon triggering a self-update, a new task named HeimdalSecurityServiceMonitor is created. This task ensures that the self-update process resumes and completes after disruptions such as a reboot or internet failure. Once the update is successfully implemented, the task is removed.