Agent Client Collector for Visibility Content default checks and policies

Agent Client Collector for Visibility Content (ACC-VC) provides various checks and policies as well as a business rule.

Policies

Note: ACC-VC policies execute at a frequency of once per day. The total data ingested would be approximately 572KB. This takes into consideration an average of approximately 1500 installed software applications and approximately 500 running processes other than CI data per machine.

<table id=“table_g55_dyy_5dc”><thead><tr><th>

Name

</th><th>

Description

</th><th>

Check definitions

</th></tr></thead><tbody><tr><td>

Enhanced Discovery

</td><td>

Runs on a schedule, by default every 24 hours (86400 seconds). The policy interval can be adjusted, for example to run every 4 hours (set the interval to 14400). The ACC-VC policy configuration is synced to all agents based on the policy filter defined by ACC-VC. Update the following ACC-F system properties, if needed:- sn_agent.disco_minimum_threshold_for_rediscovery_minutes: to avoid discovering the system too frequently. - sn_agent.disco_disable_ci_clobber_of_agentless_disco: to avoid Discovery conflicts. - sn_agent.disco_ci_clobber_of_agentless_disco_threshold_days: to avoid Discovery conflicts.

On Windows non-persistent VDI endpoints (NPVDI), ACC-VC can skip some inventory modules. For more information, see ACC-VC NPVDI system properties.

</td><td>

Enhanced Discovery

</td></tr><tr><td>

SAM Discovery

</td><td>

Responsible for capturing the software installed on any endpoint device, such as Windows desktops or macOS servers.

</td><td>

Software installations and usage metrics

</td></tr><tr><td>

SAM background

</td><td>

Enables a background job for processing the Osqueryd logs for SAM on Windows and macOS endpoint devices.

</td><td>

SAM background log check

</td></tr><tr><td>

SAM background (Non OsqueryD)

</td><td>

Enables a background job to collect SAM information using osqueryi instead of osqueryd.

</td><td>

SAM Background Policy (Non OsqueryD)

</td></tr><tr><td>

Software installed

</td><td>

Responsible for capturing the software installed on all devices except for Windows endpoint devices. The data collected is stored in the [cmdb_sam_sw_install] table. Scheduled to run every 24 hours.

</td><td>

installed software

</td></tr><tr><td>

File-based Discovery background policy

</td><td>

Takes the config file as input from the instance to an agent. Scans the system using config file parameters and stores the output in two separate files on the agent.- FBDSAMOutput.json: Stores metadata related to the set of file names generated from the samp_file_name table. - FBDFileOutput.json: Stores metadata related to files scanned by a wildcard extension.

Runs on the agent when file-based discovery is invoked. For details, see Agent Client Collector File-Based Discovery.

Default: false. To activate, navigate to All > Discovery Definition > Configuration Console and in the File Based Discovery section, activate the Enable File Based Discovery toggle switch.

</td><td>

File-based discovery background

</td></tr><tr><td>

File-based Discovery - SAM

</td><td>

Discovers known software files on the endpoint. Uses an allowlist of recognized software filenames maintained by ServiceNow. When a file on disk matches an allowlist entry, FBD uses the FileBasedDiscovery API to identify the collected software metadata (file name, path, size, and version), identifies the software package it belongs to and records the installation on the instance. Unrecognized files are tracked in the unidentified file records table (cmdb_unidentified_file_set). Runs daily.Default: false. To activate, navigate to All > Discovery Definition > Configuration Console and in the File Based Discovery section, activate the Enable File Based Discovery toggle switch.

</td><td>

File-based discovery - SAM

</td></tr><tr><td>

File-based Discovery - SWID tag

</td><td>

Enables SWID tag scanning on a Windows, Linux or macOS platform. When enabled, the scanner looks for .swid, .swidtag, and .cmptag files in the configured scan directories. Stores results in the following tables:- cmdb_swid_tag: Parsed SWID tag records - cmdb_file_information: Individual file records - cmdb_sam_sw_install: Individual software records

Default: false. To activate, navigate to All > Discovery Definition > Configuration Console and in the File Based Discovery section, activate the Enable File Based Discovery toggle switch.

</td><td>

</td></tr><tr><td>

File-based Discovery - File management

</td><td>

Discovers files based on customer-defined rules. Administrators configure which file extensions to look for and define filename matching rules such as exact match, starts with, ends with, or contains. This policy builds a device-level file inventory based on the organization’s specific needs. Results are stored in the sn_acc_vis_content_device_file_information table.Configure rules in the File Matching rules (sn_acc_vis_contet_file_config) and File extensions (sn_acc_vis_content_file_extension) properties. For details on these properties, see Agent Client Collector File-Based Discovery properties.

File Management supports delta scanning; after the initial full scan, only added, modified, and deleted files are sent on subsequent runs. For details on delta scanning, see Agent Client Collector File-Based Discovery.

Default: false. To activate, navigate to All > Discovery Definition > Configuration Console and in the File Based Discovery section, activate the Enable File Based Discovery toggle switch.

</td><td>

File-based discovery - File management

</td></tr><tr><td>

Oracle GLAS Java Process Discovery

</td><td>

Discovers running Java processes on endpoints and collects installation data for the Oracle GLAS license compliance report. Runs weekly.

</td><td>

Oracle GLAS Java Process Discovery

</td></tr><tr><td>

Oracle GLAS HW data collection

</td><td>

Executes Oracle’s hardware validation script on non-Oracle, non-macOS hosts to collect CPU/socket data for GLAS reporting. Runs weekly.

</td><td>

Oracle GLAS HW data collection

</td></tr><tr><td>

VISC Get application metric

</td><td>

Retrieves the SaaS application metrics from the agents.For details on enabling SaaS usage monitoring with ACC-VC, see the SaaS Usage Monitoring with Agent Client Collector [KB2320193] article in the Now Support Knowledge Base.

</td><td>

VISC Get application metric

</td></tr><tr><td>

VISC Get browser extension device init

</td><td>

Initializes the DEX browser extension with the host sysID.

</td><td>

VISC Get browser extension device init

</td></tr><tr><td>

VISC Get browser extension init

</td><td>

Initializes the DEX browser extension with logged-in users.

</td><td>

VISC Get browser extension init

</td></tr><tr><td>

VISC Get URL metrics

</td><td>

Controls the collection of web usage data from Windows and macOS managed devices. Runs daily.Default: Inactive. To activate the policy, set the sn_acc_vis_content.enable_full_monitoring property to true.

For details on web usage data system properties, see Web usage data collection tables and fields.

</td><td>

• VISC Get URL metrics

• VISC Get targeted URL metric

</td></tr></tbody> </table>Note: Windows endpoint devices include devices that have a Windows operating system and belong to CI class: computer.

See System properties for more details. For more details on policies, see Checks and policies.

Check type

ACC-VC has the following check types: Enhanced Discovery, SAM Advanced Discovery, and Installed Software.

• Enhanced Discovery

  This check type is responsible for invoking the EnhancedDiscoveryHandler script include that processes the payload produced by endpoint_discovery.rb as executed by ACC.

  Used by File-base Discovery.

• SAM Advanced Discovery

  This check type is for the SAM Discovery policy that invokes the EnhancedDiscoveryHandler script include for processing the SAM data produced by the sam_advanced.rb file.

• Installed Software

  This check type for the Software installed policy that invokes the EnhancedDiscoveryHandler script include for processing the installed software data produced by the installed_software.rb file.

Check definitions

<table id=“table_pkc_vdz_5dc”><thead><tr><th>

Name

</th><th>

Description

</th></tr></thead><tbody><tr><td>

Enhanced Discovery

</td><td>

Synced to all agents based on the policy filter defined by ACC-VC. The Check definition is configured to run with certain assets and determines what gets synced between the agent and the MID Server. For more details on policies, see Checks and policies.Note:

For the agent to retrieve the OS serial numbers and TCP connections along with associated running processes, sudo access for dmidecode and ss commands is required on Linux systems. For example, this content could be added to /etc/sudoers or to an individual file in /etc/sudoers.d/:

Cmnd_Alias AGENT_ACC_V = /usr/sbin/dmidecode -s baseboard-serial-number,/usr/sbin/dmidecode -s chassis-serial-number,/usr/sbin/dmidecode -s system-serial-number,/usr/sbin/dmidecode -s system-uuid,/usr/sbin/ss -tanp
servicenow ALL=(root) NOPASSWD:AGENT_ACC_V

For the sudoers configuration example, the must_sudo check parameter, and the equivalent macOS and Windows privilege requirements, see the “Privileges for running check commands” section in Checks and policies.

</td></tr><tr><td>

SAM background log check

</td><td>

Runs every 8 minutes and performs inline aggregation of data generated from Osqueryd logs. After collecting the data, it writes all the intermediate data results into a temporary marker file which is reused in the next run. This reuse limits the number of log files and disk space needed on target systems. Note: You may notice a spike in system resource consumption, as the background aggregation check runs every interval.

</td></tr><tr><td>

Software installations and usage metrics

</td><td>

Collects data every 24 hours.

</td></tr><tr><td>

Installed software

</td><td>

Fetches installed software data for all devices other than Windows and macOS endpoint devices.

</td></tr><tr><td>

File-based discovery background

</td><td>

Runs a file scanning background job on the agent.

</td></tr><tr><td>

File-based discovery

</td><td>

Fetches the file data from the agent.

</td></tr><tr><td>

Oracle GLAS Java Process Discovery

</td><td>

Runs pbd_java_discovery.rb via osquery to collect Java version, vendor, AMC, and licensing flags. Timeout: 600s. Runs on all platforms.

</td></tr><tr><td>

Oracle GLAS HW data collection

</td><td>

Runs endpoint_discovery.rb --select=oracle_glas_hw_discovery

to execute Oracle’s ct_cpuq script. Executes Oracle’s hardware validation script on non-Oracle, non-macOS hosts to collect CPU/socket data for GLAS reporting. Runs weekly.

</td></tr><tr><td>

VISC Get targeted URL metric

</td><td>

Gathers per-day usage metrics for the monitored URL from each managed device, and sends the data back to the instance.

</td></tr></tbody> </table>## Business rule

The Enhanced Discovery – On CI Delete business rule triggers the Endpoint Discovery Check when the CI associated with a given CI is deleted from sn_agent_cmdb_ci_agent.

Parent Topic:Agent Client Collector for Visibility Content reference