# US 2012/0254997 A1 · Methods and apparatuses for avoiding damage in network attacks

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254997 A1
- Document ID: US20120254997A1
- Status: Published application
- Kind: A1
- Application number: 13/177,385
- Filed: 2011-07-06
- Published: 2012-10-04
- Earliest claimed: 2011-04-01
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Karl Norrman; John Mattsson; Vesa Petteri Lehtovirta; Oscar Ohlsson
- Web page: https://patentgrep.com/patent/US20120254997A1

## CPC

- H04L 63/14: {for detecting or protecting against malicious traffic}
- H04W 12/04: Key management, e.g. using generic bootstrapping architecture [GBA]
- H04W 12/0431: Key distribution or pre-distribution; Key agreement
- H04L 63/1466: {Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks}
- H04L 63/168: {above the transport layer}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066)
- H04L 2463/061: applying further key derivation, e.g. deriving traffic keys from a pair-wise master key
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Methods and apparatuses in a client terminal (400) and a web server (402) for enabling safe communication between said terminal and server. When the terminal obtains a web page from the server in a session, the terminal creates a context-specific key, Ks_NAF′, based on one or more context parameters, P1, . . . Pn, pertaining to said session and/or web page. The terminal then indicates the context-specific key in a login request to the server, and the server determines a context-specific key, Ks_NAF′, in the same manner to verify the client if the context-specific key determined in the web server matches the context-specific key received from the client terminal. The context-specific key is thus bound to and valid for the present context or session only and cannot be used in other contexts or sessions.

## Claims

### Claim 1

A method in a client terminal for enabling safe communication with a web server, the method comprising:
obtaining a web page from the web server in a session with the web server,
determining a set of context parameters pertaining to at least one of said session and said web page,
creating a context-specific key based on said context parameters, and
using the created context-specific key for verification of the client terminal in the web server if a context-specific key determined in the web server matches the context-specific key created by the client terminal.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the created context-specific key is indicated in a login request sent to the web server.

### Claim 3 (depends on 1)

The method according to claim 1, wherein said context parameters include at least one of: a path component of a Universal Resource Locator (URL) of said web page, a current HTTP session identity of said session, and a current Transport Layer Security (TLS)/Secure Socket Layer (SSL) session identity of said session.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the context-specific key is created by applying a predefined Key Derivation Function, KDF, to said context parameters, the Key Derivation Function being known to the web server.

### Claim 5 (depends on 4)

The method according to claim 4, wherein an aggregated parameter, S, is created based on the context parameters in a predetermined manner, and wherein the Key Derivation Function is applied using as input said aggregated parameter S and an application specific key, Ks_NAF, such that
Ks_NAF′=KDF(Ks_NAF, S(P1, . . . Pn)), where Ks_NAF′ is the created context-specific key and P1, . . . Pn is the set of context parameters.

### Claim 6 (depends on 5)

The method according to claim 5, wherein the application specific key Ks_NAF has been derived from a master key, Ks, obtained from a Bootstrapping Service Function, BSF.

### Claim 7 (depends on 1)

The method according to claim 1, wherein the context parameters are determined in communication with the web server having a Network Application Function, NAF.

### Claim 8

A client terminal configured to enable safe communication with a web server, the client terminal comprising:
a receiving module configured to obtain a web page from the web server in a session with the web server,
a key creating module configured to determine a set of context parameters pertaining to at least one of said session and said web page, and to create a context-specific key based on said context parameters, and
a sending module configured to send a login request indicating the created context-specific key to the web server, to enable verification of the client terminal if a context-specific key determined in the web server matches the context-specific key created by the client terminal.

### Claim 9 (depends on 8)

The client terminal according to claim 8, wherein the key creating module is further configured to create the context-specific key by applying a predefined Key Derivation Function, KDF, to said context parameters, the Key Derivation Function being known to the web server.

### Claim 10 (depends on 9)

The client terminal according to claim 9, wherein the key creating module is further configured to create an aggregated parameter, S, based on the context parameters in a predetermined manner, and the Key Derivation Function is applied using as input said aggregated parameter S and an application specific key, Ks_NAF, such that
Ks_NAF′=KDF(Ks_NAF, S(P1, . . . Pn)), where Ks_NAF′ is the created context-specific key and P1, . . . Pn is the set of context parameters.

### Claim 11 (depends on 8)

The client terminal according to claim 8, wherein the key creating module is further configured to determine the context parameters in communication with the web server having a Network Application Function, NAF.

### Claim 12

A method in a web server for enabling safe communication with a client terminal, the method comprising:
sending a web page to the client terminal in a session with the client terminal,
receiving a login request from the client terminal indicating a context-specific key created by the client terminal,
determining a set of context parameters pertaining to at least one of said session and said web page,
determining a context-specific key based on said context parameters, and
verifying the client terminal if the context-specific key determined in the web server matches the context-specific key created by the client terminal.

### Claim 13 (depends on 12)

The method according to claim 12, wherein said context parameters include at least one of: a path component of a Universal Resource Locator (URL) of said web page, a current HTTP session identity of said session, and a current Transport Layer Security (TLS)/Secure Socket Layer (SSL) session identity of said session.

### Claim 14 (depends on 12)

The method according to claim 12, wherein the context-specific key is created by applying a predefined Key Derivation Function, KDF, to said context parameters, the Key Derivation Function being known to the client terminal.

### Claim 15 (depends on 14)

The method according to claim 14, wherein an aggregated parameter, S, is created based on the context parameters in a predetermined manner, and the Key Derivation Function is applied using as input said aggregated parameter S and an application specific key, Ks_NAF, such that
Ks_NAF′=KDF(Ks_NAF, S(P1, . . . Pn)), where Ks_NAF′ is the created context-specific key and P1, . . . Pn is the set of context parameters.

### Claim 16 (depends on 15)

The method according to claim 15, wherein the application specific key Ks_NAF is obtained from a Bootstrapping Service Function, BSF, associated with the client terminal.

### Claim 17

A web server configured to enable safe communication with a client terminal, the web server comprising:
a sending module configured to send a web page to the client terminal in a session with the client terminal,
a receiving module configured to receive a login request from the client terminal indicating a context-specific key created by the client terminal, and
a verification module configured to determine a set of context parameters pertaining to at least one of said session and said web page, to determine a context-specific key based on said context parameters, and to verify the client if the context-specific key determined in the web server matches the context-specific key created by the client terminal.

### Claim 18 (depends on 17)

The web server according to claim 17, wherein the verification module is further configured to create the context-specific key by applying a predefined Key Derivation Function, KDF, to said context parameters, the Key Derivation Function being known to the client terminal.

### Claim 19 (depends on 18)

The web server according to claim 18, wherein the verification module is further configured to create an aggregated parameter, S, based on the context parameters in a predetermined manner, and to apply the Key Derivation Function using as input said aggregated parameter S and an application specific key, Ks_NAF, such that
Ks_NAF′=KDF(Ks_NAF, S(P1, . . . Pn)), where Ks_NAF′ is the created context-specific key and P1, . . . Pn is the set of context parameters.

### Claim 20 (depends on 19)

The web server according to claim 19, wherein the verification module is further configured to obtain the application specific key Ks_NAF from a Bootstrapping Service Function, BSF, associated with the client terminal.
