Search
×
FR

Placeholder headline

This is just a placeholder headline

API Technical Report TDB-6 Chapter 6 – Density

$

204

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 560: Fired Heaters for General Refinery Services

$

721

BUY NOW

Placeholder headline

This is just a placeholder headline

API STD 64: Diverter Equipment Systems

$

324

BUY NOW

Placeholder headline

This is just a placeholder headline

API MPMS CH 17.10.1: Refrigerated Light Hydrocarbon Fluids – Measurement of Cargoes on Board LNG Carries

$

417

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 13B-1: Testing Water-based Drilling Fluids

$

418

BUY NOW

Placeholder headline

This is just a placeholder headline

API Technical Report TDB-12 Chapter 12 – Thermal Conductivity

$

214

BUY NOW

Placeholder headline

This is just a placeholder headline

API 16FI Frac Iron Guidelines and Requirements

$

129

BUY NOW

ISO 19772:2020

ISO 19772:2020 Information security – Authenticated encryption

CDN $233.00

SKU: 9b9252681a0c Category:

Description

This document specifies five methods for authenticated encryption, i.e. defined ways of processing a data string with the following security objectives:

– data confidentiality, i.e. protection against unauthorized disclosure of data;

– data integrity, i.e. protection that enables the recipient of data to verify that it has not been modified;

– data origin authentication, i.e. protection that enables the recipient of data to verify the identity of the data originator.

All five methods specified in this document are based on a block cipher algorithm, and require the originator and the recipient of the protected data to share a secret key for this block cipher.

Key management is outside the scope of this document. Key management techniques are defined in ISO/IEC 11770 (all parts).

Four of the mechanisms in this document, namely mechanisms 3, 4, 5 (AAD variant only) and 6, allow data to be authenticated which is not encrypted. That is, these mechanisms allow a data string that is to be protected to be divided into two parts, D, the data string that is to be encrypted and integrity-protected, and A (the additional authenticated data) that is integrity-protected but not encrypted. In all cases, the string A can be empty.

NOTE Examples of types of data that can need to be sent in unencrypted form, but whose integrity is to be protected, include addresses, port numbers, sequence numbers, protocol version numbers and other network protocol fields that indicate how the plaintext is to be handled, forwarded or processed.

Edition

2

Published Date

2020-11-27

Status

PUBLISHED

Pages

26

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

This document specifies five methods for authenticated encryption, i.e. defined ways of processing a data string with the following security objectives:

- data confidentiality, i.e. protection against unauthorized disclosure of data;

- data integrity, i.e. protection that enables the recipient of data to verify that it has not been modified;

- data origin authentication, i.e. protection that enables the recipient of data to verify the identity of the data originator.

All five methods specified in this document are based on a block cipher algorithm, and require the originator and the recipient of the protected data to share a secret key for this block cipher.

Key management is outside the scope of this document. Key management techniques are defined in ISO/IEC 11770 (all parts).

Four of the mechanisms in this document, namely mechanisms 3, 4, 5 (AAD variant only) and 6, allow data to be authenticated which is not encrypted. That is, these mechanisms allow a data string that is to be protected to be divided into two parts, D, the data string that is to be encrypted and integrity-protected, and A (the additional authenticated data) that is integrity-protected but not encrypted. In all cases, the string A can be empty.

NOTE Examples of types of data that can need to be sent in unencrypted form, but whose integrity is to be protected, include addresses, port numbers, sequence numbers, protocol version numbers and other network protocol fields that indicate how the plaintext is to be handled, forwarded or processed.

Previous Editions

Can’t find what you are looking for?

Please contact us at: