---
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


---

# ACC File-Based Discovery

# Agent Client Collector File-Based Discovery {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 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 Agent Client Collector File-Based Discovery

Agent Client Collector File-Based Discovery (FBD) enables ServiceNow customers to scan file systems on managed endpoints to discover installed software and maintain file inventories.
It operates as a lightweight background process within the existing Agent Client Collector agent and is fully managed from the ServiceNow instance.
Administrators configure scan directories, target files, and scan frequency.
Discovered files and their metadata---such as name, path, size, and version---are sent to ServiceNow and stored in the CMDB and relevant application tables.
Show full answer Show less  

## Key Features

* **Platform Support:** Compatible with Windows, Linux, and macOS operating systems.
* **Required Plugins:** Activation requires specific plugins including File-based Discovery, Software Asset Management - File Signature Normalization, Agent Client Collector - Visibility Content, and Software Asset Management Professional.
* **Delta Scanning:** Optimizes performance by sending only changes (added, modified, deleted files) after the initial full scan, reducing data transfer. Full scans are periodically enforced to ensure accuracy. Note that delta scanning is not applied to SAM or SWID policies, which always perform full scans.
* **Archive File Scanning:** Optional feature to inspect ZIP and JAR archives to discover embedded software files without decompressing them. Enabled via a system property requiring administrative privileges. Applies existing filtering rules and safeguards.
* **Process-Based Discovery:** Extends FBD to detect software running outside configured scan directories using process-based path detection.
* **License Key Discovery:** Automatically identifies and inventories license keys stored in files across Windows, Linux, and macOS endpoints, helping verify legitimate software usage within vendor agreements.

## Activation and Configuration

To enable File-Based Discovery, navigate to the Discovery Configuration Console within ServiceNow and toggle the Enable File Based Discovery option. Additional configuration and system properties are available to tailor FBD behavior to organizational needs.

## Practical Benefits for ServiceNow Customers

* Gain comprehensive visibility into installed software and file inventories across multiple operating systems.
* Improve discovery efficiency and reduce network load with delta scanning.
* Enhance software asset management accuracy by including files inside archives and detecting running software beyond standard directories.
* Support compliance and audit readiness by identifying license keys and verifying software legitimacy.  
Agent Client Collector File-Based Discovery (FBD) scans file systems on managed endpoints to discover installed software and track file inventories.

FBD runs as a lightweight background process within the existing Agent Client Collector agent. It is configured and controlled entirely from the ServiceNow instance. Administrators define which directories to scan, which files to look for, and how often to scan. The agent discovers matching files, collects metadata such as name, path, size, and version,
and sends the results back to the instance where they are stored in the appropriate CMDB and application tables.{#file-based-discovery-overview__file-based-discovery-overview-para-1}  
To activate FBD, navigate to the Discovery Configuration Console (AllDiscovery DefinitionConfiguration Console) and in the File Based Discovery section, activate the Enable File Based Discovery toggle switch.Figure 1. Discovery Configuration Console

For details on the FBD configuration and system properties, see [Agent Client Collector File-Based Discovery properties](https://www.servicenow.com/docs/FaIAX_IrfC~rFuwTzDTXnw "Configure File-Based Discovery behavior using system properties that control scanning paths, performance throttling, and file filtering options.").

## Supported platforms {#file-based-discovery-overview__supported-platforms}

FBD supports the following operating systems:{#file-based-discovery-overview__file-based-discovery-overview-para-2}

* Windows
* Linux
* macOS

## Required plugins {#file-based-discovery-overview__required-plugins}

The following plugins are required for File-Based Discovery on Agent Client Collector:{#file-based-discovery-overview__file-based-discovery-overview-para-3}

* File-based Discovery (com.snc.discovery.file_based_discovery)
* Software Asset Management - File Signature Normalization (com.snc.file_signature_normalization) --- Activated automatically once the File-based Discovery plugin is active
* Agent Client Collector - Visibility Content (sn_acc_vis_content)
* Software Asset Management Professional (com.snc.samp)
{#file-based-discovery-overview__ul_am5_msl_djc}

## Delta scanning {#file-based-discovery-overview__delta-scanning}

Delta scanning is a performance optimization that applies only to the File Management policy. It reduces the volume of data sent from the endpoint to the instance on repeat scans.{#file-based-discovery-overview__file-based-discovery-overview-para-5}

The delta scanning process works as follows:{#file-based-discovery-overview__file-based-discovery-overview-para-6}

1. **First scan** --- A full scan runs. All matching files are sent to the instance. A fingerprint, which is a snapshot of all discovered file paths and sizes, is saved locally on the endpoint.
2. **Subsequent scans** --- The scanner compares the current file list against the saved fingerprint and reports only the differences:
   * **Added** --- files that exist now but were not in the previous fingerprint
   * **Modified** --- files that exist in both but with a different size
   * **Deleted** --- files that were in the previous fingerprint but no longer exist on disk
3. **Periodic full scan** --- After a configured number of delta scans (default: 5), a full scan is automatically forced to verify accuracy and correct any drift.

Note:  
Delta scanning does not apply to the SAM or SWID policies. These policies always perform a full scan on each run.

## Archive file scanning {#file-based-discovery-overview__section_h2f_hyl_njc}

Archive file scanning extends file-based discovery to inspect ZIP and JAR archive files and report the files contained within them. This enables discovery of software artifacts such as executables and libraries that are packaged in
the ZIP or JAR files on the endpoint.

Archive file scanning is disabled by default. To enable it, set the sn_acc_vis_content.file_discovery.archive_scan_enabled property to true. This property requires the
discovery_admin role to modify.

When archive file scanning is enabled, the agent inspects each ZIP or JAR file encountered during a directory scan. The agent reads the archive's internal index to enumerate the files inside. No file content is extracted or
decompressed. Only metadata is collected.

For each file found inside an archive, the agent applies the same filtering rules used for regular files on disk, including SAM allowlist and File Management extension rules. Files that pass the filters are reported alongside other
discovered files.

For filtering rules and performance safeguards, see [Archive file scanning filtering rules and limits](https://www.servicenow.com/docs/ldqOh1AqsNznazfG~o3iWA "Reference information for the filtering rules and performance safeguards that apply when Agent Client Collector for Visibility Content scans ZIP and JAR archive files during File-Based Discovery.").
* **[Running process-based discovery](https://www.servicenow.com/docs/phlhYcyZdhh1Qa9GSmqvMw)**   
  Running process-based discovery extends File-Based Discovery (FBD) with process-based path detection, enabling the Agent Client Collector for Visibility Content agent to detect software running outside of standard configured scan directories.
* **[Discovering a license key in a file-based discovery framework](https://www.servicenow.com/docs/tJAL3Ue71pEmaObhJdFw2A)**   
  License key discovery across Windows, Linux, and macOS enables ACC to automatically identify and create an inventory of license keys stored in files on managed computers. A license key proves that software installation is legitimate and is being used within the boundaries the vendor agreed to at the time of purchase.

*[\>]: and then