A file-placement primitive is a weakness that lets attacker-controlled input influence where a system writes or stages files. It does not require code execution on its own, but it can poison caches, overwrite paths, or set up later compromise when privileged automation trusts the result.
Expanded Definition
A file-placement primitive is a pre-authentication or post-authentication weakness where attacker-controlled input influences a path, filename, directory, or staging location used by a system. The core issue is not code execution by itself, but control over where files land, move, or overwrite.
In NHI and agentic systems, this matters when automation writes tokens, cache artifacts, manifest files, model outputs, or task results to disk and then later trusts those files. The weakness can appear in upload handlers, export jobs, log rotation, package extraction, backup restores, or workflow engines that accept path-like values. Definitions vary across vendors, but the security implication is consistent: placement control becomes a trust boundary problem. For a standards-based control lens, NIST SP 800-53 Rev 5 Security and Privacy Controls is most relevant where systems must constrain file handling, integrity, and access boundaries.
The most common misapplication is treating it as a simple directory traversal issue, which occurs when teams miss the downstream impact of privileged automation acting on attacker-placed files.
Examples and Use Cases
Implementing file-placement controls rigorously often introduces friction in workflow design, because systems must balance flexible input handling against strict path validation, sandboxing, and deterministic storage rules.
- A CI/CD job accepts a filename from a pull request comment and writes build artifacts into a shared workspace, allowing a malicious path to overwrite a trusted configuration file.
- An agentic pipeline stages downloaded tool output into a cache directory, and a crafted path causes the cache to poison later runs that reuse the same working directory.
- A service account rotates secrets into files on disk, but the destination path is user-influenced, so an attacker redirects the write into a location that a privileged job later reads.
- A backup restore process expands archives into a target directory without strict normalization, letting an attacker place files where an administrative task will execute or ingest them.
- As documented in Ultimate Guide to NHIs, weak NHI hygiene often collides with poor file handling when credentials and automation artifacts are stored outside managed boundaries.
These patterns are commonly discussed alongside traversal and archive-extraction flaws, but the operational risk becomes higher when a privileged process later trusts the placed file. That is why NIST SP 800-53 Rev 5 Security and Privacy Controls emphasizes integrity and controlled execution paths around system-generated artifacts.
Why It Matters in NHI Security
File-placement primitives are especially dangerous in NHI environments because secrets, manifests, caches, and automation outputs often travel through unattended file workflows. If an attacker can steer where those files are written, they may not need direct credential theft to reach privilege escalation, persistence, or lateral movement.
This risk is amplified by the real-world state of NHI governance. NHI Management Group reports that only 5.7% of organisations have full visibility into their service accounts, while 96% store secrets outside secrets managers in vulnerable locations including code, config files, and CI/CD tools, as described in the Ultimate Guide to NHIs. Once file placement is attacker-influenced, those weak storage patterns become exploitation paths rather than just hygiene problems.
For threat modeling, this weakness should be mapped to path validation, workspace isolation, archive handling, and file integrity checks. It also aligns with NIST SP 800-53 Rev 5 Security and Privacy Controls expectations around controlled system operations and protected information flow. Organisations typically encounter the damage only after a privileged job consumes a planted file, at which point the file-placement primitive 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 OWASP Agentic AI Top 10 address the attack and risk surface, while NIST CSF 2.0, NIST SP 800-63 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-04 | File placement issues often lead to secret exposure, cache poisoning, and privileged workflow abuse. |
| NIST CSF 2.0 | PR.DS | Protects data at rest and during handling, which includes attacker-influenced file placement. |
| NIST SP 800-63 | Relevant when placed files contain authenticators, tokens, or recovery material. | |
| NIST Zero Trust (SP 800-207) | Zero Trust limits trust in files and paths created by untrusted or indirect sources. | |
| OWASP Agentic AI Top 10 | A-03 | Agent workflows can be steered through file writes, poisoning downstream tool use. |
Constrain file paths, isolate workspaces, and validate all staged artifacts before trusted use.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on August 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
