Join our Newsletter — 33% off our NHI Course
Home› Glossary› Governance, Ownership & Risk› Supply in Request
Governance, Ownership & Risk

Supply in Request

← Back to Glossary
By NHI Mgmt Group Updated November 5, 2026 Domain: Governance, Ownership & Risk

Supply in Request is a certificate template setting that allows the requester to provide subject information during enrollment. In AD CS, this can be dangerous if combined with weak access controls or misconfigured issuance rules, because it may let an attacker shape a certificate for unauthorized authentication purposes.

How Supply in Request Works

Supply in Request is a certificate template setting that shifts part of the enrollment workflow to the requester, allowing subject details to be entered during request time rather than relying entirely on pre-populated template data. In AD CS, that flexibility can be useful for delegated enrollment, but it also changes who influences certificate contents.

The key point is that a certificate is only as trustworthy as the identity data bound into it. When requesters can supply subject information, the template can become a control point for certificate integrity, not just a convenience setting.

Why It Matters in AD CS

In a healthy PKI design, certificate subject information should be tightly governed so the certificate represents the intended person, device, or service. Supply in Request weakens that assumption if enrollment permissions, template security, or issuance policy are loose, because the requester may influence names, subject alternative names, or other identity attributes that downstream relying parties trust.

That is why the setting is often discussed alongside template permissions and issuance requirements. A certificate with attacker-shaped identity data can still be cryptographically valid, which makes the mistake more dangerous than a simple configuration typo. The problem is trust abuse, not just misformatting.

For background on the control landscape around certificate and account security, the broader NIST SP 800-53 Rev 5 Security and Privacy Controls set is useful because it connects identification, authentication, access restriction, and auditability to certificate-related risk.

How Misuse Creates Security Exposure

Supply in Request becomes hazardous when an attacker can request a certificate that authenticates as someone else, or as a privileged service, by supplying a subject name or other identity field that the environment later accepts. In that case, the certificate can be used for impersonation, unauthorized access, or trust chain abuse.

The exposure is especially serious when certificate-based authentication is trusted by SSO, VPN, smart card logon, or service-to-service access paths. If the wrong identity is embedded at issuance time, the resulting certificate may function as a durable access token with a long lifetime and broad reuse potential.

That is why certificate template governance and privilege boundaries matter more than the setting itself. The configuration is not inherently unsafe, but it becomes risky when the enrollment path, subject naming rules, and authorization checks do not line up.

What Good Governance Looks Like

Operationally, teams should treat the setting as a policy decision, not a default convenience. If requesters are allowed to provide subject data, the environment needs a clear rule for who can enroll, what fields may be supplied, and which issuance paths are allowed to produce authentication-bearing certificates.

Template review should also consider whether requester-supplied values are validated against authoritative identity sources, whether certificate request permissions are narrow enough, and whether high-impact templates are separated from general enrollment workflows. The safer the certificate will be used for authentication, the tighter the issuance rule should be.

For a practical control lens, the NIST Cybersecurity Framework 2.0 helps frame this as a governance, protection, and detection problem rather than a single certificate option. It is also useful to map certificate handling to access control and identity controls when reviewing AD CS exposure.

The strongest rule of thumb is simple: if the certificate can be used to prove identity, then anything that lets the requester shape that identity should be tightly constrained and routinely reviewed.

Detection and Remediation Priorities

If the setting is already enabled, review whether any issued templates allow requester-controlled subject data to influence authentication or other privileged trust decisions. Look for unusual enrollment patterns, unexpected subject values, and certificates whose identity fields do not match approved naming conventions or authoritative records.

Remediation usually means tightening template permissions, restricting who can enroll, reducing subject-supply flexibility where it is not needed, and checking whether any issued certificates must be revoked and reissued under corrected controls. Where certificate-based access has already been granted, the response should include a post-issuance trust review, not just a configuration fix.

For environment-level validation, the NIST Cybersecurity Framework 2.0 and the NIST SP 800-53 Rev 5 Security and Privacy Controls both support the basic discipline of inventory, access limitation, and monitoring around issuance systems.

Risk and Threat Considerations

When requester-supplied subject data is accepted without strong validation, the main risk is certificate misuse for impersonation or unauthorized authentication. The danger is not theoretical, because a valid certificate can still bind the wrong identity if the issuance path is permissive enough.

Failure mechanism: An attacker abuses weak template permissions or loose issuance rules to shape certificate subject data, then uses the resulting certificate to authenticate as a different user, device, or service.

Impact: The attacker may gain durable access, bypass normal password or MFA expectations, or establish a trusted foothold that is harder to spot than a conventional account compromise.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 provides the primary governance reference for this term.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-2 — Identification and Authentication (Organizational Users)Certificate-based login depends on strong user authentication and controlled identity binding.
IA-9 — Identification and Authentication (Non-Organizational Users)Externally managed or delegated certificate identities need controlled authentication boundaries.
AC-6 — Least PrivilegeTemplate enrollment and subject control should be limited to only the required users and roles.
Recommendation — Bind certificate issuance to authoritative identity checks before allowing authentication use. Restrict externally managed certificate issuance to approved trust and authentication paths. Limit template permissions so requesters can only submit the minimum identity data needed.

Practitioner Guidance

Governance implication: Treat this setting as an exception path that needs ownership, approval, and periodic review. If it is necessary for business enrollment, document why subject-supplied data is allowed and what validation protects it.

What to watch for: Any template that combines requester-controlled subject fields with authentication use cases deserves tighter scrutiny than a normal enrollment template, especially when the resulting certificate can be reused broadly across systems.

Practitioner takeaway: If the certificate will be trusted for login or service authentication, minimise requester control over the identity it carries.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on November 5, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org