Opens profile photo
Follow
Click to Follow infernosec
Abhishek Arya
@infernosec
Principal Engineer and Manager, Google Open Source Security Team (GOSST)
California, USAJoined May 2009

Abhishek Arya’s Tweets

Nice to see more community partners step up and fund critical open source security audits. This is critical for OSS sustainability and security!
Quote Tweet
AWS Teams with OSTIF on Open Source Security Audits AWS will be directly funding $500,000 to @OSTIFofficial as a portion of our ongoing initiative with @theopenssf aws.amazon.com/blogs/opensour
9
There are so many hidden figures in open source. These are the people whose names you wouldn't recognize, but they write the docs, triage bugs, answer questions, and all the other stuff that doesn't show up on the stat sheet. Open source is a team sport.
5
654
3) Continuously track the location of every part - Have SBOMs - Thought: We need accurate, trustworthy SBOMs using SLSA attestations, otherwise we run into a situation like ignition switch example in article where we did have parts and version info, except that it was just wrong.
1
Show this thread
2) Use only the highest quality parts - Thought: Should have better ways to tell which version is both secure & stable. Why do we keep allowing super insecure versions of package version downloads, maybe at some point, breaking compatibility might be the right call.
1
3
Show this thread
Liked the analogies- 1) Source parts from fewer & better suppliers- Thought: scorecards helps evaluate security risk. Might be useful to add checks that tell dependency tree complexity & make better recommendations. Curated, secure OSS is great for critical apps.
1
2
Show this thread
Insightful 3-part series () on evolution of oss supply chain attacks. Great facts (25% of maven pkgs still using vuln log4j, consumer choose vuln ver 95% of time, etc), liked the analogies to auto-industry supply chain controls & evolution phases-
1
18
Show this thread
Nice research using FuzzBench platform-"While the community agrees on AFL’s effectiveness at discovering new vulns..., many of its internal design choices remain untested....careful analysis of the different parameters could help modern fuzzers to improve their perf"
Quote Tweet
The full paper is now published at ACM TOSEM dl.acm.org/doi/10.1145/35 Artifacts at github.com/eurecom-s3/dis This is one of the first papers in the community that passed through a process of preregistration, more info at fuzzbench.com/blog/2021/04/2
10
A truly humble leader & driving force behind Rust adoption in Android & several parts of Google ecosystem. He also supported several efforts around writing critical OSS projects in Rust & recently participated in OMB/NIST/NSF workshop on OSS Security. Well deserved!
Quote Tweet
We are excited to share that experienced open source leader and #rustlang advocate, @larsberg_, has been elected as the new Rust Foundation Board of Directors Chair. Learn more about this news and Lars' background via our blog. foundation.rust-lang.org/news/lars-berg
[Heading]: Announcing Lars Bergstrom  as the New Rust Foundation Board of Directors Chair [Sub-Heading 1 underneath headshot of Lars]: Lars Bergstrom, [Sub-heading 2]: (Rust Foundation Board of Directors Chair,  Founding Board Member Director,  Director of Engineering at Google).
9
My heart goes out to all my Google colleagues impacted by the layoffs. Please don't hesitate to reach out via DM/LinkedIn to help you find your next opportunity or just be a listening ear. It has been a tough 48 hours for all of us, including the ones not directly impacted.
1
44
Last day to submit an entry for SBFT, we have several submissions so far. Other than the $11,337 leetness, you will help to improve OSS-Fuzz community fuzzing service find more bugs for 850 critical projects and growing!
Quote Tweet
Calling all fuzzing engine developers: Join the SBFT competition for a chance at at least 11K. Deadline for expressing interest is Friday sbft23.github.io/tools/fuzzing
2
Really happy to see this come through, yet another commitment from our side to improve critical open source project security. What else should we get audited, share your ideas with and us!
Quote Tweet
The git audit with @X41Sec and @gitlab is complete! There's some juicy fixes in this report, including multiple RCEs. ostif.org/the-audit-of-g
Image
3
Thank you Trail of Bits, and glad we could play a small role in this collaboration! First stable version of sigstore client for the python ecosystem is now available, check it out!
Quote Tweet
We are thrilled to announce the first stable release of sigstore-python, a client implementation of Sigstore that we’ve been developing for nearly a year! blog.trailofbits.com/2023/01/13/sig
Show this thread
12
It's exciting to see announcing support for the use of ! It's been a long journey, and I look forward to watching them evaluate, adopt, & hopefully even contribute to some of the amazing libraries available in the #rustlang ecosystem
11
813
Super excited to see Naveen and Brian raise community awareness on open source security tools in key developer conferences like SCALE, FOSDEM, etc!
Quote Tweet
Our proposal for a talk at SCaLE has been accepted! We'll discuss the importance of trust in OSS and introduce the Scorecards tool developed by the OpenSSF, which allows users to assess the risk of using a specific OSS project. socallinuxexpo.org/scale/20x/pres cc @theopenssf
3
Was great to join and on the podcast for their 150th episode! 🎉 Lots of discussion here about sustainability around and as well as , , open source security and more.
Quote Tweet
Dustin Ingram (@di_codes) talks about the Open Source Security Team at Google, what they do, a rewards program called SOS Rewards (sos.dev), and Google’s role in the Sigstore project (sigstore.dev). Listen at 🎙️ podcast.sustainoss.org/150
24
Bring back memories of Travis CI incident in 2021. Discourage use of secrets in your CI/CD systems and rely on workload based identities / OIDC.
Quote Tweet
CircleCI Security Alert [4 Jan. 2023] We strongly recommend all CircleCI customers rotate secrets stored on our system. Read more: circleci.com/blog/january-4
Image
1
7
We welcome your participation in evaluating next-gen fuzzing research at scale against industry's leading fuzzing engines (afl++, libfuzzer, etc). Help spread the word and showcase your work to the fuzzing community at large!
Quote Tweet
The OSS-Fuzz and FuzzBench team is helping to run the SBFT'23 fuzzing competition this year! sbft23.github.io/tools/fuzzing Please submit an entry if you're interested in participating! Entries for expressing interest close on Jan 13.
Show this thread
14
+1. We are glad to play a small role in this, in collaboration with our partners at !
Quote Tweet
There should be more of this: sethmlarson.dev/urllib3-in-2022 I hear a lot of high profile folks lamenting about not enough help being given to OSS projects. I then check out their github profile and they are not sponsoring anyone. Walk the walk people, not just talk the talk.
9
The PyTorch team is taking all the right measures here, but this is another reminder of the importance of the work on sigstore and other tools that and the rest of the PyPI security team are leading work on.
Quote Tweet
If you installed PyTorch-nightly on Linux between Dec. 25 and Dec. 30, uninstall it and torchtriton immediately and use the latest nightly binaries. Read the security advisory here: pytorch.org/blog/compromis
Image
11