Multi-Factor Authentication for Domain Name Record Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current domain name registration systems lack effective security measures to ensure that only authorized parties can make changes to domain name records, as unauthorized entities can pose as registrants or registrars, leading to improper modifications.

Innovation Solution

Implementing a chain of trust using multi-factor authentication, such as One Time Passwords (OTPs), biometrics, and PKI technology, to verify the authenticity of requests to change domain name records, ensuring that any changes are properly authorized and authenticated through a system that binds authentication factors to EPP transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional single-factor authentication (passwords or digital certificates) is used for domain name registration, then the system is easy to operate, but security is insufficient against unauthorized entities posing as registrants or registrars

Engineering Contradiction:
ImprovesecurityVSAvoidauthentication complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication system is segmented into multiple independent factors (something you know, something you have, something you are). Each factor is verified separately through distinct mechanisms (password verification, token validation, biometric scanning), ensuring that compromise of one factor does not compromise overall security while maintaining operational clarity through modular verification steps.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A multi-factor authentication intermediary system is introduced between the registrant/registrar and the domain registration process. This intermediary verifies multiple authentication factors (passwords, tokens, biometrics) before granting access, acting as a security gatekeeper that enhances reliability without requiring the registrant to directly manage complex security protocols.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multi-factor authentication is implemented to verify registrant authorization, then security against unauthorized changes is improved, but the authentication process becomes more complex

Engineering Contradiction:
Improveauthorization verificationVSAvoidauthentication process
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

Authentication factors are verified in advance before the actual domain registration or modification operations occur. The system pre-validates passwords, issues authentication tokens, and performs biometric scans before allowing access to domain management functions, ensuring that authorization is confirmed beforehand and preventing unauthorized changes without requiring complex real-time verification during operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service authentication through user-friendly interfaces where registrants can independently complete multi-factor verification. Biometric scanners automatically capture and verify physiological data, authentication tokens are automatically validated, and the system guides users through the process without requiring manual security configuration, maintaining ease of operation while enhancing authorization verification.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8904519B2Shared registration system multi-factor authentication
Publication Date: 2014.12.02 VERISIGN INC
  • US8904519B2 patent drawing
  • US8904519B2 patent drawing
  • US8904519B2 patent drawing

AI summary

A system and method for establishing a chain of trust from a registrant to a registry. A registrant request to a registrar to change a domain name record includes at least one registrant factor, such as a one time password. The registrar can formulate an extended EPP command that includes the factor to effectuate the change and send it to a registry. The registry can verify the at least one factor using at least one validation server. If the factor is successfully verified, the EPP can be processed by the registry. If the factor is not verified, the EPP command may not be processed and an error message may be generated and sent to the registrar.