Alex Rebert retweeted
Want to get some answers about what it's like to run @defcon CTF? Our AMA post on the DEF CON subreddit is live!
old.reddit.com/r/Defcon/comme…?
old.reddit.com/r/Defcon/comme…?
0
10
21
Bit of a professional update: after almost 10 years working there, I am stepping down from ForAllSecure. I feel extremely grateful to have met and learned from all the amazing folks that have joined us on this journey (thank y'all ♥️)
1
0
13
There's a lot of work that remains to be done, and if you want to be a part of it, you should consider joining the talented folks there: forallsecure.com/careers
1
0
1
As for me, I'm hoping to take some time to relax and think about what I want to work on next. If you know of a cool project/team/opportunity, you should reach out!
0
0
1
Alex Rebert retweeted
France's infosec ("signals intelligence") agency SSI (~NSA/GCHQ/GCHB/..) has release a guide recommending secure applications be written in Rust ssi.gouv.fr/en/guide/progr…
0
4
13
API fuzzing with Mayhem, now for free with 50 monthly scans 🎉 forallsecure.com/blog/introduci…
0
2
4
Alex Rebert retweeted
I'd like to personally invite you to #FuzzCon 2021! Join me in person in Las Vegas on August 5th or virtually! Register today. fuzzcon.com sprou.tt/1bkDlnpPcLC
0
2
14
David from our team fuzzed @etcdio's web API, the distributed KV store powering Kubernetes. He found a couple of crashes, and fixed them upstream. Read more: forallsecure.com/blog/using-may…
0
1
1
Alex Rebert retweeted
A while ago I was interviewed by @robertvamosi for the Hacker Mind Podcast. I have to give huge props to the production (more about that below 1/3🧵)! You can listen to the conversation about the role of social media in hacking here:
thehackermind.com/ep-22-hacking-…
thehackermind.com/ep-22-hacking-…
1
8
48
I can't recommend this stack enough. We use it, and our code is in production minutes after a push. We have near-zero operational costs.
My talk on #ExposureNotifications at #GoogleIO starts at the top of the hour! Come learn how we engineered backend services to support millions of users with near-zero operations overhead: events.google.com/io/session/5cc…
0
1
4
Alex Rebert retweeted
ForAllSecure Co-Founder & Head of Innovation, @ayper, shares why our API #fuzzer, Mayhem for API, 💓's @getpostman #fuzzing #unleashingmayhem forallsecure.com/blog/testing-p…
0
1
2
What a great panel about software security and fuzzing, discussing some of the most important topics: bringing fuzzing to developers, regression fuzzing, fuzzing bugs as a signal for rewriting in memory-safe language, domain-specific sanitizers, ... youtube.com/watch?v=vJGfY6…
Our DS3 panel on fuzzing with @mboehme_, @kayseesee, and @metr0 has just started but it's not too late to join us live at ds3summit.github.io!
0
3
9
Alex Rebert retweeted
AWS/Amazon has jobs in SMT, model checking, deductive theorem proving, program analysis, program synthesis, etc. We have many locations. If you work in this space and you're interested in taking automated reasoning to a new and historic level, write to me and i'll link you up.
8
64
284
.@yashvi3r describes what modern security tools ought to look like to fit in CI & dev workflows #DevSecOps
Security vendors should pay attention! We certainly are. Those have been our guiding principles as we've been building automated security tooling 🤖
Security vendors should pay attention! We certainly are. Those have been our guiding principles as we've been building automated security tooling 🤖
⚒️ Changing Security Tool Requirements
@twilio's @yashvi3r describes how modern security tools should work in a #DevSecOps world:
* Results consumable by devs
* Fast
* API-first, integrations++
* High signal
* Show results in existing dev workflows
twilio.com/blog/changing-…
0
1
3
SonicWall email security is being exploited in the wild: fireeye.com/blog/threat-re…. How sophisticated did you have to be to pull off this attack? A 🧵
1
3
1
I'd love to see a public post-mortem. Again, mistakes happen. But I'd want to know what protections they had in place to prevent those mistakes, how those protections failed, and what they are doing to fix it. It'd be hard to trust them going forward without that transparency.
1
0
1