{"slug": "after-the-harvest-find-and-secure-developer-secrets-without-slowing-developers", "title": "After the harvest: Find and secure developer secrets without slowing developers down", "summary": "1Password launched Developer Watchtower and 1Password Environments to find plaintext developer credentials, including .env files and SSH keys, on local devices and move them into 1Password vaults, citing GitGuardian's 2026 State of Secrets Sprawl report that found 28.65 million new secrets in public GitHub commits in 2025, up 34% year over year, with leaked secrets for AI services up 81% in a single year. Developer Watchtower alerts developers when the 1Password desktop app detects credentials in a local .env file and offers a one-click import into 1Password Environments, while a new local disk exposure report lets admins see which users and devices are affected without viewing the secret itself. 1Password Environments, built into the desktop app, stores API keys, access tokens, database passwords, cloud credentials and environment variables and supplies them to apps on request instead of leaving plaintext secrets on disk.", "body_md": "In our first post on [__credential harvesting__](https://1password.com/blog/ai-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.\n\nFinding 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](https://1password.com/features/developer-watchtower) and [__1Password Environments__](https://www.1password.dev/environments) help teams find, replace, and manage developer secrets.\n\nFor 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.\n\nThat habit feeds secret sprawl, and the numbers are moving the wrong way. GitGuardian's [__2026 State of Secrets Sprawl__](https://www.gitguardian.com/state-of-secrets-sprawl-report-2026) 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.\n\nFor 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.\n\nThat 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.\n\n**Developer Watchtower** finds plaintext developer credentials on local devices, including .env files, and guides users to import them into 1Password\n\n**Developer credential visibility for admins** adds reporting and remediation workflows so that security teams can see credential risk across the organization\n\n**1Password Environments** gives developers a secure place to store, share, and use the secrets behind apps, services, automations, and AI-assisted workflows\n\nTogether, they give developers a safer way to use the credentials their work depends on, and give security teams the visibility and control to act before those credentials spread.\n\nDeveloper Watchtower already identified plaintext SSH keys on a developer's device. It now also covers .env files, one of the most common places secrets end up during local development.\n\nWhen the 1Password desktop app finds credentials in a local .env file, the developer gets an alert explaining the risk and offering a one-click import into 1Password Environments. The alert lets the user know which secrets may be exposed and makes it easy to move the secret into a secure 1Password vault.\n\nFor security teams, credentials that were invisible on local devices become something you can manage, share, govern, and remediate. Admins get a new report, local disk exposure, showing the plaintext .env files and SSH keys the desktop app found on local disks. With Developer Watchtower, admins can see which users and devices are affected without seeing the secret itself. That keeps the underlying value from being exposed and lets developers replace the credential without breaking the workflow.\n\n1Password Environments is built into the desktop app. It gives developers a familiar place to store API keys, access tokens, database passwords, cloud credentials, and environment variables their apps need without leaving plaintext secrets in .env files or anywhere else on disk. Instead of reading from a file, the app requests its variables when it needs them and 1Password supplies them. There is no standing .env file for an attacker, or an AI tool with file access, to find. It keeps the one-click convenience that makes .env files appealing, backed by 1Password's security.\n\nDevelopers don’t need to rebuild workflows to use managed secrets. With 1Password Environments you can:\n\nImport an existing .env file or add variables manually, organized by app, service, project, or stage\n\nUse the 1Password CLI and SDKs with the tools you already rely on, with local desktop authentication such as biometrics where available\n\nConnect service accounts to support automation\n\nUse supported AI coding workflows with managed secrets through 1Password's MCP Server, without copying secrets values into project files or pasting them into the model context\n\nFor Teams and Business customers, Environments fits into the access controls you already use in 1Password. You can share an environment with a group instead of adding people one at a time, while admins control whether Environments are available across the organization in the desktop app, CLI, and SDKs.\n\nTurn on Developer Watchtower and review the Local disk exposure report. Assume any credential it finds may have been exposed. Revoke or rotate it, then move the replacement into Environments so it doesn’t end up back in a plaintext file.\n\nThe aim is to make the secure path the fast path. With security built into the workflows developers use, the habits that created exposure can also be the ones that fix it.\n\nIf you already use 1Password, Developer Watchtower is available at no extra cost. [__Explore Developer Watchtower__](https://1password.com/features/developer-watchtower), or see how to set up these features in the [__1Password developer docs__](https://www.1password.dev/).\n\nFind plaintext secrets in .env files, secure them with 1Password Enterprise Password Manager, and keep using them as environment variables.\n\n1Password Developer Tools fit into local development, CI/CD, and AI-assisted coding tools teams already use. Find a simpler way to give apps and automation the credentials they need without copying secrets.", "url": "https://wpnews.pro/news/after-the-harvest-find-and-secure-developer-secrets-without-slowing-developers", "canonical_source": "https://1password.com/blog/secure-developer-secrets", "published_at": "2026-11-17 00:00:00+00:00", "updated_at": "2026-11-17 19:52:10.143628+00:00", "lang": "en", "topics": ["ai-tools", "ai-safety", "developer-tools"], "entities": ["1Password", "1Password Developer Watchtower", "1Password Environments", "GitGuardian", "GitHub"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/after-the-harvest-find-and-secure-developer-secrets-without-slowing-developers", "markdown": "https://wpnews.pro/news/after-the-harvest-find-and-secure-developer-secrets-without-slowing-developers.md", "text": "https://wpnews.pro/news/after-the-harvest-find-and-secure-developer-secrets-without-slowing-developers.txt", "jsonld": "https://wpnews.pro/news/after-the-harvest-find-and-secure-developer-secrets-without-slowing-developers.jsonld"}}