# 1Password

Recent content in Blog on 1Password Blog

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## How to safely use AI agents for holiday shopping

DevFeed: [How to safely use AI agents for holiday shopping](<https://devfeed.tech/articles/how-to-safely-use-ai-agents-for-holiday-shopping-144198.md>)

Original publisher: [Read original article](<https://1password.com/blog/ai-agents-holiday-shopping>)

Author: info@1password.com (Rachel Sudbeck)

Published: 2026-11-19T00:00:00Z

Content type: tutorial

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [agentic commerce fraud](<https://devfeed.tech/topics/agentic-commerce-fraud.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [AI Context Management](<https://devfeed.tech/topics/ai-context-management.md>), [Finance](<https://devfeed.tech/topics/finance.md>), [1Password](<https://devfeed.tech/topics/1password.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [holiday](<https://devfeed.tech/tags/holiday.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [safely](<https://devfeed.tech/tags/safely.md>), [security](<https://devfeed.tech/tags/security.md>), [shopping](<https://devfeed.tech/tags/shopping.md>), [tips-advice](<https://devfeed.tech/tags/tips-advice.md>)

### AI overview

AI agents can help track holiday deals, but the article recommends keeping the shopper in control of account access and purchases. Its six steps are to verify assistants and extensions before connecting accounts; keep passwords and verification codes out of prompts, using a supported password manager integration where available; limit account access to what the task needs; set clear spending and product limits and enforce them through account controls; require human approval at checkout and review purchase details; and revoke access when shopping ends. The article warns that fake extensions may steal data or install malware, and prompt injection or agent errors may lead to unintended actions. It describes 1Password for Agents as letting users approve access to a specific login and fill credentials without exposing them to the agent; integration flows vary by agent provider.

### Source excerpt

Imagine: a no-budget, no-holds-barred shopping spree. You can just go online and buy whatever you want, with no limits. It's the dream of romcom protagonists and game show contestants alike. Of course, if you're the one signing the bill, it's more like a nightmare. And the fear of someone (or something) going wild with your bank balance has been at the core of recent conversations around AI agents. According to McKinsey & Company, over 50% of global consumers now use AI for shopping, and last year saw a 70% jump in the rate at which U.S. AI users completed a purchase with AI. However, a recent Salesforce survey revealed some important caveats to this trend: only 19% of personal agent users have used their agents at checkout, and 73% of shoppers aren't comfortable giving a personal AI agent their payment information. It's understandable why many people are turning to AI agents to help with their holiday shopping. For a human, it's almost a full-time job to track prices and sales across stores for everything on your list; an agent is far better equipped to keep an eye on offers for that collector's item your sister is asking for. You save energy, but can still pounce on the best deals when they're available. At the same time, it's natural that anyone who's shopping with agents this season would want to stay in control of what that agent can access. In this blog, we'll cover some of the risks of shopping online with AI agents, as well as how you can safely and confidently take advantage of them during this holiday season. We'll also be sharing key tips and advice from Dave Lewis, 1Password's Global Advisory CISO. 6 tips for safer holiday shopping with AI agents The key to shopping with agents is making sure you are always in control of what information (financial or otherwise) the agent can access. Here are some of the risks of using agents, and controls to rein in their access, so you don't have to find out just how expensive a "free agent" can be. 1. Verify your AI s

## Finding and closing gaps in security logging with AI

DevFeed: [Finding and closing gaps in security logging with AI](<https://devfeed.tech/articles/finding-and-closing-gaps-in-security-logging-with-ai-141081.md>)

Original publisher: [Read original article](<https://1password.com/blog/ai-security-logging-gaps>)

Author: info@1password.com (Sanya Kohli)

Published: 2026-11-18T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Security Information and Event Management (SIEM)](<https://devfeed.tech/topics/siem-security.md>), [Logging](<https://devfeed.tech/topics/logging.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-skills](<https://devfeed.tech/tags/ai-skills.md>), [ai-tool](<https://devfeed.tech/tags/ai-tool.md>), [audit](<https://devfeed.tech/tags/audit.md>), [detection-rules](<https://devfeed.tech/tags/detection-rules.md>), [developers](<https://devfeed.tech/tags/developers.md>), [inventory](<https://devfeed.tech/tags/inventory.md>), [investigation](<https://devfeed.tech/tags/investigation.md>), [logging](<https://devfeed.tech/tags/logging.md>), [logs](<https://devfeed.tech/tags/logs.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [parsing](<https://devfeed.tech/tags/parsing.md>), [report](<https://devfeed.tech/tags/report.md>), [security](<https://devfeed.tech/tags/security.md>), [security-incident](<https://devfeed.tech/tags/security-incident.md>), [security-information-and-event-management](<https://devfeed.tech/tags/security-information-and-event-management.md>), [siem](<https://devfeed.tech/tags/siem.md>), [skills](<https://devfeed.tech/tags/skills.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

1Password built a scheduled audit that compares procurement and internal tool inventories with SIEM log sources, flags missing sources and collection or parsing problems, and produces a prioritized report for engineers. Code handles API data collection, matching, and publication; an AI model assesses likely security relevance and explains potential gaps. Reports are reviewed through pull requests and retain history, while checks guard against empty inputs and omitted assessments. For approved gaps, reusable AI skills guide log collection, parsing, access controls, documentation, and detection-rule preparation. Engineers verify findings, approve consequential changes, configure production credentials, and confirm logs are searchable before the workflow advances. The approach can miss tools when names are ambiguous; a SIEM name match does not prove complete activity coverage, and infrequently generated logs may need extra checks. Human review remains necessary.

### Source excerpt

A security incident is the worst time to discover that the logs you need were never collected. Even with a security information and event management (SIEM) in place, critical logging gaps can go unnoticed. Some tools may not send logs at all, while others may appear to be integrated but have collection or parsing issues that make their logs difficult to use during an investigation. With multiple tools, it can be a challenge to know what's missing or whether the logs you have are actually usable. At 1Password, finding these gaps meant manually comparing our tool inventory against SIEM log sources, one tool at a time. The process was time-consuming, difficult to keep up to date, and hard to scale as our environment evolved. We needed a more reliable way to identify gaps before they affected an investigation. We saw an opportunity to use AI to change how we identify security logging gaps and onboard new log sources. Instead of relying on time-consuming manual reviews, we built an approach that uses AI to uncover potential gaps and guide engineers through onboarding, while keeping critical decisions in human hands. Here's how we built it, what we learned, and where AI makes a difference. Collecting logs is only the beginning As 1Password adopts new tools, maintaining security visibility requires more than simply sending logs to the SIEM. We need to determine which logs matter for security, collect them, and ensure they contain the searchable information engineers need during an investigation. Even when logs are successfully ingested, important details can remain buried in unparsed text. Without proper parsing, engineers may struggle to search those details or build reliable detection rules. To address these challenges, we built an automated audit that compares our tool inventories against SIEM log sources and produces a prioritized report of potential logging gaps. For gaps we decide to close, we use AI skills: reusable instruction files that guide an AI tool through sp

## After the harvest: Find and secure developer secrets without slowing developers down

DevFeed: [After the harvest: Find and secure developer secrets without slowing developers down](<https://devfeed.tech/articles/after-the-harvest-find-and-secure-developer-secrets-without-slowing-developers-down-138315.md>)

Original publisher: [Read original article](<https://1password.com/blog/secure-developer-secrets>)

Author: info@1password.com (Baksheesh Singh Ghuman)

Published: 2026-11-17T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [after](<https://devfeed.tech/tags/after.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [ai-services](<https://devfeed.tech/tags/ai-services.md>), [can](<https://devfeed.tech/tags/can.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-assistants](<https://devfeed.tech/tags/coding-assistants.md>), [commands](<https://devfeed.tech/tags/commands.md>), [commits](<https://devfeed.tech/tags/commits.md>), [copy](<https://devfeed.tech/tags/copy.md>), [created](<https://devfeed.tech/tags/created.md>), [credential-harvesting](<https://devfeed.tech/tags/credential-harvesting.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developers](<https://devfeed.tech/tags/developers.md>), [devices](<https://devfeed.tech/tags/devices.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [unified-access](<https://devfeed.tech/tags/unified-access.md>)

### AI overview

Developer Watchtower finds plaintext credentials, including SSH keys and .env files, on local devices. Its alerts let developers import .env secrets into 1Password Environments, while admins can review a Local disk exposure report showing affected users and devices without seeing secret values. Environments stores and supplies app variables on demand, avoiding a standing plaintext .env file. Developers can import or add variables, use the CLI and SDKs, connect service accounts for automation, and use supported AI coding workflows through 1Password's MCP Server. Teams and Business customers can share environments with groups, with organization-wide availability controlled by admins. The article recommends enabling Watchtower, reviewing the report, treating found credentials as potentially exposed, revoking or rotating them, and storing replacements in Environments. It says Developer Watchtower is available at no extra cost to existing 1Password users.

### Source excerpt

In our first post on credential harvesting, we looked at what happens after an attacker gets inside an environment. The credentials they find can determine how fast and how far they move into other systems. AI is compressing that timeline, and developer machines are where many of those credentials sit. Finding exposed credentials is only half of the job. The harder part is fixing them without disrupting the way developers work. In this post we'll cover how 1Password Developer Watchtower and 1Password Environments help teams find, replace, and manage developer secrets. The riskiest copy of a secret is usually the one on disk For many developers, the fastest place to put a secret is a local .env file. It is familiar, supported by the tools they already use, and usually stored in plaintext. Even when teams provide dedicated secrets tooling, it can feel slow and disconnected from the workflow, so the familiar path wins. That habit feeds secret sprawl, and the numbers are moving the wrong way. GitGuardian's 2026 State of Secrets Sprawl report found 28.65 million new secrets in public GitHub commits in 2025, up 34% from the previous year. Leaked secrets for AI services grew 81% in a single year. For security teams, the bigger problem is visibility. A plaintext credential on a laptop is harder to monitor, rotate, revoke, or trace to the systems that depend on it. And now that AI coding assistants can access project files and run terminal commands, those credentials may be readable by more than the developer who created them. Secure developer secrets with 1Password That is the gap 1Password is closing with 1Password Environments and Developer Watchtower. They help teams find improperly stored developer credentials, secure them where employees already trust, and let developers keep using them without slowing down work. Developer Watchtower finds plaintext developer credentials on local devices, including .env files, and guides users to import them into 1Password Developer cr

## Scaling security reviews at 1Password: Adding an agentic pipeline stage (safely)

DevFeed: [Scaling security reviews at 1Password: Adding an agentic pipeline stage (safely)](<https://devfeed.tech/articles/scaling-security-reviews-at-1password-adding-an-agentic-pipeline-stage-safely-126526.md>)

Original publisher: [Read original article](<https://1password.com/blog/scaling-security-reviews-agentic-pipeline>)

Author: info@1password.com (Megan Barker)

Published: 2026-11-09T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [observability](<https://devfeed.tech/topics/observability.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [developers](<https://devfeed.tech/tags/developers.md>), [false-positive](<https://devfeed.tech/tags/false-positive.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [go](<https://devfeed.tech/tags/go.md>), [harness](<https://devfeed.tech/tags/harness.md>), [large](<https://devfeed.tech/tags/large.md>), [learn](<https://devfeed.tech/tags/learn.md>), [noise](<https://devfeed.tech/tags/noise.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [product-security](<https://devfeed.tech/tags/product-security.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [rules](<https://devfeed.tech/tags/rules.md>), [sage](<https://devfeed.tech/tags/sage.md>), [security](<https://devfeed.tech/tags/security.md>), [trust](<https://devfeed.tech/tags/trust.md>)

### AI overview

1Password's SAGE security reviewer added a Prover stage that investigates findings across the repository using read-only file and search tools. It can suppress a finding only when it cites code evidence and selects a supported reason; otherwise it fails open and posts the finding. After one month, it suppressed nearly nine in ten findings. On a 125-question replay test, it suppressed 85 of 86 false positives, kept all four real flaws without other protection, and let through findings that were real more than 90% of the time. It also suppressed 26 of 39 true positives, all hardening findings already covered by other protections. The authors report edge cases where it gave incorrect reasons, and note that four unprotected flaws are a small test sample. They are building human review of the Prover's decisions so mistakes can expand the test and guide rule changes.

### Source excerpt

In our first blog post, we introduced SAGE, our AI-assisted security code reviewer. In our second post, SuperSAGE (SAGE v2) gained context through scaffolding and consistency via the Go harness, so it could reason about the code around the diffs it reviews. The result? SAGE understands the 1Password codebase. SAGE was a great tool that was saving our engineers time. It was also missing a fundamental element: the ability to learn from its mistakes. Thankfully, we'd planned ahead. Earlier in the SAGE build process, we'd quietly implemented feedback collection. In short, after each pull request closes, SAGE gathers the thumbs-up and thumbs-down reactions our Product Security reviewers left on its findings, plus any comments they left on lines it didn't flag (potential false negatives). A dashboard shows which rules are earning which reactions, and how many findings SAGE may have missed. That dashboard revealed important information. About two-thirds of the reactions on SAGE's findings were thumbs-down. Now, as we explained in the first post in this series, the Finder stage of SAGE's pipeline is intentionally noisy; the Critic and Judge stages make things more precise. But too much noise was getting through. Every false positive that reached a human reviewer eroded a little of their trust and patience, which don't refresh nightly the way the scaffolding does. We also discovered a small subset of rules were earning a large share of the thumbs-down. Take one of our access control rules, for example. Every reaction to its findings was a thumbs-down, so we assumed something was wrong with the rule itself. But those thumbs down told us that a finding was wrong, not why. For that particular rule, the why could have been one of three things: It was firing on code it was never meant to cover, so we'd need to narrow where it applies. It was worded so broadly the Finder applied it too eagerly, so we'd need to reword it. It was flagging something that isn't really a security probl

## After the breach, attackers go credential harvesting

DevFeed: [After the breach, attackers go credential harvesting](<https://devfeed.tech/articles/after-the-breach-attackers-go-credential-harvesting-121167.md>)

Original publisher: [Read original article](<https://1password.com/blog/ai-credential-harvesting>)

Author: info@1password.com (Baksheesh Singh Ghuman)

Published: 2026-11-05T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [ai-assisted attacks](<https://devfeed.tech/topics/ai-assisted-attacks.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [.env](<https://devfeed.tech/topics/dotenv.md>), [code security](<https://devfeed.tech/topics/code-security.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [api](<https://devfeed.tech/tags/api.md>), [attacks](<https://devfeed.tech/tags/attacks.md>), [breach](<https://devfeed.tech/tags/breach.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [ci-cd-security](<https://devfeed.tech/tags/ci-cd-security.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [credential-harvesting](<https://devfeed.tech/tags/credential-harvesting.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [database](<https://devfeed.tech/tags/database.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developer-workflows](<https://devfeed.tech/tags/developer-workflows.md>), [developers](<https://devfeed.tech/tags/developers.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Credential harvesting can turn one stolen credential into broader access: the article describes attackers using a package-publishing credential to distribute a malicious package that then searched for more credentials. AI coding tools may read local settings such as .env files, so the article recommends scanning developer work locations, including .env files, SSH directories, and local configuration. 1Password Developer Watchtower checks locations teams select and shows affected users and devices without revealing secrets; developers can then revoke or rotate exposed credentials and move replacements into 1Password. For ongoing access, Developer Tools such as op run, shell plugins, the SSH agent, and the GitHub Actions integration provide credentials when needed rather than leaving plaintext values or reusable tokens in files. The article advises limiting access with scoped, short-lived credentials, tracking use, and expiring or revoking access after the work.

### Source excerpt

If you've spent the past few weeks responding to security advisories, you know what a challenge it is to keep delivery moving. As AI accelerates how quickly vulnerabilities can be found and exploited, it makes fundamentals like credential security more important. While a vulnerability may let attackers into an environment, credentials often determine how fast and how far they can move laterally within an environment. Once inside, they may search for credentials to use elsewhere. That search is known as credential harvesting. A recent incident involving a compromised CI/CD security tool showed how quickly this access can spread. Attackers obtained a package-publishing credential and used it to distribute a malicious package through AI infrastructure. Once installed, it searched for additional credentials. Within hours, a stolen credential can lead to an outage, a compromised release, a cloud incident, or a costly investigation. Not to mention reputational damage. AI changes the speed, scale, and frequency of attacks but not the fundamentals of a strong response. As AI-enabled tools reach deeper into developer workflows, security teams need to find those credentials and replace exposed copies, but the hard part is doing it without interrupting developer work. Where AI tools encounter developer credentials When you're getting an app running, the last thing you want is to stop and re-enter a credential every time you run a command. A .env file or local configuration keeps the app connected to its database or API and lets your scripts keep moving. That's why developers use them. The convenience of these workflows can make credential security easy to overlook. In a 1Password survey this year, 24% of developers reported that they hardcode credentials directly into code, scripts, or configuration files. 43% said they don't use a secrets manager or vault. The sprawl makes credentials harder to track, rotate, or remove. Now add AI. Nearly half of the developers surveyed said

## A practical security guide for developers

DevFeed: [A practical security guide for developers](<https://devfeed.tech/articles/a-practical-security-guide-for-developers-121168.md>)

Original publisher: [Read original article](<https://1password.com/blog/developer-guide-to-exposed-credentials>)

Author: info@1password.com (Mariane Bekker)

Published: 2026-11-05T00:00:00Z

Content type: tutorial

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [Threat monitoring](<https://devfeed.tech/topics/threat-monitoring.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-developer](<https://devfeed.tech/tags/ai-developer.md>), [application](<https://devfeed.tech/tags/application.md>), [apps](<https://devfeed.tech/tags/apps.md>), [attack](<https://devfeed.tech/tags/attack.md>), [attack-paths](<https://devfeed.tech/tags/attack-paths.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cli](<https://devfeed.tech/tags/cli.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cryptocurrency](<https://devfeed.tech/tags/cryptocurrency.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developer](<https://devfeed.tech/tags/developer.md>), [developers](<https://devfeed.tech/tags/developers.md>), [guide](<https://devfeed.tech/tags/guide.md>), [practical](<https://devfeed.tech/tags/practical.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The checklist recommends reviewing credentials one project at a time: find secrets in repositories and configuration, remove hardcoded copies, narrow access, restrict agent and tool permissions, and rehearse replacing credentials. Track each active credential's owner and consumers without recording its value. 1Password Developer Watchtower can find plaintext secrets in local .env files, while repository history requires a separate scanner. The CLI and SDKs deliver real secret values to applications, and Environments and CLI can supply them to local MCP servers; these methods reduce hardcoded copies but do not hide values from receiving software. Service Accounts separate automation identity from a person, but API key permissions and spending limits remain provider settings. For supported personal-agent sign-ins, 1Password for Agents can fill approved credentials outside the agent's view, though the account's permissions still matter. Practice replacement with a nonproduction credential, revoke exposed values with their issuers, and account for processes holding old values and sessions that may need separate termination.

### Source excerpt

Five steps to review the credentials behind your apps, tools, and AI agents. October's security incidents carried real consequences: more than $6 billion in cryptocurrency stolen in one attack, and at least nine AI developer platforms disclosing incidents during the month. These were separate incidents with different attack paths. For developer teams, they raise a practical question: if a credential leaked today, would you know where it's used, what it can access, and how to replace it? Pick one project and work through this checklist with your team. It focuses on credentials and access, one part of securing your development workflow. 1. Find exposed credentials You can't address a leaked credential if you don't know it exists or which systems depend on it. Scan the current repository and its history for secrets using a secret-scanning tool. Review findings and revoke or rotate exposed credentials. Review .env files, shell profiles, CI settings, and deployment configuration. Remove credentials the project no longer needs. Assign an owner to every active credential and identify its consumers so replacements can reach each dependent system. Keep secret values out of your inventory. Record names, owners, and storage locations instead. How 1Password can help: 1Password Developer Watchtower can help discover local .env files containing plaintext secrets so you can import them into Environments. Use a separate secret-scanning tool for repository history, and revoke or rotate credentials that may have been exposed. Developer Watchtower 2. Remove hardcoded secrets Every copy is another place to protect and update. Replace plaintext credentials in project configuration with secret references or runtime delivery. Run the application with the replacement setup and verify the workflows that use those credentials. Remove obsolete plaintext copies. If a value was exposed, confirm the old credential has been revoked. How 1Password can help: 1Password CLI supplies secrets as enviro

## What October's security incidents taught us about exposed credentials

DevFeed: [What October's security incidents taught us about exposed credentials](<https://devfeed.tech/articles/what-october-s-security-incidents-taught-us-about-exposed-credentials-118997.md>)

Original publisher: [Read original article](<https://1password.com/blog/october-security-incidents-exposed-credentials>)

Author: info@1password.com (Mariane Bekker)

Published: 2026-11-04T00:00:00Z

Content type: tutorial

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Security](<https://devfeed.tech/topics/security.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [principle of ephemerality](<https://devfeed.tech/topics/principle-of-ephemerality.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-api-keys](<https://devfeed.tech/tags/ai-api-keys.md>), [ai-developer](<https://devfeed.tech/tags/ai-developer.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [developers](<https://devfeed.tech/tags/developers.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [for-developers](<https://devfeed.tech/tags/for-developers.md>), [incidents](<https://devfeed.tech/tags/incidents.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [october](<https://devfeed.tech/tags/october.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [security-incidents](<https://devfeed.tech/tags/security-incidents.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

### AI overview

October's reported security incidents show how credentials can expose customer secrets and provide paths into additional systems. Reports described internal credentials reaching infrastructure, databases, and environment variables; long-lived plaintext admin credentials; exposed encrypted secrets; unauthorized API-key use; and a public key that remained usable after its file was deleted, later contributing to a release-pipeline compromise. The reports do not establish a single attacker or vulnerability behind the incidents. Recommended steps are to reduce plaintext copies by using secret references or managed storage, limit workflow permissions and separate development from production credentials, use SSH agents to reduce private-key copies, understand which component receives real credentials when giving agents access, and revoke or rotate potentially leaked credentials with the issuing provider. Also review logs and update connected systems: deleting a file does not invalidate an existing key, and managed storage cannot prevent a compromised application from exposing credentials it receives.

### Source excerpt

October brought a series of security incidents across AI and developer platforms. Several platforms reported incidents involving credentials or environment variables. Across several of those disclosures, access to one system became a way to reach credentials for others. For developers, the lesson is practical: we need to manage credentials throughout the workflows that use them. That means reducing plaintext copies, limiting permissions, and making it easier to revoke access when something goes wrong. What happened across October An October 30 industry report initially listed nine incidents affecting AI developer platforms, with more added in November. Across that roundup and vendor disclosures, several patterns stood out. Internal credentials exposed customer secrets.Reports described internal credentials being used to access infrastructure, platform databases, and environment variables. Another preliminary report identified long-lived admin credentials stored in plaintext and usable from the public internet as a root cause. Customers were urged to rotate stored credentials. One platform recommended rotating secrets and updating credentials for connected services after identifying unauthorized credential access. Another reported exposure of encrypted secrets and potential decryption of some environment variables. Deleting a leaked key didn't invalidate it. An admin key was committed to a public repository. The file was removed, but the key wasn't revoked. Months later, an attacker used it in an attack that ultimately compromised a release pipeline. Unauthorized API usage. Customers were urged to assume environment variables were compromised and rotate secrets. It also reported that customers had observed unauthorized use of AI API keys supplied to the platform. These incidents had different entry points and impacts. The public reports don't establish one attacker or vulnerability behind the entire wave, but they do show credentials serving both as a target and as a

## Reducing credential exposure as agents take on more work

DevFeed: [Reducing credential exposure as agents take on more work](<https://devfeed.tech/articles/reducing-credential-exposure-as-agents-take-on-more-work-103666.md>)

Original publisher: [Read original article](<https://1password.com/blog/reducing-credential-exposure-ai-agents>)

Author: info@1password.com (Aashish Tripathi)

Published: 2026-10-27T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [API keys](<https://devfeed.tech/topics/api-keys.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [access-tokens](<https://devfeed.tech/tags/access-tokens.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-responses](<https://devfeed.tech/tags/ai-responses.md>), [api](<https://devfeed.tech/tags/api.md>), [api-keys](<https://devfeed.tech/tags/api-keys.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cli](<https://devfeed.tech/tags/cli.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [code](<https://devfeed.tech/tags/code.md>), [config](<https://devfeed.tech/tags/config.md>), [credential-exposure](<https://devfeed.tech/tags/credential-exposure.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [database](<https://devfeed.tech/tags/database.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [developers](<https://devfeed.tech/tags/developers.md>), [environment-variables](<https://devfeed.tech/tags/environment-variables.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [fallout](<https://devfeed.tech/tags/fallout.md>), [files](<https://devfeed.tech/tags/files.md>), [security](<https://devfeed.tech/tags/security.md>), [unified-access](<https://devfeed.tech/tags/unified-access.md>)

### AI overview

The excerpt recommends reducing credential exposure by keeping secrets out of code, configuration, and pipelines, then resolving them at runtime. It describes 1Password CLI `op run` and secret references, Credential Broker with Workload Identity Federation, and scoped Service Account tokens for non-interactive workloads; that bootstrap token still needs careful protection and scoping. It also distinguishes temporary, policy-based privileged access for people and local AI agents from environment-secret management. For personal agents, a supported integration lets users approve sign-in on-device while the browser extension fills credentials without exposing them to the agent. These approaches aim to reduce copied credentials and standing access; the excerpt does not establish that they eliminate exposure risk.

### Source excerpt

At 1Password, we're building a trusted home for the credentials behind your digital life One minute, your team is merging a pull request on an average Wednesday. The next minute, the platform running your deployment tells you to rotate every secret stored there, including API keys, database credentials, and signing keys. Your security team will identify and scope the radius of the impact. Security engages the developer who owns the service and starts opening deployment settings, CI workflows, cloud consoles, old scripts, and local .env files, trying to answer: Which credentials may have been exposed? Where are all the places they appear? What can they access? And how in the world can I rotate them as fast as possible without breaking production? It's a scenario every developer and security practitioner dreads because it feels like a high-stakes treasure hunt. Recent security disclosures 1, 2, 3 have brought that challenge into focus: credentials exposed in config repos, environment variables accessed without authorization, access tokens appearing in AI responses and logs, and the scramble to identify, revoke, and replace what may have been exposed without breaking production. These incidents involved different systems and access types, but they highlight the risks when credentials collect in places where they can be copied, logged, or forgotten. Once exposed, the fallout can move downstream fast, and the rotation and cleanup can be a massive undertaking. That leaves the practical question of how to keep using these tools without making every platform, workflow, and agent another source of credential sprawl. Start where the credentials live First, keep the real credential out of the source code, config, or workflow whenever possible. Users can store the real credential in 1Password and put a reference in the config. Locally, 1Password CLI commands such as op run resolve secret references and pass the values to the launched process at runtime. With the 1Password Crede

## What it's like to build an exceptional Customer Experience team at 1Password

DevFeed: [What it's like to build an exceptional Customer Experience team at 1Password](<https://devfeed.tech/articles/what-it-s-like-to-build-an-exceptional-customer-experience-team-at-1password-103665.md>)

Original publisher: [Read original article](<https://1password.com/blog/build-a-customer-experience-team-at-1password>)

Author: info@1password.com (Steve O'Connor)

Published: 2026-10-27T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [AI for customer service automation](<https://devfeed.tech/topics/ai-for-customer-service-automation.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [Support](<https://devfeed.tech/topics/support.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [adopting](<https://devfeed.tech/tags/adopting.md>), [advocacy](<https://devfeed.tech/tags/advocacy.md>), [ai](<https://devfeed.tech/tags/ai.md>), [automation](<https://devfeed.tech/tags/automation.md>), [building](<https://devfeed.tech/tags/building.md>), [business](<https://devfeed.tech/tags/business.md>), [company](<https://devfeed.tech/tags/company.md>), [customer](<https://devfeed.tech/tags/customer.md>), [customer-experience](<https://devfeed.tech/tags/customer-experience.md>), [data](<https://devfeed.tech/tags/data.md>), [digital](<https://devfeed.tech/tags/digital.md>), [engagement](<https://devfeed.tech/tags/engagement.md>), [feedback](<https://devfeed.tech/tags/feedback.md>), [focus](<https://devfeed.tech/tags/focus.md>), [growth](<https://devfeed.tech/tags/growth.md>), [helps](<https://devfeed.tech/tags/helps.md>), [history](<https://devfeed.tech/tags/history.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [journey](<https://devfeed.tech/tags/journey.md>), [life-at-1password](<https://devfeed.tech/tags/life-at-1password.md>), [remote-work](<https://devfeed.tech/tags/remote-work.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

1Password's Customer Experience organization is shifting from manual, activity-focused account work toward coordinated, outcome-focused customer support as the company grows. It spans Customer Success, Digital Customer Success, Customer Engagement, Support, Implementation, and CX Operations. Product, data, automation, and AI are intended to reduce repetitive preparation and administrative tasks, summarize customer history, surface risks and opportunities, find relevant content, and recommend next steps--leaving staff more time for direct conversations, trust-building, and complex customer problems. The team emphasizes customer feedback, collaboration across functions, continuous improvement, and connecting customer outcomes with retention, adoption, advocacy, expansion, and revenue protection. The leader says candidates should bring curiosity, adaptability, and a commercial mindset; the work involves change and experimentation.

### Source excerpt

Hi, I'm Steve O'Connor, and I lead Customer Experience (CX) at 1Password. Our CX organization spans Customer Success, Digital Customer Success, Customer Engagement, Support, Implementation, and CX Operations. Each team has a different role, but together we ensure that customers experience one company and one connected journey. That vision is shaping how we're building the team and the way we work with customers. What we're building 1Password is growing quickly, and our work is expanding with it. To support that growth, we're evolving away from a highly manual, human-led model to one where product, data, automation, and AI help us focus our people where they can make the greatest difference for our customers. By reducing repetitive preparation and administrative work, AI gives our people more time to listen, build trust, and help customers solve complex problems. We're also shifting our focus from account ownership and activity to customer outcomes. How are customers adopting our products and realizing value from them? How are we building relationships that lead to retention, expansion, and advocacy? These are the questions that guide our work today. How AI is changing the work AI assists and augments the expertise that already exists within our team, helping us remove unnecessary work that gets in the way of building meaningful customer relationships. It helps us prepare for stronger conversations, from summarizing customer history and identifying risks and opportunities, to surfacing relevant content and recommending next steps. As technology helps us scale, our team's role is evolving as well. We're more focused than ever on meeting with customers and understanding what matters to them directly. How we win together The culture we're building starts with keeping customers at the center. Their feedback influences how we prioritize, improve, and make decisions. Since CX spans so many teams, it's especially important that we operate as part of the broader 1Password ec

## 1Password recognized in the 2026 Gartner® Magic Quadrant™ for Privileged Access Management

DevFeed: [1Password recognized in the 2026 Gartner® Magic Quadrant™ for Privileged Access Management](<https://devfeed.tech/articles/1password-recognized-in-the-2026-gartner-magic-quadranttm-for-privileged-access-management-98258.md>)

Original publisher: [Read original article](<https://1password.com/blog/1password-recognized-in-2026-gartner-magic-quadrant-for-privileged-access-management>)

Author: info@1password.com (1Password)

Published: 2026-10-23T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [1Password](<https://devfeed.tech/topics/1password.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [2026](<https://devfeed.tech/tags/2026.md>), [access-management](<https://devfeed.tech/tags/access-management.md>), [ai](<https://devfeed.tech/tags/ai.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [databases](<https://devfeed.tech/tags/databases.md>), [gartner](<https://devfeed.tech/tags/gartner.md>), [gartner-magic-quadranttm](<https://devfeed.tech/tags/gartner-magic-quadranttm.md>), [identity](<https://devfeed.tech/tags/identity.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [mention](<https://devfeed.tech/tags/mention.md>), [news](<https://devfeed.tech/tags/news.md>), [non-human-identities](<https://devfeed.tech/tags/non-human-identities.md>), [permission](<https://devfeed.tech/tags/permission.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [policy](<https://devfeed.tech/tags/policy.md>), [privileged-access](<https://devfeed.tech/tags/privileged-access.md>), [privileged-access-management](<https://devfeed.tech/tags/privileged-access-management.md>), [production-infrastructure](<https://devfeed.tech/tags/production-infrastructure.md>), [risk](<https://devfeed.tech/tags/risk.md>), [sensitive-data](<https://devfeed.tech/tags/sensitive-data.md>)

### AI overview

1Password Privileged Access received an Honorable Mention in the 2026 Gartner Magic Quadrant for Privileged Access Management. The article describes a shift from standing permissions to task-scoped, time-bound access for people, workloads, and AI agents across cloud and hybrid environments, Kubernetes, and databases. It maps existing permissions, evaluates requests through contextual Dynamic Guardrails--with lower-risk requests eligible for automatic approval and higher-risk ones routed to a reviewer--and creates approved permissions in native policy layers before automatically deprovisioning them. Requests and access events are logged; session review is available where supported. AI Agent Control gives each agent a distinct identity and task-scoped role. Intent-Based Access Control, currently in beta, compares declared intent with actions in real time and can restrict or revoke access before an out-of-scope action, subject to supported integration capabilities.

### Source excerpt

1Password Privileged Access was named an Honorable Mention in the 2026 Gartner® Magic Quadrant™ for Privileged Access Management. 1Password Privileged Access eliminates standing access for human and non-human identities across cloud and hybrid environments, databases, and Kubernetes. It provides just-in-time, just-enough privileges created at request time, scoped to the task, and automatically deprovisioned when the work is done. This secures production infrastructure and sensitive data for every identity and resource. We feel this honorable mention in the 2026 Gartner® Magic Quadrant™ for Privileged Access Management reflects the recognition that privilege should be created for the task at hand and removed when the work is done. Why standing access persists Standing access emerges as a byproduct of daily operations. What begins as a quick fix to remediate a bug or launch an AI agent often leaves a long tail of access risk and manual cleanup. Today, every engineer, service account, and AI agent in your environment carries more access than needed, and each permission is an opportunity attackers can exploit. Consider a team that brings on a contractor for a three-month project and grants access across its cloud environment, K8s cluster, and database. When the engagement ends, the access remains because removing it requires checking several systems and confirming nothing else depends on the account. Permissions granted for legitimate work outlive the work that justified them. Across the infrastructure, an organization may manage an AWS role, a K8s RBAC binding, and a database account through separate tools with no shared policy layer. Each new system adds another inventory to maintain. When the project ends, the contractor leaves, or a workload changes, teams must manually track and trigger cleanup, which quickly outpaces what they can secure or manage. In AI-agent workflows, standing access is harder to identify and contain. Many organizations still manage agent acces

## SaaS access governance: Does access end when employees leave?

DevFeed: [SaaS access governance: Does access end when employees leave?](<https://devfeed.tech/articles/saas-access-governance-does-access-end-when-employees-leave-91070.md>)

Original publisher: [Read original article](<https://1password.com/blog/saas-access-governance-checklist>)

Author: info@1password.com (Stephanie Torto)

Published: 2026-10-20T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Access Control](<https://devfeed.tech/topics/access-control.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>), [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [ai-governance](<https://devfeed.tech/topics/ai-governance.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [2025](<https://devfeed.tech/tags/2025.md>), [account](<https://devfeed.tech/tags/account.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-application](<https://devfeed.tech/tags/ai-application.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [awareness](<https://devfeed.tech/tags/awareness.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [business](<https://devfeed.tech/tags/business.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [company](<https://devfeed.tech/tags/company.md>), [complete](<https://devfeed.tech/tags/complete.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [employees](<https://devfeed.tech/tags/employees.md>), [governance](<https://devfeed.tech/tags/governance.md>), [leave](<https://devfeed.tech/tags/leave.md>), [saas](<https://devfeed.tech/tags/saas.md>), [saas-management](<https://devfeed.tech/tags/saas-management.md>), [security](<https://devfeed.tech/tags/security.md>), [tips-advice](<https://devfeed.tech/tags/tips-advice.md>)

### AI overview

Disabling an employee's identity provider account may leave access to non-SSO SaaS apps, shared credentials, OAuth connections, files, and workflows intact. The excerpt recommends inventorying applications and access paths; tying onboarding, role changes, contractor end dates, and terminations to owned workflows; removing permissions that no longer match a person's role; and verifying removal with completion records and regular process checks. It describes 1Password SaaS Manager as supporting discovery of managed and unmanaged SaaS and AI apps, OAuth connections, and permissions, plus lifecycle workflows through 400+ integrations. Depending on the integration, those workflows may support provisioning and deprovisioning, OAuth token revocation, license removal, and ownership transfer.

### Source excerpt

Cybersecurity Awareness Month encourages organizations to examine the controls behind everyday security habits. Training helps employees spot phishing and use strong authentication but does not resolve gaps in systems that govern access. Many organizations manage employee access through an identity provider (IdP) and single sign-on (SSO). However, not every AI or SaaS application connects to those systems. Other access paths, including shared credentials and OAuth connections, may require separate controls, especially when they provide access to company-owned resources that outlive an individual account. Employees join companies, change roles, and leave every day. Contractors, seasonal employees, and business partners use many of the same applications. Each transition can change what access a person has or should have. Consider a contractor who connects an AI application to company documents during a project. When the engagement ends months later, IT disables the contractor's account in the IdP. But who revokes the application's OAuth access? Who transfers ownership of connected files? Who verifies the connection is no longer active? If those steps rely on a spreadsheet or a message to an application owner, that is an access governance gap. According to 1Password's 2025 Access-Trust Gap Report, 38% of employees have successfully accessed a former employer's account. This finding reminds us that access can outlive the role it was created for, accruing cybersecurity and non-compliance costs. This October, security awareness should include the systems behind employee behavior. Effective SaaS governance helps IT discover applications and access paths across connected data sources. It governs access beyond SSO and creates repeatable workflows for onboarding, role changes, and offboarding. Why employee access persists after people leave or change roles When an employee leaves, IT may disable their primary account and assume the process is complete but work rarely happens

## Launching post-quantum safe passkeys

DevFeed: [Launching post-quantum safe passkeys](<https://devfeed.tech/articles/launching-post-quantum-safe-passkeys-92823.md>)

Original publisher: [Read original article](<https://1password.com/blog/post-quantum-passkeys>)

Author: info@1password.com (René Léveillé)

Published: 2026-10-20T00:00:00Z

Content type: release

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Post-quantum cryptography](<https://devfeed.tech/topics/post-quantum-cryptography.md>), [Passkeys](<https://devfeed.tech/topics/passkeys.md>), [Quantum Computing](<https://devfeed.tech/topics/quantum-computing.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [1Password](<https://devfeed.tech/topics/1password.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [cryptography](<https://devfeed.tech/tags/cryptography.md>), [data-breaches](<https://devfeed.tech/tags/data-breaches.md>), [error-correction](<https://devfeed.tech/tags/error-correction.md>), [ietf](<https://devfeed.tech/tags/ietf.md>), [ml-dsa](<https://devfeed.tech/tags/ml-dsa.md>), [news](<https://devfeed.tech/tags/news.md>), [nist](<https://devfeed.tech/tags/nist.md>), [passkeys](<https://devfeed.tech/tags/passkeys.md>), [passwordless](<https://devfeed.tech/tags/passwordless.md>), [phishing](<https://devfeed.tech/tags/phishing.md>), [post-quantum](<https://devfeed.tech/tags/post-quantum.md>), [post-quantum-cryptography-pqc](<https://devfeed.tech/tags/post-quantum-cryptography-pqc.md>), [pqc-migration](<https://devfeed.tech/tags/pqc-migration.md>), [quantum](<https://devfeed.tech/tags/quantum.md>), [quantum-computer](<https://devfeed.tech/tags/quantum-computer.md>), [quantum-computers](<https://devfeed.tech/tags/quantum-computers.md>), [qubits](<https://devfeed.tech/tags/qubits.md>), [research](<https://devfeed.tech/tags/research.md>), [rfc](<https://devfeed.tech/tags/rfc.md>), [risk](<https://devfeed.tech/tags/risk.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

1Password says version 8.12.44 adds support for ML-DSA post-quantum passkeys as a precaution, citing research that lowered estimated requirements to break elliptic-curve signatures from about 13 million to 26,000 physical qubits; the article says the largest quantum computer then had 6,100. Existing passkeys remain safe because no cryptographically relevant quantum computer exists. ML-DSA keys will be created only for websites that support the algorithm. Users can try registration at webauthn.io, but creating ML-DSA passkeys is not yet supported on iOS or through the native macOS autofill extension; authentication works on supported platforms. 1Password says it is working with W3C and FIDO Alliance on seamless updates to existing passkeys.

### Source excerpt

Passkeys make authentication safer by resisting phishing attacks and eliminating shared secrets like passwords that attackers can steal from a website to access your accounts. By removing the secrets from servers, they reduce the risk of data breaches. However, advances in quantum computing threaten to increase the risk of those data breaches yet again by breaking the cryptography passkeys currently use. As another step in our Post-Quantum Cryptography (PQC) migration, 1Password is adding support for ML-DSA passkeys in order to preserve their benefits over the long term. By supporting this algorithm early, we signal websites to start supporting ML-DSA passkeys. This helps protect our customers' credentials against future attackers. Why now? We've talked about quantum computers and passkeys before, back in 2023 to be precise. Back then, a Cryptographically Relevant Quantum Computer (CRQC) seemed far off, so why are we rolling out quantum-safe passkeys only three years later? Well, because things changed and research has accelerated. We've been closely monitoring the research to ensure we act well ahead of any concerning developments. Back in 2023, governments were mandating a migration to PQC algorithms by 2035, and the estimated amount of qubits estimated to be required to break elliptic curve digital signatures was around 13 million physical qubits. Now, in 2026, improvements in error correction and recent research reduce that estimate to only 26,000 physical qubits. This is still far from the latest largest quantum computer at 6,100 physical qubits, though the gap has shrunk enough for us to start migrating. NIST standardized the post-quantum safe signature algorithm, ML-DSA, in 2024. The IETF standardized ML-DSA's encoding in COSE in RFC 9964 in May of 2026. COSE is the format that WebAuthn/CTAP2 uses to transfer the passkey back to the website. This means that the stage is set for ML-DSA passkey adoption. Given all these advances and 1Password's ongoing PQC migr

## A path to user verification in 1Password

DevFeed: [A path to user verification in 1Password](<https://devfeed.tech/articles/a-path-to-user-verification-in-1password-90221.md>)

Original publisher: [Read original article](<https://1password.com/blog/user-verification-passkeys>)

Author: info@1password.com (Daryl Martin)

Published: 2026-10-19T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Passkeys](<https://devfeed.tech/topics/passkeys.md>), [1Password](<https://devfeed.tech/topics/1password.md>), [Firefox extension](<https://devfeed.tech/topics/firefox-extension.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [browser](<https://devfeed.tech/tags/browser.md>), [building-1password](<https://devfeed.tech/tags/building-1password.md>), [passkeys](<https://devfeed.tech/tags/passkeys.md>), [security](<https://devfeed.tech/tags/security.md>), [shared-responsibility](<https://devfeed.tech/tags/shared-responsibility.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

1Password explains how its mobile and desktop apps now prompt for local user verification during passkey flows when a website requires it. It also proposes a browser.secureCache WebExtensions API to support platform backed credentials and native verification in extension only setups, where extensions lack a standard way to call native APIs directly.

### Source excerpt

At 1Password, we believe strong security should feel like part of the workflow, not an interruption. That is the goal behind our work on user verification (UV) for passkeys. UV is a local identity check a website can require as part of a passkey action, to confirm the person approving the action is the person authorized to do so. This decision belongs to the website, not 1Password, as the site will validate UV occurred before accepting the operation. A useful analogy is paying with a bank card. For some transactions, tapping the card is enough. For higher-risk transactions, the terminal asks for a PIN. The card shows the credential is present, and the PIN adds confidence that the authorized cardholder is using it. Passkeys have a similar distinction; when stronger assurance is needed, UV asks for a fingerprint, face scan, device PIN, or password. If someone can add or use a passkey without proving they are authorized, a hijacked browser interaction or temporary access to an unlocked session could become lasting account access. Imagine someone steals your bank card and tries to buy a new TV. In that moment, you want the terminal to ask for a PIN. UV plays the same role for passkeys, ensuring high-impact operations are approved by the right person, not whoever has the computer. Not every passkey flow needs UV, but when a website requests it, we want the experience to be as seamless as possible. The website has the context to decide when stronger assurance is needed, and 1Password's role is to honor that request and ensure the local verification check is completed. Protecting the user is a shared responsibility between the website and client. User verification for passkeys is now available for mobile and desktop applications As of August 27th, our mobile and desktop apps have prompted for UV whenever a passkey flow requires it. In these supported flows, 1Password can call the native APIs provided by the operating system to trigger a familiar platform prompt, such as bi

## 5 signs that standing privileges are putting systems at risk

DevFeed: [5 signs that standing privileges are putting systems at risk](<https://devfeed.tech/articles/5-signs-that-standing-privileges-are-putting-systems-at-risk-90220.md>)

Original publisher: [Read original article](<https://1password.com/blog/signs-standing-privilege-risk>)

Author: info@1password.com (Gabriel Avner)

Published: 2026-10-19T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [principle of ephemerality](<https://devfeed.tech/topics/principle-of-ephemerality.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>)

Tags: [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [saas](<https://devfeed.tech/tags/saas.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>), [tips-advice](<https://devfeed.tech/tags/tips-advice.md>), [unified-access](<https://devfeed.tech/tags/unified-access.md>)

### AI overview

The article identifies five signs of standing privilege risk: excess administrators, long-lived credentials, permissions broader than actual use, sensitive actions with too little friction, and limited visibility into access. It describes zero standing privileges as a way to replace permanent access with temporary, task-scoped, auditable elevation, and presents 1Password Privileged Access as a product for implementing these controls.

### Source excerpt

In most organizations, standing privileges don't show up all at once. They accumulate quietly. A role is added "temporarily." A contractor needs broad access to finish a project. A service account gets oversized permissions because no one has time to fine-tune them. None of these choices seem harmful in the moment, but over time they build into a privilege surface that's far too large to monitor and far too easy to misuse. The challenge is that standing privileges often look harmless until something finally goes wrong. The indicators are visible long before the incident, but only if you know where to look. Top indicators of standing privileges Here are five of the clearest signs that your environment is carrying more access risk than it should. 1. You have more admins than your environment actually needs Admin creep happens naturally. In fast-moving environments, the easiest way to unblock a task is to give someone full access. It works, it's quick, and that access is rarely revisited. Multiply that across cloud accounts, SaaS tools, Kubernetes clusters, and databases, and you end up with dozens or even hundreds of identities that hold far more privilege than they need. The problem isn't just security. Admin sprawl amplifies operational fragility. A single mistake or a single malicious action can ripple far beyond its intended scope; the blast radius from an incident expands because privileges were broader than they needed to be. If you can't articulate why every admin in your environment truly needs that level of access, that's a strong indicator that standing privileges have taken root. 2. Long-lived keys and credentials are still everywhere API keys, service account tokens, SSH keys, and automation secrets are some of the easiest paths into a cloud environment. They're also some of the least governed. Many businesses have: Credentials that never expire Keys embedded in pipelines or code Secrets used across multiple systems, including by AI agents Tokens with full

## Detection engineering meets AI-driven adversary emulation

DevFeed: [Detection engineering meets AI-driven adversary emulation](<https://devfeed.tech/articles/detection-engineering-meets-ai-driven-adversary-emulation-87989.md>)

Original publisher: [Read original article](<https://1password.com/blog/ai-driven-adversary-emulation>)

Author: info@1password.com (Taiga Walker)

Published: 2026-10-15T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Detection engineering](<https://devfeed.tech/topics/detection-engineering.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Threat Research](<https://devfeed.tech/topics/threat-research.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ci](<https://devfeed.tech/tags/ci.md>), [detection](<https://devfeed.tech/tags/detection.md>), [detection-engineering](<https://devfeed.tech/tags/detection-engineering.md>), [emulation](<https://devfeed.tech/tags/emulation.md>), [security](<https://devfeed.tech/tags/security.md>), [software](<https://devfeed.tech/tags/software.md>), [software-engineering](<https://devfeed.tech/tags/software-engineering.md>)

### AI overview

The article describes a detection-as-code pipeline that tests security detections in CI by mapping each changed rule to an adversary technique, running that technique, and checking for its events in logs. It explains the distinction between technique-based validation and checks against existing logs, along with limitations such as skipped rule types, advisory failures, and the SaaS coverage gap.

### Source excerpt

In the first post in this series, Wade shared how our team laid the foundation for using AI in detection engineering. The short version is that an LLM doesn't know your stack. Without documentation and workflow context, it can produce plausible results that are difficult to trust, regardless of which model you use. That post closed with an instruction: Validate before you ship, because the output can look completely right and still be wrong. Every detection an agent writes still needs to go through the same review and testing as a human-written detection. Let's discuss that last part, because it's harder than it sounds. We'd built a detection-as-code pipeline, and we were proud of it. Rules live in a repository. Changes arrive as pull requests, and they get peer-reviewed, planned, and applied through CI. We had the structure of a software engineering team, and we tested queries against the logs we had. For everything else, we had never watched the detections fire. We shipped those because they looked right. Validating a detection without the logs in your environment means running the attack technique yourself and watching it fire. We didn't have time to do that manually for every rule, and we had no automated way to do it. So here's the question. How many of your deployed detections have you watched fire? Not reviewed - actually watched fire. You don't want to be answering that question the day an incident happens. Now that detections are code, they need to be tested like code. This post is about what it took to give our detections tests. An AI model did one job to make that possible, which is picking the attack technique to run against each detection. Why "it looks right" is not proof Before we get to the pipeline, it helps to see how a detection that looks right can still be broken. Reading a detection tells you what the query says, not what it actually does. It doesn't tell you whether the query matches any real logs, or whether the detection catches what you wro

## How attackers maintained persistence in AWS after stealing credentials

DevFeed: [How attackers maintained persistence in AWS after stealing credentials](<https://devfeed.tech/articles/how-attackers-maintained-persistence-in-aws-after-stealing-credentials-87045.md>)

Original publisher: [Read original article](<https://1password.com/blog/aws-credential-theft-persistence>)

Author: info@1password.com (Gabriel Avner)

Published: 2026-10-14T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>), [AWS IAM](<https://devfeed.tech/topics/aws-iam.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [aws inspector](<https://devfeed.tech/topics/aws-inspector.md>), [Amazon GuardDuty](<https://devfeed.tech/topics/amazon-guardduty.md>), [fake account fraud](<https://devfeed.tech/topics/fake-account-fraud.md>), [Nitro Isolation Engine](<https://devfeed.tech/topics/nitro-isolation-engine.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [ai](<https://devfeed.tech/tags/ai.md>), [aws](<https://devfeed.tech/tags/aws.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cyberattack](<https://devfeed.tech/tags/cyberattack.md>), [iam](<https://devfeed.tech/tags/iam.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [security](<https://devfeed.tech/tags/security.md>), [zero-standing-privilege](<https://devfeed.tech/tags/zero-standing-privilege.md>)

### AI overview

The article describes an AWS cryptomining campaign in which attackers used stolen IAM credentials to provision EC2 and ECS resources, create roles, and make instances harder to terminate. It recommends Zero Standing Privilege controls such as temporary, task-scoped access and presents 1Password Privileged Access as a way to implement them.

### Source excerpt

In the cloud, attackers don't need to break in. They just need a working set of keys. Several AWS customers learned this the hard way when threat actors used compromised IAM credentials to deploy a rapid cryptomining campaign across EC2 and ECS environments. The incident didn't rely on vulnerabilities or sophisticated exploitation; it simply relied on valid credentials and overly permissive access. Below is a clear breakdown of what happened, what matters, and how organizations can strengthen their defenses using a Zero Standing Privilege (ZSP) approach. What happened during the AWS cyberattack When an attack of this scale occurs, it's important to understand how attackers gained access and what they did with it. How the attackers gained initial access According to reporting from Dark Reading, as well as AWS's own analysis, attackers used stolen IAM credentials to authenticate into customer environments and immediately begin provisioning cryptomining workloads. The campaign was active across multiple AWS customers, who were directly notified. AWS also confirmed this was not the result of a flaw in its infrastructure. The privileges attached to the compromised identity permitted every action the attackers took. Once inside, the attackers: Targeted EC2 and ECS resources to spin up mining infrastructure Used automation to deploy workloads within about 10 minutes of initial access Leveraged AWS APIs to create new roles, extending their control Enabled persistence by modifying instance attributes to make resources harder to terminate This combination of legitimate access and rapid provisioning made the campaign highly effective and very difficult to stop in its early stages. For full details, you can read the AWS security blog here. How the attackers stayed in control After gaining access, the attackers created two new IAM roles using the victim's own permissions to achieve their goals and persistence: A service-linked role for Auto Scaling groups A Lambda execution role

## Niantic Spatial CEO on bringing AI into the physical world

DevFeed: [Niantic Spatial CEO on bringing AI into the physical world](<https://devfeed.tech/articles/niantic-spatial-ceo-on-bringing-ai-into-the-physical-world-65642.md>)

Original publisher: [Read original article](<https://1password.com/blog/physical-ai-authority-model>)

Author: info@1password.com (Chris Fowler)

Published: 2026-10-06T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Physical AI](<https://devfeed.tech/topics/physical-ai.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [World models](<https://devfeed.tech/topics/world-models.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [developers](<https://devfeed.tech/tags/developers.md>), [podcasts](<https://devfeed.tech/tags/podcasts.md>)

### AI overview

Niantic Spatial's leaders discuss how spatial representations help physical AI systems understand their environments and train before deployment. The article connects this grounding to production authentication, scoped agent permissions, ongoing evaluations, and continuous authorization as agent workflows change.

### Source excerpt

Zero-Shot Learning is a podcast about how AI is built, secured, and deployed. Hosted by Nancy Wang, 1Password CTO, and Dev Tagare, Senior Director of Engineering at Google Gemini, it offers a builder's view of the architecture and complex decisions involved in shipping AI. Niantic Spatial's CEO Inhi Cho Suh and Director of Product Management Eugene Chong joinedZero-Shot Learning to explore why spatial understanding is essential for AI systems operating in the physical world and how a grounding layer can turn spatial data into something models can use. Niantic Spatial builds real-world foundation models for physical AI. Before joining the company, Inhi spent over two decades at IBM and later led product and technology at DocuSign. Her career has focused on turning emerging technical capabilities into products and platforms others can build on. Their conversation raises a practical question for anyone building agents that can act in the world. What does an agent know about the environment it operates in, and what should it be authorized to access or do? From spatial representation to production identity Physical details are rarely part of the context supplied to a language model, but they determine whether a physical system can navigate and act safely. A language model can tell you that an office contains desks and chairs but to move them safely through a space, a robot needs to know where those objects are, how much space surrounds them, and potentially how much they weigh. This is the kind of physical context Niantic Spatial builds into systems operating in the real world. In the interview, Eugene described a project with Flexion, a robotics company developing general-purpose robot intelligence. From a ten minute, 360-degree video, Niantic Spatial reconstructed an office setting to give Flexion a metric-scale environment where it could train a policy before deploying the robot in the physical space. As the grounding layer for world models, Niantic Spatial provides p

## 1Password named a leader in the GigaOm Radar for Enterprise Password Management

DevFeed: [1Password named a leader in the GigaOm Radar for Enterprise Password Management](<https://devfeed.tech/articles/1password-named-a-leader-in-the-gigaom-radar-for-enterprise-password-management-65296.md>)

Original publisher: [Read original article](<https://1password.com/blog/gigaom-radar-for-enterprise-password-management>)

Author: info@1password.com (Rachel Sudbeck)

Published: 2026-10-06T00:00:00Z

Content type: news

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [1Password](<https://devfeed.tech/topics/1password.md>), [Secrets Management](<https://devfeed.tech/topics/secrets-management.md>), [HashiCorp Vault](<https://devfeed.tech/topics/hashicorp-vault.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [OpenAPI Specification](<https://devfeed.tech/topics/openapi.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [breach](<https://devfeed.tech/tags/breach.md>), [gigaom-radar](<https://devfeed.tech/tags/gigaom-radar.md>), [news](<https://devfeed.tech/tags/news.md>), [passwordless](<https://devfeed.tech/tags/passwordless.md>), [secrets-management](<https://devfeed.tech/tags/secrets-management.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

The article announces that GigaOm named 1Password a Leader and Disruptive Pioneer in its Enterprise Password Management Radar, marking the fifth consecutive year as a leader. It describes the report's evaluation of 23 vendors, including developer secrets management, API and identity integrations, and credential governance for AI agents and other non-human identities.

### Source excerpt

Identity and access have changed drastically in the past decade. To meet the needs of the modern enterprise perimeter, Enterprise Password Managers (EPM) have evolved far beyond traditional workplace password storage. The GigaOm Radar: Enterprise Password Management charts this evolution of the category. As the report states, "...evaluation now turns on what surrounds the vault: passwordless login paths, machine and AI-agent credential delivery, breach intelligence, and the administrative machinery to govern all of it at scale." As such, it's an honor to announce that GigaOm Radar positions 1Password as a Leader and Disruptive Pioneer among Enterprise Password Management platforms. This is the fifth year running that 1Password has been named a leader in EPM. Read on to learn more about the Radar's analysis and criteria for EPM platforms, and how 1Password's solutions are built to manage the complex access needs of modern companies. Why GigaOm declared 1Password a leader in Enterprise Password Management GigaOm's report analyzes 23 EPM vendors according to how well they meet essential enterprise password management requirements, such as strong cryptography and the ability to manage developer secrets. It also analyzes emerging critical capabilities within enterprise password management, such as managing credential and secrets access for AI agents. The report calls attention to how EPM platforms serve various security and management needs across the "Tech Buying Triad" of CIOs, CTOs, and CISOs. Across the core capabilities for these buyers, 1Password EPM ranked highly on several distinct criteria. These include, among others: Browser and application coverage Developer API ecosystem Identity integration extensibility Passwordless and passkey support Secrets management integration Compliance certifications Vault cryptography architecture 1Password's strength is depth on two axes, developer tooling and identity integration. The developer surface carries published OpenAPI

## 1Password SaaS Manager releases read-only AI assistant for SaaS reports

DevFeed: [1Password SaaS Manager releases read-only AI assistant for SaaS reports](<https://devfeed.tech/articles/stop-digging-just-ask-get-renewal-ready-ai-and-saas-reports-in-seconds-61921.md>)

Original publisher: [Read original article](<https://1password.com/blog/ai-and-saas-reports-in-seconds>)

Author: info@1password.com (Evan Sandhu)

Published: 2026-09-29T00:00:00Z

Content type: release

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [SaaS Management](<https://devfeed.tech/topics/saas-management.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [soc 2](<https://devfeed.tech/topics/soc-2.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [news](<https://devfeed.tech/tags/news.md>), [saas](<https://devfeed.tech/tags/saas.md>), [saas-management](<https://devfeed.tech/tags/saas-management.md>), [security](<https://devfeed.tech/tags/security.md>), [security-and-privacy](<https://devfeed.tech/tags/security-and-privacy.md>)

### AI overview

1Password announces general availability of an AI assistant in SaaS Manager. Users can ask questions in plain language and receive answers based on their SaaS data, with links to filtered views. The post also describes security and privacy controls; the assistant's tools are read-only.

### Source excerpt

The information you need before a renewal meeting usually exists in SaaS Manager. Getting to it is another matter, because you have to know which report holds it, how to filter it, and whether the results actually answer the question you were asked. For an IT admin who works in the product daily, that's a minor detour. For a colleague in finance who opens SaaS Manager a few times a quarter, it can be the reason the question goes back to IT instead. Today, we're announcing the general availability of an AI assistant in 1Password SaaS Manager. You can ask about your SaaS and AI environment in your own words and get a written answer based on your SaaS Manager data, along with a link to the relevant view with filters already applied. The practical effect is that finding an answer depends on knowing what you want to ask rather than knowing your way around the product, which matters as more finance and technology leaders get involved in decisions about software and AI spend. The assistant is included with existing SaaS Manager plans at no additional cost. Opening that door raised a second set of questions for us. An assistant that can retrieve information about your applications and access needs clear limits on what it can reach and what should happen when someone tries to push it past those limits. We wanted customers to understand those decisions as clearly as they understand the feature itself, so this post covers both what the assistant helps you do and how we built its security and privacy controls. Ask about your SaaS environment in your own words Suppose you're reviewing applications that may need closer attention because of their cost or access risk. You can ask: "Which apps have spend over $100,000, high access risk, and no owner?" The assistant provides a written answer based on your SaaS Manager data with a link to the relevant view, with filters and sorting already applied. You can then examine the underlying records and continue your review in the product. If

## Secure agent access in development workflows with 1Password + NVIDIA OpenShell

DevFeed: [Secure agent access in development workflows with 1Password + NVIDIA OpenShell](<https://devfeed.tech/articles/secure-agent-access-in-development-workflows-with-1password-nvidia-openshell-60731.md>)

Original publisher: [Read original article](<https://1password.com/blog/1password-nvidia-openshell>)

Author: info@1password.com (Clara Yeung and KC Li)

Published: 2026-09-28T00:00:00Z

Content type: release

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [OpenShell](<https://devfeed.tech/topics/openshell.md>), [1Password](<https://devfeed.tech/topics/1password.md>), [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-security](<https://devfeed.tech/tags/agent-security.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [ai](<https://devfeed.tech/tags/ai.md>), [developers](<https://devfeed.tech/tags/developers.md>), [news](<https://devfeed.tech/tags/news.md>), [partners](<https://devfeed.tech/tags/partners.md>), [secrets-management](<https://devfeed.tech/tags/secrets-management.md>), [security](<https://devfeed.tech/tags/security.md>), [unified-access](<https://devfeed.tech/tags/unified-access.md>)

### AI overview

1Password for NVIDIA OpenShell is available as a developer preview in the 1Password nightly build. It connects a 1Password Environment to the OpenShell runtime so agents can access approved systems without exposing credential values to the model. The article describes scoped, time-limited access for agent workflows.

### Source excerpt

null 1Password for NVIDIA OpenShell is available now as a developer preview in the [1Password nightly build](https://support.1password.com/betas). Connect a 1Password Environment to the OpenShell runtime and let your agents work with the systems it needs without exposing real credentials to the model. Set up the integration 65% of developers say they're expected or encouraged to use AI agents, but only 33% say they have a highly secure way to do so, according to 1Password's 2026 Developer survey. Developers are leveraging coding agents to handle more of software development, including code debugging, development, documentation, and architecture. In fact, 91% of developers are either using agents today or expect to within the next two years. The problem with agent credentials Agentic workflows introduce a fundamental security challenge: credentials. An agent needs access to repositories, APIs, and internal services. A long-lived secret gives an agent a broader and longer-lived path than a single task requires, but keeping every credential away from the agent prevents it from completing useful work. Developers need a controlled path between those two extremes. The better approach is to make the credential available to the agent only where it is approved and for as long as it's needed, without exposing the credential values in the agent's context. That is the problem 1Password for NVIDIA OpenShell is designed to solve. How 1Password + NVIDIA enable developer velocity and agent security NVIDIA OpenShell -- part of NVIDIA Open Agent Security Platform -- is an open, secure runtime for autonomous fleets of agents. It governs how agents execute, what they can see and do, and where inference is routed. Its controls are enforced outside the agent, so the agent cannot change the rules that govern its own access. 1Password for NVIDIA OpenShell extends 1Password's secrets management workflow to agents. Developers have a secure path to adopt agentic workflows to automate repetitive

## Building Customer Success for what's next at 1Password

DevFeed: [Building Customer Success for what's next at 1Password](<https://devfeed.tech/articles/building-customer-success-for-what-s-next-at-1password-55184.md>)

Original publisher: [Read original article](<https://1password.com/blog/building-customer-success-for-whats-next-at-1password>)

Author: info@1password.com (Audrey Weber)

Published: 2026-09-18T00:00:00Z

Content type: opinion

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Automation](<https://devfeed.tech/topics/automation.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [1password](<https://devfeed.tech/tags/1password.md>), [ai](<https://devfeed.tech/tags/ai.md>), [automation](<https://devfeed.tech/tags/automation.md>), [building-1password](<https://devfeed.tech/tags/building-1password.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [culture](<https://devfeed.tech/tags/culture.md>), [identity-security](<https://devfeed.tech/tags/identity-security.md>), [life-at-1password](<https://devfeed.tech/tags/life-at-1password.md>), [upskilling](<https://devfeed.tech/tags/upskilling.md>)

### AI overview

A 1Password customer success leader describes how the team is evolving through automation, AI fluency, product and industry expertise, and a focus on customer value. The article also outlines the culture and skills sought as the team grows.

### Source excerpt

Hi! I'm Audrey Weber, Senior Director of Customer Success (CS) at 1Password. If you're considering your next step in Customer Success, I'd love to share what we're building at 1Password, how the work is changing, and why it matters to the future of identity security. How we're evolving Customer Success We win when our customers win, and that's at the core of our CS mission. As our customers' needs evolve, we're growing the team and the systems that support our work, investing in automation, and helping our people deepen their product and industry expertise. Helping customers move forward with confidence AI is changing the way work happens; that shift requires us to understand what matters to CISOs and security leaders today and how those priorities are connected to our product offerings. This is where Customer Success becomes a value advisor. We're focused on upskilling our team, helping them help our customers grow and get the most out of their investment in 1Password. We show up with consistency, clarity, and trust, building long-term relationships that create a stronger foundation for the work ahead. Using AI to create better customer experiences We're investing in a culture of AI fluency that enables our team to focus on the work that matters most. In practice, that means we're "automating the predictable and humanizing the meaningful," a phrase my colleague coined. As AI shapes our industry and the way we work, our success motions continue to be built with humans at the center. We're focused on making it easier for customers to reach their goals, curating experiences that drive value for them wherever they are in their journey, and giving our team the tools and development opportunities to do great work. Growing a team that learns and wins together Our culture is grounded in collaboration, transparency, innovation, and a shared focus on results. We win together, and when something doesn't work, we learn and adjust. Everything we do is designed to build trust an

## Chainguard's CTO on why every build needs an identity

DevFeed: [Chainguard's CTO on why every build needs an identity](<https://devfeed.tech/articles/chainguard-s-cto-on-why-every-build-needs-an-identity-58066.md>)

Original publisher: [Read original article](<https://1password.com/blog/software-supply-chain-identity-security>)

Author: info@1password.com (Chris Fowler)

Published: 2026-09-08T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [supply-chain-security](<https://devfeed.tech/topics/supply-chain-security.md>), [open-source-security](<https://devfeed.tech/topics/open-source-security.md>), [Security](<https://devfeed.tech/topics/security.md>), [Risk](<https://devfeed.tech/topics/risk.md>), [.env](<https://devfeed.tech/topics/dotenv.md>)

Tags: [access-controls](<https://devfeed.tech/tags/access-controls.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [cto](<https://devfeed.tech/tags/cto.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [developers](<https://devfeed.tech/tags/developers.md>), [open-source-security](<https://devfeed.tech/tags/open-source-security.md>), [podcasts](<https://devfeed.tech/tags/podcasts.md>), [security](<https://devfeed.tech/tags/security.md>), [software-supply-chain-security](<https://devfeed.tech/tags/software-supply-chain-security.md>)

### AI overview

A podcast discussion with Chainguard CTO Matt Moore examines how software supply chain security intersects with identity and scoped access. It covers risks from open-source dependencies, base images, stolen credentials, and AI coding agents, and argues that teams should verify what enters a build, who changed it, and which credentials workflows can access.

### Source excerpt

How build identity and scoped access secure software Zero-Shot Learning is a podcast about how AI is built, secured, and deployed. Hosted by Nancy Wang, 1Password CTO, and Dev Tagare, Senior Director of Engineering at Google Gemini, it offers a builder's view of the architecture and complex decisions involved in shipping AI. Matt Moore, co-founder and CTO of Chainguard, joined the podcast to discuss the overlap between open-source software supply chain security and identity and access controls. Modern applications depend on open-source packages, base images, and tools that most teams don't maintain internally. When one of those dependencies is vulnerable, compromised, or published using stolen credentials, the compromise can move through the build and into software that reaches production. As AI coding agents gain authority, they introduce a new layer of uncertainty to the software development lifecycle. Matt argued that before shipping, teams need to know what enters a build, who or what changed it, and which credentials the workflow can access. Most of what you ship is inherited Developing with open-source projects includes known security risks. For teams working under time constraints, open-source projects provide packages, runtimes, tools, and the images they need to build applications and jumpstart a build, but those components also become part of the software an organization must inventory and update. Across industries, open-source software is a critical building block of the software supply chain. Black Duck's 2026 Open Source Security and Risk Analysis Report found open-source components in 98% of the 947 audited codebases it analyzed. The amount of software that we actually write to ship modern applications is this tiny tip of the iceberg, compared to what we're actually running in our environments." -Matt Moore, co-founder and CTO, Chainguard To help developers make safe choices, many organizations create approved package lists, internal registries, depend

## 1Password signs OpenAI open letter calling for collective action on cyber defense

DevFeed: [1Password signs OpenAI open letter calling for collective action on cyber defense](<https://devfeed.tech/articles/1password-signs-openai-open-letter-calling-for-collective-action-on-cyber-defense-1944.md>)

Original publisher: [Read original article](<https://1password.com/blog/openai-open-letter-cyber-defense>)

Author: info@1password.com (1Password)

Published: 2026-08-28T00:00:00Z

Content type: opinion

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [cursor](<https://devfeed.tech/topics/cursor.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [audit-trail](<https://devfeed.tech/tags/audit-trail.md>), [aws](<https://devfeed.tech/tags/aws.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [codex](<https://devfeed.tech/tags/codex.md>), [collective](<https://devfeed.tech/tags/collective.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [identity](<https://devfeed.tech/tags/identity.md>), [openai](<https://devfeed.tech/tags/openai.md>), [security](<https://devfeed.tech/tags/security.md>), [unified-access](<https://devfeed.tech/tags/unified-access.md>)

### AI overview

1Password supports OpenAI's call for collective cyber defense, arguing that AI agents need least-privilege access, traceable identities, clear boundaries, and audit trails.

### Source excerpt

As AI moves from answering questions to taking actions, the ecosystem around it will determine whether organizations can use it safely and with confidence. OpenAI's open letter on collective cyber defense warns that defenders have a limited window to strengthen security. It urges organizations to fix their highest-risk weaknesses, build least privilege and strong access controls, verify fixes, and make agentic identities traceable and accountable. The real work is building the ecosystem that lets them act safely and earn trust in production. That is why we continue working with OpenAI on trusted access for people and their agents. 1Password integrations with OpenAI, Codex, Anthropic Claude Code, Cursor, Kiro, Perplexity, and AWS Secrets Manager extend trusted access across development and cloud workflows. People should give agents access to key systems without exposing underlying credentials to the AI model. Cyber defense is a leadership responsibility. AI changes who and what can act inside the most sensitive systems, so identity security can no longer stop at human login. OpenAI is right to call for urgency, coordination, and fixes that organizations can verify without disrupting essential services. The standard is simple: every agent needs an identity, a boundary, and an audit trail." -Nancy Wang, Chief Technology Officer, 1Password Status quo security won't be enough Every security organization balances known weaknesses, technical debt, and limited time. The challenge for CISOs is deciding where to focus first and finding controls that reduce risk across the environment where AI is changing who and what can act inside an organization. Agents that work across browsers, repositories, terminals, cloud infrastructure, and production systems create a security challenge that begins before they take action. Standing access gives an agent more authority than a specific task requires and keeps it available after the task ends. If the agent is compromised or follows untru

## How to start the AI-accelerated defense

DevFeed: [How to start the AI-accelerated defense](<https://devfeed.tech/articles/how-to-start-the-ai-accelerated-defense-1898.md>)

Original publisher: [Read original article](<https://1password.com/blog/ai-assisted-detection-engineering>)

Author: info@1password.com (Wade Wells)

Published: 2026-08-27T00:00:00Z

Content type: article

Language: en

Sources: [1Password](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Detection engineering](<https://devfeed.tech/topics/detection-engineering.md>), [Prompt Engineering](<https://devfeed.tech/topics/prompt-engineering.md>), [Large Language Model](<https://devfeed.tech/topics/llm.md>), [log management](<https://devfeed.tech/topics/log-management.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [documentation](<https://devfeed.tech/tags/documentation.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [llm](<https://devfeed.tech/tags/llm.md>), [logging](<https://devfeed.tech/tags/logging.md>), [onboarding](<https://devfeed.tech/tags/onboarding.md>), [security](<https://devfeed.tech/tags/security.md>), [validation](<https://devfeed.tech/tags/validation.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

This article explains how a security team began adopting AI for detection engineering by supplying the documentation and workflow context that AI systems lack. It covers an AI Detection Engineering stack involving logging pipelines, log onboarding, detection validation, threat modeling, and detection logic, and shows why better context produces more reliable results than relying on prompts or increasingly powerful models.

### Source excerpt

Early on in the AI adoption boom, I gained a reputation for just throwing everything at it to see what would stick. That wasn't the most effective strategy, and my token usage was crazy high. There are a ton of talks and posts on all the cool ways you can use AI for detection engineering, but I didn't see any that showed you where to begin. So, this isn't another blog about why you need to use AI in your defensive workflows. It seems most people understand why we need that. My focus is to show how our team got started and realized that providing AI with the necessary context is key to detection engineering successfully adopting AI. This is not just about building detection logic, but that is one of the goals. This foundation helps create the AI Detection Engineering stack: logging pipelines, log onboarding, detection validation, threat modeling, and more. An LLM does not know your stack, so out of the box it has limited value in a security review. In our experience, reliable results depend less on the fanciest model and more on the documentation and context around the workflow. If a human reads your log inventory and still has to ask three people what the ingestion method is, your agent does too. Why cold prompting fails When we first started using AI tooling, we realized prompts alone could get stuff done, but the output was inconsistent. Fields were missed, assumptions were made, and some detection logic was wrong. We saw it write queries that would not work in our SIEM. Usually these were around wildcards. The playbooks it wrote were generic, the tuning was poor, and some detections were just bad. With enough re-prompting, the output would improve, but it always required some massaging. The effort invested in the agent inputs had a noticeable impact on the quality of the outputs. TL;DR: garbage in, garbage out. Where our context came from At the start, this was just internal documentation we built to make our own lives easier. It started with new-hire materials a

[Next page](<https://devfeed.tech/sources/blog-on-1password-blog.md?cursor=WyIyMDI2LTA4LTI3VDAwOjAwOjAwKzAwOjAwIiwgImJiZWNmOTBiLTdiNWMtNDlhZS1iZjY2LWY0M2IzNjg5YWQ4MSJd>)