--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # File-based Discovery # File-based Discovery {#ariaid-title1} Release version: Australia Updated March 25, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of File-based Discovery File-based Discovery helps ServiceNow customers identify software running on Windows, UNIX, and macOS servers and devices, even when no registration information exists. It enables management of software licenses, detection of unlicensed or forbidden files, and evaluation of potential threats from unwanted files by scanning for known file signatures and matching discovered files to software products. Show full answer Show less ## Key Features * **Plugin requirements:** Activation of the *File-based Discovery \[com.snc.discovery.filebaseddiscovery\]* plugin is necessary; this also activates the *Software Asset Management - File Signature Normalization* plugin. * **Discovery process:** Runs during the exploration phase of normal Discovery, scanning configured paths for specific file names and extensions. * **File signature filtering:** Uses signature lists tailored for Windows and UNIX, with filtering handled differently due to list size---Windows filtering occurs on the MID Server, UNIX filtering occurs directly on the target. * **Data storage:** Discovered file data is stored in the *File Information \[cmdbfileinformation\]* table, linked to the corresponding server CI. Unmatched files are stored in the *Unidentified File Set \[cmdbunidentifiedfileset\]* table for manual updating. * **Integration with Software Asset Management (SAM):** When SAM is active, matched files populate software product data in the *Software Installation \[cmdbsamswinstall\]* table and update license records. Without SAM, only file data is recorded. * **SWID tag support:** Optional enabling of SWID tags in the Discovery Configuration Console allows collection of detailed software identification data, stored in the *cmdbswidtag* table. Base64 package is required on UNIX/Linux for SWID tag scanning. * **Supported platforms:** Windows versions from 2008 through 2019 and later (excluding Windows with PowerShell 7), UNIX variants including AIX and HP/UX, POSIX-compliant UNIX probes compatible with Linux and Solaris, and macOS. ## Key Outcomes * Enables accurate software identification even without registration data, improving software asset visibility. * Supports license compliance by identifying unlicensed or unauthorized software files. * Improves security posture by detecting forbidden or damaged files and evaluating threats. * Provides detailed file and software metadata, facilitating better management and reporting. * Allows customers to maintain and update unidentified file records to enhance future discovery accuracy. * Flexible enablement and disablement within the Discovery Configuration Console to suit operational needs. ## Additional Considerations * File version information is only populated for files that include version metadata, commonly for executable files like .exe and .jar. * Special configuration is required for Ubuntu 20 to change the default shell to bash for successful discovery. * Error handling notes include a known PowerShell cmdlet recognition issue when running on unsupported environments. File-based Discovery helps you identify what software is running on your Windows and UNIX servers and devices, even if there's no registration information available. You can then manage and maintain records of your software licenses, check for unlicensed files, detect forbidden or damaged files, and help evaluate any threats from unwanted files. ## Required plugins {#file-based-discovery__section_cys_3jr_13b} The File-based Discovery \[com.snc.discovery.file_based_discovery\] plugin is required for file signature filtering. Your Discovery subscription includes this plugin, but you must [request activation](https://www.servicenow.com/docs/access?context=t_RequestAPlugin&version=australia&pubname=australia-platform-administration&ft:locale=en-US). Once the File-based Discovery plugin is active, the Software Asset Management - File Signature Normalization \[com.snc.file_signature_normalization\] plugin is also activated. For more information on the File Signature Normalization plugin, see [File Signature Normalization](https://www.servicenow.com/docs/access?context=sam-file-based-discovery&version=australia&pubname=australia-it-asset-management&ft:locale=en-US). ## How File-based Discovery works {#file-based-discovery__section_ifz_rbp_x2b} File-based Discovery enhances the pre-existing discovery of installed software. It scans target servers for a known list of file signatures and processes those files with an established set of rules. The resulting data enhances the identification of installed software and identifies unregistered software products. For information about using Agent Client Collector for Visibility Content to perform file-based discovery, see [Discover Java installation data using Agent Client Collector for Visibility Content File-Based Discovery](https://www.servicenow.com/docs/lHg3lP_v6bb_PJ0qg_uKyg "Discover file information in your system using Agent Client Collector for Visibility Content (ACC-VC) File-Based Discovery (FBD)."). File-based Discovery is triggered in the exploration phase of normal Discovery. File-based Discovery probes execute a scan searching for specific file extensions or file names in paths that you configure. The resulting file information is returned in the probe payload. The sensor attempts to match the discovered files with installed software, using the file name, size, and version returned by the probe. File-based Discovery uses file signatures to detect software that might not have been registered. This information is then stored in the File Information \[cmdb_file_information\] table with a reference to the CI of the server. You can view the files found from each CI in a related list on this table. For more information, see [Related list of CI components](https://www.servicenow.com/docs/access?context=r_RelatedListsOfCIComponents&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). When [Software Asset Management](https://www.servicenow.com/docs/access?context=c_SoftwareAssetMgmt&version=australia&pubname=australia-it-asset-management&ft:locale=en-US) (SAM) is active, if any file matches a software product, Discovery populates the Product and Publisher information for that file. Use this information to understand what software is running on your server and to help evaluate any threats from unwanted files. Discovery uses lists of known file signatures for Windows and UNIX to constrain the scope of the search. The filtering process for Windows and UNIX hosts is executed differently because their signature lists differ greatly in size. The smaller UNIX signature list is included with the Unix - File Discovery probe and processed directly on the target. The Windows signature list is larger and can't be processed on the target. The Windows - File Discovery probe scans the target for specific file extensions and paths and returns these results to the MID Server. The MID Server performs file signature filtering using the entire Windows list. The MID Server then sends all file information back to the instance for normalization and matching. If SAMP is active on the instance, File-based Discovery creates or updates identified software products in the Software Installation \[cmdb_sam_sw_install\] table and updates matched software package licenses. Without SAMP, no software records are created. Only the file information goes into the File Information \[cmdb_file_information\] table. You can enable SWID tags in the Discovery Configuration Console. With SWID tag enabled, when running File-based Discovery, the SWID tag information then populates the \[cmdb_swid_tag\] table. Information about the software installed on a particular machine includes name, file information, publisher, version, installed on, and content. The software_installation column in the \[cmdb_swid_tag\] is a reference to the \[cmdb_sam_sw_install\] table. Note: Base64 package is a prerequisite for any UNIX or Linux servers to scan SWID tag files using File-based Discovery. File-based Discovery inserts any file not matched by the normalization process into the Unidentified File Set \[cmdb_unidentified_file_set\] table. You can update the records in this table and provide additional details for previously unidentified files. If you provide values for the Product and Publisher fields for a file, SAMP settings can enable File-based Discovery to use that file for installed software matching in future discoveries. You can disable File-based Discovery at any time by changing the setting in the [Discovery Configuration Console](https://www.servicenow.com/docs/Dd4Yjm8isniEARaNj8bgVw#c_DiscoveryConfigurationConsole "Use the Discovery Configuration Console to manage what kind of configuration items (CIs) and CI information you want to discover."). If you disable File-based Discovery before scan results are returned, the file data is ignored. Note: File-based Discovery supports Windows, UNIX, and macOS devices. The UNIX probe is POSIX-compliant and should run on any Linux/Solaris server. Discovery supports Windows versions 2008, 2008R2, 2012R2, 2016, 2019, and above with PowerShell 3.0--7. Discovery also supports AIX versions 5.3, 6.1, and 7.1 and HP/UX 8.11. File-based Discovery and Windows ADME are not supported on Windows with PowerShell 7. File-based Discovery fails with the following error message: `Error(s) during file-based discovery: Unable to start background scan. System.Management.Automation.CommandNotFoundException: The term 'Invoke-WmiMethod' is not recognized as a name of a cmdlet, function, script file, or executable program.` If you're running File-based Discovery on Ubuntu version 20, modify the default Bourne shell (sh) to point to Bourne Again shell (bash). Version information is populated only for the files with version information returned from probes. Not all files have versions. Files with extensions such as .exe, .jar, and so on, have versions. **Related tasks** * [Run File-based Discovery](https://www.servicenow.com/docs/PUMRzUkdPjIVC9xJnsPX1Q#run-file-based-discovery "Run File-based Discovery to find all of your installed software whether it is registered or not. You can enable and configure File-based Discovery at any time using the Discovery Configuration Console.") **Related reference** * [File-based Discovery references](https://www.servicenow.com/docs/mhh8lvi5vJsgY735Dpsazg "Review this reference material for further details on File-based Discovery.") * [File-based Discovery issue resolution](https://www.servicenow.com/docs/jMday1zZtOq5Kn4n4gGPdQ "If you have any issues while setting up or running File-based Discovery, follow the actions listed here to help resolve them.")