1200kmSECURITY RESEARCH

1200KM / sigma-rule

Bitbucket Project Secret Scanning Allowlist Added — Sigma Rule

Sigma rule 42ccce6d-7bd3-4930-95cd-e4d83fa94a30. Bitbucket Project Secret Scanning Allowlist Added — Sigma Rule. Detects when a secret scanning allowlist rule is added for projects.

Rule metadata and linked tags

Author: Muhammad Faisal (@faisalusuf). Source status: test; severity: low. 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: d70f2e95f30bb863542d3b9ff3891705110986446bf24170e4f27480e30b0145

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 Project Secret Scanning Allowlist Added
id: 42ccce6d-7bd3-4930-95cd-e4d83fa94a30
status: test
description: Detects when a secret scanning allowlist rule is added for projects.
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: 'Projects'
        auditType.action: 'Project secret scanning allowlist rule added'
    condition: selection
falsepositives:
    - Legitimate user activity.
level: low

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.