---
sourceDocument: Brazil IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-operations-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# File-based Discovery

# File-based Discovery {#ariaid-title1}

Release version: Brazil  
Updated October 13, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 6 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 enables ServiceNow customers to identify software running on Windows and UNIX servers and devices, even when no registration information exists.
This capability helps maintain accurate software license records, detect unlicensed, forbidden, or damaged files, and assess potential security threats from unwanted files.
Show full answer Show less  
The feature is included with your Discovery subscription but requires activation of the **File-based Discovery \[com.snc.discovery.filebaseddiscovery\]** plugin. Activating this plugin also enables the **Software Asset Management - File Signature Normalization** plugin automatically.

## How It Works

File-based Discovery operates during the exploration phase of normal Discovery. It scans configured file paths and extensions on target servers, returning file information such as name, size, and version (Windows only) in the probe payload.

* On Windows, the MID Server performs file signature filtering due to the large signature list size.
* On UNIX/Linux, the smaller signature list is processed directly on the target via the Unix - File Discovery probe.

Discovered files are matched against known software products, enhancing software identification and detecting unregistered software. Data is stored in the **File Information \[cmdbfileinformation\]** table and linked to the server CI.

If Software Asset Management (SAM) is enabled, matching files populate the **Software Installation \[cmdbsamswinstall\]** table and update license information. Without SAM, only file information is recorded without creating software records.

Enabling SWID (Software Identification) tag scanning populates the **Swid Tags \[cmdbswidtag\]** table, linking software installation data to software records. This requires the **base64** package on UNIX/Linux servers.

Files not matched by normalization are stored in the **Unidentified File Set \[cmdbunidentifiedfileset\]** table, allowing manual updates for improved future matching.

File-based Discovery supports Windows (2008 and later), UNIX/Linux (POSIX-compliant), macOS, AIX, and HP/UX systems. Special configuration is required for PowerShell 7 on Windows and for Ubuntu 20's shell.

## Software Version Information

Version data is returned only for files supporting version metadata, primarily on Windows (.exe, .jar, etc.). UNIX/Linux probes do not return version info; instead, version details come from rpm- and dpkg-based discovery probes or SWID tags.

To obtain version information on UNIX/Linux systems, selectively enable SWID tag scanning for products providing valid SWID tags to avoid unnecessary overhead.

## Permissions and System Requirements

File-based Discovery requires the discovery credential to have appropriate file system permissions on target systems:

* **UNIX/Linux:** Read and execute permissions on scanned directories, read permissions on files, and read/write access to temporary directories (typically /tmp). Read access on SWID files if SWID scanning is enabled.
* **Windows:** Access through WinRM/WMI using the credential's NTFS permissions. The scan writes temporary files to the administrative share (admin$).

The discovery account can only scan files and directories it has permission to access; inaccessible items are silently skipped.

Required operating system tools must be available in the system path on target servers, including core utilities like `find`, `grep`, `awk`, `sed`, and others. Base64 or uuencode is required when SWID tag scanning is enabled.

## Practical Benefits for ServiceNow Customers

* Enhanced visibility into installed and unregistered software across Windows and UNIX/Linux servers.
* Improved software license management and compliance through accurate software identification and detection.
* Ability to detect unlicensed, forbidden, or damaged files to support security and audit requirements.
* Integration with SAM for automatic updates to software installation and license records.
* Support for SWID tags provides richer software metadata, including version information on UNIX/Linux systems.
* Configurable scanning scope and the option to disable File-based Discovery as needed.  
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=brazil&pubname=brazil-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=brazil&pubname=brazil-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/R4bilrqSC9yfiE2QLIApzA "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. On Linux and UNIX devices, the Unix - File Discovery probe doesn't return version information. 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=brazil&pubname=brazil-servicenow-platform&ft:locale=en-US). When [Software Asset Management](https://www.servicenow.com/docs/access?context=c_SoftwareAssetMgmt&version=brazil&pubname=brazil-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](https://www.servicenow.com/docs/xwZtpGPWSkK1Ib7N7e3PYw#c_DiscoveryConfigurationConsole "Use the Discovery Configuration Console to manage what kind of configuration items (CIs) and CI information you want to discover."). With SWID tag enabled, when running File-based Discovery, the SWID tag information then populates the Swid Tags \[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 Swid Tags \[cmdb_swid_tag\] table is a reference to the Software Installations \[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/xwZtpGPWSkK1Ib7N7e3PYw#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 later with PowerShell 3.0--7. Discovery also supports AIX versions 5.3, 6.1, and 7.1 and HP/UX 8.11.
* 
* To use File-based Discovery on target hosts that run PowerShell 7, configure the MID Server to prefer PowerShell 7. For more information, see [Configure MID Server parameters for PowerShell 7](https://www.servicenow.com/docs/RPdP2lEw1csJ6lNWJWWjBg "Configure two MID Server parameters to run File-based Discovery and Windows ADME on target hosts that use PowerShell 7.").
* 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. On Windows devices, files with extensions such as .exe, .jar, and so on, have versions. On Linux and UNIX devices, the probe doesn't return version information. For more information, see the following section.
{#file-based-discovery__ul_e1h_4nw_wkc}

## Software version information on Linux and UNIX devices {#file-based-discovery__section_linux_version_limitation}

The Unix - File Discovery probe returns file name and file size only for Linux and UNIX devices. It is not designed to collect file version metadata. As a result, the Version field in the File Information \[cmdb_file_information\] table is empty for files discovered on Linux and UNIX devices. This is expected behavior, not a configuration issue. Linux software versions in the Software Installation \[cmdb_sam_sw_install\] table are populated by the rpm- and dpkg-based discovery probes instead, such as the Linux - Install Software probe.

To obtain version information for software on Linux and UNIX devices, enable SWID tag scanning for products that provide valid SWID tags. SWID tags include version data and populate the Swid Tags \[cmdb_swid_tag\] table. Enable SWID tag scanning selectively for
products known to provide valid SWID tags rather than enabling it across all servers, to avoid unnecessary scanning overhead. For more information, see [Discovery Configuration Console](https://www.servicenow.com/docs/xwZtpGPWSkK1Ib7N7e3PYw#c_DiscoveryConfigurationConsole "Use the Discovery Configuration Console to manage what kind of configuration items (CIs) and CI information you want to discover.").

## Target system permissions {#file-based-discovery__section_r2f_3wk_4jc}

File-based Discovery connects to each target system with the configured discovery credential and reads files directly as that credential's account. On both UNIX and Windows target systems, the credential's own file system permissions determine what File-based Discovery can access. File-based Discovery skips any directories and files that the account can't read and doesn't report an error for them.

On Windows systems, File-based Discovery reads files with the NTFS permissions of the discovery credential's account through WinRM/WMI. The scan writes its working files to the admin$ administrative share, which defaults to
`C:\Windows\Temp\<mid-instance-name>`.

Required permissions (UNIX)

:   The Discovery user needs the following permissions on each UNIX target system:

    {#file-based-discovery__table_y3m_lwk_4jc__entry__2}

    | Permissions required | Description |
    |-|-|
    | Read and execute (traverse) on the directories in the scan path | Enables the scan to move through the directory trees you select. Directories that the credential's account can't traverse are skipped, with no error reported. |
    | Read on the files that match the scan list | Enables File-based Discovery to read each file's size and details. Files that the account can't read are skipped, with no error reported. |
    | Read and write on the temporary directory, /tmp by default | Enables the scan to write and read its working files on the target system. |
    | Read on SWID files, when SWID tag scanning is enabled | Enables File-based Discovery to read software identification details from SWID files. |
    [ ]

    {#file-based-discovery__table_y3m_lwk_4jc}  
    Note:  
    File-based Discovery scans the `/opt` and `/etc` directories on a Linux system. If the discovery credential's account doesn't have read and execute permissions on these directories, File-based Discovery skips them without reporting an error. It reports only the software in directories that the account can read.

Required operating system tools
:   File-based Discovery uses standard operating system tools on each target system. The following tools must be available in the system path on each target:

    * find, wc, awk, and grep
    * ps and nohup
    * sh or bash
    * sed, cat, mv, rm, chmod, tr, and head

    {#file-based-discovery__ul_zv2_xwk_4jc}

    When SWID tag scanning is enabled, base64 or uuencode must also be available. File-based Discovery uses uuencode first and falls back to base64.
**Related tasks**   

* [Run File-based Discovery](https://www.servicenow.com/docs/QpnHWEivsWoySY0bhZCREw#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/Zs18qVirLYubsVCfYWM2eQ "Review this reference material for further details on File-based Discovery.")
* [File-based Discovery issue resolution](https://www.servicenow.com/docs/s8XzFQOVP6uA8BIx_sp9HQ "If you have any issues while setting up or running File-based Discovery, follow the actions listed here to help resolve them.")

