Four ways to collaborate
Pick the one that fits, or mix them.
Technical collaboration
Joint vulnerability research on embedded targets. Security analysis of IoT and OT products, code review, joint write-ups. If you are working on something interesting in hardware security and want a second team on it, we are in.
Academic partnership
End-of-study project and thesis topics in embedded security: firmware analysis, RFID, BLE, protocol reversing. Talks at engineering schools. We can provide real targets, tooling, and mentoring from people who have the CVEs to back it up.
Internship
3 to 6 month research internship in embedded and IoT security. Vulnerability research, firmware reverse engineering, tool development. We work on real targets: no sandbox, no toy projects. You get your name on what you find.
CTF & events
Challenge co-creation, hardware donation, co-organizing IoT and OT CTF events. We run our own platform with 28 challenges and 1,479 players. Open to joint events, guest tracks, and hardware sponsorship.
Support the research
Independent research has real costs. Hardware to audit, infrastructure to run, tools to build.
What we need
- Hardware and IoT/OT targets to audit and research
- Infrastructure: hosting, domains, bandwidth
- Financial support to cover association operating costs
- Visibility: relay of our CVEs, tools and publications
What sponsors get
- Logo and mention on espilon.net
- Attribution in relevant write-ups and publications
- A direct line to an active embedded security research team