Remote Triggered Self Patch Management
The Healthjump Cloud Agent supports a command line argument that enables an upgrade-in-place process of the installed agent so that it retains the agent secret key, Client ID, and License Key configuration on the system. This allows upgrades and patches to be installed with zero impact to the production processes.
Healthjump constantly monitors the Windows Server landscape for new threats that could pose a risk to the Agent's already strict security protocols. In the event a new Windows vulnerability agent patch is required to maintain the Healthjump security protocols, Healthjump would apply a mass update to circumvent the vulnerabilities of the agent to the host server environment. While Healthjump constantly prepares for this event, to date, this event has never been triggered.
Most agent updates are intended to add functionality and features to the agent. These updates do not trigger updates to existing agents.
Version updates to the agent are typically a year apart, and not only include all of the previous year's patches, but may introduce performance and stability features that could be important to the Healthjump Customer product. These updates will not trigger an automated update, but may be discussed with the Healthjump customer for planning and deployment if necessary.
If a customer or practice does not want Healthjump to trigger a self-update of any kind without consent, the Healthjump customer / practice's Client Success Manager can be notified to note the agent to force consent prior to updates.
Security based patches will be communicated via Email to the Healthjump customer, and once vetted and approved, can subsequently be updated.