A managed way to deliver environment variables and other secrets to approved workflows without hardcoding them into files or repositories. It supports runtime access control, helping teams keep credentials out of source code while still making them available to approved applications and AI agents when needed.
Expanded Definition
1Password Environments are a controlled delivery pattern for secrets and environment variables that lets approved workflows retrieve credentials at runtime instead of storing them in source code, config files, or ad hoc pipelines. In NHI security, the distinction matters because the control is not only about where a secret lives, but also about which workload, agent, or pipeline run is allowed to receive it and under what conditions.
Usage in the industry is still evolving because different teams use the phrase to describe either a product feature, an operational pattern, or a broader secret distribution model. The security value comes from reducing static exposure while preserving automation for applications and AI agents that need access to APIs, databases, and internal services. That makes the concept closely related to secrets governance, runtime authorization, and least privilege in the NIST Cybersecurity Framework 2.0.
The most common misapplication is treating it as a secure substitute for secret governance, which occurs when teams move credentials out of code but fail to enforce scope, rotation, or workload-specific access.
Examples and Use Cases
Implementing 1Password Environments rigorously often introduces operational dependency on vault policy and workflow design, requiring organisations to weigh automation speed against tighter access controls and change management overhead.
- A CI/CD pipeline pulls database credentials at runtime for test, staging, and production jobs without embedding values in repository files.
- An AI agent is granted only the environment variables needed to call an internal API, while broader vault access remains blocked.
- A deployment workflow uses separate secret sets for development and production, reducing blast radius if a lower-trust environment is compromised.
- Security teams map environment-based delivery to a broader NHI program documented in the Ultimate Guide to NHIs, then validate that each workflow only receives the secrets it truly needs.
- Platform teams integrate runtime secret retrieval with policy checks inspired by NIST Cybersecurity Framework 2.0 to keep service access aligned with approved operational intent.
In practice, the term is most useful when a workflow needs temporary access to secrets but should never permanently own them.
Why It Matters in NHI Security
Secrets sprawl is a recurring NHI failure mode, and runtime delivery helps reduce the chance that credentials are copied into code, logs, images, or developer laptops. That matters because NHIMG reports that 96% of organisations store secrets outside of secrets managers in vulnerable locations, and 79% have experienced secrets leaks, with 77% of those incidents causing tangible damage, as detailed in the Ultimate Guide to NHIs.
For NHI governance, the key question is whether the environment mechanism is enforcing least privilege at the moment of use. If the answer is no, the organisation may still have secret exposure even when the credentials are no longer hardcoded. This is especially important for agentic workflows, where an AI agent can move quickly through tools and services if granted broad environment access. The concept should therefore be paired with rotation, short-lived access, and explicit workload identity controls.
Organisations typically encounter the operational cost of poor environment secret handling only after a leaked pipeline token, a compromised service account, or an exposed deployment artifact forces emergency credential revocation, at which point the delivery model becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and CSA MAESTRO address the attack and risk surface, while NIST CSF 2.0, NIST Zero Trust (SP 800-207) and NIST AI RMF set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-02 | Covers improper secret management, including exposed environment-delivered credentials. |
| NIST CSF 2.0 | PR.AC-4 | Addresses access permissions and least privilege for system and workload access. |
| NIST Zero Trust (SP 800-207) | AC-4 | Zero Trust requires decisions based on explicit authorization at the time of access. |
| CSA MAESTRO | IAM-01 | Agentic systems need controlled tool and secret access to prevent unsafe action chains. |
| NIST AI RMF | AI risk management includes constraining operational dependencies and access pathways. |
Deliver secrets only at runtime, scope access tightly, and remove hardcoded values from code and pipelines.
