Add JA4 signatures for login attempts #476
Merged
+20
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added dedicated fields to document JA4, JA4HTTP & JA4TCP signatures when a TA / phishing kit attempts to authenticate toward a service, typically Entra. As an example, Entra records since December 2025 JA4 signatures in field GatewayJA4.
Member
|
It makes sense. Thank you very much! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added dedicated fields to document JA4, JA4HTTP & JA4TCP signatures when a TA / phishing kit attempts to authenticate toward a service, typically Entra.
As an example, Entra records since December 2025 JA4 signatures in field GatewayJA4.
We use misp-attribute
textto store these signatures, as JA4 is currently only modelled as a MISP object.