CyberKit

Honeytoken

Also called Canary Token, Honey Credential.

Fake data planted to fire an alert the moment it is touched.

What it is

A honeytoken is a piece of decoy data (a fake credential, file, account, or URL) deliberately planted where legitimate users have no reason to touch it, so that any access generates a high-confidence alert. It exists only to be triggered by an intruder.

Why it matters

Honeytokens are among the lowest-noise detections available, because there is no benign reason to interact with them. A fired token is a strong indicator of compromise or insider activity, and it often catches attackers during reconnaissance.

In practice

Seeding a fake administrator credential in a password vault and alerting the instant anyone attempts to use it.

What to look for

  • Fake credentials, API keys or documents with alerting attached.
  • Any use of the token, which should never happen.
  • Tokens placed where attackers look, such as config files.

Common mistake

Placing them where nobody will find them. They need to sit in the path an attacker would take.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

Read next

  • Behavioral Detection: Detecting threats by the actions they take, not static indicators.
  • False Positive: An alert that flags benign activity as malicious.
  • UEBA: Analytics that profile users and entities to flag risky deviations.

Sources