Skip to content
TERO · Cybersecurity monitoring & detection

Detect attacks.
Investigate the evidence.

Spot suspicious access before it becomes a bigger problem. Tero helps your team detect attackers interacting with realistic Decoys and investigate what they accessed, what they attempted and what actually happened.

Built for your environment

  • Linux
  • Windows Server
  • Amazon Web Services
  • Microsoft Azure
  • Google Cloud
See Tero in actionExplore the softwareDeploy Tero Sensors across your office, on-premises servers and supported cloud environments. Monitor suspicious interactions and investigate the evidence from one platform.
TERO / SensorsIllustrative product view

Sensors

Your deployments. A connected view.

aws-finance-sensor-01Finance & operations · EC2
Connected
azure-office-sensor-01Corporate office · Azure VM
Connected
gcp-engineering-sensor-01Product engineering · Compute Engine
Connected
Install in your network. Manage centrally from Tero.
Recorded alertReview required
REPORTING DATABASE · MYSQL

Schema exploration detected

Finance & operations

Source address10.60.20.14
Recorded outcomes3 succeeded · 1 denied
Inspect the evidence

Illustrative recorded activity.

Familiar technologies. A focused layer of detection.

Explore decoy services and deployment foundations your team recognises.

MongoDB
PostgreSQL
MySQL
Redis
Git
Kubernetes
Linux
Windows
Docker

Support varies by capability and Sensor platform. Third-party marks identify technologies, not endorsements.

The Tero platform

See how Tero detects
suspicious activity.

Deploy realistic Decoys in your network. Monitor the activity they reveal. Investigate the evidence behind an alert.

01 Cover the places an intruder would explore

Monitoring built around
your business.

Deploy Sensors and Decoys in the offices, cloud networks and business areas you want to monitor. When suspicious access is recorded, Tero links the activity to the system and Environment involved.

Focus your deploymentPut Decoys in the networks and workflows you need to monitor.
Keep the context readySee the business Environment and resource behind an interaction.
TERO / Garnet Technology / EnvironmentsIllustrative product view

Environments

Business context for every deployment and investigation.

3 environments
Deployment hierarchy
EnvironmentFinance & operationsGarnet Technology
Sensorfinance-sensor-01Connected · Private network
MySQLReporting database
PostgreSQLOperations database
RedisApplication cache
3Environments
4Connected Sensors
12Deployed Decoys
EnvironmentSensorsMonitoring
Finance & operationsAccounting · Business systems
1 connected4 / 4 verified
Product engineeringDevelopment · Cloud workloads
2 connected5 / 5 verified
Corporate officeInternal resources · Shared files
1 connected2 / 3 verified
Environment · Sensor · Decoy — the context stays linked.
Sensor detailsConnected
FINANCE & OPERATIONS

finance-sensor-01

Private network · Ubuntu

Decoys deployed4
Monitoring verified4 / 4
✓ Latest heartbeat received

Recreated product views · Illustrative customer data

02 Make suspicious access visible

Reveal suspicious access
set intruder traps.

Give suspicious activity a place to surface. Tero Decoys look like familiar databases, internal APIs and source repositories, with synthetic business data and recorded interactions.

Use familiar servicesChoose database, development and business-system Decoys.
Turn interaction into evidenceRecord requests and outcomes instead of relying on a connection alone.
TERO / Decoys / Add a decoyIllustrative product view

Add a decoy

Believable resources. A focused layer of detection.

Sensor connected
Environment Finance & operationsSensor finance-sensor-01

MySQL / MariaDB selected · Illustrative product interaction.

MySQL / MariaDB

Synthetic business records. Real service interactions you can investigate.

  • Recorded service interactions
  • Linked evidence
  • Deployment health

Selected Sensor
finance-sensor-01

03 Keep your detection layer working

Monitor your deployments.
Spot suspicious activity.

See recorded events and open alerts alongside deployment health. Check which Decoys are monitored and which need attention, then follow the activity that deserves investigation.

Find the gapsSpot a disconnected Sensor or a monitoring check that needs review.
Focus on the activityMove from a Decoy to its recorded interactions and related investigation.
TERO / Garnet Technology / DecoysIllustrative product view

Decoys

See what’s running. Know what needs your attention.

12 deployments
Recorded activity Last 24 hours
18Recorded events
2Open alerts
Environment monitoring Current checks
12Deployed
11Verified
1Needs attention
Finance & operations
4 / 4
Product engineering
5 / 5
Corporate office
2 / 3
Decoy inventory 12 deployments across 3 environments
Decoy / typeEnvironment / SensorMonitoring / runtimeDetails
Reporting databaseMySQL / MariaDB
Finance & operationsfinance-sensor-01
ReadyRuntime: Online
Operations databasePostgreSQL
Finance & operationsfinance-sensor-01
ReadyCurrent checks
Payments APIKubernetes API
Product engineeringengineering-sensor-01
ReadyRuntime: Online
Internal repositoryGit repository
Corporate officeoffice-sensor-01
Needs attentionCollection check required
Recorded alertReview required
REPORTING DATABASE · MYSQL

Database schema explored

Finance & operations

Source address10.60.20.14
Linked investigationSchema exploration
Inspect the recorded sequence
Illustrative product details

Reporting database

MySQL / MariaDB · Finance & operations. Runtime online and monitoring verified in this example. Recorded schema discovery and a denied write are linked to the investigation shown below.

04 Investigate with evidence

Investigate attack activity.
Review the evidence.

See the source, the resource, the requested action and the recorded outcome. Follow the sequence from discovery to data access or a denied write, and assess what the evidence supports.

Understand the sequenceReview each recorded operation and its observed outcome.
Make a better-informed responseDistinguish successful access from a blocked attempt before drawing conclusions.
TERO / Investigations / Reporting databaseIllustrative product view
RECORDED CASE Review required

Reporting database — schema exploration

Recorded interactions on one MySQL Decoy. Actor identity and production impact remain unconfirmed.

ENVIRONMENTFinance & operations
SENSORfinance-sensor-01
DECOYReporting database
4 recorded operations8 observationsCase open
Recorded sequence Observed time
Decoy account authenticationSucceeded
garnet_reader · session establishedRequest and response evidence linked
Database schema discoverySucceeded
SHOW TABLES · garnet_operationsNative database response recorded
Synthetic customer records requestedSucceeded
SELECT * FROM customers LIMIT 5Read result recorded · synthetic data only
Database write attemptedDenied
UPDATE invoices SET total_cents = total_cents WHERE 1 = 0Permission denied · attempt retained as evidence
See your next layer of detection

Make cybersecurity surveillance.
part of your everyday defence.

See how TERO connects your environments, decoys and investigation workflow.

Request a product demo Explore pricing