Deception/ Data
D019F4 Data

🗄️ Honey Database

Decoy RDS/DynamoDB/CosmosDB with fake PII data.

What it is

A small database, or a decoy table inside a real one, holding generated records that look like personal data. Databases are a prime target for theft and extortion. Logins and queries are recorded by the database engine's own audit logging, which has to be switched on; the cloud control-plane log does not record SQL activity.

Implementation requirements

Technologies

AWSAzureGCP

ATT&CK coverage 8

TechniqueTacticStatusConfidenceTier
T1119
Automated Collection
Collection confirmed strong T3
↳ Detection point: the decoy fires at a later step of the attack
↳ Evidence (3 sources)
T1213
Data from Information Repositories
Collection confirmed strong T2
↳ Detection point: the decoy fires at a later step of the attack
↳ Evidence (5 sources)
T1213.006
Databases
Collection confirmed strong T3
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (3 sources)
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.

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)
T1565
Data Manipulation
Impact theoretical moderate T2
↳ Detection point: the attack step itself touches the decoy
↳ Evidence (2 sources)

Direct when the attacker alters the decoy's own records; database-level audit not yet sourced.

T1657
Financial Theft
Impact theoretical weak T4
↳ Evidence (1 source)

Financial theft is an outcome; access to decoy billing data is collection.

Evidence