Threat detection
Bring perimeter triggers, camera events and access logs together for a defensive threat review.
Example tags
What you can learn
- Fence trigger, then nearby camera movement
- Movement after hours with no matching access log
- Same plate seen 3 times, no gate entry
- Repeated boundary triggers within 10 minutes
- Denied badge scan followed by a door trigger
- Camera movement at 2 perimeter points in sequence
Built from recorded events, using the rules we agree with you.
Say what you want to learn. See how it is defined.
DataGlue shows the formula: which events count, in what order, and over what time. Our team builds and checks it with you.
This is an example rule. Your event names, time limits and links are agreed in the build.
Example formulaEvents → tag
Flag a perimeter pattern for operator review.
- Perimeter sensor: boundary triggered
- Camera: nearby movement recorded
- Access control: no permitted entry in that window
Within 5 minutes at the same site boundary; an operator reviews the alert.
Tag created
Perimeter pattern needs review
Start with a question that matters.
Review perimeter alerts with context
Join a sensor trigger, nearby camera movement and access logs before an operator reviews it.
Find repeated unusual movement
Group camera events and sensor triggers at the same boundary outside permitted hours.
Check sightings against gate entries
Join recorded vehicle sightings and gate logs to find sightings with no matching entry.
Each system adds a piece of the story.
Camera events
Recorded movement by location and time.
Perimeter sensors
Fence, door and boundary triggers.
Access control
Permitted entries, denied entries and badge scans.
Number-plate readers
Vehicle sightings near site gates.
We agree how each source connects through your warehouse, API or the connections in your build. Person records need a shared id to join. Vehicle, shipment, machine and site tags stay on those records.
Send the tag where your team works.
Choose the destination. We build the route so the result can reach the tools your team already uses.
- Security alerts
- Incident tools
- BI dashboards
These are example destinations. The formula stays the same wherever the tag is sent.
Describe the outcome. We’ll join the data.
Bring one perimeter review question. We’ll join the defensive site records.
A dedicated team builds the connections, rules and destinations with you.