EventHappy HourAfter Security LIVE!
Elastio Happy Hour in London(October 8, after Security LIVE! Europe)
Catch ransomware before encryption begins. Talk about it over a drink first.
- Thursday, October 8, 2026 | 5:30 – 7:30 PM BST
- London — venue shared when you register
- Hosted by Elastio
Register
Save Your Spot
We'll confirm by email and send you the venue.
Overview
Elastio is hosting a happy hour in London on the evening of AWS Security LIVE! Europe. The sessions wrap at 5:15 PM; we start at 5:30. Come by on your way out.
A day of threat detection and security operations content tends to leave one question unanswered: when the detection comes too late, is the data you fall back on still clean, and how would you prove it to a board, an auditor, or a regulator?
What the evening looks like
- Drinks and conversation from 5:30 PM, picking up right where the Security LIVE! sessions leave off.
- A relaxed end to the day with people who own the same problem — no slides, no pitch, no booth.
- Register and we will email you the venue along with your confirmation.
What Elastio adds
- Hunts for ransomware, malware, and data corruption across your live data, replicated data, and backup data at the file level.
- No agents on your instances. No separate infrastructure to operate.
- When a threat is found, you get the specific files affected, the timeline of infection, the last provable recovery point, and a verified restore confirmation.
Who should join us
- CISOs and security practitioners attending Security LIVE! Europe who want recovery confidence, not just backup coverage.
- Security and cloud teams in London responsible for detection, response, and what happens after an incident.
- Resilience and risk owners under DORA and UK operational resilience expectations who have to evidence recovery rather than assert it.
- Anyone who has watched ransomware resurface during a restore and would rather not repeat the experience.
Not waiting until October to get an answer?
An Elastio assessment shows you what your current backup environment would actually deliver in an incident — which copies are clean, and which ones you only assume are.