Lumeta is pleased to announce the general availability of Lumeta 3.3.2, which introduces a variety of new features, chief among which is a new discovery type called Cloud Discovery. This release recommended for all Lumeta users.
Please be advised that a Command Center upgraded to Lumeta 3.3.2 is compatible with a Scout that has also been upgraded to Lumeta 3.3.2 only. See for the recommended sequence for upgrading.
|Upgrading to Lumeta 3.3.2|
|Upgrade Path||Upgrade Process||Upgrade Package|
3.3.0 to 3.3.1.x Command Center
|3.3.2 Command Center|
Lumeta 3.3.2 upgrade package
3.3.0 to 3.3.1.x Scout
3.3.0 to 3.3.1.x Portal
New and enhanced features introduced in the Lumeta 3.3.2 release include the following:
- FireMon Integration
The Lumeta Corporation, having recently been acquired by FireMon, is pleased to begin integrating our solutions. With this release, Lumeta can now ingest FireMon-managed devices. See FireMon Security Intelligence Platform for the configuration procedure and FireMon Management Dashboard to see sample results in a dashboard.
- Cloud Discovery
This 3.3.2 release features Cloud Discovery, a new discovery type designed to identify active networks and devices on the cloud providers AWS and Azure. This new discovery type identifies the presence of network assets active in a cloud infrastructure or in a combination of cloud and traditional infrastructure. Associated Cloud Discovery reports identify cloud devices by IP and MAC address, and report the zone in which each device is active, and provides a timestamp of when Lumeta first and most recently observed it as being active. See Active: Cloud to learn how to configure Lumeta Cloud Discovery.
- Cloud Discovery Support
To support for the use of Cloud Discovery, Lumeta has added a number of CLI and API commands. See for command-line syntax and examples. See Cloud API Calls for APIs.
- Cloud Reporting
- Providing a view into the results of this new discovery type are two new reports: AWS Devices and Azure Devices, which show the attributes of devices Lumeta found in an AWS or Azure cloud.
- Cloud is reported in the Device Info tab when the discovery type Lumeta used to find the device is Cloud Discovery.
- Cloud Discovery Support
To shorten and better organize the Dashboards menu, we've collapsed the Integrations options onto its own submenu and given manager-level users the option to customize or replace the Dashboard menu. To the Performance Metrics dashboard, we've added a new widget, and to the top-line Dashboard menu, we've added the dashboard described ahead.
- Integrations Submenu
Applications that can can be connected to Lumeta such as Carbon Black, FireMon and McAfee are now presented in their own Integrations submenu.
- User-created Dashboards
If you're a user with the manager or sysadmin role, you can also create an entirely new accordion-style dashboard menu. You can name a new dashboard menu option and then nest dashboards within it. Also, a single dashboard widget can be displayed on as many dashboards as you might like. See Creating the Dashboard Menu for more.
- Endpoint Trends Dashboard
This new dashboard provides snapshot counts of devices discovered and profiled in a 24-hour period. Read more and learn how to adjust the scanning interval here.
- Integrations Submenu
Queue Latency Widget
To the Performance Metrics dashboard, we've added a new widget called Queue Latency. Queue Latency is the delay before data processing begins following an instruction to process data.This widget will help you assess the health of the Lumeta system in terms of processing capacity—how long data sits waiting to be processed.
Average - Average time data files have been in the queue awaiting processing (aka queue latency)
Max - Maximum time data files have been in the queue awaiting processing
You can select which of these time metrics display on the widget by clicking on a colored circle to toggle that metric on or off. Notice that the scale of the Y-axis adjusts based on the range of change.
See Performance Metrics Dashboard for more on the Queue Latency Widget.
Export Historical Reports
Users now have the ability to export the reports that have been generated on a set schedule. See Exporting Dashboards & Reports for the procedure.
- PKI Improvement: OCSP Protocol
PKI user authentication now supports the use of Online Certificate Status Protocol (OCSP). OCSP (Online Certificate Status Protocol) is one of two common schemes for maintaining the security of a server and other network resources. See and to learn CLI and API methods.
- Zone-level Avoid List
release introduces a Zone-level Avoid List that enables you to set up an Avoid List that is honored by all collectors within a zone—not just one.
The zone-level Avoid List can be configured from the Lumeta GUI or CLI. See Adding & Managing Lists (Zone Networks & Discovery Spaces) for GUI procedures and Essential CLI Procedures for the CLI procedures.
- Data Retention - NACK Expansion
Lumeta's data retention policy is disabled by default. To enable the policy, send a request via the CLI. For more information on data retention in Lumeta, see Data Retention Policy.
- Data Expiration
Attributes - The attributes of devices discovered by Lumeta have been made to expire in 48 hours. Exceptions are made for user-created device attributes and system attributes, which are retained. This means, for example, that if a device responded with a sysDecsr of ABC at 9 a.m today, that response would expire in 48 hours. Whenever the device responds with a sysDescr, the clock resets and restarts the 48-hour countdown-to-expiry. This 48-hour expiration of attributes is default Lumeta behavior; it is not affected by any data retention settings you may have in place.
SNMP Credentials - Similarly, SNMP credentials to which a device no longer responds are expired in 48hours. This means that credentials that you've removed from the SNMP Credentials List get removed from Lumeta's response table by the system in 48 hours. The record of a device's responsiveness to SNMP credentials is more current and better maintained because the Lumeta system does not continue to use a credential that no longer elicits a response.
This release introduces four new password controls that you can view, enable, or disable via the Lumeta CLI and API. See Password Controls for more.
- Expanded Profile Data - Device profiles (including MAC addresses) have been added for firewall vendors. With this addition, newly discovered firewall devices are profiled with a greater degree of accuracy and confidence.
- External Data Connector (EDC): Device Ingestion
Device data external to Lumeta can be successfully ingested into Lumeta via API, incorporated into its data tables, and scanned in priority order. This feature provides a way to cue the additional scanning of addresses discovered through other means and via other systems. See for more. The Discovery Statistics by Discovery Type summary and detail reports indicate the devices that came into the Lumeta system from an external source.
- SWADLed 3.3.2 WADL
The "SWADLed" WADL of Lumeta 3.3.2 is provided here: The viewer provides you with a readable (not machine-readable), interactive Web Application Description Language (WADL) to Lumeta.
New pages added to this site for Lumeta 3.3.2 include the following
- Grouping & Highlighting by Custom Attribute
- Adding & Managing Labels & Custom Attributes
- Overwriting vs. Appending Custom Attributes
Data Retention - NACK
External Device Connector
OCSP & CRL
Upgrading to 3.3.2
Several issues reported by customers have been resolved.
On the Device Details and Notifications pages, the
|Provided zone-level avoid list feature requested by customers and described above in Features.||PO-6538|
|The generation of leak discovery targets now stops when Leak Discovery is disabled. This corrects disabled Leak Discovery from taking place.||PO-7850|
|Erroneous "untrusted certificate" message with "Accept this x15 API server certificate" label has been corrected and no longer appears when users log in.||PO-7891|
|Changed device type attributes, removed and grouped various profile patterns to enhance device profiling and reporting.||PO-8199|
Customer-reported issues pertaining to the gathering of ARP entries via SNMP have been resolved by changing the method by which Lumeta represents values such as 5c260a67510d so that the system correctly interprets them as a MAC address and not line breaks.
|To the Performance Metrics and Endpoint Trends dashboards, added labels to the Y-axis of widgets where missing. Also updated widget hover text.||PO-8732|
While creating Settings > Real Time Notifications, the Notification column was not populating as it should when the user opted to receive all notifications at every priority for selected zones. This has been fixed and is now working as expected.
Client was not seeing interface data in device details for a device that had interface data in the device file. This was remedied by adding code that incorporates interface addresses to a calculation.
|On the Dashboard Manager, the column sorting feature now works properly.|
|The labels on pie charts and bar chart widgets are difficult to read under some conditions such as when more than 30 items are represented or when labels are more than 18 characters in length. To work around this issue, please "zoom out" on your browser and, to the extent you can, keep labels short.||PO-7224|
We'll make you aware of any known issues and the work-arounds here.
|1||On Maps, the number of devices counted as having a particular custom attribute comes from the sum of all nodes—including expanded attached devices, layer 2 nodes, and nodes nested within groups. Nodes in the count are therefore not necessarily visible on the map. Please be aware that this cumulative method of counting is different from the way counts are done on the adjacent Active/Inactive tab, in which only visible devices represented on the map are counted.|
On the Command Center GUI of new or upgraded systems, uploading a file containing a cloud credential alias that matches an existing alias causes the new alias and attributes to overwrite the old alias and attributes.
|3||When you view a zone map from the read-only mode of Lumeta Portal, alert notifications do not display. This issue is under investigation.||PO-8759||9/24|
Custom attributes having unique label:value pairs do not upload to the Custom Attributes screen as expected.
Unable to export AWS device data in Browse Historical
In Reports > Browse Historical > View > Export, the Leaking Devices, Leaks by Direction and Leaks by Protocol reports do not display exported data in resulting CSV files as expected.
|7||The current password control settings restrict users from changing their password more often than once per day. The capability for users to reduce the frequency of password changes to not more than once in 3 days has not yet been implemented as planned.||PO-8695||9/24|
Lumeta 3.3.2 resolves Common Vulnerabilities & Exposures (CVEs) and incorporates a variety of security-related (and non-security-related) enhancements. See CVEs Fixed in Lumeta 3.3.2 for a preliminary list of resolved CVEs. A finalized listing will be made available post-GA.
Database Schema 3.3.2
Please see Change Log on Lumeta 3.3.2 for a listing of changes made in preparation for this Lumeta 3.3.2 release.