Improve protocol validation for Kerberos port-88 alerts

Aperta Adatta ai principianti
#7,145 0 commenti 1 reazione 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@eric-forte-elastic ci sta già lavorando.

Dal 9/11/2026.

  • #7146 di @hack-ita — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
76/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python

Direzione di ricerca

Leggi la guida all’indagine in rules/windows/credential_access_kerberoasting_unusual_process.toml e confronta le indicazioni attuali con i tre miglioramenti proposti. Aggiorna la guida per spiegare la convalida del protocollo, la correlazione con Event ID 4769 e i suoi limiti, e come valutare le prove senza considerare una connessione sulla porta 88 come prova di Kerberoasting. Il lavoro è completato quando le indicazioni mantengono l’attribuzione del processo nella telemetria degli endpoint e registrano l’assenza di dati 4769 come una lacuna dell’indagine.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

community Rule: Tuning Team: TRADE
Link to Rule

https://github.com/elastic/detection-rules/blob/main/rules/windows/credential_access_kerberoasting_unusual_process.toml

Rule Tuning Type

False Positives - Reducing benign events mistakenly identified as threats.

Description

The rule identifies outbound endpoint network events to destination port 88 from processes other than the expected or excluded processes.

The current investigation guide correctly notes that the rule is port-based and does not identify the application protocol. Unrelated traffic, such as HTTP on a non-standard port, can therefore produce false positives.

The guide recommends checking whether the destination is a Domain Controller and reviewing Event ID 4769, but it does not explain how to confirm the protocol or correlate the endpoint event with the Domain Controller event accurately.

I suggest a documentation-only improvement to the investigation guide, without changing the detection query:

  1. Validate the application protocol when packet data is available. Use the Wireshark display filter "kerberos" to confirm that the payload is decoded as Kerberos. A capture filter can scope collection to "udp port 88 or tcp port 88". If packet or payload telemetry is unavailable, classify the protocol as unknown rather than treating destination port 88 as proof of Kerberos.

  2. Correlate with Domain Controller Event ID 4769 where applicable. Compare the endpoint event timestamp and client/source IP with the DC event's "IpAddress". Review "TargetUserName", "ServiceName", "TicketEncryptionType", and "Status" to understand the requester, requested service, encryption type, and outcome. Event 4769 is generated when the KDC receives a TGS request; it does not identify the originating endpoint process, so process attribution should remain grounded in endpoint network and process telemetry.

  3. Avoid treating one port-88 connection or one TGS request as proof of Kerberoasting. Consider the requested service/SPN, whether the requester and source host are expected, the volume and distribution of requests, and surrounding endpoint activity. Missing 4769 telemetry should be recorded as an investigation gap, not automatically as benign evidence.

References

Disclosure: I maintain the HackITA resource above. The proposed investigation-guide improvements are intended to stand on their own; please include that reference only if it meets the project's usual relevance and quality bar.

Would this be a useful direction for improving the rule's investigation guide?

Example Data

No response

Lingua principale
Python
Stelle
3k
Fork
759
Merge medio
3g 4h
PR unite (30g)
52

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di elastic/detection-rules

Tutte le issue di elastic/detection-rules

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.