Before public-share
A tunneled request still carries customer addresses, hostnames, and application payload bytes.
AI packet analysis can help investigate a capture, but raw PCAPs often contain subscriber IDs, hostnames, IPs, MACs, SIP/IMS identifiers, device names, credentials, and customer topology.
anoncap creates a safer sibling capture while leaving the original untouched. The anonymized copy preserves useful diagnostic structure so Agent, Copilot, vendors, customers, and reviewers can work from packet evidence with less exposure of raw identifiers.
A tunneled request still carries customer addresses, hostnames, and application payload bytes.
Identifiers are deterministically replaced and supported headers remain readable while unsupported payload is truncated.
A tunneled request still carries customer addresses, hostnames, and application payload bytes.
Identifiers are deterministically replaced and supported headers remain readable while unsupported payload is truncated.
Use the open-source CLI to create a local anonymized sibling capture, or evaluate PacketSafari's private profile when production captures need broader protocol tuning, managed workflow, and customer-controlled deployment.
Create a local sibling capture with the public sharing baseline.
./bin/anoncap --public-share input.pcapng
./bin/anoncap --explain-defaults
./bin/anoncap --paranoid input.pcapng --report anon.report.json`--public-share` writes `input-anon.pcapng` by default. Add `-w output.pcapng` to choose a name, or `--overwrite` to replace an existing output.
Enterprise anonymization
Extend the open-source baseline with PacketSafari-maintained profiles for sensitive production and telecom captures.
Compare deployment options