Oso’s cover photo
Oso

Oso

Software Development

New York, NY 4,160 followers

Visibility and controls to secure agents.

About us

Oso gives organizations the visibility and controls to get their arms around agent adoption: discover every agent running inside your company, monitor all approved AI traffic, detect anomalous behavior and policy violations, enforce rules on what agents can and can't do, and produce complete audit logs of every action. Trusted by teams at Webflow, Brex, Vanta, Duolingo, and more. Backed by Sequoia and Felicis.

Industry
Software Development
Company size
11-50 employees
Headquarters
New York, NY
Type
Privately Held
Founded
2018

Employees at Oso

View 80 employees at Oso

or

By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.

See all employees

Locations

Updates

  • Oso reposted this

    Nobody can tell the difference between you doing something and your AI agent doing it. That's the whole problem with agent identity right now, and it's the same access problem security teams never solved for humans. Graham Neray, Co-Founder and CEO Oso spoke to Ashish and Caleb about why agents go straight for production credentials. The reason agents are dangerous is the same reason they're useful: you hook them up to production systems and real data. Most of those systems are badly over-permissioned, and everyone already knows it. We never solved least privilege for slow, non-automatic humans. Access scoped to exactly what you need, only when you need it, only for as long as you need it. Agents just expose that gap at machine speed. Save this for the next time someone pitches you an agent that needs full prod access on day one. Follow AI Security Podcast for practitioner takes on securing AI systems. #aisecurity #cloudsecurity #identitysecurity #leastprivilege #aisecuritypodcast

  • Oso reposted this

    "Passwords are the keys to the kingdom. You need to go to someone that's trusted." - Graham Neray, Co-founder and CEO of Oso on why the team started using 1Password from day one. With the rise of AI agents, Graham says credential security is “table stakes.” We agree. Credential sprawl doesn't announce itself. It accumulates quietly across SaaS apps, shared logins, AI tools, and accounts created to get work done. That’s the problem 1Password is built to solve, for every employee, agent, and machine identity in your organization. #IdentitySecurity #CredentialSecurity #Startups #Cybersecurity #AgenticAI #1Password

  • View organization page for Oso

    4,160 followers

    New research from the Cloud Security Alliance quantifies the risk of over-permissioned agents: 65% of enterprises experienced a security incident caused by AI agents in the past year. 61% of those resulted in data exposure. The root cause isn't that agents are malicious; it's that they're operating with more access than they need. Our own research found that 96% of permissions go unused by humans, opening up a major security risk for agents who inherit human access. 👇 Link to both research reports in the comments

  • Oso reposted this

    "I thought I was being so clever. We don't need to build blocking, no one's ever gonna use it." Then every buyer asked for it anyway. So they built it. And almost nobody turns it on. Graham Neray of Oso spoke to Ashish and Caleb about why the most demanded control in agent security sits switched off and what teams actually run instead. Human in the loop. Security teams still trust their engineers to apply judgment. They just want someone looking closely at what the agent is about to do, before it does it. Blocking gets you through the security review. Human in the loop is what engineering teams actually leave on. Caleb called it the always untold story of security, the feature everyone demands and no one uses. Follow AI Security Podcast for practitioner takes on securing agents. #aisecurity #aisecuritypodcast

  • View organization page for Oso

    4,160 followers

    Thanks Ashish Rajan 🤴🏾🧔🏾♂️ for having Graham Neray on your podcast!

    View organization page for AI Security Podcast

    3,969 followers

    Least privilege for AI agents sounds like a config problem. It's an authorization problem you never solved for humans either. Think about what access actually is inside your company. People get permissions when they join. More pile on as roles change. They almost never get taken away. Everyone knows this. It just never made the top of the list. That was survivable because humans apply judgment, and there's a ceiling on what one person can break before someone notices. Agents break both. No judgment, they get tricked, they hallucinate, they'll dig a live production credential out of a local file just to help. And they run at machine speed: more damage in a minute than you'd do in a week. Graham Neray, founder and CEO of Oso, spoke to Caleb and Ashish about why the agent isn't a new problem, it's the old over-permissioning problem with the safety margin removed. "No destructive actions" reads clean on a slide and falls apart in practice. Everyone asks for blocking. Almost nobody turns it on. The fix isn't more rules, it's knowing the why behind an action. Save this if you're being pushed to ship agents before deciding what they can touch. Follow AI Security Podcast for practitioner takes on securing agents. #aiagents #aisecurity #aisecuritypodcast #aiauthz

    • No alternative text description for this image
  • Oso reposted this

    Why are security leaders terrified of connecting AI agents to production data? Because unlike humans, AI agents don't apply judgment, and they operate at machine speed, meaning they can relentlessly hunt down production credentials and do catastrophic damage before a human analyst even blinks. In this episode, Ashish and Caleb sit down with Graham Neray, CEO of Oso, to tackle the massive, unsolved problem of AuthZ (Authorization) for autonomous AI. We explore why the industry's reliance on static, over-permissioned human identities is a recipe for disaster when applied to tools like Claude Code and Notion Agents. Graham explains the dangerous pitfalls of allowing agents to adopt the permissions of their human operators (privilege escalation), versus the complexity of assigning agents their own unique service accounts. The conversation dives deep into the fragmented agent security market. Should you deploy a browser extension, an endpoint sensor, or an edge proxy?. Learn why blocking destructive actions is a flawed approach (because agents *need* to destroy things to work), and why the future of AI AuthZ requires dynamic, data-level policies and continuous "human in the loop" validation. #aisecurity #aisecuritypodcast

    Why Human Least Privilege Fails for Autonomous Agents

    www.linkedin.com

Similar pages

Browse jobs