1200KM / sigma-rule
Bitbucket Secret Scanning Rule Deleted — Sigma Rule
Sigma rule ff91e3f0-ad15-459f-9a85-1556390c138d. Bitbucket Secret Scanning Rule Deleted — Sigma Rule. Detects when secret scanning rule is deleted for the project or repository.
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: 3ca6f685a345129055070df5e36158373ff3fdc0af4f8317592130c051c37ac4
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 Rule Deleted
id: ff91e3f0-ad15-459f-9a85-1556390c138d
status: test
description: Detects when secret scanning rule is deleted for the project or repository.
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'
- 'Repositories'
auditType.action:
- 'Project secret scanning rule deleted'
- 'Repository secret scanning rule deleted'
condition: selection
falsepositives:
- Legitimate user activity.
level: low
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.