The CyberSnap Platform

Threat detection in your recovery points. Response guidance before and after the damage.

Two business modules and one research layer, built on the snapshots you already keep. Ransom Recovery drives the restore decision. Damage Prevention extends the investigation to earlier discovery of slow-moving attacks. CyberSnap AI Research keeps both of them current.

Available Core product capability In development Extension not yet released to customers Planned Future direction

One research system. Two business modules.

Component
Business role
Main output
Ransom Recovery
Ransomware detection, investigation and recovery guidance
A recovery point candidate per server or folder, based on scan findings
Damage Prevention
Earlier discovery of quiet and slow-moving attacks
Linked findings, investigation and damage-reduction recommendations
CyberSnap AI Research
Continuous research and improvement for both modules
Detection content, models and tuning that pass quality control
Module 1 · Foundation

Ransom Recovery: find the source, return to the right point.

Ransom Recovery scans the files inside your recovery points for evidence of ransomware, malware and suspicious change. It combines forensic findings with AI recommendations to show where the attack came from, how it unfolded over time, and which recovery point suits each server or folder.

The value is less uncertainty at the moment of recovery, and a return to operations based on evidence. A point with no findings is a restore candidate within the checks that were run. It is not a promise that no threat exists.

app.cybersnap.io · SnapMap · servers
SnapMap server rows: threat findings in red and snapshots with no findings in green, per server over time

SnapMap, demonstration scenario. Newest snapshot on the left.

What each scan level checks, and what it does not claim.

Each level answers a different question. Actual coverage depends on version, platform and the type of data available for inspection.

Level 1

Triage Scan

A first picture, fast, and a focus for the rest of the investigation. In incident response, triage is the sorting stage: where are the meaningful signs, which recovery points need attention, where to run a deeper check. While the business is down, the team can start working with findings before the full investigation is done.

Mass file changes

Ransomware can rewrite large numbers of files, add extensions or delete originals after creating encrypted copies. Thousands of documents changed in the same window are a possible sign of the Impact stage.

Extensions and ransom notes

Extensions linked to ransomware families and files that may be ransom notes. A normal instructions file is not necessarily a ransom note, and no note does not rule out an attack. Meaning grows when several signs appear together.

Entropy

Encrypted content looks highly random. But ZIP files, images and other compressed formats can look similar, so file type and other evidence are taken into account. High entropy alone is not proof.

Masquerading

A file named like harmless data, such as update.dat, whose internal structure matches a Windows or Linux executable. Renaming a file does not change what it is.

Output: an evidence-based first sort that shows the team where to focus and what needs further investigation. A planned mass data migration can also change many files, which is why context matters.

Level 2

Threat Hunt Scan

Goes inside file contents with the YARA-X engine and detection rules from CyberSnap or the customer. A rule can combine text strings, byte sequences and logical conditions that characterize the content being hunted.

Detection rules

Rules rely on content, not names, so they keep matching after a file is renamed, and one rule can catch a pattern shared by several malware samples.

Indicators of compromise

Known malicious files or suspicious content characteristics that may show a system was compromised, including signs from before the visible encryption.

Fingerprint versus rule

A SHA-256 hash identifies identical content precisely, and changes when the content changes. A rule can still match if the patterns remain. They are complementary tools.

Accumulated know-how

Rules and correlations built from field experience help separate a suspicious file, evidence of malicious activity and signs of actual damage.

Output: a finding the team can investigate: which file, which rule and which recovery point. The scan is deterministic, so the same content with the same rules, settings and engine version returns the same result.

Level 3

Forensic Scan

Adds operating-system context. The key concept is persistence: mechanisms that let an attacker keep access or re-run malicious code after a login, a restart or another system event.

Persistence

Windows services, scheduled tasks, auto-start and registry run entries. On Linux, cron jobs and systemd services. Legitimate mechanisms that attackers abuse.

Forensic artifacts

Event logs, service settings, scheduled tasks and other traces that show what was configured or happened. A task set to run a file is not proof that it ran; each finding has its own level of proof.

Timeline of findings

In which points the signs were found, when they first appear in the inspected history and what changed after. It helps estimate how long suspicious activity was present.

Honest limits

A system-disk snapshot can hold operating-system evidence; a file share holds file content without full server context. A historical disk does not bring back the memory of that moment.

Example: Threat Hunt finds a suspicious file. Forensic adds a scheduled task pointing to it. Earlier points show both existed two days before the encryption. Restoring to the point just before the encryption would have brought back the file and the mechanism that runs it.

Every scan adds evidence. Your team decides.

TriageFinds an executable disguised as a data file
Threat HuntFinds a pattern inside it that matches a detection rule
ForensicFinds a mechanism set to launch it
HistoryShows the findings came before the encryption
DecisionA suitable recovery point per server, based on evidence

SnapMap also shows what was scanned, what was excluded and whether the scan completed. A point with no findings in a partial scan is not the same as a point that passed a full scan. The first indicator in the inspected history is not necessarily when the intrusion began.

▸ MODULE 2 · DAMAGE PREVENTION

Discover quiet attacks before the damage.

Not every attack starts with encryption. Damage Prevention analyzes accumulated scan data over time for each server and across the whole infrastructure, using AI agents and correlation between findings. It is aimed at quiet attacks, espionage, persistence and targeted disruption, including patterns that can appear in AI-assisted attacks. The business value: moving investigation and response to the stage where damage can still be reduced.

Deep forensic evidence Available

Operating-system evidence from Windows and Linux. Live investigation of a server copy in an isolated environment is In development.

Slow-moving attacks In development

Checks whether findings that look separate across servers and points in time belong to one attack that develops slowly.

AI analysis agents In development

Agents examine sequences, anomalies and links between evidence, and attach an explanation and a confidence level to each finding. The AI recommends; the deterministic detection engine decides.

AI Damage Prevention is aimed at earlier investigation and damage reduction. It does not claim to guarantee prevention of every attack.

Two engines

AI connects the evidence. You regain control.

The cyber engine is deterministic. It inspects the data, applies detection rules and indicators, correlates findings by defined logic and produces an assessment of malware and ransomware. Same input, same engine version and rules, same result, so every finding can be explained and re-run.

The AI engine adds context. It receives findings and metadata, not raw files, along with the server role, operating system and infrastructure. It assesses false positives, recommends severity and suggests where to investigate next.

Your team decides. An AI recommendation to lower severity never deletes a finding and never marks a recovery point as free of threats.

Hypothesis-driven investigation, where the AI proposes follow-up checks that the cyber engine validates and runs, is proven in controlled development and is being extended to production in stages.

app.cybersnap.io · Reports
CyberSnap scan report with recovery score, AI threat analysis and AI second opinion

Context and hypotheses, grounded in the findings.

What it receives
  • Findings and metadata: detection method, file names and paths, severity, number of occurrences, locations and scan history.
  • Customer and asset context: server role, operating system, services and infrastructure.
  • No raw files. File content is inspected by the cyber engine.
What it does
  • Checks whether a finding matches known legitimate activity.
  • Looks for evidence that strengthens or weakens the suspicion.
  • Links findings across points in time into a picture of how the incident developed: persistence, activity before the encryption, related findings.
What it produces
  • A reasoned interpretation of the findings.
  • A false-positive assessment and a severity recommendation.
  • Directions for further investigation, and what is still missing to reach a firm conclusion.
Hypothesis-driven investigation In development

The AI turns its analysis into a defined investigation proposal. The cyber engine stays in charge of what actually runs.

01The AI proposes

Identifies missing information and drafts a follow-up check.

02The cyber engine validates

Against allowed actions, available capabilities, scope and the approved run budget.

03The cyber engine runs it

Only what passed the check. New findings come back as evidence.

04The hypothesis updates

Strengthened, weakened or narrowed, based on the new evidence.

Proven in controlled development and being extended to production in stages. The asynchronous path lets AI analysis run alongside the scan without making the cyber engine wait for each recommendation.

For the business

A restore decision that respects RTO and RPO.

The choice of recovery point affects two familiar targets: the recovery time objective and the recovery point objective. A point that is too old gives up data that could have been kept. A point that is too recent can bring the attack back.

CyberSnap gives the team the evidence to choose a point and plan the return to work around the findings, the dependencies between systems and the needs of the business.

Too earlyLost work

Days of data given up that the evidence did not require.

Suitable pointEvidence-based

As close to the present as the findings allow, per server.

Too lateA second incident

Malware and persistence return to production with the data.

Built to run every day, not only on the worst day.

Scans run on a schedule, so when a crisis hits the history and the findings are already there.

Policies and scheduling

Set once, run consistently

Define scan targets, scope and timing in managed policies: hourly, daily, weekly or monthly, manual or in sync with new snapshots. Less dependence on manual runs.

Quick and full modes

Coverage you can read

Choose a quick path or a full one, depending on need and supported capabilities. The coverage of each run is part of how its result is read.

Findings and exclusions

Prioritized by severity

Findings are grouped by severity to set priorities. Exclusions handle known items, with visibility into how each exclusion affects results.

Reports and alerts

For every team involved

Scan results, findings, recovery score and AI threat analysis for the people who investigate and the people who decide.

Console and API

One place to manage

Policies, assets and results in one console. The API brings supported actions and data into your own workflows.

Deployment

Agentless by design

Two virtual machines beside your storage and virtualization layer. A trial on one system is the usual way to start.

Every capability, by module and status.

A check mark shows which module a capability belongs to. Status shows its maturity. Actual availability depends on version, platform, scan coverage and how the capability is enabled in your environment.

Capability
Ransom Recovery
Damage Prevention
Status
Detection
Ransomware evidence scanning
✓
✓
Available
Malware detection with YARA-X rules
✓
✓
Available
Abnormal encryption and file changes
✓
✓
Available
Forensic investigation
✓
✓
Available Extensions in development
AI analysis and recommendations
✓
✓
Available Extensions in development
Agentless snapshot scanning
✓
✓
Available
Historical snapshot scanning
✓
✓
Available
First indicators and timeline
✓
✓
Available Extensions in development
Early discovery
Slow-moving attack detection
–
✓
In development
Correlation across servers and time
–
✓
In development
AI agents for attack-pattern detection
–
✓
In development
AI Damage Prevention
–
✓
In development
Recovery
Last recovery point with no findings, per server
✓
–
Available
Autonomous recovery point verification (full scan)
✓
–
In development
Cyber Sandbox
✓
✓
Available Extensions in development
Recovery and damage-reduction recommendations
✓
✓
Available Extensions in development
SnapMap
✓
✓
Available Extensions in development
Operations
Policies and automatic scheduling
✓
✓
Available
Quick and full scan modes
✓
✓
Available
Findings by severity, and exclusions
✓
✓
Available
Reports and alerts
✓
✓
Available Extensions in development
Central management console and API
✓
✓
Available
Cyber Sandbox · where supported

Validate before production.

Start copies of selected servers from a chosen snapshot in an isolated environment, for checks and investigation before they return to production. A single VM, a single snapshot or several VMs together, with revert and cleanup when the check is done.

An extension in development combines evidence from the live run with the scan and history findings, only after isolation is verified.

app.cybersnap.io · Sandbox
CyberSnap Cyber Sandbox restore history

Detection that keeps learning.

CyberSnap AI Research serves both modules. It is not a third module. It combines threat research, learning of the customer environment and quality control, so detection improves continuously without waiting for a new product release.

Threat research

What is changing outside

New threats and attacks, intelligence sources and trends, attack methods that use AI, and new AI tools and detection models worth adopting.

Customer learning

What matters inside

The customer's business and key assets, infrastructure and dependencies, specific risks, and patterns seen in the customer's own scan findings, linked to global intelligence.

Detection content

What gets better

New YARA-X rules, deterministic engine updates, a dynamic statistical model, tuning of the decision engine, and better AI models and agents.

Quality control

What gets released

Every update is validated before release, rolled out in stages and can be rolled back. Updates that need customer approval can be reviewed, approved or deferred.

Status: the research management, content distribution and change-control foundation is in place. Its connection to the customer environment is in development. The areas above describe the intended scope of the system.

Works with the infrastructure you already run.

In a typical deployment, one virtual machine connects to the storage through its API and a second connects to the virtualization management layer. Nothing is installed on the production servers being inspected.

File shares and objects do not always provide the evidence of a full system disk. Sandbox restore and run depend on the target type and the supported integration.

See it on your own snapshots.

We install on one system that matters to your business, scan the snapshots you already keep and review the findings with your team.