1200kmSECURITY RESEARCH

1200KM / sigma-rule

Bitbucket Secret Scanning Exempt Repository Added — Sigma Rule

Sigma rule b91e8d5e-0033-44fe-973f-b730316f23a1. Bitbucket Secret Scanning Exempt Repository Added — Sigma Rule. Detects when a repository is exempted from secret scanning feature.

Rule metadata and linked tags

Author: Muhammad Faisal (@faisalusuf). Source status: test; severity: high. Source dates: 2024-02-25 / not supplied.

{
  "product": "bitbucket",
  "service": "audit",
  "definition": "Requirements: \"Basic\" log level is required to receive these audit events."
}

Pinned original Sigma rule · Detection Rule License 1.1

Source SHA-256: 4f29864b43757abb6e0bceb272fab2e26693a5cd85453f8fa149365ae1fc4837

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: Bitbucket Secret Scanning Exempt Repository Added
id: b91e8d5e-0033-44fe-973f-b730316f23a1
status: test
description: Detects when a repository is exempted from secret scanning feature.
references:
    - https://confluence.atlassian.com/bitbucketserver/audit-log-events-776640423.html
    - https://confluence.atlassian.com/bitbucketserver/secret-scanning-1157471613.html
author: Muhammad Faisal (@faisalusuf)
date: 2024-02-25
tags:
    - attack.defense-impairment
    - attack.t1685
logsource:
    product: bitbucket
    service: audit
    definition: 'Requirements: "Basic" log level is required to receive these audit events.'
detection:
    selection:
        auditType.category: 'Repositories'
        auditType.action: 'Secret scanning exempt repository added'
    condition: selection
falsepositives:
    - Legitimate user activity.
level: high

Original YAML and metadata in JSON

False positives

  • Legitimate user activity.

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.