---
title: "Tag: Veeam"
description: "1 blog entry tagged Veeam, newest first, each with published and updated dates."
url: https://policycortex.com/blog/tags/veeam
sealed: 2026-10-29
amended: 2026-10-29
register: blog/tags/veeam
records: 3
digest: sha3:13542bc09e107298c51ac096a016b673d29071012e09de84ef531e9c6e73bed5
---

# Blog entries tagged Veeam

Resources / Blog / Tag: Veeam

Every blog entry tagged Veeam, newest first. Tags group the blog by subject so a reader working one requirement can follow it across entries as the rules change. Each entry shows when it was published and last updated; every entry is listed on the blog index.

1 entry · Last published 2026-10-29

## Entries, newest first

| Published | Entry | Reading |
|---|---|---|
| 2026-10-29 | [Veeam Backup Flaw Lets an Attacker Bypass Authorization](https://policycortex.com/blog/veeam-cdp-coordinator-authorization-bypass): Veeam fixes a 9.1 authorization bypass in Backup and Replication 13. | 4 min |

## Related records

Guides and articles describe the work. The evidence that work produces is described in three proof pages and one architecture page.

- **proof.state**: [Proof of State](https://policycortex.com/proof/state). What the environment was, as of a date someone else picks: point-in-time records, content hashed and chained.
- **proof.change**: [Proof of Change](https://policycortex.com/proof/change). Who or what altered the environment, under what authority, with before and after state hashes.
- **proof.agency**: [Proof of Agency](https://policycortex.com/proof/agency). What a machine was permitted to do before it acted, what it did, and what would have stopped it.
- **architecture**: [Architecture](https://policycortex.com/architecture). How the chain is built and where it lives: inside your tenant, with no egress of evidence.

Read the entries. Then verify the record they describe. [Request Access](https://app.policycortex.com/auth?mode=request-access) · [Book a call](https://policycortex.com/book)

## Register colophon

| Seq | Label | SHA3-256 | Prev |
|---|---|---|---|
| REC 0000 | HEAD | 98a236edefc7 | 65ad7d4d6aee |
| REC 0001 | ENTRIES | 856a9df97658 | 98a236edefc7 |
| REC 0002 | RELATED RECORDS | 13542bc09e10 | 856a9df97658 |

Head sha3:13542bc09e107298c51ac096a016b673d29071012e09de84ef531e9c6e73bed5. Each digest is SHA3-256 over the previous digest, the register key, the record label, and the record copy; a second party can recompute it from this document.