> For the complete documentation index, see [llms.txt](https://powv-protocol.gitbook.io/powv-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://powv-protocol.gitbook.io/powv-protocol-docs/security/threat-model.md).

# Threat Model

A public threat taxonomy for the physical-to-digital trust boundary.

The public threat model describes what the architecture must resist or make visible without disclosing how individual controls are implemented.

| Threat                    | Failure mode                                                            | Assurance response                                           |
| ------------------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------ |
| Source substitution       | Evidence is associated with the wrong asset, device, place, or operator | Strengthen provenance and contextual consistency             |
| Measurement manipulation  | A reported physical value does not reflect the relevant event           | Require corroboration appropriate to risk                    |
| Record alteration         | Evidence changes after origin without authorized trace                  | Make integrity failure detectable                            |
| Replay or duplicate claim | A prior event is reused as if it were new                               | Surface uniqueness conflicts                                 |
| Custody break             | Asset and evidence histories diverge during handoff                     | Preserve reviewable continuity                               |
| Context spoofing          | Time, location, identity, or operational context is misrepresented      | Evaluate cross-context consistency                           |
| Insider collusion         | Multiple accountable parties coordinate manipulation                    | Reduce dependence on one authority and preserve review paths |
| Connectivity disruption   | Evidence is delayed, fragmented, or lost                                | Support durable and controlled reconciliation                |
| Downstream misuse         | A valid assurance outcome is used outside its authorized purpose        | Enforce purpose and access governance                        |

## Residual risk

PoWV does not claim to eliminate physical-world risk. The objective is to reduce blind trust, increase the cost and visibility of manipulation, and provide a defensible basis for independent review.

## Out of public scope

Exact controls, trust anchors, algorithms, key-management design, firmware validation, anti-replay construction, thresholds, topology, and incident procedures remain restricted.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://powv-protocol.gitbook.io/powv-protocol-docs/security/threat-model.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.