NETWORKING EVENT

Before the Build: Securing the Modern Software Supply Chain

Tuesday, November 17, 5:30pm PST

Adobe Global Headquarters

Protect What Enters Your Pipeline

Stop Threats Before They Reach
Your Builds and Clusters

The software supply chain is changing, and security teams are rethinking where and how they stop risky dependencies.

We’re bringing together engineering and security leaders for a casual evening of drinks and discussions around evolving security controls, managing dependency risks, and protecting the packages and artifacts moving through modern CI/CD and Kubernetes environments.

⇒ Layers Café @ Adobe HQ

⇒ East Tower Lobby, 345 Park Ave, San Jose, CA 

 

Whether you're focused on DevOps, platform engineering, security, or developer experience,

you'll leave with practical ideas you can apply immediately to your own pipelines.

Block the known. Quarantine the unknown.

Scanners like JFrog Xray only catch vulnerabilities after dependencies are pulled in, by which point it is too late. Artifact Firewall enforces policy the moment a package is requested, stopping malware and vulnerable versions before they are installed, across npm, PyPI, Maven, and NuGet.

 

Block known risks

Deny versions matched by OSV intelligence or your own rules, returning a clear policy reason.

Hide risky versions

Risky versions no longer count as latest. The latest becomes the latest approved version, while a pinned version still installs.

Quarantine unknown packages

Hold new versions for a configurable window, long enough for the community to flag malicious uploads.

Serve approved packages

Pass approved versions straight through, so builds resolve to a safe release.