Acceptance criteria
Identify installation and running process for tools such as Ollama or LM Studio.
Why it matters
Local models move data off the monitored path entirely.
How to verify
A local runtime installed on a pilot device is discovered and cataloged.
OWASP adoption context
Local runtimes are relevant to shadow use and code-agent workflows even when no traffic reaches a hosted model provider.
Framework mappings
Installed-versus-running local-runtime evidence supplies software-inventory and activity-monitoring inputs, including offline AI. Discovery alone neither maintains the inventory nor detects anomalies or controls installation. Finding a runtime does not establish prompt inspection.
Local-runtime discovery supplies control information about hidden software and access exposure. It does not itself restrict installation or access.
Identifying installed and running local model runtimes documents part of the AI tooling landscape. It does not establish computing capacity, resource adequacy or prompt-inspection coverage.