UIAO
  • Home
  • Getting started
    • 10-minute quickstart
    • Adapter authoring tutorial (30 min)
    • Substrate status
  • Findings
  • Academy
  • Modernization
  • Customer Documents

UIAO — Unified Identity-Addressing-Overlay Architecture

A universal governance substrate for identity, addressing, and overlay networks.

Universal Enterprise · Open Architecture · Zero Trust

Identity is the root namespace.

UIAO is a universal governance substrate that unifies identity, addressing, and overlay networks across federal, regulated, and commercial enterprises — without rip-and-replace.

Explore the Repo Architecture Overview
⬡Zero Trust ⬡SSOT Architecture ⬡Drift Detection ⬡FedRAMP 20x ⬡NIST CSF 2.0 ⬡TIC 3.0 ⬡NIST 800-63 ⬡AD → Entra ID ⬡Six Control Planes ⬡FIMF Adapter Registry ⬡Zero Trust ⬡SSOT Architecture ⬡Drift Detection ⬡FedRAMP 20x ⬡NIST CSF 2.0 ⬡TIC 3.0 ⬡NIST 800-63 ⬡AD → Entra ID ⬡Six Control Planes ⬡FIMF Adapter Registry

Three Pillars

Governance, Compliance, and Modernization — unified.

UIAO ships as a single substrate that delivers all three. No per-vertical product split. Federal compliance is one mode of operation; commercial, hybrid, and multi-cloud are first-class targets.

Governance

Canon as the source of truth.

A protected corpus of authoritative schemas, registries, and policies. Every governance claim traces to a certificate-anchored origin. No backfilling, no orphan claims.

Governance canon
Compliance

Continuous evidence, not quarterly attestation.

163 cryptographically-signed Key Security Indicators. OSCAL-native SSPs. Drift detection across schema, semantic, provenance, authorization, and identity classes — with SLA-enforced remediation.

Compliance pillar
Modernization

Migration without rip-and-replace.

Vendor-neutral adapters for AD → Entra ID, PKI, RADIUS, DNS/DHCP/IPAM, and overlay fabric. Every step is incremental, reversible, and evidence-driven — across heterogeneous directory and network stacks.

Modernization program

The Problem

Enterprise identity, addressing, and policy don't talk.

Directory migrations, network modernizations, and compliance programs each solve a slice of the problem in isolation. The seams between them are where evidence vanishes, drift accumulates, and audits fail. UIAO unifies those slices under a single architectural substrate.

  • DNS / DHCP / IPAM fragmentation and SSOT failures
  • GPO, SPN, and service-account blind spots during AD → Entra ID migrations
  • Telemetry gaps that block Zero Trust, TIC 3.0, and FedRAMP 20x posture
  • PKI, RADIUS / NPS, and LDAP-dependent apps left outside migration scope
  • No vendor-neutral governance layer across heterogeneous directory and network stacks

Understanding UIAO

What UIAO actually is.

UIAO is not a dashboard, a monitoring tool, or a consulting engagement. It is a governance transformation platform — a universal substrate that unifies identity, addressing, and overlay network governance under a single architectural model. Every governance claim in UIAO traces to a cryptographically-anchored origin. No backfilling. No orphan assertions. No "we'll fix it in the audit."

The thesis is straightforward: Active Directory was never just an identity store. For twenty-five years, AD silently governed DNS resolution, DHCP scoping, certificate issuance, network segmentation, application authentication, Group Policy enforcement, and service account lifecycles. When organizations migrate to Entra ID, they move the identity — but leave behind the governance surface that AD provided. The result is an invisible crisis: eleven categories of hidden dependencies that break silently across security, compliance, and operations.

UIAO exists to solve that crisis. It maps every hidden AD dependency, builds a vendor-neutral adapter layer across heterogeneous infrastructure, and delivers continuous, evidence-driven governance — not quarterly attestation artifacts. The platform operates alongside existing infrastructure with no rip-and-replace requirement, enabling incremental, reversible, and auditable modernization at every step.

The Root Cause

Eleven hidden dependencies that break when AD goes away.

Every enterprise migrating from Active Directory to Entra ID faces the same invisible problem. These eleven dependency categories silently govern your infrastructure — and none of them migrate automatically.

# Dependency Category What Breaks
D-01 Group Policy Objects (GPO) Security baselines, drive maps, login scripts, software deployment
D-02 DNS / DHCP / IPAM Name resolution, scope assignment, IP address management integrity
D-03 Service Principal Names (SPN) Kerberos delegation, SQL auth, IIS app pools, clustered services
D-04 Certificate Authority / PKI Auto-enrollment, certificate templates, OCSP, CRL distribution
D-05 RADIUS / NPS Network access control, 802.1X, VPN authentication
D-06 LDAP-Bound Applications Legacy apps using LDAP bind for authentication and authorization
D-07 Service Accounts Unmanaged credentials, password rotation, privilege escalation paths
D-08 OU-Based Delegation Administrative boundaries, RBAC models, help desk permissions
D-09 Trust Relationships Cross-forest authentication, resource access, SID history
D-10 Schema Extensions Custom attributes, third-party integrations, directory-dependent workflows
D-11 Site Topology / Replication DC placement, replication boundaries, subnet-to-site mappings

The Journey

Six phases from legacy to continuous governance.

UIAO guides organizations through a structured modernization arc — each phase is incremental, reversible, and evidence-driven.

00
Discovery
Map every AD dependency, hidden governance surface, and implicit trust relationship
01
Foundation
Stand up the platform substrate, adapter registry, and canon governance layer
02
Ingestion
Connect legacy systems via FIMF adapters; ingest current-state telemetry
03
Transformation
Apply identity, policy, and network transforms with drift detection at every step
04
Validation
Run validation suites against target state; produce compliance evidence artifacts
05
Governance
Continuous monitoring, drift remediation, and evidence-driven compliance posture

Deep Dive

Read the full story.

These four documents tell the complete UIAO narrative — from the problem statement through the architecture and into operational governance.

Executive Brief
UIAO Executive Brief
The authoritative overview: what UIAO is, what problem it solves, and how the governance substrate works.
Architecture Series
Client-Server to Hybrid-Cloud
The 11-chapter series covering the full transformation arc from legacy AD to cloud-native governance.
Architecture
AODIM Architecture
The Attribute-Oriented Dynamic Identity Model — UIAO's approach to identity as governance surface.
Whitepaper
AD to Entra ID: The Migration Problem
Why every AD migration is a governance migration in disguise, and what organizations miss.

Architecture

Eight Core Concepts.

UIAO's architecture is expressed through eight foundational concepts spanning the full lifecycle of enterprise identity, addressing, overlay, and governance.

01
Identity as Root Namespace
Every entity — user, device, service, workload — is anchored to a governed identity before any other attribute is assigned.
02
Unified Addressing
DNS, DHCP, and IPAM are treated as a single coordinated plane, not independent silos. SSOT is non-negotiable.
03
Overlay Governance
Network overlays are policy-governed surfaces, not infrastructure afterthoughts. Every segment carries identity context.
04
DRIFT Modules
Composable governance modules that encode authoritative rules for drift detection, authorization, and remediation.
05
FIMF Adapter Registry
A vendor-neutral interface layer. InfoBlox, BlueCat, and any directory or network system registers as an adapter.
06
No Rip-and-Replace
UIAO operates alongside existing infrastructure. Migration is incremental, reversible, and evidence-driven at every step.
07
Evidence-Driven Compliance
Compliance posture is computed continuously from live telemetry — not asserted at audit time. Zero Trust as a runtime property.
08
Universal Enterprise Scope
Designed for any enterprise. Federal compliance is one vertical. Commercial, hybrid, and multi-cloud are first-class targets.

Control Planes

Six planes. One coherent architecture.

UIAO separates concerns across six distinct control planes, each with its own governance surface and adapter interface — enabling independent evolution without architectural coupling.

Identity Control Plane — root namespace governance
Addressing Control Plane — DNS · DHCP · IPAM
Overlay Control Plane — network fabric governance
Authorization Control Plane — policy enforcement
Telemetry Control Plane — observability and drift detection
Migration Control Plane — AD · Entra · PKI · RADIUS

Compliance Alignment

Built for the standards that matter — federal and commercial.

UIAO produces continuous, machine-readable compliance evidence across the federal mandates that define government posture and the commercial frameworks that govern regulated enterprise.

Zero Trust
CISA Zero Trust Maturity
TIC 3.0
NIST 800-63
FedRAMP 20x
GCC Moderate
M-22-09
CMMC
NIST CSF 2.0
ISO 27001
SOC 2
HIPAA
PCI DSS
OSCAL

Open Source · Active Development

Start with the architecture. Build toward governance.

The UIAO canon, DRIFT modules, adapter specifications, and governance tooling are all maintained in the open. Contributions and collaboration welcome.

Explore on GitHub 10-Minute Quickstart
Back to top

UIAO is under active development (v0.4.0). Much of this site describes target architecture — the canon is authoritative, but many components are not yet implemented, integrated, or operationally tested at scale. Do not treat statements on this site as representations of current production capability without checking the Substrate Status page for per-component adoption state. Pages describing capabilities that are canonically declared but not yet fully adopted carry an additional Aspirational callout at the top.