---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Archive file scanning rules and limits

# Archive file scanning filtering rules and limits {#ariaid-title1}

* Release version: Yokohama
* 
* Updated June 8, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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.

## Filtering rules {#archive-file-scanning-reference__archive-file-scanning-reference-filtering-rules}

Archive entries are filtered using the same rules as files found on disk, with the following differences.{#archive-file-scanning-reference__archive-file-scanning-reference-para-1}
{#archive-file-scanning-reference__archive-file-scanning-filtering-rules-table__entry__3}

| Capability | Regular files | Archive entries |
|-|-|-|
| SAM allowlist matching | Yes | Yes |
| File Management extension rules | Yes | Yes |
| MIME type detection (Linux) | Yes | No. The file does not exist on disk, so the system can't inspect its content type |
| Version detection | Yes | No. Version can't be queried for a file that hasn't been extracted |
| SWID tag support | Yes | No. Archive contents aren't decompressed or read, so SWID tags inside ZIP or JAR files aren't processed |
[Table 1. Archive file scanning filtering rules]

{#archive-file-scanning-reference__archive-file-scanning-filtering-rules-table}  
Note:  
On Linux, File Management matching relies on MIME type detection rather than extension rules. As a result, archive entries can only be matched by SAM rules, not by MIME type.

## Performance safeguards {#archive-file-scanning-reference__archive-file-scanning-reference-performance-safeguards}

The following limits are enforced to prevent archive scanning from affecting agent performance or endpoint stability.{#archive-file-scanning-reference__archive-file-scanning-reference-para-2}
{#archive-file-scanning-reference__archive-file-scanning-performance-safeguards-table__entry__3}

| Safeguard | Limit | Behavior when exceeded |
|-|-|-|
| Maximum archive file size | 500 MB | Archive is skipped entirely |
| Maximum entries per archive | 50,000 files | Scanning stops after the limit; entries discovered so far are retained |
| Per-archive timeout | 30 seconds | Scanning of that archive is aborted; entries discovered so far are retained |
| Corrupt or password-protected archives | Not applicable | Detected automatically, logged, and skipped |
| Nested archives (archive inside an archive) | Not applicable | Not scanned. Only top-level archives on disk are inspected |
| Global file limit (maxFiles) | Configured per policy | Archive entries count toward the global file limit; scanning stops when the limit is reached |
[Table 2. Archive file scanning performance safeguards]

{#archive-file-scanning-reference__archive-file-scanning-performance-safeguards-table}