Deception-generated threat intelligence

Threat intelligence created from real adversary interaction

FIRCY Sense turns interactions with controlled decoys into environment-specific intelligence for investigation. Decoys include web applications, credentials, APIs, MCP surfaces and documents. Analysts and approved tools can use the available evidence and context through configured investigation, export and response workflows.
  • Environment-specific evidence
  • Targeting and infrastructure context
  • Risk and confidence signals
  • CTI and SOC-ready outputs
Try it out See integrations

From interaction to intelligence

FIRCY Sense threat intelligence signal flow illustration

The strongest intelligence begins with controlled evidence: what was touched, where it came from, what it resembled, and what should happen next.

Generated by interaction

Create intelligence from real adversary activity with your own decoys, APIs, MCP server surfaces, services, credentials, and sensitive paths.

Enriched with context

Add network, infrastructure, targeting, behavioural, and historical context without treating every match as the same kind of evidence.

Ready for operations

Move validated findings into investigation, hunting, case, automation, and CTI workflows.

AI in FIRCY Sense

Three separate AI-related functions

Detecting suspicious AI-agent activity, assisting analysts with AI, and connecting approved AI tools are different functions. Each uses different evidence and controls, so FIRCY Sense keeps them distinct.

Detect suspicious AI-agent activity

Observe suspicious interaction with decoy APIs, MCP surfaces, credentials and documents. Use the available evidence to investigate unknown automation or approved agents operating outside their task, without treating a decoy interaction alone as proof of AI identity or malicious intent.

  • MCP enumeration and resource access
  • Tool-call and prompt-probe behaviour
  • Follow-on access to decoy-token and callback signals

Investigate with AI assistance

Where enabled, AI-assisted summaries and follow-up guidance can help analysts explore a finding. Keep generated explanations tied to the evidence and distinguish observed facts from interpretation.

  • Summary and why-it-matters context
  • Recommended next actions
  • Follow-up questions and saved outputs where enabled

Connect approved AI tools

Use the production FIRCY Sense MCP integration to provide approved tools with configured intelligence context for investigation. This is separate from monitoring interactions with decoy MCP surfaces.

  • Scoped access for approved tools
  • IP, ASN, and targeted-activity context
  • Useful for analyst-guided AI workflows

What makes it different

Start with observed behaviour, then add context

Generic intelligence can be useful, but it does not always answer why your team should care right now. FIRCY Sense anchors intelligence in observed interaction with your environment, then adds context that helps analysts decide what matters.

Observed interaction

Capture evidence from activity that should not normally occur, including what was accessed, tested, followed, reused, or probed.

Environment-specific targeting

Show which decoys, services, locations, paths, identities, and themes were touched so the event is tied back to your environment.

Operational context

Add enough surrounding context for analysts to triage, hunt, escalate, or publish without rebuilding the story from raw events.

How it fits

Not another generic threat feed

FIRCY Sense is not designed to replace strategic threat intelligence, dark web monitoring, vulnerability intelligence, or global IOC feeds. It adds a customer-specific evidence layer: suspicious interaction with deception signals in your own environment.

Use external CTI to understand the broader landscape

Threat actors, campaigns, malware, vulnerabilities, infrastructure, and industry targeting still matter.

Use FIRCY to understand signals earlier

Deception signals show which lures, credentials, APIs, MCP server surfaces, paths, services, and workflows attracted suspicious interaction.

Use both to improve decisions

External context can enrich FIRCY events, while FIRCY events can make external intelligence more relevant to your SOC.

Example outputs

What analysts receive

The output should be more useful than a raw alert. FIRCY Sense is designed to preserve the evidence, explain the context, and make the next workflow clear.
  • Triggered signal and affected decoy, credential, API, MCP server surface, service, or path
  • Source, network, infrastructure, and user-agent context where available
  • Targeting context tied back to the customer environment
  • Risk and confidence explanation
  • Suggested triage, hunting, containment, or enrichment actions
  • Export, webhook, or publication path into configured SOC and CTI workflows
  • MCP service access for approved AI tools where configured

Threat intelligence capabilities

Turn deception telemetry into intelligence analysts can use

The value is not a longer alert. It is a clearer view of the source, the infrastructure involved, what attracted attention, and the response path available to your team.

See what was targeted

Connect source activity to the specific decoys, APIs, MCP server surfaces, services, application paths, identity artefacts, and sensitive workflows that attracted attention.

  • Target events and locations
  • Services and paths touched
  • Environment evidence linked to the same source

Understand the source in context

Enrich source infrastructure with ownership, network, location, reputation, and historical activity context where available.

  • Network and owner context
  • First-seen and last-seen activity
  • Risk scoring and confidence bands

Separate evidence from neutral context

Help analysts distinguish evidence that raises concern from infrastructure context that may simply explain what a source is.

  • Malicious indicator matches kept distinct
  • Neutral infrastructure context labelled separately
  • Risk handled without flattening every match into an alert

Pivot across related activity

Move from a single event into related IP, ASN, service, targeted-asset, and user-agent context so analysts can scope activity more quickly.

  • IP and ASN investigation
  • Targeted asset and service pivots
  • User-agent and tooling patterns

Package validated findings for CTI workflows

Move selected findings into structured intelligence workflows with export, publish, provenance, and policy-aware handling when configured.

  • Structured event packages
  • Provenance-aware records
  • Policy-controlled publication

From signal to CTI

How deception-generated intelligence moves through FIRCY Sense

FIRCY Sense is designed to preserve the path from raw interaction to usable intelligence, so analysts can see the evidence and response teams can act on it.

Interaction occurs

A source, identity, or actor touches a decoy, credential, path, service, or sensitive workflow that should not be part of normal activity.

Suspicious touchpoint triggered Event and environment context captured Related evidence linked

Context is added

The source and behaviour are enriched with infrastructure, targeting, reputation, history, and user-agent context where available.

Source context reviewed Targeting context attached Risk and confidence updated

Analysts get a usable story

The event becomes a structured investigation object that can support triage, hunting, publication, or response automation.

Similar activity surfaced Next actions suggested Validated findings routed

For analysts

Make intelligence useful at the point of investigation

A strong intelligence workflow helps analysts answer practical questions quickly: who or what appears to be interacting with us, what did they target, what else have we seen, and what should we do next?

Threat briefing

Summarise recent activity, meaningful patterns, and the events most worth attention.

IP and ASN lookup

Review source activity, targeting, risk context, and related environment evidence from one investigation view.

Event chaining

Connect events across time, source, target, and behaviour so a single signal can become a fuller investigation.

Timeline and pattern views

Understand when activity emerged, how it developed, and whether it resembles previous activity.

Event insights

Generate evidence-scoped summaries, next actions, similar-event context, and follow-up answers where enabled.

CTI hand-off

Export or publish selected findings into downstream intelligence and SOC workflows when the tenant workflow is configured.

Grounded by evidence

Useful intelligence stays honest about confidence and context

FIRCY Sense is careful about the difference between observed evidence, enrichment context, and validated findings. That distinction matters when intelligence is used for investigation or defensive action.

Customer-specific first

The strongest signal comes from activity around your environment, then enrichment adds context rather than replacing the evidence.

Context is labelled

Infrastructure context, reputation, and malicious indicator matches are handled differently so analysts can reason about them properly.

Configured per tenant

Enrichment, export, publication, and downstream routing depend on the deployment model and tenant configuration.

AI is assistive

Generated summaries and follow-up answers can help analysts move faster, while evidence and deterministic workflows remain central.

Make intelligence operational

Map threat intelligence from deception signals to your workflows

We can work through the signals you care about, how FIRCY Sense should enrich them, and where validated intelligence should land for your analysts, response teams, and approved AI tools.