Infrastructure Deception · Preview

Put decoys where attackers look. Know when they’re touched.

Attackers look for backup servers, hypervisors, domain services and management systems. DecoyStack creates purpose-built infrastructure decoys that give your security team a useful signal when someone interacts with them.

23 implemented profilesInternally lab-qualifiedStructured event export
Example decoy eventSynthetic data

Unexpected decoy interaction

Review

A designated virtualization decoy received an interaction from an internal source.

Represented systemVMware vCenter
SourceIdentified internal host
Observed serviceHTTPS management surface
Event stateReady for investigation
Illustrative example. A decoy contact gives the SOC a reason to investigate; the analyst determines intent.
23/23 passed defined internal lab checks5 infrastructure families representedJSONL · Syslog · CEF event formats
Why It Matters

Unexpected infrastructure activity can hide in routine network traffic.

During an intrusion, attackers may look for virtualization platforms, backup systems, directory services and management interfaces. That activity can be difficult to distinguish from routine network traffic.

Make unexpected access stand out

A connection to a designated decoy gives your SOC a clear reason to investigate.

Watch the infrastructure that matters

Represent backup, virtualization, identity, server management and network-security technologies.

Give analysts useful context

See which decoy was contacted, where the interaction came from and which service was involved.

A probe contacting an isolated decoy before critical infrastructure
The DecoyStack Advantage

A clearer starting point for your next investigation.

Traditional monitoring provides essential visibility, but understanding why an interaction matters can require correlating several sources.

Traditional monitoring

A connection was observed

Is it routine activity, authorized scanning or something that deserves investigation?

  • Context may be distributed across several tools.
  • The system’s role still has to be established.
  • The analyst decides whether the activity matters.
DecoyStack

A designated decoy was contacted

The event identifies the decoy, the source and the observed service.

Virtualization decoy contactedSynthetic example
DecoyvCenter profile
SourceInternal host identified
ServiceHTTPS management
StatusReview recommended
Less guesswork about what was contacted. More context to decide what happens next.
Built on Real Engineering

23 infrastructure decoys backed by defined internal lab checks.

DecoyStack represents technologies commonly found in enterprise infrastructure through version-specific profiles.

Virtualization

VMware ESXi, VMware vCenter and Proxmox VE

Backup & Recovery

Veeam Backup & Replication

Identity Services

Windows Server Domain Controller

Server Management

Dell iDRAC, HPE iLO and Lenovo XClarity

Network Security

Palo Alto PAN-OS

23/23 passed defined internal lab checks. Internal qualification covers defined project checks. Each profile implements selected protocol surfaces from the represented product.
Simple Concept · Controlled Deployment

Choose your decoys. Observe the activity. Use the signals.

01

Choose what to represent

Select infrastructure profiles that match the technologies you want to monitor.

02

Place your decoys

Run isolated decoy identities with separate network identities and defined exposure.

03

Investigate unexpected contact

Capture structured events and send them into your existing security workflow.

Supports JSONL, Syslog RFC 5424 and CEF event formats. These are standards-based event formats; DecoyStack does not claim certified vendor connectors.

Security by Design

A decoy should create evidence, not unnecessary exposure.

DecoyStack uses network isolation, restricted outbound communication and defined service behavior.

Separate identities

Decoy instances have individual network identities and operating boundaries.

Restricted communication

Outbound connections follow restrictive policies with explicit operational allowances.

Controlled exposure

Services expose selected protocol surfaces rather than unrestricted host access.

Technical details and operating limits
Profiles run with separate network identities and restrictive outbound policies. These controls reduce potential exposure but do not eliminate deployment risk. Safe operation requires appropriate network segmentation, host security and operational review.
Design Partner Conversations

Help shape a better way to detect unexpected infrastructure activity.

We’re looking to speak with SOC teams, security leaders, MSSPs and infrastructure specialists interested in how DecoyStack could fit their security operations.

  • Infrastructure deception use cases
  • Decoy placement and security requirements
  • Event collection and SOC workflows
  • Requirements for a potential future controlled evaluation
Technical Preview: DecoyStack remains a Technical Preview without general availability. Conversations cover potential collaboration; access, pilots and release dates remain uncommitted.

Contact Engineering

Submit your evaluation context. Our engineering team reviews each inquiry directly.

Privacy & Governance: No tracking cookies. Inquiries are stored securely and routed to engineering ([email protected]).