Skip to content

Home TrapSignal

A 360CyberX product

Catch attackers the moment they touch a trap

TrapSignal places decoy identities, credentials, documents, cloud keys and canary tokens across your estate. When an intruder touches one, the signal is graded, correlated and in front of your SOC, with the investigation already under way.

TrapSignal investigation showing a decoy credential used after a canary document was opened, with linked detections and an agent recommendation waiting for a person
6links in the chain, from a decoy to a verdict
11integrations that ship today
2people approve every decoy placement
4plans, priced by your estate, never by detections

Most detection asks

Is this activity unusual?

It needs a baseline to learn and thresholds to tune, and unusual is not always hostile.

TrapSignal asks

Did anyone touch this?

No baseline needed. Nobody has a reason to touch a decoy, so one touch is the signal.

Canary triggeredFY26 bonus plan.xlsx · just now

Why deception

A decoy has no legitimate use, so every touch is worth a look

Attackers who are already inside go looking for credentials, file shares, cloud keys and documents worth taking. TrapSignal plants convincing ones that carry nothing real, so the first interaction becomes a high-confidence signal instead of one more alert in the queue.

  • Alerts you can trust

    Real users have no reason to open a decoy, so a hit is rarely noise. Your team spends its time on intruders, not false alarms.

  • Decoys that stay alive

    Every placement is approved by a second person, and scheduled checks confirm that placed decoys still work.

  • Your stack stays in place

    Your SIEM and EDR keep doing their jobs. Detections flow to them, and their evidence flows back into the case.

How it works

Follow one decoy from placement to verdict

Six steps, one ingestion path, one permission model and one audit trail, so no tool or connector can skip a step. Each slide shows where the step happens in TrapSignal.

Explore the platform

Step 1 of 6

Deploy the trap

Decoy identities, credentials, documents and cloud keys are registered, approved by a second person and placed on real assets.

See how decoys are placed
The TrapSignal signal fabric: decoy identities, credentials, documents and cloud keys feeding deploy, touch, signal, correlate and investigate, connected to the security stack

Step 2 of 6

The attacker touches it

A decoy has no legitimate use, so any interaction is worth a look. Here a canary document is opened on a file share.

See the attacks it catches
A Canary triggered alert for FY26 bonus plan.xlsx above three linked detections rated high, medium and critical

Step 3 of 6

A signal is generated

Repeats are folded together and each signal is graded for severity and confidence, with every factor recorded so anyone can see why.

How signals are graded
The attack story stages with linked detections, and an answer explaining why the case is high priority from its three detections

Step 4 of 6

Activity is correlated

Authorised scanners are recognised, rules matched, MITRE ATT&CK mapped and related detections grouped into one case with its entities.

Inside a TrapSignal case
Three detections correlated into one case, with the decoy, identity and host it involves and the case file listing detections, entities, evidence, tasks and response actions

Step 5 of 6

Your SOC is alerted

The case reaches your SIEM, chat or ticketing system with a priority score and an owner, and evidence from your tools flows back into it.

See the integrations
Investigation INV-2026-0142 marked critical, priority 86 and owned by SOC tier 2, with its attack story, entities and agent recommendation

Step 6 of 6

The investigation begins

The Agent recommends a resolution and stops. A person accepts or rejects it, higher risk actions wait for approval, and a case closes only with a verdict.

How approvals are enforced
The Agent recommendation awaiting a person with accept and reject buttons, and the approvals queue with three tiers of actions

Screens show a demonstration investigation.

Integrations

Connect the tools you already run

Console sign-in uses Microsoft Entra ID. Connecting your other tools is optional, and everything they collect goes through the same pipeline as a canary hit. Integration credentials are kept in a managed secrets vault, never in the database.

  • Microsoft Sentinel
  • Microsoft Defender XDR
  • Microsoft Entra ID
  • Splunk
  • CrowdStrike Falcon
  • Okta
  • ServiceNow
  • Jira Service Management
  • Microsoft Power BI
  • Slack
  • Webhook

These ship today. See what each one does on the TrapSignal platform page.

Plans

Priced by the estate you protect, never by detections

TrapSignal never charges by decoys, detections or investigations. Choose the plan that fits your estate, and the team prices it for you on request.

01

Essentials

For a single security team starting with deception: one production environment, a few hundred assets, and the core decoys, canary tokens and investigations.

02

Professional

For a SOC running deception across several environments, with the Agentic SOC, automation and every integration included.

03

Enterprise

For large or regulated estates: thousands of assets, many cloud accounts and premium support.

04

Custom

For very large or complex environments, with dedicated hosting available, custom retention, negotiated AI capacity, a premium SLA and a named technical account manager.

Want to try it first? Choose Start a trial on the pricing page and the TrapSignal team sets one up with you, with an agreed end date.

Questions

What security teams ask first

More detail is on the TrapSignal resources page, its security and trust page and its pricing questions.

Does TrapSignal replace our EDR or SIEM?

No. They stay in place. TrapSignal sends each detection to them and to your ticketing and chat tools, and brings their evidence back into the case.

What do we need to get started?

A Microsoft Entra ID tenant for console sign-in, and somewhere to place decoys, such as your directory, file shares, endpoints, repositories or cloud accounts. Connecting the tools you already run is optional.

Could a decoy ever be used against us?

Decoys carry nothing real. The platform refuses a decoy that contains a working secret, and decoy identities cannot sign in to anything.

Does the Agent take action on its own?

Only low-risk steps such as enriching an event run automatically, and they are audited. Any step that changes something stops at the approval gate until a person decides.

Who builds and supports TrapSignal?

360CyberX, the Dallas cybersecurity and IT firm behind this website. TrapSignal runs on its own platform at trapsignal.360cyberx.com, with its own sign in and security controls.

Get started

See the chain run on the parts of your estate that matter

A working session with the TrapSignal team: where decoys would sit in your environment, what fires, and how it reaches the tools your SOC already runs.

Demo requests, pricing and sign in continue on trapsignal.360cyberx.com, the TrapSignal site run by 360CyberX.