> 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.md).

# Security

A capability-level security model for the physical-to-digital trust boundary.

PoWV applies a defense-in-depth philosophy to the physical-to-digital boundary. The public model begins from a simple assumption: devices, networks, operators, organizations, and software can fail or be manipulated.

![PoWV public security model](https://1151534167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWO75canbSRCuzukBrP8n%2Fuploads%2FJYhmNKpmM8HTsrCF07yP%2Fsecurity-model.svg?alt=media)

## Public security objectives

| Threat class                    | Security objective                                           |
| ------------------------------- | ------------------------------------------------------------ |
| Source substitution             | Preserve confidence in the origin and context of a claim     |
| Record tampering                | Make unauthorized modification detectable                    |
| Duplicate or conflicting claims | Expose reuse, repetition, or inconsistency                   |
| Custody discontinuity           | Maintain reviewable continuity across handoffs               |
| Connectivity failure            | Preserve evidence for controlled recovery and reconciliation |
| Insider manipulation            | Avoid dependence on a single unreviewable authority          |

## Security is an assurance argument

PoWV does not describe security as one algorithm, device, or network. Security is the combined argument that:

* the source context is defensible;
* evidence integrity can be assessed;
* conflicting claims can be surfaced;
* exceptions remain reviewable;
* authorized parties can evaluate the basis of a decision.

## Explore security

* [Threat Model](/powv-protocol-docs/security/threat-model.md)
* [Disclosure Boundary](/powv-protocol-docs/security/disclosure-boundary.md)

Security reports: **<powv.protocol@proton.me>**


---

# 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.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.