---
title: "Security"
description: "181 posts about Security, summarised, each linking to the original."
---

# Security
> 181 posts about Security, summarised, each linking to the original.

## Articles

### [Take Control: Customer-Managed Keys for Lakebase Postgres](https://yomu.fyi/post/take-control-customer-managed-keys-for-lakebase-postgres.md)
- Company: [Databricks](https://yomu.fyi/company/databricks.md)
- Author: Ben Hagan
- Published: Apr 20, 2026
- Type: Announcement

Lakebase Customer Managed Keys (CMK) gives regulated enterprises control of the root of trust through customer-owned keys from AWS KMS, Azure Key Vault, or Google Cloud KMS. Because Lakebase separates persistent storage from elastic Postgres compute that can scale to zero, CMK protects both layers and their caches rather than storage alone. Its hierarchical envelope-encryption model uses the CMK as the root, transient Key Encryption Keys (KEKs) to wrap Data Encryption Keys (DEKs), and unique DEKs for each data segment, while plaintext CMKs remain in the customer’s KMS. Account Admins bind a configured key to a workspace, after which new projects inherit the CMK; rotation needs no re-encryption or downtime, revocation terminates compute instances, and audit services record cryptographic operations.


### [Run cloud agents in your own infrastructure](https://yomu.fyi/post/run-cloud-agents-in-your-own-infrastructure.md)
- Company: [Cursor](https://yomu.fyi/company/cursor.md)
- Author: Katia Bazzi
- Published: Mar 25, 2026
- Type: Announcement

Cursor has made self-hosted cloud agents generally available, allowing code, tool execution, and build artifacts to remain within an organization’s network. Each agent runs in an isolated virtual machine or dedicated worker with a terminal, browser, and full desktop; it can clone repositories, configure environments, write and test code, and push changes for review. A worker connects outbound to Cursor’s cloud over HTTPS, receives tool calls from the agent harness, and returns execution results, while organizations can run long-lived or single-use workers and manage large fleets through a Helm chart, Kubernetes operator, or fleet management API. The product retains cloud-agent capabilities including multi-model support, plugins, and team permissions, while giving teams access to internal caches, dependencies, endpoints, and security controls without maintaining a separate agent stack.


### [Securing our codebase with autonomous agents](https://yomu.fyi/post/securing-our-codebase-with-autonomous-agents.md)
- Company: [Cursor](https://yomu.fyi/company/cursor.md)
- Author: Travis McPeak
- Published: Mar 16, 2026
- Type: Announcement

After a fivefold increase in pull-request velocity over nine months, the team found static analysis and rigid code ownership insufficient for security at scale. It built a fleet of Cursor Automations powered by cloud agents, webhook and GitHub integrations, and a security MCP deployed as a just-in-time serverless Lambda function. The MCP provides persistent data, semantic deduplication using Gemini Flash 2.5, and consistently formatted reporting and follow-up actions, while Terraform standardizes review and deployment. Four templates cover PR review, segmented vulnerability hunting, dependency patching with reachability analysis and tests, and daily invariant-drift monitoring. Agentic Security Review has run on thousands of PRs in two months and prevented hundreds of issues from reaching production; the team says more automations are planned.


### [How we built security into Custom Agents](https://yomu.fyi/post/how-we-built-security-into-custom-agents.md)
- Company: [Notion](https://yomu.fyi/company/notion.md)
- Author: Sean Keenan, Jacob Brackett
- Published: Feb 27, 2026
- Type: Explainer

Custom Agents were designed for collaborative workspaces where useful access must be balanced against dangerous actions. They use a build-from-nothing model with no default read, write, or interaction permissions, then add resource-level controls such as page-level access, Slack “read and reply,” email confirmation, and selected MCP tools. Runtime safeguards combine permission controls with prompt-injection mitigations, monitoring of external data, warnings, owner confirmation for risky actions, and remediation such as deleting an incorrect Slack message. Alpha testing across Notion and customers produced more than 3,000 internal and 25,000 customer agents, and exposed overly broad Slack write access that could reach #general. That finding led to the custom permission and reinforced the case for first-party integrations, while planned work includes admin-approved broader scopes, Workers integrations, and additional permission modes.


### [We proactively fixed ~100 security issues in 6 days with 0 humans](https://yomu.fyi/post/we-proactively-fixed-100-security-issues-in-6-days-with-0-humans.md)
- Company: [Ramp](https://yomu.fyi/company/ramp.md)
- Author: Eli Block
- Published: Feb 20, 2026
- Type: Tutorial

Ramp Security Engineering describes a six-day experiment in which home-grown agents found, validated, and fixed nearly 100 latent backend security issues, including some high-severity findings, without human involvement until pull-request review. The issues had not been uncovered by penetration testing, bug bounty testing, static analysis, or trials of 10+ code-scanning vendors, and all were patched within a week of discovery. The pipeline used specialized vulnerability detectors, adversarial manager agents that rejected 40% of initial proposals in sample testing, integration tests for validation, and an internal coding agent that generated patches. Live interactive validation struggled with complex preconditions, so test-based validation became the main approach; a human team member still reviewed and landed each pull request.


### [Implementing a secure sandbox for local agents](https://yomu.fyi/post/implementing-a-secure-sandbox-for-local-agents.md)
- Company: [Cursor](https://yomu.fyi/company/cursor.md)
- Author: Ani Betts, Yash Gaitonde & Alex Haugland
- Published: Feb 18, 2026
- Type: Problem & solution

Auto-approved terminal commands make coding agents more capable but increase the risk of destructive changes and secret leakage, while repeated approval prompts create approval fatigue. Over three months, the team rolled out a uniform sandbox API across macOS, Linux, and Windows, allowing agents to run freely inside controlled environments and request approval mainly for internet access. macOS uses dynamically generated Seatbelt profiles; Linux combines Landlock, seccomp, and overlay filesystems to enforce workspace and ignored-file restrictions; Windows runs the Linux sandbox through WSL2. Changes to tool descriptions and result rendering help agents recognize constraints and escalate instead of retrying failed commands. Production data reports that sandboxed agents stop 40% less often, and the sandbox now handles a third of requests on supported platforms, although native Windows isolation remains under development.


### [Box chooses Cursor for enterprise-grade quality, security, and control](https://yomu.fyi/post/box-chooses-cursor-for-enterprise-grade-quality-security-and-control.md)
- Company: [Cursor](https://yomu.fyi/company/cursor.md)
- Author: Cursor
- Published: Feb 13, 2026
- Type: Announcement

Box selected Cursor as its enterprise agentic coding platform after evaluating data privacy, security, and agent-quality controls. More than 85% of Box developers, or over 800 people, now use Cursor daily, while the company reports a 30–50% increase in product-roadmap throughput and migrations completed 80–90% faster. Box encodes agent guardrails in custom Cursor rules and commands, including a frontend AI toolkit, automated test-coverage work, and rules for React and design-system migrations. A mentorship program pairing power users with newer adopters increased Cursor usage by 75% and power users by 25% in six weeks, while Box says it can move faster without compromising product quality, security, or accessibility.


### [Securely indexing large codebases](https://yomu.fyi/post/securely-indexing-large-codebases.md)
- Company: [Cursor](https://yomu.fyi/company/cursor.md)
- Author: Jeremy Stribling
- Published: Jan 27, 2026
- Type: Problem & solution

Cursor describes a secure way to index large codebases for semantic search, where naive processing can delay availability for hours. The system builds a Merkle tree of file and directory hashes, synchronizes only divergent branches, and caches embeddings by chunk content to reduce repeated work. For new users, a client-generated simhash finds a similar index within the same team or user's indexes, which is copied while background synchronization reconciles differences. Content proofs derived from the client's full Merkle tree filter search results so users see only files they can prove they possess. Reported time-to-first-query falls from 7.87 seconds to 525 milliseconds for the median repository, and from 4.03 hours to 21 seconds at the 99th percentile.


### [Okta Developer Connect Recap](https://yomu.fyi/post/okta-developer-connect-recap.md)
- Company: [Okta](https://yomu.fyi/company/okta.md)
- Author: Akanksha Bhasin
- Published: Jan 19, 2026
- Type: Announcement

Okta Developer Connect Bengaluru was Okta’s first flagship Developer Connect event in India, bringing developers, architects, engineering managers, IAM practitioners, and technology leaders together to discuss identity as systems scale and AI agents work alongside humans. Sessions framed identity as foundational infrastructure spanning users, applications, APIs, services, and AI agents, while connecting core standards and practices to platform use cases including the Okta MCP Server, Cross App Access, Okta Integration Network, Okta Workflows, lifecycle management, and Verifiable Digital Credentials. Interactive discussions, audience Q&A, quizzes, surveys, and a research panel complemented talks and enabled exchanges with Okta engineers, product leaders, and advocates. The Bengaluru event begins an ongoing series intended to support practical identity education and open technical dialogue about enterprise-ready systems, identity standards, and AI-driven access and security assumptions.


### [From deployment slop to production reality: How BriX bridges the gap with enterprise-grade AI infrastructure](https://yomu.fyi/post/from-deployment-slop-to-production-reality-how-brix-bridges-the-gap-wi.md)
- Company: [Grab](https://yomu.fyi/company/grab.md)
- Author: Sneh Agrawal
- Published: Jan 16, 2026
- Type: Problem & solution

BriX addresses “deployment slop,” the gap between quickly built AI prototypes and enterprise production, where inconsistent versions, reliability failures, and security risks can block adoption. The platform centralizes production infrastructure so semi-technical domain experts can configure deployments rather than become DevOps specialists, covering scaling, monitoring, audit trails, access controls, data connections, and consistent behavior. BriX supports switching among models such as Claude, GPT, and Gemini; its Model Context Protocols (MCPs) provide standardized, pre-built connectors to approved enterprise data sources with built-in access controls and query logging. Centralized system prompts and context files enforce shared guardrails, while custom frontends and persistent, shareable reports extend use beyond chat interfaces. The stated result is a platform intended to turn deployment into a configuration task, helping teams move from prototypes to enterprise-grade tools in days rather than months.


### [Hooks for security and platform teams](https://yomu.fyi/post/hooks-for-security-and-platform-teams.md)
- Company: [Cursor](https://yomu.fyi/company/cursor.md)
- Author: Michael Feldstein, Michael Scherr & Travis McPeak
- Published: Dec 22, 2025
- Type: Announcement

Cursor has announced ecosystem partnerships around hooks, which run before or after defined stages of its agent loop to observe, block, or modify behavior. The integrations target MCP governance, code security, dependency scanning, agent safety, and secrets management, connecting Cursor with security tooling, observability platforms, secrets managers, and compliance systems. MintMCP, Oasis Security, and Runlayer provide MCP inventory, least-privilege enforcement, audit trails, and centralized tool-interaction visibility, while Corridor and Semgrep give coding-time feedback and vulnerability scanning. Endor Labs intercepts package installations to scan for malicious dependencies, Snyk’s Evo Agent Guard reviews agent actions for prompt injection and dangerous tool calls, and 1Password validates that all required environment files from 1Password Environments are properly mounted before shell commands execute, enabling just-in-time secrets access without writing credentials to disk.


### [A Decade of Defense: Celebrating Grab's 10th Year Bug Bounty Program](https://yomu.fyi/post/a-decade-of-defense-celebrating-grab-s-10th-year-bug-bounty-program.md)
- Company: [Grab](https://yomu.fyi/company/grab.md)
- Author: Pei Shan Yap
- Published: Dec 1, 2025
- Type: Announcement

Grab marks the tenth anniversary of its bug bounty program, launched with HackerOne and initially involving 23 researchers. Over the decade, it grew into a global community, partnering with more than 850 active HackerOne researchers to help protect over 187 million users across Southeast Asia. The program broadened its scope in 2023–2024, adding assets that included Indonesian financial services and AI systems, while introducing a mobile-specific bounty table and experimenting with campaigns and reward methods. Grab says it now ranks among HackerOne’s top 20 programs worldwide and top three in Asia, and credits live hacking events and regional club campaigns with expanding testing coverage and researcher relationships. Anniversary activities included invite-only campaigns in Germany, Morocco, and India, plus a broader campaign that received 461 submissions, with xchopath receiving the Best Hacker Bonus.


### [Introducing Cursor for Enterprise](https://yomu.fyi/post/introducing-cursor-for-enterprise.md)
- Company: [Cursor](https://yomu.fyi/company/cursor.md)
- Author: Cursor
- Published: Oct 31, 2025
- Type: Announcement

Cursor is introducing enterprise features intended to make its coding agents more capable, transparent, and secure for organizations already using the product. Hooks expose the agent loop to custom scripts that can log actions and tool calls, enforce compliance or command allowlists, scrub sensitive material, connect external systems, and trigger automations; they can be distributed through MDM or Cursor’s cloud option. Team Rules provide shared context and can recommend or require standards such as API schemas, conventions, and workflows, while upgraded analytics report activity, adoption, AI lines of code, directory-group filters, and exportable data with updates every two minutes. The release also adds an Audit Log covering 19 event types and Sandbox Mode, which restricts network and file access by default, with administrators controlling availability and team-wide Git and network access.


### [Kurt Got Got](https://yomu.fyi/post/kurt-got-got.md)
- Company: [Fly.io](https://yomu.fyi/company/fly-io.md)
- Published: Oct 8, 2025
- Type: Incident / postmortem

Fly.io recounts the takeover of its X/Twitter account after CEO Kurt Mackey entered credentials on members-x.com in response to a phishing email from alerts-x.com. The attackers revoked existing tokens, configured new 2FA, changed the account email, and used it for a crypto scam; the company says no customer systems or accounts were at risk, though the incident caused more than 15 hours of brand damage. Fly.io attributes the exposure to treating the shared social account as a legacy exception rather than protecting it through its normal Google IdP and phishing-resistant MFA. The post explains how FIDO2, U2F, and Passkeys prevent fake sites from receiving real credentials, while noting that the 1Password browser plugin could also have flagged the mismatched domain. The account is now protected with Passkeys.


### [Securing Salesforce Integrations with Heroku AppLink](https://yomu.fyi/post/securing-salesforce-integrations-with-heroku-applink.md)
- Company: [Heroku](https://yomu.fyi/company/heroku.md)
- Author: David Baliles
- Published: Sep 10, 2025
- Type: Explainer

Salesforce integrations commonly use Connected Apps or External Services, but long-lived OAuth tokens and public vendor endpoints can expose org data to replay and misuse. Heroku AppLink provides a managed bridge in which a service mesh admits requests only from explicitly connected Salesforce orgs, validates context, and exposes services as native Salesforce actions. For calls back to Salesforce, its SDK obtains short-lived, scoped credentials at runtime through user, user-plus, or authorized-user modes, avoiding refresh-token storage in vendor systems. The mesh uses the x-client-context header to convey org and user information, while the SDK keeps bearer credentials out of application code. The post describes setup commands for the AppLink add-on, service-mesh buildpack, External Service publication, and authorizations, concluding that AppLink improves governance, least privilege, and replay resistance.


### [Updating sales restrictions for unsupported regions](https://yomu.fyi/post/updating-sales-restrictions-for-unsupported-regions.md)
- Company: [Anthropic](https://yomu.fyi/company/anthropic.md)
- Published: Sep 4, 2025
- Type: Announcement

Anthropic is updating its Terms of Service to address access by companies from regions where its products are not permitted, including entities operating through foreign subsidiaries. The company says ownership or control from jurisdictions such as China can create legal obligations to share data, cooperate with intelligence services, or support military and intelligence objectives. Under the change, companies or organizations more than 50% owned directly or indirectly by companies headquartered in unsupported regions are prohibited from using the services, regardless of where they operate. Anthropic frames the update as aligning its restrictions with real-world national-security risks and reiterates support for export controls, US energy projects, and rigorous evaluation of AI models for capabilities relevant to national security.


### [It's Time to Evolve Authentication Security](https://yomu.fyi/post/it-s-time-to-evolve-authentication-security.md)
- Company: [Okta](https://yomu.fyi/company/okta.md)
- Author: Alisa Duncan
- Published: Aug 6, 2025
- Type: Explainer

Identity-based attacks and compromised credentials are driving a need for stronger authentication, while security requirements must be balanced against user friction and application sensitivity. The guidance recommends phishing-resistant factors, including smart cards, biometric-capable hardware, FIDO2 with WebAuthn, and Passkeys, while warning against security questions, SMS codes, email TOTP, and password antipatterns. It also advises using strong MFA as a backup, dynamic authentication policies and threat detection, and OAuth 2.1/OIDC through an identity provider, with step-up authentication to maintain assurances during a session. For application integration, the recommended approach is to redirect users to an Okta-hosted Sign-In Widget through vetted OIDC client libraries or Okta SDKs, reducing implementation errors in PKCE and token verification while supporting evolving standards.


### [Introducing CIBA for Secure Transaction Verification](https://yomu.fyi/post/introducing-ciba-for-secure-transaction-verification.md)
- Company: [Okta](https://yomu.fyi/company/okta.md)
- Author: Indranil Jha
- Published: Jul 31, 2025
- Type: Explainer

CIBA addresses identity verification when an application cannot use an interactive login on the consumption device, including bank customer-service changes, retail POS payments, browser-constrained devices, and shared kiosks. Client-Initiated Backchannel Authentication decouples authentication from the application: a client sends a back-channel request to an OAuth 2.0 authorization provider, while the user approves it on a separately enrolled phone or smartwatch. CIBA extends OpenID Connect with a grant type, discovery metadata, and poll, ping, and push token-delivery modes; in the described banking flow, the application receives a user-scoped token to update the email address. The approach improves least-privilege access and avoids exposing credentials on shared devices, but can enable MFA-fatigue-style attacks, should not be used same-device, and may warrant device code flow in some cases.


### [Using Kamal 2.0 in Production](https://yomu.fyi/post/using-kamal-2-0-in-production.md)
- Company: [Fly.io](https://yomu.fyi/company/fly-io.md)
- Published: May 29, 2025
- Type: Announcement

Sam Ruby describes publishing an online guide to using Kamal 2.0 for production after finding existing material insufficient for deploying a real project. The guide grew from research for the Deployment and Production chapter of Agile Web Development with Rails 8, then was converted from Pragmatic Programming’s XML grammar to Markdown with GitHub Copilot and proofread with it. It presents an opinionated starter list with defaults and alternatives, covering seven initial requirements alongside Docker builders, container repositories, secret management, hosting choices, load balancing, and managed databases. It also treats production as including database backups, searchable logs, monitoring, and application security, and invites community corrections or additions under a CC0 license.


### [Streamlining RiskOps with the SOP agent framework](https://yomu.fyi/post/streamlining-riskops-with-the-sop-agent-framework.md)
- Company: [Grab](https://yomu.fyi/company/grab.md)
- Author: Fujiao Liu
- Published: May 8, 2025
- Type: Problem & solution

Risk Operations teams investigating Account Takeover (ATO) cases must gather data across systems, run SQL queries, and make decisions under pressure, creating delays and error risk. The SOP-driven LLM agent framework represents the workflow as a natural-language, indentation-based tree whose steps specify queries, external functions, and decision criteria. During execution, the SOP planner navigates the tree and produces JSON-formatted instructions, while a Worker Agent invokes APIs or SQL queries and stores results in a feedback loop. The process ends by synthesising investigation data into a report and final decision. In reported results, handling time fell from 22 to 3 minutes per ticket, 87% of ATO cases were automated since launch, and the error rate was zero.


[Newer posts](https://yomu.fyi/topic/security/page/6.md) · [Older posts](https://yomu.fyi/topic/security/page/8.md)