The following files cannot be scanned:
- Local files opened directly in the browser (e.g., file:// paths).
- Full page saves (Ctrl+S / Cmd+S) cannot be intercepted.
- Certain browser-internal URLs (extension blobs, untrusted contexts,
null-origin blobs).
- Domains excluded via configuration are skipped entirely.
Only the Advanced Wildfire scanning provider is
supported. Other providers configured in the policy are silently skipped --
the file transfer proceeds without scanning.
Policy Effects Not Yet Supported
The following effects are configured in policy but not yet enforced. In all
cases, the transfer is blocked rather than applying the intended effect:
| Effect | Applies to |
|---|
| Allow Protected | Downloads |
| Save to Organizational Storage | Downloads |
| Encrypt | Downloads and Uploads |
| Non-encrypt (allow only non-encrypted) | Uploads |
Policy Options Not Yet Supported
The following interactive options are not yet implemented. When
configured, the transfer is blocked instead:
Bypass ("Proceed Anyway")
Bypass with reason ("Require Reason")
MFA challenge
Admin approval (downloads only)
Content filters / DLP pattern inspection
Metadata Filters
| Filter | Status |
|---|
| File size | Supported |
| File type / extension | Supported |
| File Hash | Not currently supported |
Upload-Specific Limitations
- Folders dragged and dropped - are not scanned. There are silently
allowed.
- Folder upload via directory picker is not intercepted.
- File path and file type may not always be identifiable
Download-Specific LimitationsWhen the file cannot be fetched for scanning or a mismatch
is detected between the scanned copy and the actual download, the
download currently proceeds unscanned
File size may briefly display as 0 during scanning
A long-running scan on a download that opened in a new tab
may delay the tab from closing
