Deception/ Storage
D015F3 Storage

📦 Honey Storage Bucket

Decoy S3/Blob/GCS buckets with attractive names.

What it is

A storage bucket named in the normal scheme and filled with fake but plausible files. Storage is a common first target, because buckets often hold backups, exports and credentials. Listing or reading inside the decoy bucket is recorded by data-access logging; listing all buckets in the account does not single it out.

Implementation requirements

Technologies

AWSAzureGCP

ATT&CK coverage 14

TechniqueTacticStatusConfidenceTier
T1074
Data Staged
Collection theoretical weak T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)

Staging into a defender-planted location is not documented attacker behaviour.

T1074.002
Remote Data Staging
Collection theoretical weak T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (1 source)

Staging into a decoy location is not documented behaviour.

T1119
Automated Collection
Collection confirmed strong T3
↳ Detection point: the decoy fires at a later step of the attack
↳ Evidence (3 sources)
T1530
Data from Cloud Storage
Collection confirmed strong T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (4 sources)
T1222
File and Directory Permissions Modification
Defense Impairment theoretical moderate T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (3 sources)
T1135
Network Share Discovery
Discovery theoretical moderate T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)

Moderate: listing share names (net view) does not access the share; the alert fires when the attacker opens it.

T1526
Cloud Service Discovery
Discovery theoretical moderate T1
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (3 sources)

Moderate: discovering that a service exists does not necessarily touch a decoy resource in it.

T1580
Cloud Infrastructure Discovery
Discovery theoretical moderate T1
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (3 sources)

Moderate: a plain List call does not name the decoy. The alert fires when the attacker queries the decoy resource itself, which the token documentation does not break down by API call.

T1619
Cloud Storage Object Discovery
Discovery confirmed strong T1
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (1 source)
T1537
Transfer Data to Cloud Account
Exfiltration theoretical weak T4
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)

Transfers to the attacker's own account touch no decoy, unless a decoy snapshot or bucket is shared out.

T1485
Data Destruction
Impact theoretical moderate T4
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (4 sources)

Deleting a decoy snapshot or database is a management event; deleting objects in a decoy bucket needs data events enabled.

T1486
Data Encrypted for Impact
Impact confirmed strong T4
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (3 sources)
T1491.002
External Defacement
Impact theoretical weak T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (1 source)

Defacing a decoy property needs access that would already have alerted.

T1080
Taint Shared Content
Lateral Movement confirmed strong T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)

Evidence