Skip to content

Canary Token

A canary token is a deceptive artifact, such as a fake credential, file, URL or API key, placed in an environment so that security teams are alerted when an attacker accesses it. Named after the canaries once used in coal mines to warn of danger, canary tokens act as tripwires: legitimate users have no reason to touch them, so any interaction is a high-confidence signal of an intrusion. They are a simple, low-cost way to detect attackers early, and they form one building block of enterprise deception.

 This guide covers how canary tokens work, their limitations at enterprise scale, MITRE ATT&CK coverage, compliance mapping, and how Acalvio ShadowPlex extends deception across IT, OT, cloud, and identity environments.

At a glance

  • What it is: a canary token is a fake file, credential, URL, or API key that no legitimate user needs, so any access to it raises a high-confidence alert.
  • How it works: each token carries a unique DNS, HTTP, or authentication callback that fires when the artifact is opened, used, or resolved.
  • Three layers: file-based tokens, credential and identity tokens, and cloud and infrastructure tokens.
  • Same idea, different scale: the free Canarytokens tool from Thinkst and enterprise deception platforms such as ShadowPlex both use the alert-on-access principle; platforms add automated placement, lifecycle management, and investigation.
  • Where it fits: canary tokens run alongside your SIEM, EDR, and IAM tools rather than replacing them.

What is a canary token?

Definition and core concept

A canary token is a lightweight deception artifact, a fake credential, file, URL, or API key, placed inside a network or system to alert security teams the moment an attacker accesses it.

The detection model is deterministic: no scoring, no thresholds, just access equals alert. No legitimate user should ever touch a planted deception artifact, so access is itself strong evidence of intrusion.

Historical origin

In 1986, Clifford Stoll, a systems administrator at Lawrence Berkeley National Laboratory, followed a 75-cent billing discrepancy to a KGB-linked hacker moving across government and defense networks. His account, The Cuckoo’s Egg (1989), is the first published story of deception-based detection.

The name comes from the coal-mine canary, which warned miners of gas before they could smell it. A canary token is an early warning, not a barrier: it tells you an attacker is present before they can escalate.

The technique has moved through three generations: manual tripwires, purpose-built canary token tools with managed callbacks, and AI-driven deception platforms that generate, place, and rotate artifacts automatically.

Many practitioners know the idea through Canarytokens, a free tool from Thinkst Applied Research. It generates tokens such as Microsoft Word and Excel documents, Adobe PDFs, AWS API keys, DNS names, kubeconfig files, and WireGuard configurations, and sends an alert when one is triggered. The project is open source, and Thinkst publishes a Docker-based installation for teams that want to self-host.

Explore the full deception technology resource library →

Where canary tokens fit in deception technology

  • Canary token: a lightweight tripwire inside real environments that raises a binary alert on access. The entry point to deception.
  • Honeytoken: a data-layer artifact in real data stores such as Active Directory and databases. Identity honeytokens (honey hashes, honey SPNs, decoy accounts) detect credential dumping, Kerberoasting, and lateral movement.
  • Honeypot: a full decoy system deployed alongside real infrastructure.
  • Deception technology: the platform category that manages all three, handling placement, lifecycle, coverage analytics, and investigation.

How do canary tokens work?

Canary tokens work through an alert-on-access model: each token carries a unique DNS or HTTP callback that fires the instant an attacker opens, authenticates with, or resolves the artifact.

Picture a fake admin credentials file on a network share, a decoy API key in a GitHub repository, and a fake AWS IAM key in a developer’s config directory. None has an operational function. When an attacker, a curious insider, or a credential-scanning tool touches one, a beacon fires.

The alert-on-access model

Opening a canary Word document fetches a remote resource and triggers a DNS callback. Using a fake IAM key surfaces as a login attempt on a credential that should never be used. Requesting a ticket for a honey SPN appears in the domain controller’s event log. Each alert carries the artifact, access method, timestamp, and source IP or account.

This is preemptive detection: the alert fires on access itself, before behavioral analytics have enough correlated signals. Your existing tools still see the activity; the canary token answers a question they find hard to judge in isolation: why did anything touch an asset no legitimate process should need?

Deployment and placement

Placement should follow the attacker’s search path. After initial access, attackers enumerate file shares, query Active Directory for service accounts, and inspect repositories for API keys, so the share gets a fake “credentials-backup.xlsx,” Active Directory gets a decoy service account, and the repository gets a decoy API key.

Canary token examples: 8 types and use cases

Eight primary canary token types exist: file, credential, API key, DNS, cloud, email, database, and network. Each maps to a specific point in the attack chain where adversaries search, collect, or test stolen artifacts.

File-based canary tokens

A file canary carries a remote resource reference that triggers a DNS or HTTP callback when opened. Common formats, familiar from Canarytokens, include Microsoft Word and Excel files, Adobe PDFs, Windows folders, kubeconfig files, and WireGuard VPN profiles. Place them on attractively named shares (ADMIN, PASSWORDS), privileged users’ systems, and backup directories. Files placed alphabetically first in a directory fire early in a ransomware encryption run.

Detection coverage: MITRE ATT&CK T1083 (File and Directory Discovery) and T1005 (Data from Local System) for local system canaries. T1039 (Data from Network Shared Drive) for network share canaries.

Credential and identity canary tokens

A credential canary is a fake local, Active Directory, or service account with an attractive name that alerts on its first authentication attempt. Identity honeytokens go further: a honey hash is a fake NTLM hash planted in memory that alerts when dumped and replayed, and a honey SPN is a fake Kerberos service whose ticket requests are a high-confidence indicator of Kerberoasting.

Detection coverage: T1078 (Valid Accounts) through credential canaries. T1552 (Unsecured Credentials) through API key canaries. T1003 (OS Credential Dumping) and T1550.002 (Pass the Hash) through honey hashes. T1558.003 (Kerberoasting) through honey SPNs.

Cloud and infrastructure canary tokens

Cloud IAM key canaries in AWS, Azure, and GCP detect unauthorized access through T1078.004 (Cloud Accounts). API key canaries in serverless function environment variables, container configurations, and CI/CD pipeline variables detect T1552 (Unsecured Credentials) and T1528 (Steal Application Access Token). Object canaries in S3 buckets, Azure Blob storage, and GCS containers trigger on GET requests, detecting T1567 (Exfiltration Over Web Service).

DNS canary tokens carry a unique hostname that beacons on resolution, so an exfiltrated document opened outside the network reveals that data left (T1048, Exfiltration Over Alternative Protocol).

Email, database, and network canary tokens

Email canary tokens are unique decoy addresses planted in contact lists, mailbox exports, or CRM records. Any message sent to one shows that the list was harvested, which maps to T1114 (Email Collection).

Database canary tokens are fake records, such as a customer row or a credentials table entry, that alert when queried or exported. They detect T1213 (Data from Information Repositories).

Network canary tokens are fake services on unused IP addresses. Because no production system should connect to them, an internal connection is a strong signal of scanning or lateral movement (T1021, T1046).

Free Canarytokens or a deception platform?

Canarytokens is a capable free tool, and for many teams it is the right answer. The choice depends on your situation.

Your situationFree CanarytokensEnterprise deception platform
A handful of tripwires on a few sensitive files or foldersThe right choice. Create a token on canarytokens.org in minutes, at no cost.More than you need.
You need to self-host rather than use the hosted serviceSupported. The server is open source on GitHub, with a recommended Docker install that you run and maintain.A commercial platform with vendor support and maintenance.
Deploying hundreds of tokens across an enterprise environmentPossible, but each token is created, placed, and tracked by your team.ShadowPlex Fluid Deception automates placement, freshness, and rotation.
Detecting Kerberoasting or other AD-specific techniquesThe documented token types include an Azure Entra ID login token; no honey SPN or honey hash token is listed.Identity honeytokens (honey SPNs, honey hashes, decoy accounts) through ShadowPlex Identity Protection.
Producing evidence for an auditPer-token alert records; inventory and coverage reporting are yours to build.Deployment manifests, coverage analytics, and alert histories.
Turning a single alert into a full investigationAn alert with token and source details; investigation happens in your own tools.ATT&CK-mapped alerts, SIEM and SOAR integration, and the Threat Hunting Workbench.

Canary tokens vs. honeytokens: key differences

Canary tokens are tripwires that alert on access. Honeytokens sit inside real data stores and detect identity attacks such as credential dumping, Kerberoasting, and lateral movement.

Canary tokens vs. enterprise honeytokens: capability comparison

DimensionCanary tokensEnterprise honeytokens (e.g., ShadowPlex)
ArchitectureTripwire artifact, alert on accessData-layer artifact, embedded in real data stores
EnvironmentPrimarily IT networksIT, OT, cloud, identity
Alert outputBinary access alertThreat intelligence with ATT&CK technique mapping
SophisticationStatic tripwireDynamic, refreshed, context-aware

Canary tokens vs. honeypots: what is the difference?

Honeypots are full decoy systems that sit beside production on dedicated infrastructure and observe attacker behavior over a session. Canary tokens sit inside production and need nothing beyond the artifact. Use canary tokens for lightweight tripwires, honeypots for behavioral intelligence on attacker TTPs, and both in a mature program.

Canary tokens vs. honeytokens vs. honeypots: architecture comparison

Canary tokenHoneytokenHoneypot
What it isTripwire artifact embedded in real environmentData-layer artifact embedded in real data storesFull decoy system deployed alongside real infrastructure
DetectsFile access, credential use, API key use, DNS resolutionCredential dumping, Kerberoasting, pass-the-hash, lateral movementAttacker TTPs, tools, commands, lateral movement patterns
InfrastructureNone (file, credential, or DNS record)None (data record or hash in existing store)Dedicated server or network segment
Alert typeBinary: access equals alertAttack chain: credential theft through lateral movementContinuous behavioral observation over session
Best forFast detection coverage in file systems, cloud, and reposIdentity attack chain detection in AD and credential storesDeep behavioral intelligence on attacker TTPs

Canary token pros and cons

Advantages

  • High-fidelity signals. Deterministic detection with no scoring or thresholds to tune.
  • Lightweight deployment. No agents, servers, or production changes; about five minutes per token manually.
  • Broad coverage. From ransomware early warning to Kerberoasting and cloud key abuse. Acalvio’s mapping lists 13 HIGH-confidence techniques across Initial Access, Credential Access, Lateral Movement, Discovery, Collection, Exfiltration, and Impact.

Limitations

Five architectural gaps emerge when canary tokens are deployed at enterprise scale: single-event detection without campaign visibility, manual lifecycle causing silent coverage erosion, no coverage analytics, no compliance documentation, and architecture failures in agentless OT and cloud environments. The decision table above covers correlation, lifecycle, and audit evidence; the remaining gaps are below.

Canary token limitations and enterprise deception platform responses

Canary token limitationEnterprise deception platform response
No coverage analyticsCoverage dashboards showing deception density by environment, subnet, and asset class
OT environment gapNetwork-layer honeypots emulating industrial protocols without touching production control systems
Cloud coverage degradationProvisioning-layer integration that seeds honeytokens at workload launch

MITRE ATT&CK coverage: what canary tokens detect

The tables below map canary token coverage to the MITRE ATT&CK framework (v20), including what falls outside it.

Technique coverage in Acalvio’s mapping: HIGH confidence (13 techniques)

Canary token coverage, HIGH-confidence techniques (MITRE ATT&CK v20)

Technique IDTechnique nameTacticHow detectedDeception type
T1078Valid AccountsInitial Access / Persistence / Privilege Escalation / StealthCredential canary fires on authentication attempt against fake accountCredential canary, identity honeytoken
T1003OS Credential DumpingCredential AccessHoney hashes in memory trigger when dumped credentials are subsequently used for authenticationIdentity honeytoken
T1558Steal or Forge Kerberos TicketsCredential AccessHoney SPNs detect Kerberoasting (T1558.003). Honey accounts without pre-auth detect AS-REP Roasting (T1558.004)Identity honeytoken
T1552Unsecured CredentialsCredential AccessAPI key canaries in config files, credential canaries in documentation, cloud canaries at metadata endpointsAPI key canary, credential canary, cloud canary
T1550Use Alternate Authentication MaterialLateral MovementHoney hashes detect pass the hash (T1550.002). Fake Kerberos tickets detect pass the ticket (T1550.003)Identity honeytoken
T1021Remote ServicesLateral MovementHoneypots running RDP, SMB, SSH, and WinRM detect lateral movement. Any internal connection to a decoy service is a high-confidence threat signalNetwork canary, low-interaction honeypot
T1486Data Encrypted for ImpactImpactFile canaries placed alphabetically first in directories detect ransomware encryption. Alert fires when canary file is modified or encryptedFile canary
T1083File and Directory DiscoveryDiscoveryFile canary tokens in directories detect access activity during adversary enumerationFile canary
T1005Data from Local SystemCollectionFile canary tokens on local systems detect data collection attemptsFile canary, document honeytoken
T1039Data from Network Shared DriveCollectionFile canary tokens on network shares detect unauthorized browsing and collectionFile canary
T1213Data from Information RepositoriesCollectionDatabase canary records and honeytoken entries in wikis detect unauthorized data accessDatabase canary, database honeytoken
T1048Exfiltration Over Alternative ProtocolExfiltrationDNS canary tokens embedded in exfiltrated documents trigger when opened externally, resolving the canary’s unique hostnameDNS canary
T1528Steal Application Access TokenCredential AccessAPI key canaries and cloud token canaries detect token theft when stolen tokens are used for authenticationAPI key canary, cloud canary

MEDIUM-confidence techniques (5 techniques)

Canary token coverage, MEDIUM-confidence techniques (MITRE ATT&CK v20)

Technique IDTechnique nameWhy medium confidenceDeception type
T1595Active ScanningNetwork honeypots on unused IPs detect scanning, but legitimate vulnerability scanners may trigger. Context-dependentNetwork canary, low-interaction honeypot
T1046Network Service DiscoveryHoneypots presenting fake services detect enumeration, but legitimate network management may trigger alertsLow-interaction honeypot, network canary
T1110Brute ForceHoneypot authentication services attract brute force, but automated internet scanners reduce confidence without IP contextLow-interaction honeypot, network canary
T1018Remote System DiscoveryDNS canaries and network canaries detect discovery, but scope of legitimate management activity varies by environmentDNS canary, network canary
T1114Email CollectionEmail canaries detect harvesting, but spam delivery to decoy addresses creates false positive potential. Unique address generation reduces noiseEmail canary

MITRE Engage mapping

MITRE Engage formalizes the defender activities that counter ATT&CK behavior, under three goals (Expose, Affect, Elicit) and their approaches.

MITRE Engage mapping for canary token operations

Canary token operationEngage activityEngage approach (goal)Operational meaningATT&CK countered
Decoy credentialLuresDetect (Expose)Deploy fake credentials that alert when used. The Engage formalization of the credential canary tokenT1078, T1003, T1552, T1110
Decoy accountLuresDirect (Affect)Create fake user accounts to attract credential harvesting, guiding adversaries toward monitored accountsT1078, T1087, T1558
Decoy contentLuresDetect (Expose)Create fake content to attract adversary attention. Formalizes the file canary token conceptT1005, T1039, T1083
Lived-in artifactsPocket LitterReassure (Elicit)Add realistic artifacts to deception environments to make decoys appear lived-in. Supports credibility of all deception operations(Supports all)
Redirect to decoy segmentIsolationPrevent (Affect)Redirect lateral movement toward honeypot network segments, isolating adversary from production systemsT1021, T1570

Detection gaps: techniques canary tokens do not cover

  • T1087 and T1482 (Account and Domain Trust Discovery) need identity honeytokens, not simple tripwires. ShadowPlex covers these with platform-level identity honeytokens.
  • T1046, T1110, and T1595 at enterprise scale need coordinated honeypot coverage across subnets.
  • Privilege escalation is not observed directly. Identity honeytokens detect the abuse of escalated credentials afterward (T1078, T1550), so do not evaluate deception as a host-based escalation detector.

Canary tokens and compliance

NIST SP 800-53 Rev. 5 includes two controls written for deception. SC-26, “Decoys,” reads: “Include components within organizational systems specifically designed to be the target of malicious attacks for detecting, deflecting, and analyzing such attacks.” SC-30, “Concealment and Misdirection,” covers techniques that make it harder for adversaries to target and compromise systems. Neither control is selected in the Low, Moderate, or High baselines in SP 800-53B. They are optional controls an organization chooses to adopt, not a mandate. Where an organization selects them, deception technology directly satisfies SC-26 and supports SC-30.

Additional frameworks align with deception capabilities without explicitly requiring them: PCI DSS v4.0.1 Requirements 10 and 11 (logging, monitoring, and security testing), NIST CSF 2.0 DE.CM (continuous monitoring), ISO/IEC 27001:2022 Annex A 8.16 (monitoring activities), and SOC 2 CC7.2 (monitoring for anomalies and security events).

Auditor requirements vs. what canary tokens and enterprise platforms provide

Auditor requirementStandalone canary tokensEnterprise deception platform
Deployment documentationNone, no logging of where tokens were placedAutomated deployment manifests
Coverage reportsNone, no visibility into total coverageCoverage analytics dashboards with percentage metrics
Alert historyPer-alert logs (where exported to SIEM)Centralized alert history with correlation
Rotation schedulesManual, if maintained at allAutomated rotation with scheduling logs
Incident correlationManual, analyst must link alertsAutomated ATT&CK technique mapping, attack chain visualization
SC-26 evidence (where selected)Alert logs onlyDeployment topology plus technique coverage mapped to SC-26

Implementation best practices

Where you place canary tokens, and how many, determines whether you detect attackers or create the appearance of detection. An attacker who encounters a canary token with an obviously fake name will recognize it as a tripwire. An attacker who encounters “svc_sqlprod_backup_2024.txt” next to real credential files will access it without hesitation.

Placement strategy

Place canary tokens where attackers search, not where defenders think attackers search. The attacker’s search pattern follows the attack chain: initial enumeration of file systems and shares, discovery of Active Directory structure and service accounts, inspection of code repositories and configuration files, lateral movement through high-value workstations.

High-value locations for file canary tokens: Network shares with names suggesting credentials or sensitive data. Home directories of privileged users. Backup directories. Shared drives where configuration files accumulate.

High-value locations for credential canary tokens: Active Directory OUs containing service accounts. Local administrator accounts on high-value servers. IAM key stores in cloud environments. Configuration files in code repositories.

Blending requirements: Every canary token must appear indistinguishable from legitimate artifacts. Realistic file names matching surrounding naming conventions. Metadata matching surrounding files’ age and authorship. Credential names following the organization’s service account convention. Content that appears authentic on inspection.

Scale considerations

Manual (fewer than 50 tokens): Feasible for one engineer; genuine but narrow detection with no lifecycle automation. Semi-automated (50 to 200 tokens): Scripts and spreadsheets manage records, but gaps multiply faster than manual processes can address. Enterprise (200+ tokens, multi-environment): Requires a platform with automated placement, lifecycle management, coverage dashboards, and SIEM integration. ShadowPlex’s Fluid Deception methodology uses AI to automate credential deployment and freshness by matching metadata (creation dates, last-logon timestamps, password age) to the environment’s real credential patterns, and rotating artifacts on schedules aligned with production service accounts. This AI-driven lifecycle management maintains contextually authentic deception across production environments.

Integration requirements

Canary token alerts must feed directly into existing SIEM and SOAR infrastructure. An alert that sits in a separate monitoring console, disconnected from the SOC’s operational toolchain, is easy to delay or overlook.

SIEM integration ensures deception alerts appear in the same interface as all other security events, with the same escalation workflows and analyst routing. SOAR integration enables automated response playbooks triggered at the moment a canary fires. ATT&CK technique mapping converts a raw canary alert into structured threat intelligence, immediate investigation context that a raw alert does not provide.

For enterprise deployments requiring automated placement, lifecycle management, and SIEM integration, Acalvio ShadowPlex integrates with your existing SIEM and SOAR infrastructure, forwarding deception alerts for correlation and automated response. For identity-layer coverage, see ShadowPlex Identity Protection for Active Directory.

Why canary tokens matter for enterprise security

Mandiant’s M-Trends 2026 report found that global median dwell time rose to 14 days, up from 11 days. CrowdStrike’s 2026 Global Threat Report measured average eCrime breakout time at 29 minutes in 2025, with the fastest observed breakout at 27 seconds. Canary tokens shorten that detection gap from days to the moment of artifact access. They represent the preemptive layer in an enterprise detection stack, delivering detection at the point of access and operating ahead of the attacker’s timeline rather than behind it. When an attacker accesses a planted deception artifact, the security team has a high-confidence signal of an active intrusion, with a specific artifact type and location as the starting point for investigation.

Insider threat detection

Canary tokens detect insider threats in scenarios where behavioral analytics struggle, because an authorized user accessing files they should not access looks nearly identical to an authorized user accessing files they should access. No legitimate user should ever access a planted deception artifact. When one does, whether through malice, curiosity, or following instructions from an external attacker who has compromised their credentials, the signal is clear. Identity honeytokens extend insider detection to credential misuse: an insider who extracts and uses a honey hash, or who attempts to authenticate with a decoy service account, generates a high-confidence alert without the long-baseline behavioral analysis that most insider threat tools depend on.

From canary tokens to enterprise deception

Deception technology turns every network artifact into a potential detection surface, and it runs alongside your SIEM, EDR, and IAM tools rather than replacing them. Acalvio’s proof points include 25 patents, recognition as a GigaOm Radar Leader, and a Gartner Tech Innovator designation in Preemptive Cybersecurity. ShadowPlex provides automated placement, coverage analytics, compliance documentation, and the Threat Hunting Workbench to convert a single deception alert into a complete investigation.

See how ShadowPlex deception works: schedule a demo →

Additional resources

Frequently Asked Questions

A canary token is a lightweight deception artifact, a fake credential, file, URL, or API key, placed inside a network or system to alert security teams the moment an attacker accesses it. Named after the coal-mine canary metaphor, canary tokens provide a binary detection signal: because no legitimate user should ever interact with a planted deception artifact, any access is a high-confidence indicator of a threat. Access equals alert, with no behavioral analysis or threshold tuning required.

Eight primary types exist: (1) file canary tokens, documents that generate a DNS or HTTP beacon when opened. (2) credential canary tokens, fake Active Directory accounts or IAM keys that alert on authentication. (3) API key canary tokens, fake tokens in code repositories and configuration files. (4) DNS canary tokens, unique DNS names that beacon on resolution. (5) cloud canary tokens, AWS access keys, Azure service principals, and GCP credentials. (6) email canary tokens, decoy addresses in contact lists that detect harvesting. (7) database canary tokens, fake records in databases that alert on query. (8) network canary tokens, fake services on unused IP addresses. Identity honeytokens, honey hashes, honey SPNs, and decoy accounts, extend credential canaries into the full identity attack chain at the data layer.

Canary tokens use an alert-on-access detection model. When an attacker accesses, opens, or resolves a canary artifact, it triggers a DNS or HTTP beacon that notifies the security team. The detection is deterministic: access equals alert, and a properly deployed canary token produces a high-fidelity detection signal.

Canary tokens are single-tripwire artifacts embedded inside real environments, a fake credential in a file share, a planted API key in a code repository. Honeytokens are data-layer deception artifacts embedded in real data stores, designed to detect more sophisticated activities: credential dumping via honey hashes, Kerberoasting via honey SPNs, and identity-based lateral movement via decoy accounts. Honeypots are full decoy systems, servers, services, or network segments, deployed alongside real infrastructure to observe attacker TTPs over extended sessions. The taxonomy: canary tokens are the most lightweight entry point, honeytokens operate at the data layer, and deception technology platforms orchestrate all three artifact types with lifecycle management.

Sophisticated adversaries may avoid obvious canary tokens through metadata analysis, timing correlation, or network traffic analysis. Countermeasures: realistic artifact naming matching the surrounding environment, natural file paths, environment-matched metadata (creation dates, file sizes, authorship), and AI-driven placement that continuously adapts deception artifacts to the production fingerprint.

NIST SP 800-53 Rev. 5 includes SC-26 (Decoys) and SC-30 (Concealment and Misdirection), but neither is selected in the Low, Moderate, or High baselines, so they apply only where an organization chooses to adopt them. Where selected, deception directly satisfies SC-26 and supports SC-30. PCI DSS v4.0.1 Requirements 10 and 11, NIST CSF 2.0 DE.CM, ISO/IEC 27001:2022 Annex A 8.16, and SOC 2 CC7.2 align with deception capabilities without requiring them.

Yes. Canary tokens are a long-established defensive technique, and the artifacts are inert: a token only reports that it was opened, used, or resolved. The main risks are operational, such as an authorized user or a backup job touching a poorly placed token, so place tokens where legitimate processes have no reason to go and tell the right people in your SOC they exist.

The Canarytokens tool from Thinkst is free to use at canarytokens.org, and its source code is available on GitHub for teams that want to self-host. Enterprise deception platforms such as ShadowPlex are commercial products that add automated placement, lifecycle management, coverage analytics, and investigation workflows for large environments.

Start where attackers look first after initial access: network shares with attractive names, privileged users’ home directories, Active Directory service account OUs, and configuration files or repositories that hold API keys. Name each token to match the surrounding files or accounts so it blends in, and route its alerts into your SIEM so the SOC sees them alongside other events.

External Citations

  1. Mandiant M-Trends 2024, Attacker dwell time: 10 days median
  2. Verizon Data Breach Investigations Report, Identity in breaches: more than 80%
  3. NIST SP 800-53 Rev 5, Control SC-26 “Honeypots”: https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final
  4. MITRE ATT&CK v15.1: https://attack.mitre.org
  5. MITRE Engage v1.0: https://engage.mitre.org
  6. Clifford Stoll, The Cuckoo’s Egg, 1989
  7. MITRE ATT&CK T1078 (Valid Accounts): https://attack.mitre.org/techniques/T1078/
  8. MITRE ATT&CK T1558.003 (Kerberoasting): https://attack.mitre.org/techniques/T1558/003/
  9. CrowdStrike 2024 Global Threat Report: https://www.crowdstrike.com/en-us/resources/reports/crowdstrike-2024-global-threat-report/
Acalvio, the Ultimate Preemptive Cybersecurity Solution.