Enroll in the Tripwyre Beta
Background
Ransomware and insider threats remain two of the most urgent cybersecurity challenges facing organisations today. The Deadbolt project, founded by Daniel Jones, Dennis Groves, and Ric Richardson is committed to fighting this threat with its flagship technology: TripWyre.
TripWyre is a next-generation surveillance system that monitors access to unstructured data on file shares such as Google Drive, iCloud and Dropbox by flagging potential data exfiltration threats before they become breaches. Rather than reading file contents, TripWyre leverages metadata surveillance to detect suspicious behaviors, such as large downloads, automation activity and nefarious AI, suspicious activity outside business hours, or activity from unexpected IP addresses.
Because TripWyre works via network mirrors or taps, it stays invisible to attackers while maintaining full privacy compliance. When a Tripwyre is triggered, administrators are notified through a secure out-of-band (OOB) smartphone app, allowing immediate actions like quarantining shares or shutting down account access.
Why a VPN-Based Version?
To make testing and deployment simpler, we’ve created a version of TripWyre that uses a secure VPN connection as the surveillance point. Instead of altering internal infrastructure, users connect via our VPN. The surveillance server then monitors traffic flowing through that tunnel. This approach accelerates deployment and is ideal for pilots or short-term trials.
The Beta Program
We’re inviting selected organisations to join a limited Beta Test Program. Participation includes:
VPN access to our TripWyre-monitored network
Use of real-world file services (e.g., Google Drive, Dropbox) to simulate typical user activity
Access to the TripWyre interface, showing real-time alerts and behaviour grading:
Green: Normal
Amber: Suspicious
Red: Breach
Optional access to the OOB smartphone app for alert response and emergency actions
This exclusive trial is focused on gathering feedback and validating core use cases in real environments. Your insights will help shape our roadmap and threat detection models.
How to Test Tripwyre:
To help improve our system, we’re especially interested in testing the following 10 types of file access behaviors that may trigger TripWyre alerts:
Mass downloads – A user downloads a large number of files in a short time.
Access from overseas – Someone accesses files from an unexpected geographic location.
After-hours activity – Files are retrieved late at night or during weekends.
Automated tool behaviour – Files are accessed at consistent, machine-like intervals.
High-frequency access – A user repeatedly opens the same sensitive document.
Unusual user/IP combo – A user logs in from a device or IP address they’ve never used before.
New employee spike – A new or junior user suddenly accesses high-value data.
Shadow access – Data is accessed by a role or user that normally shouldn’t.
Department cross-over – HR files being accessed by someone in Finance or IT.
Sudden download bursts – Large file transfers occur just before a person leaves the company.
These examples will help us refine TripWyre’s ability to detect threats accurately and reduce false positives.
Our Ask of You:
Willingness to participate for 1–2 weeks
Use of a small test team accessing shared files via VPN
No installation needed—just existing file services and VPN access
Agreement to provide feedback at the end of the test
Legal Notice
By participating in the beta, you agree to grant Deadbolt Cyber full rights to any data, metadata, or usage analytics collected during the trial. Deadbolt Cyber may use this data for system training, testing, and commercial improvement.
Participants acknowledge and accept that the beta is experimental and provided "as is," with no warranties or guarantees of performance. Deadbolt Cyber is not liable for any loss, disruption, or damages arising from use of the beta system.
Everyone who takes part in the beta will be asked to agree to a simple set of rules. These make sure everyone understands that Deadbolt Cyber has permission to use the data collected, and that Deadbolt Cyber is not responsible for any problems or losses that might happen during the test.