Deployment pathway 4. Hybrid/ Separated

Hybrid log management with separated data zones

Pathway 4 extends Snare into cloud while keeping a fully isolated on-premises zone, with each zone holding its own policy and routing. It suits regulated or sensitive environments that are adopting cloud but must preserve strict separation.

Isolated on-premises zone | Separate policy and routing per zone | AskSnare optional in each zone | Cloud zone hosted in the region you choose |

At a Glance

Cloud adoption without mixing zones

Pathway summary
Products
Snare Agent, Snare Central, Snare Reflector, with AskSnare available per zone
Where data lives
Cloud sources and an isolated on-premises zone, kept distinct
AI-assisted investigation
Available, and enabled zone by zone
Best for
Policy-driven separation, sensitive or sovereign zones, staged cloud adoption
Change from today
Moderate

How it Works

Two zones, each with its own policy and routing

Each zone runs as its own collection, retention and routing domain.

COLLECT FROM EVERY ENVIRONMENT

Snare Agent collects from endpoints and servers. Snare Central also takes in cloud sources, including cloud workloads, SaaS applications and security tools.

Reply-all Reply-all UNIFY IN SNARE CENTRAL

All sources are managed, searched and retained in one place, under one set of policies, with retention from 90 days to 7+ years.

ROUTE CONSISTENTLY

Snare Reflector applies the same filtering, aggregation, deduplication and field remapping to every source before routing to your SIEM and other destinations.

Search Search INVESTIGATE

Where AskSnare is enabled, analysts ask questions across the unified record in plain English.

Isolated on-premises zone
Cloud zone
Sources
Endpoints, servers and on-premises systems, collected by Snare Agent
Cloud workloads, SaaS applications and security tools
Snare Central
Local only
Cloud collection, hosted by Snare
Hosting
Your own environment
AWS or Oracle Cloud, in the region you choose
Snare Reflector
Its own routing and destinations
Its own routing and destinations
Policy
Its own collection and retention policy
Its own collection and retention policy
AskSnare
Optional. Add it as in Pathway 2, or leave it out
Optional

The on-premises zone operates as a fully on-premises deployment. Its logs remain completely on-premises and are not mixed with the cloud collection environment.

Is this your pathway?

When this pathway fits

Check Check

You are adopting cloud services but must keep a classified, regulated or operational network isolated.

Check Check

Different parts of your environment fall under different regulatory or contractual obligations.

Check Check

You want AI-assisted investigation in some zones and not in others.

Check Check

You need collection governed zone by zone, on one platform.

This pattern is common in government and defence, energy and utilities, and financial services. Frameworks such as NERC CIP, the Essential Eight and ISO/IEC 27001 all place logging obligations on environments that must also remain segregated.

Preserving isolation

Separation is the core reason for this pathway

Consistent routing means you decide what each destination receives. Snare Reflector can filter and deduplicate events before they reach a SIEM that charges by ingest volume, while Snare Central retains the complete record.

AskSnare in both zones

AskSnare can be deployed in both zones, so each can have AI-assisted investigation.

Your choice on the protected side

Add AskSnare to the protected on-premises zone, as in Pathway 2, or leave it out to keep that zone completely separate.

Fed by Snare Reflector

In each zone, AskSnare receives its log data from that zone’s Snare Reflector, queries data where it lives and does not replicate it.

A unified record also simplifies audit evidence, because one retention policy and one reporting set cover every source. Snare supports evidence for the standards below.

Complements what you run

Works alongside your existing stack

Each zone routes to the destinations it is permitted to use. Snare Reflector supports the destinations shown here, so a zone can feed the SIEM approved for it.

Where this pathway leads

A pathway that suits your requirements

Fully on-premises is a complete deployment in its own right. There is no requirement to move to the cloud or introduce AI, and on-premises deployments remain fully supported and continue to evolve. If your requirements change, the same architecture extends.

Pathway 1

Fully On-premises

The baseline architecture this pathway builds on.

Pathway 2

On Premises + AskSnare

Add AI- assisted investigation without changing where your data lives.

Pathway 3

Unified collection

Bring every source together in Snare Central where separation is not required.

FREQUENTLY ASKED QUESTIONS

Questions from security architects and engineers

What is a hybrid, separated log deployment?

It is a deployment that collects cloud sources while keeping a fully isolated on-premises zone. Each zone has its own policy and routing.

Does adopting cloud change my isolated on-premises zone?

No. The isolated zone continues to collect, retain and route its logs on-premises under its own policy.

Can AskSnare be enabled in one zone and not another?

Yes. AskSnare can be deployed in both zones, or left out of the protected on-premises zone to keep it completely separate.

Does AskSnare move data between zones?

AskSnare queries data where it lives and does not replicate it.

How is this different from Unified Collection?

Unified Collection brings all sources together in Snare Central. Hybrid / Separated keeps on-premises and cloud as distinct zones.

Snare Solutions
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.