TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Show HN: Proactive Security Monitoring for GitHub Actions Workflows

32 点作者 fkjadoon9411 个月前
Hey HN, it&#x27;s Farrukh and Umar. We&#x27;re building listen.dev–a tool for proactive security monitoring in GitHub Actions to secure software releases from supply chain threats.<p>Why we built this:<p>As friends and collaborators for over a decade, we&#x27;ve been working on various startup ideas in dev tools and infrastructure. In 2017, while building an ML ops toolkit on Kubernetes, we got hacked. During a pilot with a fintech customer, our cluster became victim to a crypto-jacking attack.<p>As it turned out, a dependency in our container base image contained malware (a Monero miner) which triggered inside the customer&#x27;s environment. Needless to say, we lost the customer and racked up a massive cloud bill as a tiny startup. This first-hand experience introduced us to one of the biggest challenges in software security today.<p>The Problem:<p>Modern engineering teams rely heavily on 3rd parties—from open source packages, base images and 3rd-party tooling to build &amp; deploy software quickly. But this creates security blind spots exploited in modern supply chain attacks. Some high-profile cases targeting developer environments include:<p>(1) event-stream: a malicious transitive dependency injected a wallet-drainer payload into the build process for CoPay’s bitcoin wallet (2) SolarWinds: a compromised build tool injected malicious code into downstream releases (3) Codecov: a bash uploader script inside the testing tool stole secrets when run in CI<p>While most teams today incorporate some form of security scanning, it typically focuses on known vulnerabilities. In contrast, we detect zero-day threats and harden your build &amp; release processes against malicious activity. With a focus on developer experience.<p>Enter listen.dev: a tool to analyze the behavior of your GitHub Actions workflows. How it works:<p>- Native integration via a simple workflow step. You can instrument your build, test, and release processes in any language or stack. - Observes low-level behaviors using eBPF (network, file, process signals) over each run - Detects anomalies and malicious activity using threat intelligence and out-of-the-box detections for known bads (e.g., info stealers making unknown network connections, reverse shells, tampering of builds etc.) - Offers in-line PR feedback with context, plugging into existing toolchains via webhooks<p>Behind listen.dev is a team of builders and OSS maintainers with years of experience in security observability and developer tools—having previously worked on eBPF runtime security projects like Falco and Tracee. We&#x27;re seeking feedback from DevOps and security folks to help us improve.<p>You can sign up for free at <a href="https:&#x2F;&#x2F;lstn.dev&#x2F;hn" rel="nofollow">https:&#x2F;&#x2F;lstn.dev&#x2F;hn</a>, install our GitHub action in under a minute, and start monitoring your repos.<p>We&#x27;d love to hear from you–any feedback and questions are welcome. To learn more see <a href="https:&#x2F;&#x2F;docs.listen.dev" rel="nofollow">https:&#x2F;&#x2F;docs.listen.dev</a> and a video of how it works: <a href="https:&#x2F;&#x2F;lstn.dev&#x2F;demo-video" rel="nofollow">https:&#x2F;&#x2F;lstn.dev&#x2F;demo-video</a>

3 条评论

rst1311 个月前
Interesting take. I’ve been looking a lot into hardening build clusters for our dev teams. We’re a k8s shop and use a mix of egress controls, host isolation, and Falco for detections (although we’ve had stability issues running the sidecar architecture).<p>- How do you capture context from the builds beyond vanilla ebpf traces? is there a way to see the detection ruleset&#x2F;customize it<p>- I’m generally wary of running ebpf stuff on prod infra. Whats the threat model for your tool?<p>I&#x27;d love to give this a spin, but browsing through docs it seems like listen.dev works on Github hosted runners right now. Is self-hosted support on the roadmap?
评论 #40804648 未加载
belikebakr11 个月前
Hey, a couple questions:<p>1. Can listen.dev handle the monitoring of dynamically generated or short-lived GitHub Actions, which may only exist for the duration of a pull request? 2. How does listen.dev differentiate between normal and anomalous behavior without extensive prior data on a new user’s workflows?
评论 #40803723 未加载
ghiaadev11 个月前
Tried a test run for my node repo. It worked fine when I used the semver version of the action, but not when I pin the action to the latest release hash as shown in the GitHub marketplace listing docs (Shouldn&#x27;t the safer practice here work by default??)
评论 #40811209 未加载