This second update in the month of September brings to you the following valuable enhancements: Publish patches to multiple endpoint management systems: Up until now, you were able to publish SPS and VPM patches to a single endpoint management system, for example, Microsoft ConfigMgr, VMware Workspace ONE, etc configured in the SVM Patch Publisher using the Create Update Package Wizard. This update enables you to select multiple connections configured for each endpoint management system or a tenant, in the case of a cloud solution like Intune, and publish patches to all the selected connections at the same time. If your environment has more than one endpoint management system targeting different geographical locations, devices or migrating from one to the other, this capability will help you select all your systems and publish patches at once saving you time and repetitive work. QuickPatch and subscribing patches for automation also provide the ability to select connections to publish patches. Scan cloud storage solutions without triggering downloads: You can now scan files on the cloud storage solutions like OneDrive, Dropbox, etc without downloading the files on the device. The Windows and Mac scan agents will not trigger the download of files during scanning. Such files will not be seen in the scan result as those files will not be physically available on the device. To see the full release notes, please click here. ... View more

This new update to SVR adds the following enhancements: New Status column on the Software Suggestion page: A new Status column on the Software Suggestion page displays the status of your software suggestion requests. A status of Completed indicates the suggested software is added to SVR. Enhanced Product API: The Product API (/api/products/) will now return a new data column vt_id and supports a new data filter vt_id. The vt_id is an internal unique identifier assigned to each product in SVR. This value is now also shown in the user interface as "ID" in response to customer demand as shown below.     To see the full release notes, please click here.   ... View more

This new update of SVM Cloud and the new version of SVM Patch Publisher (v7.3.79) brings to you the following new features: Inventory-Based Vulnerability Assessment SVM’s current capability of file-level-based assessment provides definitive, actionable insights about the vulnerability status of a specific version of software on your endpoints. We are now introducing an alternative inventory-based assessment. You can import a software inventory, in the form of a CSV file, in SVM for vulnerability assessment. This beta feature of SVM can provide directional (less definitive) inventory results depending largely upon the detail of the version information contained in the supplied inventory data. For more information on Inventory Assessment and future plans, please click here. Send a request to AdminStudio to create a patch AdminStudio is an industry de-facto tool for producing the best quality packages to achieve reliable deployment to endpoints. In the Bring Your Own Patch (BYOP) view of SVM Patch Publisher, you will be able to send a request to AdminStudio for creating patches for the products which are not covered by SPS and VPM patches. Right-click on a product for which you wish to send a request to AdminStudio for creating a patch and click on the menu option Request Patch. The new Service Connection view under the Settings menu provides options to establish a connection between SVM and AdminStudio. Active Directory Scan in the SVM’s New Web Interface you can configure Active Directory scan and use the schedule options to set Active Directory scans at selected intervals using the daemon. To see the full release notes, please click here. ... View more

The actionable SVM’s vulnerability assessment results are achieved by performing a file-level scan against special criteria we have identified (referred to as a file signature). This capability provides definitive, actionable insights about the vulnerability status of a specific version of software on your endpoints. Such results require the SVM scanner to be executed on desired endpoints. Often this is achieved by running a scheduled task with an endpoint management solution like ConfigMan, Intune, or Workspace ONE. Alternatively, the scanner may be installed as an agent.   However, we are often asked by our customers if an assessment may be made against existing software inventory data to avoid the need to run scans on endpoints. While a file-based scan using our file signatures will always provide the best possible results, we are introducing an alternative inventory-based assessment. This beta feature of SVM can provide directional (less definitive) inventory results depending largely upon the detail of the version information contained in the supplied inventory data. An inventory-based vulnerability assessment may be desired if: You are looking for directional assessment information to determine the security risk of software titles not being scanned. There may be some devices, such as servers, which might be excluded from scans in some environments. In an M&A situation, you may wish to scan against inventory data taken from another environment to get an initial impression of risk prior to rolling out the SVM scanner. A file signature-based assessment does not identify products for which there are no file signatures. Without comparing inventory data against scan results, it can be difficult to identify software not being scanned. An inventory-based assessment will report any unknown software for investigation. You can now import a software inventory in SVM for vulnerability assessment. Inventory data is easily exported to a CSV file from endpoint management systems like Microsoft ConfigMgr, Intune, Workspace ONE, or software inventory and asset management solutions like Flexera FNMS. SVM accepts a simple CSV file for inventory import. While it may include additional columns disregarded by the scan, the CSV file must contain the columns, product, vendor, and version. Rename the appropriate columns at the start of your CSV file to match these specific names if necessary, before importing.   Click on Import Inventory to browse to a CSV file that contains the inventory. You may import multiple inventory files into SVM. To better identify those inventories, they may be named upon import (a default name is populated to match that of the CSV file name). After an inventory is imported successfully in SVM, you will see it assigned one of the following statuses: In Queue – The inventory has been imported successfully, but the inventory has not yet been assessed. Refresh this screen later to see if it has changed. In Progress – A job running on the SVM server has picked up the inventory file and is performing the assessment. Success – The inventory assessment is completed, and the results are available. Failed – Inventory assessment failed. Some reasons for the failed assessment include: the product name was missing in all the inventory records, the column names of the CSV file were named incorrectly, etc. Determining the vulnerability status of software based on inventory information can be challenging due to a lack of detail (especially when a full, detailed, version number is required to determine security status and inventory reports seldom include such detail. To better account for the less definitive nature of inventory-based assessment, the following statuses have been introduced for inventory-based assessment: Potentially Insecure: These products have a version number that is incomplete, and what is provided is less than the known secure version. For example, v2.2.4 is secure, and inventory only reports v2 v3.8.1.3 is secure, and inventory only reports v3.8.1 Unknown: These products are either not matching correctly or are not currently being tracked by SVM.       Limitations and Future Enhancements: This new Inventory Assessment capability is in beta. Please play with it and provide feedback in the SVM Discussion Forums as we plan to enhance this feature in future releases. Currently planned enhancements include: The Unknown Results tab displays the list of products not matching or supported by SVM. A new option will be introduced to suggest select products from this list for consideration. The current inventory assessment may result in an elevated number of unknown products due to the limitations of matching to provided software titles. We are planning to leverage Flexera's Data Normalization capability to achieve better matching and assessment results in the future.  The ability to delete, re-assess and edit imported inventory data. The introduction of new Smart Group attributes to cover inventory-based assessment results We would love to hear any feedback or ideas you may have to improve this evolving inventory assessment capability to better serve you. Please submit your ideas on the Flexera Idea portal or discuss in the SVM Discussion Forum.  ... View more

AdminStudio 2022 Service Pack 1 is live now. This minor release includes: Repackager, Automated Application Converter (AAC), and the Conversion Wizard in Application Manager now support Windows Services for MSIX Packages. A Windows Service installed while converting a legacy package format (MSI/EXE), using any of the mentioned tools, will be captured and packaged into the MSIX package upon conversion. Few important security and customer-reported bug fixes. To see full release notes, please click here. AdminStudio 2021 R2 SP1 is available for download from the Product and License Center. ... View more

A new update on SVM Cloud and a new version of SVM Patch Publisher (v7.2.785) is released today. This new version of the SVM Patch Publisher enables you to suggest software that is not detected by SVM. A new button is introduced in the ribbon to suggest software. Clicking on the Suggest Software button will launch the SVM Software Suggestion Tool. Specify the details of the software that you wish to be added to SVM in the tool and click on Send to Flexera. Providing the Program File, which could be the main executable (.exe) (or.dll or .ocx file) of the software, will help us produce the file signature for this software. File signatures enable SVM for accurate detection and vulnerability assessment of software. Therefore, is it recommended you always provide the program file while suggesting software. Click Send to Flexera to submit the software suggestion request to Flexera. Our team picks up requests for further assessment and research and adds the software to SVM when all the requirements are met. You will get an email confirmation upon successful processing of the software suggestion request. Clicking on the View My Software Suggestions button on the SVM Software Suggestion Tool will redirect you to the new Software Suggestions view in the new web console of SVM that gives you visibility into the status of all your software suggestion requests. To see the full release notes, please click here.   ... View more