---
id: "hardman-what-does-telco-need-requirements-for-organizational"
type: "paper"
type_label: "Papers and paper collections"
title: "What Does Telco Need? Requirements for Organizational Identity Evidence"
maintainer: "Daniel Hardman"
authors:
  - "Daniel Hardman"
date: "2026-03-11"
year: 2026
reading_level: "practitioner"
reading_level_label: "Practitioner"
reading_level_meaning: "architects, product people and adopters who know identity systems"
evidence: "informative"
evidence_meaning: "an author's paper, deck, tutorial or post explaining the suite"
status: "quiet"
status_meaning: "no change in six to eighteen months; still correct"
access: "public"
access_meaning: "anyone with the link"
topics:
  - "theory"
  - "deployments"
roles:
  - "security-architect"
  - "infrastructure-operator"
  - "product"
  - "communications"
  - "investor"
  - "business-development"
  - "researcher"
source_url: "https://dhh1128.github.io/papers/telco-ev-reqs.html"
source_license: null
source_license_note: null
found_on: "hardman-papers"
kerisse_credit: false
abstract_license: "CC BY 4.0"
abstract_license_url: "https://creativecommons.org/licenses/by/4.0/"
abstract_attribution: "KSKB, the KERISuite Knowledge Base (https://kskb.dev/)"
last_checked: "2026-10-15"
kskb_url: "https://kskb.dev/cards/hardman-what-does-telco-need-requirements-for-organizational/"
kskb_app_url: "https://kskb.dev/#item/hardman-what-does-telco-need-requirements-for-organizational"
kskb_record_url: "https://kskb.dev/data/kskb/resources/hardman-what-does-telco-need-requirements-for-organizational"
kskb_markdown_url: "https://kskb.dev/export/cards/hardman-what-does-telco-need-requirements-for-organizational.md"
---

# What Does Telco Need? Requirements for Organizational Identity Evidence

A 2026 position paper by Daniel Hardman setting out requirements for an evidence layer for organizational identity, authority and accountability in telecommunications. It proposes five essential properties and an appendix of detailed requirements, non-goals and evaluation questions, as a fair test for candidate architectures rather than a comparison of them. For standards participants, operators and regulators evaluating proposals.

Labels: reading level Practitioner; evidence informative (an author's paper, deck, tutorial or post explaining the suite).
Source: https://dhh1128.github.io/papers/telco-ev-reqs.html (license not recorded).
The abstract is KSKB's own text under Creative Commons Attribution 4.0 (CC BY 4.0), https://creativecommons.org/licenses/by/4.0/; credit KSKB, the KERISuite Knowledge Base (https://kskb.dev/).