GDPR Compliance for your Pcap files
all stacks, all layers

Pcap files often contain sensitive data, including personal data of network users. GDPR compliant procedures for sharing citizens personal data with entities outside EU are very restrictive. As a result, Pcap files can no longer be freely shared with suppliers and customers, and even internally. SafePcap is built to address this problem.

SafePcap is a scriptable L2-L7 Pcap anonymizer, sanitizer, scrambler, universal full-stack editor and a GDPR Compliance Solution. SafePcap allows for easy editing of Pcap data in situ at any stack layer while fully preserving the data binary integrity. Data modifications are done in a break-proof manner with the lengths, checksums, offsets and all other service fields auto-recalculated for all affected protocol layers. A file sanitized with SafePcap allows for effective forensic analysis with commonly used Pcap analysis tools like Wireshark™. Automation is fully supported via SafePcap CLI.

For example, the following command scrambles IMSI values in all Mobile Core protocols by replacing the last ten digits with zeros using a simple RegEx:

-

SafePcap is a GDPR compliance solution for Pcap files

Key Features
WYSIWYG Packet Editing

Visually edit a captured packet at any stack layer. Obfuscate any field. Add/Delete an optional field of the packet with a click.

Auto Anonymization

Pre-programmed anonymization commands. With a few clicks obfuscate IP addresses at all layers (L2-L4), phone and IMSI numbers, texts, email addresses, etc.

Custom Data Obfuscation

Use a RegEx to target specific data at a specific field of a specific protocol layer for editing/obfuscation. Easily create custom obfuscation functions.

Auto Dependencies ReCalc

Dependencies in the modified data are recalculated automatically. No worry about offsets, checksums, encoding, etc.

Total Automation

Automation is supported. To repeat a multi-step editing/scrubbing operation, run each step from a CLI in a batch file.

Frequently Asked Questions
What problem SafePcap is addressing? What does it have to do with GDPR?

A Packet Capture (Pcap) file holds "bits on the wire" networking data, a time-stamped collection of captured packet binaries. While sharing of Pcap files is essential for development, monitoring, and troubleshooting of computer networks, the proprietary data often present in the files makes sharing "as is" problematic. The files have to be sanitized first.

Selectively scrambling bits of the captured network traffic while fully preserving the binary integrity of the data is a complex task due to a variety of protocols involved and the intricacy of packets' intra and inter-dependencies. In the absence of the Pcap anonymization solution the Pcap sharing problem has been addressed by having NDAs between the parties. Without an NDA in place the most popular option is to dump the decoded Pcap file into text, obfuscate the sensitive parts there, and share the resulted text file. Another approach is to zero out the packet data above TCP/UDP. The big downside of both approaches is a loss of detailed information about the binary structure of the data making effective analysis of the networking issues impossible.

GDPR has made sharing of Pcap files even more problematic. Customers personal data can no longer be easily sent outside EU. SafePcap is built to address these problems.

Does SafePcap support 3GPP Mobile Core Protocols?

Full support for all 4G/LTE 3GPP Mobile Core protocols and interfaces including SS7, RANAP, DIAMETER, and VoLTE.

What's the difference between SafePcap and WireEdit?

Both tools are created by Omnipacket. WireEdit is a demo Desktop application released in 2014. It's available for a free download. WireEdit has limitations and isn't intended for a production environment.

SafePcap is an enterprise-level commercial product. Its features and capabilities are a superset of WireEdit features and capabilities. The major additional SafePcap features/capabilities are: pcap-ng format support, native builds for Linux and OSX, support for large files (> 2 Gig), hundreds of additional protocols, fine-grained replace operations, higher speed of execution, GDPR Compliance algorithms, support for Command Line Interface, enterprise-level support.

What data is considered sensitive in Pcap files?

IP Addresses, port numbers, phone numbers, IMSI numbers, email addresses, passwords, texts, HTTP headers, etc. In fact, data at any stack layer could be considered sensitive in some use cases. SafePcap allows anonymizing data of any type at any stack layer of the captured network traffic while fully preserving the packets binary integrity. Specific values in specifically named data fields at a specific network stack layer could be precisely targeted for bulk anonymization.

What is the difference between SafePcap and other packet editing tools?

One could think of SafePcap as a Microsoft Word™ for network packets. All other packet editing tools are very limited in their ability to edit binary encoded stack layers above TCP/UDP without breaking packets integrity. SafePcap is a full-stack packet editor by design.

What is the difference between SafePcap and other Pcap anonymizers?

Other tools can't anonymize binary encoded stack layers above UDP/TCP. Instead, they take a simplistic approach of zeroing them out. This approach is far from ideal for many use cases. For example, it makes an effective analysis of anonymized 3GPP Mobile Core Pcap files impossible.

A popular opinion on the Subj is expressed here. Our response is here. SafePcap by design allows editing/obfuscation of any field at any stack layer above TCP/UDP without breaking packets' binary integrity.

What language SafePcap is written on?

Highly optimized C++. One needs every CPU cycle to process large Pcap files.

Do you support editing/anonymizarion of ASN.1 based protocol layers?

Yes, absolutely! Watch this short video: Editing GSM Mobile Application Part.

Are there *any* limitations on binary encoded network protocols to be supported?

No limitations. We can support anonymizing any networking protocol at any stack layer, provided we have the specs.

What protocols are supported by SafePcap today?

New protocols are added all the time. Here is the partical list:

IP, Ethernet II, IEEE 802.1Q, IPv4, IPv6, UDP, TCP, SCTP, GRE, TLS, TPKT, VXLAN, NetBIOS, SMB, HTTP, HTTP2, FTP, IMAP, POP3, DNS, NTP, OpenFlow, MODBUS, FIXT, ICMPv4, ICMPv6, IGMP Ver 1, IGMP Ver 2, IGMP Ver 3, TELNET, SSH, DHCP, DHCPv6, ARP, RARP, LLDP, XMPP, LDAP, SNMPv1, SNMPv2c, SNMPv2u, SNMPv3, RSVP, BGP, OSPF, CAPWAP, DTLS, SoupBinTCP, NASDAQ OUCH 4.2, CPE-WAN over SOAP, HNCP, Radiotap, IEEE 802.11, L2TPv2, L2TPv3, 802.3/LLC, Cisco AN, Cisco AN, ESP, ISAKMP, CESoPSN, PPPoE, PPPoE, PPP, PPP LCP, PPP IPCP, PPP PAP, SIP, RTP, RTCP, RFC 2833, CISCO Skinny, MSRP, DIAMETER, H.248.1 v1 Text, H.248.1 v1 BER, H.248.1 v2 Text, H.248.1 v2 BER, H.248.1 v3 Text, H.248.1 v3 BER, Q.931/H.225, MGCP, H.323, H.245, RADIUS, SDP, IMS XML App part, T.38, SCSI, iSCSI, SCSI, MODBUS, Bluetooth, HCI, L2CAP, DNP3, MPEG2 TS, DOCSIS, MTP3b ITU, MTP3 ITU, MTP T&M ITU, BICC ITU, ISUP ITU, SCCP ITU, SCMG ITU, TCAP/INAP-CS1, TCAP/INAP-CS2, TCAP/INCS1-PLUS-C, TUP ITU, TCAP/INAP-CS2-ETSI, TCAP/SINAP6i, TCAP/SINAP7M, MTP2 ANSI, MTP3b ANSI, MTP3 ANSI, MTP T&M ANSI, ISUP ANSI, SCCP ANSI, SCMG ANSI, ISUP China, TUP China, ISDN, QSIG, DPNSS, IUA, M2UA, M3UA, SUA, M2PA, DUA, IUP UK, ISUP UK, ISUP Rus, ISUP Israel, ISUP France, T-ISUP, TCAP/T-INAP, GSM Abis L3, GSM Abis O&M, GSM TRAU 16k, GSM TRAU 8k, GSM TFO, GSM BSSAP, GSM DTAP, GSM BSSMAP, SGsAP, GSM BSSAP-LE, GSM DTAP-LE, GSM BSSMAP-LE, GSM Radio L3, GSM Radio SS, GSM Radio GMM/SM, GSM Radio LCS, GSM RRLP, GSM Radio SM-CP, GSM SM-RP, BSSAP PLUS, GSM LLP, GSM BSSLAP, TCAP/MAP Ph1, TCAP/MAP Ph2, TCAP/MAP R96, TCAP/MAP R97, TCAP/MAP R98, TCAP/MAP R4, TCAP/MAP R7, TCAP/MAP R9, TCAP/CAP1, TCAP/CAP2, TCAP/CAP3, TCAP/CAP4, GSM SM-TP, SMPP, UCP, CIMD, GPRS, GSM Gb NS, GSM BSSGP, GSM Gb LLC, TOM, SNDCP, GTPv1, GTPv0, GTP PRIME, GTPv2-C, RANAP, NBAP, LTE S1AP, LTE NAS, LTE EMM, LTE ESM, LTE X2AP, IuUP, IS-41, TCAP/IS-41-D, TCAP/IS-41-E, CDMA PDS IS-801, CDMA PDS IS-801, CDMA SMS IS-637, SMS EIA-136-710, SMS EIA-136-710, CDMA, CDMA A11, CDMA A1 BSAP, CDMA A1 BSMAP, CDMA A1 DTAP, CDMA A9.