Product · Bundle formats
Bundle formats, by status
The table below is LogVeil's public roadmap and carries three statuses only. Supported in early access means within the scope of the early-access programme; in development means being built now; planned means committed but not yet started.
The public roadmap
The register, family by family
"Supported in early access" describes the programme’s scope, not a statement that it has opened: LogVeil is in development, and an early-access programme opens after our first field trial.
| OEM | Bundle family | Status |
|---|---|---|
| Cisco | Secure Firewall Management Center (FMC) troubleshoot bundle Nested archives, rotated logs, object dumps, certificates and embedded databases are inventoried and handled per policy. | supported in early access |
| Cisco | Secure Firewall Threat Defense (FTD) troubleshoot bundle, including high-availability pairs Same family as the FMC bundle; handled by a profile. | supported in early access |
| Cisco | Identity Services Engine (ISE) support bundle Encrypted bundles are decrypted with the key entered at job start and re-encrypted for the recipient; large database exports are declared, never silently passed. | supported in early access |
| Cisco | Catalyst Center (formerly DNA Center) RCA and support bundles Very large, deeply nested bundles; processing streams with bounded memory. | supported in early access |
| Check Point | Gaia cpinfo Single-file bundle with embedded sections. | in development |
| Cisco | IOS-XE show tech-support and binary trace (btrace) archives Binary trace members are declared in the attestation. | in development |
| Radware | Alteon ADC and vADC techdata Includes embedded packet captures, which are declared. | in development |
| Radware | DefensePro / NIPS support bundle | in development |
| Cisco | Catalyst 9800 wireless LAN controller debug bundle | planned |
| Fortinet | FortiGate TAC report and console log | planned |
| Infoblox | NIOS support bundle | planned |
| Juniper | Junos request support information (RSI) | planned |
| Palo Alto Networks | PAN-OS tech support file (TSF) | planned |
| Any | Packet captures (pcap, pcapng) — standalone or inside a bundle Recognised, inventoried and declared today (passed through or dropped by policy); rewriting of capture contents is planned. | planned |
| Any | Generic text archive (unknown bundle types) Conservative defaults with a loud non-assertion in the attestation. | planned |
Statuses move only on approval, with the date recorded in the register.
Reading the table
A family, not a file type
in developmentA vendor or product not on this list is added by writing a profile — a declarative description of the bundle family — not by changing the engine.
A family, not a file type.
Each row is an OEM bundle family — the archive a device or a management system produces for the vendor's support centre — not a file extension. Inside a family LogVeil handles the members it finds: nested archives, rotated logs, object dumps, configuration grammars, certificates, database exports, packet captures, binaries. Members that cannot be rewritten are dropped or passed through by the customer's policy, and every one is declared in the Sanitisation Attestation.
Packet captures.
Standalone or inside a bundle, captures are recognised, inventoried and declared today — passed through or dropped as the policy says — and rewriting of capture contents is planned. Nothing here implies that captures are rewritten now.
Unknown bundle types.
A generic text-archive profile with conservative defaults is planned; until then an unrecognised bundle type is exactly that, and the attestation says so as a loud non-assertion.
A vendor or product not on this list
is added by writing a profile — and, only where a member format has a grammar nobody has seen before, a content transformer for it. The engine has five kinds of plugin, each with a versioned interface, and a conformance harness that tests every pack on recall and over-masking before it is accepted. Adding a vendor never touches the core.
What these families look like inside
Scale, measured on real bundles in our lab.
- files
- 11,412
- seven levels deep — one Cisco FMC troubleshoot bundle
- files
- 40,821
- nine deep — a Cisco FTD high-availability troubleshoot
- files
- 11,529
- eleven deep — a third bundle
- one member
- 4.98 GB
- inside a Cisco ISE support bundle
- expansion
- 15×
- a Catalyst Center RCA bundle, to 73 GB
- of content
- 113.8 GB
- from 11.4 GB on disk — nine bundles, 66,802 files, 2,216 nested archives
A single Cisco FMC troubleshoot bundle holds 11,412 files nested seven levels deep; a Cisco FTD high-availability troubleshoot, 40,821 files, nine deep; a third bundle, 11,529 files, eleven deep; a Cisco ISE support bundle carries one member of 4.98 GB; a Catalyst Center RCA bundle expands fifteen-fold, to 73 GB. Across nine bundles: 66,802 files, 2,216 nested archives, 113.8 GB of content from 11.4 GB on disk. Nobody hand-scrubs that.
Not on the list?
LogVeil is in development. An early-access programme opens after our first field trial.
Early access is a free, guided proof-of-concept on your own bundles inside your own network: you choose the bundles, you write the policy with our help, and you keep the key; we hand over the offline kit, run the first jobs with your engineers, and leave you with the attestations.