Credential Whitelist Validation for Data Exfiltration Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Data exfiltration poses a significant security risk in business environments that rely on third-party code for functionality, as malicious code can be used to transfer data unauthorizedly to external storage services, which may go unnoticed if the service is also used for legitimate purposes.

Innovation Solution

Implementing a system where a storage service provider maintains a whitelist of credentials for each customer environment, validating digital signatures, and encrypting data with a customer-controlled cryptographic key to prevent unauthorized data transfers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If remote storage services are used for legitimate business purposes, then data accessibility and convenience are improved, but data exfiltration risk increases

Engineering Contradiction:
Improvedata accessibilityVSAvoiddata exfiltration risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The system performs preliminary actions by establishing credential whitelists and digital signature validation mechanisms before data access occurs. The service provider pre-configures which credentials are authorized to access which customer environments, and validates these credentials through digital signatures before allowing any data transfer operations.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The service provider acts as an intermediary between the customer environment and the storage service. It mediates all data access requests by validating credentials against whitelists and verifying digital signatures, thereby controlling and monitoring data flows to prevent exfiltration while allowing legitimate access.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If third party code is used for application functionality, then application versatility is improved, but security reliability deteriorates

Engineering Contradiction:
Improveapplication functionalityVSAvoidsecurity reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The system applies preliminary anti-action by implementing credential whitelisting and digital signature validation to prevent malicious third-party code from exfiltrating data. Before any data transfer can occur, the system checks whether the requesting credential is in the approved whitelist and whether its digital signature is valid, thereby blocking potential attacks in advance.

Inventive Principle:
Principle #9Preliminary anti-action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring and validating credentials against whitelists. When a data access request is made, the service provider checks the credential against the whitelist and validates its digital signature, providing immediate feedback by allowing or denying the operation based on security verification.

Inventive Principle:
Principle #23Feedback

3Difficulty of detecting and measuring

If data transfer monitoring is implemented to detect exfiltration, then detection capability is improved, but system complexity increases

Engineering Contradiction:
Improveexfiltration detection capabilityVSAvoidmonitoring system complexity
Core Design Contradiction:
Difficulty of detecting and measuringVSDevice complexity

Solution Approach 1:

Instead of monitoring data transfers after they occur, the system takes preliminary action by validating credentials before data access is granted. The credential whitelist and digital signature validation are established in advance, and all security decisions are made at the point of access request, eliminating the need for complex ongoing monitoring of data flows.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service security by having the service provider automatically validate credentials against whitelists and verify digital signatures without requiring external monitoring systems. The credential validation process is self-contained and automated, reducing the need for additional complex monitoring infrastructure.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10764294B1Data exfiltration control
Publication Date: 2020.09.01 AMAZON TECH INC
  • US10764294B1 patent drawing
  • US10764294B1 patent drawing
  • US10764294B1 patent drawing

AI summary

A service request and a credential are sent from a customer environment to a service provider. The service provider maintains information, such as a credential whitelist, that identifies which credentials may be used with each customer environment. The service provider identifies the particular customer environment from which the service request was submitted using the IP address of the requester (or other environment-identifying information), and retrieves information that restricts the use of the credentials. A request may be approved or rejected based on the presence of the associated credential in a whitelist notwithstanding whether the credential otherwise authorizes the service request. In some examples, the system is used to limit data exfiltration from a customer environment.