IPsec SPI Privacy Protection via Data Plane Management

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing IPsec protocols face vulnerabilities in SPI management, particularly in scenarios where SPI updates are observed by passive attackers, potentially revealing session tracking information.

Innovation Solution

A method is introduced where a receiving node manages a plurality of stored SPI values associated with a Security Association (SA), including current, next, and previous SPI values, to handle SPI updates without relying on control plane traffic, thus enhancing security by masking SPI renewal processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If SPI updates are performed via IKEv2 control plane mechanism, then SPI can be updated securely, but control plane traffic can be observed by passive attackers revealing session tracking information

Engineering Contradiction:

ImproveSPI update securityVSAvoidpassive attack observation

Core Design Contradiction:

ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the SPI management function from the control plane (IKEv2) and implements it independently in the data plane. Each node maintains its own SPI update logic and state, allowing SPI changes to occur without control plane involvement, thus preventing passive attackers from observing control plane traffic to infer session information.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent enables nodes to autonomously update their own SPI values using local algorithms and stored parameters. Each node independently generates new SPI values and updates its Security Association without requiring IKEv2 negotiations, making the SPI update process self-contained and invisible to external observers.

Inventive Principle:

Principle #25Self-service

2Device complexity

If a single SPI value is used per Security Association, then packet identification is simple, but SPI updates create detectable patterns for attackers

Engineering Contradiction:

ImproveSPI management simplicityVSAvoidsession tracking vulnerability

Core Design Contradiction:

Device complexityVSObject-affected harmful factors

Solution Approach 1:

The patent pre-generates multiple SPI values and stores them locally at each node before they are needed. When an SPI update is required, the node simply switches to using a pre-computed SPI value from its local storage, eliminating the need for real-time generation or control plane coordination during the update process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent changes the SPI parameter dynamically by switching between multiple pre-stored SPI values associated with the same Security Association. This allows the SPI to change over time without altering the underlying SA or requiring control plane intervention, making updates imperceptible to passive attackers.

Inventive Principle:

Principle #35Parameter changes

Data Source

PatentUS12301545B2IPsec privacy protection

Publication Date: 2025.05.13 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

Systems and methods for maintaining privacy of security protocol parameters are provided. A node receives an encrypted packet and determines if the Security Parameters Index (SPI) value has been updated. The node can modify its stored SPI value(s) accordingly and process the encrypted packet.