Lucy Sweet @int_underflow

🏳️‍⚧️ 26, occasional plane flyer, running infrastructure @uber Views my own Denmark Joined May 2015

Tweets

268
Followers

291
Following

230
Likes

422

Lucy Sweet @int_underflow

3 years ago

Lunch with @JoshGrant9 at #kubecon 😋

0 0 1 0 0

Download Image

Lucy Sweet @int_underflow

3 years ago

Amazing dinner and great company with @bwiczling @JoshGrant9 @RobKielty @bobymcbobs @willsewell_ @abalutoiu #kubecon #Valencia

4 2 9 0 1

Download Image

Bo English-Wiczling @bwiczling

3 years ago

AMAZING team dinner before #KubeConEU at Irish pub @clannbar serving Spanish food run by Argentinians. It makes sense. @d_gerrity @int_underflow @snafuz @skzern @OracleDevs @groundbreakers

1 2 12 0 0

Download Image

Bo English-Wiczling @bwiczling

3 years ago

Chocolate overload @masusapaellabar! @kamcmahon @ThatEliGuyatOCI @int_underflow @RobKielty

0 1 2 0 0

Download Image

Bill Demirkapi @BillDemirkapi

4 years ago

New documents for the Okta breach: I have obtained copies of the Mandiant report detailing the embarrassing Sitel/SYKES breach timeline and the methodology of the LAPSUS$ group. 1/N

New documents for the Okta breach: I have obtained copies of the Mandiant report detailing the embarrassing Sitel/SYKES breach timeline and the methodology of the LAPSUS$ group. 1/N https://t.co/e0T4EdWPxT

61 943 2K 0 368

Download Image

66 893 3K 0 700

Download Image

Lucy Sweet @int_underflow

4 years ago

Nice to see the UK Government has found a new project to waste money on: A propaganda campaign to undermine internet security #NoPlaceToHide

0 0 0 0 0

Lucy Sweet @int_underflow

4 years ago

I've published a blog post about how we keep Monzo's most sensitive secrets nice and secure :) monzo.com/blog/2021/11/1…

1 6 32 0 5

Lucy Sweet @int_underflow

5 years ago

I really need a holiday if Covid eventually passes...

0 0 2 0 0

Today In Infosec @todayininfosec

6 years ago

1989: Brian Fox introduced code into Bash, later released as version 1.03, which included the first of the Shellshock vulnerabilities publicly reported 9,169 days later. That's 25 years, 1 month, and 13 days of exploitability. Takeaway? You're always running exploitable code.