[\/et_pb_text][et_pb_text admin_label=”Intro” module_id=”1″ _builder_version=”4.27.5″ _module_preset=”default” background_color=”#f5f7fb” z_index=”0″ custom_margin=”||50px||false|false” custom_padding=”2%|2%|2%|2%|true|true” custom_css_main_element=”font-family:%22Pandora-Light%22;” border_radii=”on|10px|10px|10px|10px” locked=”off” global_colors_info=”{}”]<\/p>\n
There are two types of versions<\/a> in Pandora FMS: LTS (Long-Term Support)<\/strong> versions, such as 777 LTS \u00abAndromeda\u00bb, and FR (Feature Release)<\/strong> versions, such as 778, \u2026, 786. This update corresponds to 800 LTS.<\/p>\n LTS versions<\/strong> include frequent and periodic updates (fixes) that correct both security issues and critical bugs detected in the tool. These are the versions we recommend using in production environments. LTS versions<\/strong> are released approximately once a year.<\/p>\n FR versions<\/strong> incorporate new features, improvements, and bug fixes in each release. Due to their evolving nature, they may also include capabilities that are still maturing, as well as experimental features enabled through a setup token. These versions are released approximately every two months and are aimed at users who want to try new capabilities before they are consolidated in an LTS version.<\/p>\n [\/et_pb_text][et_pb_text admin_label=”Aviso” module_id=”1″ _builder_version=”4.27.5″ _module_preset=”default” background_color=”#fef6b2″ z_index=”0″ custom_margin=”0px||50px||false|false” custom_padding=”2%|2%|2%|2%|true|true” custom_css_main_element=”font-family:%22Pandora-Light%22;” border_radii=”on|10px|10px|10px|10px” locked=”off” global_colors_info=”{}”]<\/p>\n Notices<\/strong><\/p>\n This version introduces significant changes in the internal architecture of Pandora FMS. For this reason, we recommend following our upgrade guide from version 777 onwards<\/a> and contacting the support team if any issues arise during the process.<\/p>\n [\/et_pb_text][et_pb_divider color=”#eaeaea” divider_weight=”1px” admin_label=”=== SEPARADOR 1 ===” module_id=”1″ _builder_version=”4.22.0″ _module_preset=”default” z_index=”0″ module_alignment=”center” custom_margin=”0px||0px||true|false” custom_padding=”0px||20px||false|false” border_color_all=”#eaeaea” locked=”off” global_colors_info=”{}”][\/et_pb_divider][et_pb_text admin_label=”Novedades desde la anterior LTS” module_id=”1″ _builder_version=”4.27.5″ _module_preset=”default” z_index=”0″ custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||true|false” custom_css_main_element=”font-family:%22Pandora-Light%22;” locked=”off” global_colors_info=”{}”]<\/p>\n The following changes were introduced in versions 778, 779, 780, 781, 783, 784, 786 and 800.<\/strong><\/p>\n Pandora SIEM is a fully integrated solution that adds a Security Information and Event Management (SIEM)<\/strong> system to the monitoring capabilities of Pandora FMS.<\/p>\n Pandora FMS agents collect information that can now be normalized in order to generate specific security events through the SIEM rules engine. Pandora SIEM can also process information received via syslog<\/strong> by the Pandora FMS Syslog Server<\/strong>.<\/p>\n The Pandora FMS SIEM engine is extensible by users. Custom processing and normalization rules can be defined, as well as event generation rules. This allows the integration of any type of application or appliance that generates security-related information. Pandora SIEM operates independently from raw log collection, which continues to be stored in parallel.<\/p>\n The Pandora FMS SIEM interface allows users to visualize information through several dashboards<\/strong>, an event viewer with filtering capabilities, and a visual management interface for available decoders and rules. Pandora SIEM is partially compatible with Wazuh decoders and rules<\/strong>.<\/p>\n A complete functionality for remote system management has been incorporated, based on the software agent (PFMS EndPoint)<\/strong>. A new executable, included with this updated version of the agents, allows immediate management and information gathering from groups of systems connected to the server.<\/p>\n The RMM (Remote Monitoring and Management)<\/strong> functionality allows patching MS Windows\u00ae<\/strong> systems, updating packages in Linux\u00ae<\/strong>, restarting systems and services, among other operations. It is extensible by users to run custom scripts and supports bulk actions as well as alert-triggered execution.<\/p>\n We have created a new website to replace the plugin library, offering improved search capabilities and smoother integration with the Pandora FMS console. It allows not only plugins to be downloaded directly into Discovery, but also report templates, policies, and other configuration items.<\/p>\n The new site is now available at: marketplace.pandorafms.com<\/a><\/p>\n We will continue improving this portal to provide new useful components.<\/p>\n As part of the expansion of Pandora FMS security monitoring capabilities, a new File Integrity Monitoring (FIM)<\/strong> feature has been incorporated.<\/p>\n It will be available for MS Windows\u00ae and Linux\u00ae agents<\/strong> running at least version 784<\/strong>, and it will work together with SIEM event monitoring<\/strong> in environments where it is enabled. It allows integration with dynamic IOCs<\/strong>, so that alerts can be generated through file hashing<\/strong> when new files appear on any endpoint.<\/p>\n The operation and interface of network discovery from the Pandora FMS server have been improved, making it smarter and providing more information by default.<\/p>\n It is now possible to create discovery tasks without the need to specify multiple parameters, as well as configure more complex tasks to automatically discover networks or run specific scans.<\/p>\n In addition, the process now includes different phases, which are completed progressively and can be viewed from the Pandora FMS console.<\/p>\n A provisional network map can also be displayed while the scan is in progress, as well as with the final result, making it easier to review the discovered devices. This network map can also be created automatically from the task in the Topological Maps<\/strong> section of the Web Console<\/strong>.<\/p>\n Improvements, fixes, and changes have been introduced in the generation and rendering of network maps.<\/p>\n Among the most notable features is the representation of network maps, which will include two visible and delimited areas: one representing the visible area in the minimap, and a larger area with limits that cannot be exceeded (for maps that are larger and require more space).<\/p>\n Regarding map generation, the network map context menu now includes two options: one to load newly discovered nodes into the network map, and another to redraw the position of the elements already present in the network map. Neither option now removes elements or relationships created by the user within the map, preserving any custom configuration that has been defined.<\/p>\n New inventory modules have been added and the existing ones in MS Windows\u00ae agents<\/strong> have been improved to monitor installed software and installed patches on the system.<\/p>\n As a result of these changes, vulnerability monitoring has also been improved for both Windows and Linux software agents<\/strong>, displaying more information<\/strong> and expanding the existing vulnerability database.<\/p>\n Related to the previous point, and integrated with the Pandora FMS RMM<\/strong> capabilities, it will be possible to schedule the update and installation of Microsoft\u00ae patches<\/strong> with a click in order to remediate vulnerabilities detected by the monitoring system that can be fixed through official Microsoft\u00ae patches<\/strong>.<\/p>\n Administrators will be able to install Pandora ITSM<\/strong> directly from the Pandora FMS Web Console<\/strong>, with the system fully configured and ready to use<\/strong>. This installation is carried out entirely within Pandora FMS, so there is no need for an additional server or extra configuration.<\/p>\n Pandora FMS includes a default alert command for sending notifications via Telegram FZ-LLC\u00ae<\/strong>. Until now, this command required a token to be configured by manually editing the command itself.<\/p>\n To simplify its management, a new field has been added to the General Configuration<\/strong>, allowing this token to be updated centrally.<\/p>\n In order to simplify and streamline the deployment of the most essential monitoring, new agents created from the Web Console<\/strong> will include automatically generated default monitoring (Host Alive<\/strong> and Network Latency<\/strong>). This option can be disabled when creating an agent, if preferred.<\/p>\n To match the event view as closely as possible, a new report element type has been added, allowing events to be filtered in a way that closely mirrors the event view itself.<\/p>\n This type of report element will replace the event report elements used up to now in future versions.<\/p>\n The credential store<\/strong> allows sets of usernames and passwords to be configured for different types of monitoring. They could already be used in Discovery<\/strong>; they can now also be used for standard WMI monitors<\/strong>.<\/p>\n We continue adding endpoints to the new Pandora REST API 2.0<\/strong>, incorporating ITSM<\/strong> and SIEM<\/strong> endpoints, as well as expanding some of the existing ones.<\/p>\n The following changes were introduced in versions 784 and 785.<\/strong><\/p>\n The most significant change introduced is the new internal architecture of the Pandora FMS server. This refers to the processes available in the server and the distribution of the different types of monitoring across them.<\/p>\n This is an important change that modifies the distribution of monitoring threads<\/strong>. The objective is to unify tasks of a similar nature<\/strong> in order to optimize the use of server resources and avoid the need to deploy environments with unnecessarily high requirements.<\/p>\n The most visible change is the removal of the following servers, whose functionalities are now handled by other servers:<\/p>\n And the introduction of the following servers, which will assume the tasks previously handled by them:<\/p>\n The Network Server<\/strong> will handle the following types of monitoring:<\/p>\n The Network High Performance Server<\/strong> replaces the former ICMP Enterprise Server<\/strong> and SNMP Enterprise Server<\/strong>, taking over ICMP and SNMP monitoring tasks (only for numeric values) and allowing modules to be executed at much shorter polling intervals (e.g., 15 seconds<\/strong>).<\/p>\n The Heavy Server<\/strong> will handle the following types of monitoring:<\/p>\n The complete list of servers is therefore as follows:<\/p>\n These changes mean that tasks which previously had dedicated threads will now share the execution queue with other elements. The main advantage of this change is that it removes the need to allocate dedicated servers and threads to monitoring groups that may represent only a small portion of the workload.<\/p>\n For example, if an environment had very little WMI monitoring but a large amount of ICMP or SNMP monitoring, it was still necessary to allocate at least one server with one full thread exclusively for WMI monitoring. By unifying these tasks in the same queue, the same resources of the Network Server<\/strong> can now handle all monitoring workloads.<\/p>\n In line with the previous point and the new architecture, Pandora FMS can now execute basic network checks with polling intervals of up to 15 seconds<\/strong> (under certain conditions). This applies to centralized servers; the Satellite Server<\/strong> has always been able to perform checks with polling intervals of up to one second<\/strong>, when required.<\/p>\n In the update procedure through WARP<\/strong>, there was a limitation that in some cases required the pandora_server<\/strong> process to be restarted manually in order to complete the update.<\/p>\n From this version onwards, this will no longer be necessary in most cases, as a process called pandora_supervisor<\/strong> has been incorporated to perform this action automatically when the server is updated through WARP<\/strong>.<\/p>\n This change will be transparent to Pandora FMS users, who will not need to perform any additional configuration.<\/p>\n All Pandora FMS services have been fully migrated to SystemD<\/strong>, removing the previous startup scripts.<\/p>\n It is now possible to configure an agent so that the execution of its modules is automatically balanced across the available remote servers.<\/p>\n Regarding high availability (HA)<\/strong>, it will also be possible to enable or disable it for agents, providing greater configuration flexibility in distributed environments.<\/p>\n Some Console options, such as the SNMP wizard<\/strong>, allow requests to be made from a different server, for example a Satellite Server<\/strong>.<\/p>\n This functionality was handled through the Exec Server<\/strong>, which previously had to be configured manually.<\/p>\n From now on, it will be possible to configure a reverse SSH tunnel<\/strong> directly from the console for any Satellite Server<\/strong> or Pandora FMS Server<\/strong> by entering just a few required parameters. This tunnel will be used for actions performed through the Exec Server<\/strong>.<\/p>\n Along with the previous functionality, some options have been added for Satellite Servers<\/strong> to simplify their management and enhance their capabilities. The most notable are:<\/p>\n It should be taken into account that, due to these new functionalities, users who deployed monitoring for their Satellite agents<\/strong> through policies will need to redefine those modules using the new forms.<\/p>\n The following changes were introduced in versions 778, 784 and 800.<\/strong><\/p>\n Pandora FMS is now compatible with RHEL 9<\/strong> and Rocky Linux 9<\/strong> operating systems.<\/p>\n Pandora FMS now provides official support for MySQL 8.4<\/strong>, subject to the following considerations:<\/p>\n The Pandora FMS Web Console<\/strong> is compatible with and supported on PHP 8.4<\/strong>.<\/p>\n With this new LTS version, support for SNMPv3 monitoring<\/strong> has been improved by adding AES<\/strong> and SHA 256\/512<\/strong>, resulting in the following supported methods:<\/p>\n The following changes were introduced in versions 785, 786 and 800.<\/strong><\/p>\n In order to improve the usability of the tool, both the Web Console<\/strong> and the Command Center<\/strong> have been reviewed and updated.<\/p>\n This is not just an aesthetic change<\/strong>, as some menu sections have been reorganized to improve interface usability. In addition, the main filters have been reorganized into a new side menu system, providing more workspace in the main views.<\/p>\n These changes are especially noticeable in the Console\u2019s dark theme, where the color palette has been completely changed.<\/p>\n In line with the previous point, we continue working on the modernization of the application interface. In this phase, all icons used in the visual consoles<\/strong> have been redesigned.<\/p>\n If the previous icon set is required, it can be found in our Marketplace<\/a>. During migrations, the previous images can be preserved by copying the image directory (see the migration guide for more details).<\/p>\n In some environments, licenses had expired without users noticing until a couple of days later.<\/p>\n To prevent these situations from leading to more serious issues, we have added a highly visible notice in the console to indicate the status of licenses that are close to expiring or have already expired.<\/p>\n The following changes were introduced in versions 778, 780, 782, 784, 785 and 786.<\/strong><\/p>\n Permission checks in Dashboards<\/strong> have been modified for both management and visualization, specifically at the widget level.<\/p>\n With a new monitor type, ready to retrieve information from any standard REST API<\/strong>.<\/p>\n A new API endpoint is also included to queue monitoring data as an alternative to sending it through XML files.<\/p>\n In version 780<\/strong>, the future discontinuation of XML reports<\/strong> in the Pandora FMS console was announced, and this became effective in version 782<\/strong>. Our roadmap already includes the creation of reports in JSON<\/strong> format, using the new reporting engine currently under development.<\/p>\n Traditionally, the software installed on Linux<\/strong> and MS Windows<\/strong> systems for local monitoring has simply been called an Agent<\/strong>, just like the entity used in the Pandora FMS console to represent each monitored system.<\/p>\n This caused confusion in certain cases, so from now on we will use the term Endpoint<\/strong> to refer to what was traditionally called the software Agent<\/strong>.<\/p>\n To make Pandora FMS installation packages lighter, all PFMS Discovery<\/strong> packages have been removed from the automatic distribution.<\/p>\n This does not mean that these packages will no longer be available, as they can still be accessed through the Pandora FMS Marketplace<\/strong>, either from a web browser or through the connection directly integrated into the Pandora FMS Console<\/strong>.<\/p>\n This change only means that the code of those .disco<\/strong> packages will no longer be updated automatically with each new version, and will instead need to be updated from the Pandora FMS Web Console<\/strong>.<\/p>\n Due to the improvements being made in Satellite Server<\/strong> management, we have temporarily removed two interface sections for complete renewal: Satellite mass operations<\/strong> and Satellite credential boxes management<\/strong>.<\/p>\n They will be available again soon with optimized functionality.<\/p>\n [\/et_pb_text][et_pb_divider color=”#eaeaea” divider_position=”center” divider_weight=”1px” admin_label=”=== SEPARADOR 2 ===” module_id=”2″ _builder_version=”4.27.5″ _module_preset=”default” z_index=”0″ module_alignment=”center” custom_margin=”0px||0px||true|false” custom_padding=”75px||75px||true|false” border_color_all=”#eaeaea” locked=”off” global_colors_info=”{}”][\/et_pb_divider][et_pb_text admin_label=”Otras funcionalidades y mejoras desde la anterior LTS” module_id=”1″ _builder_version=”4.27.5″ _module_preset=”default” z_index=”0″ custom_margin=”0px||0px||true|false” custom_padding=”0px||0px||true|false” custom_css_main_element=”font-family:%22Pandora-Light%22;” locked=”off” global_colors_info=”{}”]<\/p>\n For further features and improvements, please refer to the release notes for each version:<\/p>\n 778<\/a><\/strong><\/p>\n 779<\/a><\/strong><\/p>\n 780<\/a> \/ 781<\/a><\/strong><\/p>\n 782<\/a><\/strong><\/p>\n 783<\/a><\/strong><\/p>\n 784<\/a><\/strong><\/p>\nNew features<\/h2>\n
Improvements and new features since the previous LTS<\/h3>\n
Pandora SIEM<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-06-2.jpg\")
<\/p>\nRemote Management and Monitoring (RMM)<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-09.jpg\")
<\/p>\nNew Pandora FMS Marketplace<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-07-2.jpg\")
<\/p>\n![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-08-2.jpg\")
<\/p>\nNew security monitoring feature \u2013 FIM (File Integrity Monitoring)<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-10.jpg\")
<\/p>\nNetwork scanning in Discovery<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-11.jpg\")
<\/p>\n![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-12.jpg\")
<\/p>\nNetwork maps<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-13-2.jpg\")
<\/p>\nImprovements in vulnerability monitoring<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-14.jpg\")
<\/p>\nMicrosoft\u00ae patch management from vulnerability monitoring<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-15.jpg\")
<\/p>\nPandora ITSM installation from the Pandora FMS console<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-16.jpg\")
<\/p>\nTelegram alert configuration<\/h4>\n
Automatic default monitoring for new agents<\/h4>\n
New report element: Event list<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-17.jpg\")
<\/p>\nUse of stored credentials in WMI monitoring<\/h4>\n
New endpoints for API 2.0<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-22.jpg\")
<\/p>\nArchitecture changes since the previous LTS<\/h3>\n
Changes in the PFMS server architecture<\/h4>\n
\n
\n
\n
\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-01.jpg\")
<\/p>\nNew high-performance server for short polling intervals<\/h4>\n
New process: pandora_supervisor<\/h4>\n
Complete startup migration to SystemD<\/h4>\n
Automatic load balancing in remote checks<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-02.jpg\")
<\/p>\n![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-03.jpg\")
<\/p>\nExec Server – Automatic configuration of a reverse SSH tunnel<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-04.jpg\")
<\/p>\nImprovements and changes in Satellite configuration<\/h4>\n
\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-05.jpg\")
<\/p>\nVersion support since the previous LTS<\/h3>\n
Pandora FMS compatibility with RHEL 9 and Rocky Linux 9<\/h4>\n
MySQL 8.4 compatibility<\/h4>\n
\n
PHP 8.4 compatibility<\/h4>\n
Support for security protocols in SNMPv3<\/h4>\n
\n
Visual changes since the previous LTS<\/h3>\n
Revised graphical interface<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-18-2.jpg\")
\n![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-19-2.jpg\")
\n![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-20.jpg\")
<\/p>\nUpdated icons for Visual Console<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-23.jpg\")
<\/p>\nLicense status notification<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-21.jpg\")
<\/p>\nOther relevant changes since the previous LTS<\/h3>\n
Permission changes in Dashboards<\/h4>\n
\n
Native API monitoring<\/h4>\n
![\"Pandora](\"https:\/\/pandorafms.com\/wp-content\/uploads\/2026\/03\/800-24.jpg\")
<\/p>\nDiscontinuation of XML reports<\/h4>\n
Terminology change \u2013 Endpoint<\/h4>\n
All .disco packages removed from automatic distribution<\/h4>\n
Temporarily removed sections<\/h4>\n
Other features and improvements<\/h2>\n
\n
\n
\n
\n
\n
\n