George B.

George B.

Holler, Germany · Senior Software Engineer · CYBERR

University of Strasbourg

54 followers

About

Senior Backend Engineer focused on building secure, scalable cloud platforms and distributed systems. Currently working at the intersection of backend engineering, cloud security and compliance at Cyberr...

Specialties

  • SOC Analyst

Experience

  • Senior Backend Engineer

    CYBERR

    Aug 2026 — Present

    Luxembourg

  • Full Stack Developer

    Salonkee

    Oct 2021 — Aug 2026

    Luxembourg, Luxembourg

  • Full Stack Developer

    Kaer Labs

    May 2020 — Oct 2021

    Nantes, Pays de la Loire, France

5 experiences in total

Education

  • University of Strasbourg

    Masters, Computer Science

    Jan 2010 — Jan 2015

Recent posts

5 days in a row on the Cyberr daily challenge.

Today at senior level: detection engineering, threat intelligence and application security.

Can you beat 2/3 on Detection engineering?

https://cyberr.ai/daily/23f4a3ec-c412-4cdd-806a-2952ba2286f0

View post

Git blame is going to be a very uncomfortable conversation with myself

https://thehackernews.com/2026/11/claude-codes-dont-ask-again-file.html

View post

Q2: Your company's e-commerce platform stores customer PII in a third-party cloud service. A peer retailer just disclosed that unauthorized access to its third-party cloud service may have exposed 7.7 million customers' data. As security lead, what should you prioritise first?

===

We should prioritise vendors handling sensitive PII, review access logs for suspicious activity, and rotate credentials where exposure is suspected.

View post

Someone remotely defrosting supermarket fridges overnight. An S3 bucket exposing customer data.

Try today's set.

https://cyberr.ai/daily/a477f0fa-864e-47dd-8871-01bbc259e3f2

View post

The Savannah disclosure is a good case for reviewing where validated data gets reused: an RFC-valid email address became shell syntax in a GPG helper, opening a path to Bash maintainer impersonation. I’d bring this into code review as a question about which interpreter receives a value next—“already validated” tells you very little without that context.

https://www.hacktron.ai/blog/hacking-gnu-savannah

View post

View George B.'s profile on Cyberr