Entity-Based Trust Verification for Online Resources

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Domain-based trust mechanisms in online data processing are user-unfriendly and vulnerable to deception, as they rely on domain name binding, which can lead to confusion with similar domain names, and require separate certificates for each domain owned by an entity, necessitating new certificates for name changes or additions.

Innovation Solution

Implementing entity-based trust systems that use a certificate issuing/signing chain to determine the root CA associated with an entity, allowing for a single reputation score to establish trust across multiple resources, and utilizing a brand dossier to link and verify trustworthiness across different namespaces.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If domain-based trust mechanisms are used to establish security, then certificate validation can be performed, but users may be deceived by confusingly similar domain names

Engineering Contradiction:
Improvecertificate validation reliabilityVSAvoidphishing risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the trust verification process into two independent components: domain name verification and entity identity verification. By separating these functions, the system can validate certificates against domain names while simultaneously verifying the actual entity controlling the resource, preventing phishing attacks that exploit similar domain names.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary entity (the resource controller or entity owner) that acts as a mediator between the certificate authority and the end user. This intermediary provides additional verification layers beyond domain name binding, such as entity authentication and identity confirmation, thereby reducing phishing risks.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If separate certificates are issued for each domain name owned by an entity, then domain-specific trust can be established, but certificate management becomes complex

Engineering Contradiction:
Improvedomain-specific trustVSAvoidcertificate management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent merges multiple domain-specific certificates under a single entity-level trust framework. Instead of managing separate certificates for each domain name, the system consolidates trust verification at the entity level, allowing one certificate or trust anchor to validate multiple domain names controlled by the same entity.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates a universal entity-level trust mechanism that serves multiple functions: it validates certificates across different domain names, simplifies certificate management, and maintains domain-specific trust relationships. This multi-functional approach eliminates the need for separate certificate management for each domain.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If domain name binding is used for certificate issuance, then trust can be established for specific domains, but trust cannot be transferred to other domains owned by the same entity

Engineering Contradiction:
Improvedomain binding trustVSAvoidcross-domain trust
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent adds a new dimension to trust verification by introducing entity-level identity as an additional layer beyond domain name binding. This dimensional expansion allows trust to be established not only at the domain level but also at the entity level, enabling cross-domain trust for all domains controlled by the same verified entity.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The patent effectively copies the trust relationship from domain-specific certificates to entity-level verification. By verifying the entity's identity and control over multiple domains, the system replicates trust across different domain names, allowing a single verification to validate multiple domains without requiring separate domain-specific trust establishment.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9282092B1Systems and methods for determining trust when interacting with online resources
Publication Date: 2016.03.08 GOOGLE LLC
  • US9282092B1 patent drawing
  • US9282092B1 patent drawing
  • US9282092B1 patent drawing

AI summary

Systems and methods for determining trust when interacting with online resources are described, including requesting a secure connection with an online resource; receiving a certificate from the online resource, wherein the certificate is signed by a chain of at least one certificate authority (CA) with the last CA in the chain being a root CA; determining that the root CA is an entity root CA without determining whether the root CA is a third-party root CA, wherein the entity root CA is associated with an entity certificate issued to an entity and the entity is associated with a score; determining whether the score is equal to or greater than a threshold; and, if the score is equal to or greater than the threshold, establishing the secure connection with the online resource.