A suite of network fingerprinting standards for TLS, TCP, HTTP, SSH, and other protocols to facilitate threat detection and security analysis.
JA4+ is a suite of open-source network fingerprinting standards that generate unique identifiers for network traffic across protocols like TLS, TCP, HTTP, and SSH. It solves the problem of identifying and tracking devices, applications, and threat actors on a network by creating consistent, readable fingerprints from protocol handshakes and attributes.
Security analysts, threat hunters, network engineers, and developers of security tools who need to detect malicious traffic, identify devices, or analyze network behavior.
Developers choose JA4+ for its modern, extensible design that overcomes limitations of older methods like JA3, its wide adoption across industry tools, and its human-readable format that enables both automated detection and manual analysis.
JA4+ is a suite of network fingerprinting standards
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports fingerprinting across TLS, TCP, HTTP, SSH, DHCP, and more in a unified suite, enabling multi-layered threat detection as listed in the methods table.
Uses an a_b_c structure that is both machine-parsable and easy for analysts to interpret manually, facilitating ad-hoc hunting and debugging.
Integrated into major tools like Wireshark, Zeek, and cloud platforms (e.g., AWS, Google Cloud), ensuring interoperability and community-driven updates.
Designs like sorting ciphers and extensions counter fingerprint randomization tactics (e.g., cipher stunting), making it more robust than older methods like JA3.
JA4+ methods beyond JA4 are under the FoxIO License 1.1, which restricts monetization without an OEM license, creating legal hurdles for vendors.
Requires tshark (Wireshark CLI) for full functionality, adding installation and configuration steps that complicate deployment in lean environments.
Generating multiple fingerprints per packet can introduce processing latency, especially for high-volume traffic, which may not suit all monitoring setups.
The a_b_c format and protocol-specific nuances demand deep network knowledge to effectively use for threat hunting, limiting accessibility for junior analysts.