A domain portfolio is the full set of domains, subdomains, certificates, and related trust settings owned by an organisation. In practice, it should be managed as a governed asset set with assigned ownership, lifecycle tracking, and change control, not as a collection of isolated registrations.
Expanded Definition
A domain portfolio is the governed inventory of domains, subdomains, certificates, DNS records, and trust relationships that define an organisation’s external and internal presence. In NHI security, the portfolio matters because every domain can host identities, issue trust, route authentication traffic, or expose administration surfaces. Treating it as an asset set means assigning ownership, renewal responsibility, and change approval rather than leaving registrations dispersed across teams. That governance lens aligns with the NIST Cybersecurity Framework 2.0, which emphasises asset visibility, protection, and lifecycle control. Definitions vary across vendors on whether parked domains, vanity domains, and certificate-only assets belong in scope, so organisations should document inclusion criteria explicitly. A mature portfolio also tracks DNS delegation, certificate issuance paths, and registrar access because those links often outlive the original business purpose. The most common misapplication is treating domains as one-time purchases, which occurs when renewal, delegation, and certificate ownership are not mapped to accountable operators.
Examples and Use Cases
Implementing domain portfolio governance rigorously often introduces coordination overhead, requiring organisations to weigh faster local autonomy against reduced exposure and better traceability.
- A security team discovers a forgotten subdomain still points to a decommissioned cloud service, creating a takeover risk until the record is removed and ownership is reassigned.
- A certificate renewal calendar is tied to the portfolio so that expiring TLS assets cannot silently break service authentication or trigger emergency exceptions.
- During an NHI review, domain names are mapped to service accounts and API endpoints to confirm where tokens, federated trust, and callback URLs are actually used.
- A merger requires consolidating registrar accounts and DNS controls into a single governance model, reducing duplicated trust boundaries and inconsistent policy enforcement.
- The DeepSeek breach illustrates how exposed systems and poorly governed assets can combine into a larger trust failure when external-facing infrastructure is not tracked as a portfolio.
Why It Matters in NHI Security
Domain portfolio control is central to NHI security because domains anchor authentication flows, certificate trust, email identity, and many AI and API integration paths. If the portfolio is incomplete, defenders can miss shadow domains, abandoned subdomains, or stale certificates that attackers can exploit for phishing, impersonation, or trust-chain abuse. It also becomes harder to enforce zero standing privilege for registrar, DNS, and certificate authority access when ownership is unclear. NHIMG research shows how quickly attackers act when credentials are exposed: in the LLMjacking: How Attackers Hijack AI Using Compromised NHIs report, AWS credentials were attempted within an average of 17 minutes after public exposure. The same urgency applies to domain assets because a compromised registrar account or misissued certificate can redirect trust at scale. Organisations that ignore portfolio governance often discover the problem after a hijack, certificate outage, or phishing campaign, at which point domain portfolio management becomes operationally unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 address the attack and risk surface, while NIST CSF 2.0 and NIST Zero Trust (SP 800-207) set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-01 | Domain portfolios expose ownership, lifecycle, and trust gaps across NHI assets. |
| NIST CSF 2.0 | ID.AM | CSF asset management covers domain and certificate inventories needed for governance. |
| NIST Zero Trust (SP 800-207) | Zero Trust depends on trusted endpoints and strong control over domain-based access paths. |
Inventory domains and certificates, then assign owners and review change control continuously.
Related resources from NHI Mgmt Group
- Why do cross-domain attacks create more risk than single-domain intrusions?
- How should security teams build a cross-domain identity programme?
- How should security teams harden domain controllers that still need legacy authentication support?
- Why do domain controllers with NTLMv1 enabled increase domain compromise risk?
