---
title: "Tag: Ivanti Connect Secure"
description: "1 blog entry tagged Ivanti Connect Secure, newest first, each with published and updated dates."
url: https://policycortex.com/blog/tags/ivanti-connect-secure
sealed: 2026-10-22
amended: 2026-10-22
register: blog/tags/ivanti-connect-secure
records: 3
digest: sha3:328f9185d971447fdaa729afb0e32f2b7ee5ceab67d9dea17bcf1d1a4f34202c
---

# Blog entries tagged Ivanti Connect Secure

Resources / Blog / Tag: Ivanti Connect Secure

Every blog entry tagged Ivanti Connect Secure, 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-22

## Entries, newest first

| Published | Entry | Reading |
|---|---|---|
| 2026-10-22 | [Two Exploited Flaws, One Short Clock: Windows and Ivanti on the KEV List](https://policycortex.com/blog/windows-ivanti-kev-zero-days-governance): CISA added a Windows Shell command injection flaw and an Ivanti Connect Secure login bypass to the KEV list on October 13, 2026. | 5 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 | 5093f29d0c23 | 40eb10688ce1 |
| REC 0001 | ENTRIES | a46f3255e3f4 | 5093f29d0c23 |
| REC 0002 | RELATED RECORDS | 328f9185d971 | a46f3255e3f4 |

Head sha3:328f9185d971447fdaa729afb0e32f2b7ee5ceab67d9dea17bcf1d1a4f34202c. 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.