You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+24-35Lines changed: 24 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,15 @@
1
-
# CyberChef
1
+
# CyberChef - Payments
2
+
This fork extends **CyberChef** with a focused set of payment cryptography operations intended for engineering, debugging, and interoperability work in regulated payment environments. The upstream Cyberchef is automatically merged weekly to track the orign.
CyberChef is a simple, intuitive web app for carrying out all manner of "cyber" operations within a web browser. These operations include simple encoding like XOR and Base64, more complex encryption like AES, DES and Blowfish, creating binary and hexdumps, compression and decompression of data, calculating hashes and checksums, IPv6 and X.509 parsing, changing character encodings, and much more.
10
8
11
9
The tool is designed to enable both technical and non-technical analysts to manipulate data in complex ways without having to deal with complex tools or algorithms. It was conceived, designed, built and incrementally improved by an analyst in their 10% innovation time over several years.
12
10
13
-
## Payment Cryptography Extensions
14
-
15
-
This fork extends **CyberChef** with a focused set of payment cryptography operations intended for engineering, debugging, and interoperability work in regulated payment environments.
16
-
17
11
### Scope
18
-
The extensions are designed to help inspect, parse, validate, and construct common payment-industry cryptographic structures without requiring access to live HSMs or production systems.
12
+
The payment extensions are designed to help inspect, parse, validate, and construct common payment-industry cryptographic structures without requiring access to live HSMs or production systems.
19
13
20
14
They are also intended to support software emulation of common HSM-style payment workflows for development, QA, interoperability, and integration testing.
21
15
@@ -32,8 +26,6 @@ Current coverage includes:
32
26
- IBM 3624 PIN offset and VISA PVV issuer-verification helpers
33
27
- Test PAN generation and PAN parsing across major card networks
34
28
- Deterministic, test-vector-driven transformations suitable for offline analysis
35
-
36
-
Future extensions may include:
37
29
- TR-31 key block decryption with provided KBPKs
38
30
39
31
### Non-goals
@@ -76,7 +68,6 @@ Payment-specific recipe chains and standalone operations, pre-loaded at [cyberch
-[Key Generate then KCV (fresh key with check value)][p19]
80
71
-[PAN Generate: Visa curated test card number][p20]
81
72
-[PAN Parse: classify a card number by network][p21]
82
73
-[Card validation data: generate CVV2][p22]
@@ -86,20 +77,19 @@ Payment-specific recipe chains and standalone operations, pre-loaded at [cyberch
86
77
87
78
## Live demo
88
79
89
-
CyberChef Payments is still under active development. As a result, it shouldn't be considered a finished product. There is still testing and bug fixing to do, new features to be added and additional documentation to write.
80
+
CyberChef Payments will always be considered an unfinshed product as it emulates functionality implemetned by Thales, Futurex, and Utimaco HSMs without a formal way to verify all edge cases for implementation specifics. The best validation we can do, and it's a pretty good option if I do say so myself, is known value testing against AWS Payment Cryptograpy and it's Futurex backed HSM fleet.
90
81
91
82
Cryptographic operations in CyberChef should not be relied upon to provide security in any situation. No guarantee is offered for their correctness.
92
83
93
84
[A live demo can be found at cyberchef.jacobmarks.com][1] - have fun!
0 commit comments