Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

Aviram (Jit Co-Founder) chats with Pixellot about cutting SCA noise by focusing only on vulnerable packages that are direct dependencies and proven loaded at runtime. Delivered as a daily/weekly report via a custom Jit agent.

In software, speed is great, but safety is critical. How do you get both? That's the "Sec" in. It’s why has gained popularity: moving from the end of the line to the very beginning. Instead of a final check, it becomes a "shared responsibility" for Dev, Sec, and Ops teams at every stage of software development and delivery.

In this walkthrough, you’ll see two Agent Gallery workflows in action. The Daily Zero-Day Analyst pulls newly published CVEs from the last 24 hours, classifies them (CVSS, CWE, attack vector), and checks your environment for exposure using SBOM/package data—then can send daily updates to Slack. The Top 10 High-Risk Repositories agent scans your codebase, consolidates findings per repository, and ranks the repos with the most critical risk so you can prioritize remediation. You’ll also see how to review and edit the prompt, set schedules, enable notifications, and browse the Agent Gallery to add more agents.

This video breaks down the architecture behind Jit security agents and why it’s required for agents that work reliably in real environments. We walk through Jit’s three layers—ingestion, correlation, and action—using concrete examples across code, applications/knowledge bases, and cloud runtime. You’ll see how Jit continuously normalizes and reconciles incompatible security data, materializes it into a Security Context Graph (knowledge graph), and then executes agent workflows safely using graph queries and domain-specific tools.