1200kmSECURITY RESEARCH

1200KM / sigma-rule

Juniper BGP Missing MD5 — Sigma Rule

Sigma rule a7c0ae48-8df8-42bf-91bd-2ea57e2f9d43. Juniper BGP Missing MD5 — Sigma Rule. Detects juniper BGP missing MD5 digest. Which may be indicative of brute force attacks to manipulate routing.

Rule metadata and linked tags

Author: Tim Brown. Source status: test; severity: low. Source dates: 2023-01-09 / 2023-01-23.

{
  "product": "juniper",
  "service": "bgp",
  "definition": "Requirements: juniper bgp logs need to be enabled and ingested"
}

Pinned original Sigma rule · Detection Rule License 1.1

Source SHA-256: cbc1481e0e65e9b7d90693bffc0280c716cb4aae49c80d40e04c84d28b50a5e2

Detection logic

Original source YAML. Source-tag agreement is not proof of complete semantic coverage. This rule has not been compiled for a SIEM backend or validated against live telemetry here.

title: Juniper BGP Missing MD5
id: a7c0ae48-8df8-42bf-91bd-2ea57e2f9d43
status: test
description: Detects juniper BGP missing MD5 digest. Which may be indicative of brute force attacks to manipulate routing.
references:
    - https://www.blackhat.com/presentations/bh-usa-03/bh-us-03-convery-franz-v3.pdf
author: Tim Brown
date: 2023-01-09
modified: 2023-01-23
tags:
    - attack.initial-access
    - attack.persistence
    - attack.privilege-escalation
    - attack.credential-access
    - attack.collection
    - attack.stealth
    - attack.t1078
    - attack.t1110
    - attack.t1557
logsource:
    product: juniper
    service: bgp
    definition: 'Requirements: juniper bgp logs need to be enabled and ingested'
detection:
    keywords_bgp_juniper:
        '|all':
            - ':179' # Protocol
            - 'missing MD5 digest'
    condition: keywords_bgp_juniper
falsepositives:
    - Unlikely. Except due to misconfigurations
level: low

Original YAML and metadata in JSON

False positives

  • Unlikely. Except due to misconfigurations

Source references

Connected ecosystem references

Exact source-tagged techniques

Telemetry review

Read the original logsource above, then inspect the linked detection workspaces for technique-level sensor context. No per-rule telemetry equivalence is inferred.

Pinned research references. No browser attack runner, live simulation result or validated detector is asserted. Source mappings and validation limits are preserved. ATT&CK / Atomic provenance · Detection provenance.