For CISOs · security, infosec, AppSec, AI security

Runtime accountability, without replacing IAM.

KYE Protocol™ sits on top of your existing IAM, OAuth, API gateway, workflow, SIEM, GRC and AI-agent stack — it adds a delegated-authority and Evidence Pack™ layer, never replaces what the security team already runs.

KYE Runtime Console™ — your view

What KYE™ refuses (or admits) on your watch.

A 3-row preview of the canonical 6-row PDP state grid, filtered to policy = blocked OR delegation = invalid — the action classes that matter to ciso. The full grid (Authority · Scope · Delegation · Policy · Decision · Evidence) renders at /runtime-console.html with a live synthetic stream.

sample filter: policy = blocked OR delegation = invalid
CheckStateDetail
Authority verified OAuth chain resolves; rotated key admitted
Delegation invalid sub-delegate signed with key revoked at 03:14 UTC — lateral-movement attempt
Decision deny refused; SIEM event emitted alongside signed refusal envelope

monitor_heart See the full Runtime Console →

Full reference index — every page tagged for ciso (307) ↓
Derived from the graph

307 pages tagged for ciso.

This page is a derived view over internal. Adding or retagging a page rebuilds this landing on the next CI run — no hand-curated list to maintain.

Evaluate

Evaluate — 220 pages

Decide whether KYE Protocol™ is the right rail for the problem in front of you.

Operate

Operate — 4 pages

Run KYE Protocol™ in production — deploy, govern, observe, recover.

Audit

Audit — 6 pages

Audit a KYE™-governed system in days, not months — signed evidence, public-key verifiable.

Build

Build — 6 pages

Build against the rail — SDKs, agents, conformance pack, sandbox.

Learn

Learn — 30 pages

Learn the rail — glossary, frameworks, frameworks-explained.

Reference

Reference — 41 pages

Look up the canonical definition — schemas, dictionaries, ID format.

Ready to evaluate KYE Protocol™?

Start in shadow mode. We’ll deliver your first Evidence Pack™ in 4–8 weeks.