Skip to main content

How to Update Monarx Sofware to the Latest Version

S
Written by Salvador Aguilar
Updated today

Keeping your Monarx components updated ensures your infrastructure is protected by our latest AI detection models and performance optimizations. Depending on your technical workflow, you can update manually via the command line or through automated orchestration.

The update process is divided into two parts: the core file-scanning agent and the ThreatShield RASP module.

Updating the Monarx Agent (Antivirus)

The monarx-agent is the core service responsible for on-disk file scanning and background remediation.

For RHEL-Based Systems (CloudLinux, AlmaLinux, Rocky Linux, CentOS)

# Update the Core Antivirus Agent 
yum update monarx-agent-autodetect

For Debian and Ubuntu LTS Systems

# Update local index and upgrade the agent 
sudo apt-get update; sudo apt-get install --only-upgrade monarx-agent-autodetect

2. Updating Monarx Protect (ThreatShield)

The monarx-protect-autodetect package manages the ThreatShield RASP module, which secures your PHP runtime.

For RHEL-Based Systems (CloudLinux, AlmaLinux, Rocky Linux, CentOS)

# Update the ThreatShield RASP Module 
yum update monarx-protect-autodetect

For Debian and Ubuntu LTS Systems

# Update local index and upgrade the RASP module 
sudo apt-get update; sudo apt-get install --only-upgrade monarx-protect-autodetect

3. Automated Fleet Management (Infrastructure as Code)

For hosting providers managing large-scale infrastructure, manual updates are often replaced by automation. Because Monarx uses standard .rpm and .deb packages, it integrates seamlessly with modern DevOps tools:

  • Ansible: You can create playbooks that target your entire server fleet to ensure both monarx-agent-autodetect and monarx-protect-autodetect are set to the latest state.

  • Puppet & Chef: Define the Monarx packages in your manifests to maintain version consistency across all nodes automatically.

  • Terraform: Ensure that your "golden images" or cloud-init scripts are configured to pull the latest versions during the provisioning phase of new server instances.

4. Scheduled Updates

If you prefer a "set and forget" approach without full orchestration, you can schedule the update commands via a cron job. This ensures your servers check for and apply updates during low-traffic windows (e.g., weekly at 3:00 AM).

Pro-Tip: When updating ThreatShield (monarx-protect-autodetect), the system will automatically attempt to update the Zend module for all detected PHP versions. It is good practice to verify your PHP status after a bulk update to ensure seamless execution.

Did this answer your question?