Interface CryptoDeterministicConfigOrBuilder (3.58.0)

Version 3.58.0

• 3.59.0 (latest)
• 3.58.0
• 3.57.0
• 3.56.0
• 3.55.0
• 3.53.0
• 3.52.0
• 3.51.0
• 3.50.0
• 3.49.0
• 3.48.0
• 3.47.0
• 3.46.0
• 3.45.0
• 3.44.0
• 3.43.0
• 3.41.0
• 3.40.0
• 3.39.0
• 3.38.0
• 3.37.0
• 3.36.0
• 3.35.0
• 3.34.0
• 3.33.0
• 3.32.0
• 3.31.0
• 3.28.0
• 3.27.0
• 3.26.0
• 3.25.0
• 3.24.0
• 3.23.0
• 3.22.0
• 3.21.0
• 3.20.0
• 3.19.0
• 3.18.0
• 3.17.0
• 3.16.0
• 3.15.0
• 3.13.0
• 3.12.0
• 3.11.0
• 3.10.0
• 3.9.0
• 3.8.0
• 3.7.6
• 3.6.7
• 3.5.0
• 3.4.0
• 3.3.2
• 3.2.1
• 3.1.4

public interface CryptoDeterministicConfigOrBuilder extends MessageOrBuilder

Implements

MessageOrBuilder

Methods

getContext()

public abstract FieldId getContext()

A context may be used for higher security and maintaining referential integrity such that the same identifier in two different contexts will be given a distinct surrogate. The context is appended to plaintext value being encrypted. On decryption the provided context is validated against the value used during encryption. If a context was provided during encryption, same context must be provided during decryption as well.

If the context is not set, plaintext would be used as is for encryption. If the context is set but:

1. there is no record present when transforming a given value or

2. the field is not present when transforming a given value,

   plaintext would be used as is for encryption.

   Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems.

.google.privacy.dlp.v2.FieldId context = 3;

Returns
Type	Description
FieldId	The context.

getContextOrBuilder()

public abstract FieldIdOrBuilder getContextOrBuilder()

A context may be used for higher security and maintaining referential integrity such that the same identifier in two different contexts will be given a distinct surrogate. The context is appended to plaintext value being encrypted. On decryption the provided context is validated against the value used during encryption. If a context was provided during encryption, same context must be provided during decryption as well.

If the context is not set, plaintext would be used as is for encryption. If the context is set but:

1. there is no record present when transforming a given value or

2. the field is not present when transforming a given value,

   plaintext would be used as is for encryption.

   Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems.

.google.privacy.dlp.v2.FieldId context = 3;

Returns
Type	Description
FieldIdOrBuilder

getCryptoKey()

public abstract CryptoKey getCryptoKey()

The key used by the encryption function. For deterministic encryption using AES-SIV, the provided key is internally expanded to 64 bytes prior to use.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1;

Returns
Type	Description
CryptoKey	The cryptoKey.

getCryptoKeyOrBuilder()

public abstract CryptoKeyOrBuilder getCryptoKeyOrBuilder()

The key used by the encryption function. For deterministic encryption using AES-SIV, the provided key is internally expanded to 64 bytes prior to use.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1;

Returns
Type	Description
CryptoKeyOrBuilder

getSurrogateInfoType()

public abstract InfoType getSurrogateInfoType()

The custom info type to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom info type followed by the number of characters comprising the surrogate. The following scheme defines the format: {info type name}({surrogate character count}):{surrogate}

For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom info type 'Surrogate'. This facilitates reversal of the surrogate when it occurs in free text.

Note: For record transformations where the entire cell in a table is being transformed, surrogates are not mandatory. Surrogates are used to denote the location of the token and are necessary for re-identification in free form text.

In order for inspection to work properly, the name of this info type must not occur naturally anywhere in your data; otherwise, inspection may either

• reverse a surrogate that does not correspond to an actual identifier

• be unable to parse the surrogate and result in an error

  Therefore, choose your custom info type name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE.

.google.privacy.dlp.v2.InfoType surrogate_info_type = 2;

Returns
Type	Description
InfoType	The surrogateInfoType.

getSurrogateInfoTypeOrBuilder()

public abstract InfoTypeOrBuilder getSurrogateInfoTypeOrBuilder()

The custom info type to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom info type followed by the number of characters comprising the surrogate. The following scheme defines the format: {info type name}({surrogate character count}):{surrogate}

For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom info type 'Surrogate'. This facilitates reversal of the surrogate when it occurs in free text.

Note: For record transformations where the entire cell in a table is being transformed, surrogates are not mandatory. Surrogates are used to denote the location of the token and are necessary for re-identification in free form text.

In order for inspection to work properly, the name of this info type must not occur naturally anywhere in your data; otherwise, inspection may either

• reverse a surrogate that does not correspond to an actual identifier

• be unable to parse the surrogate and result in an error

  Therefore, choose your custom info type name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE.

.google.privacy.dlp.v2.InfoType surrogate_info_type = 2;

Returns
Type	Description
InfoTypeOrBuilder

hasContext()

public abstract boolean hasContext()

A context may be used for higher security and maintaining referential integrity such that the same identifier in two different contexts will be given a distinct surrogate. The context is appended to plaintext value being encrypted. On decryption the provided context is validated against the value used during encryption. If a context was provided during encryption, same context must be provided during decryption as well.

If the context is not set, plaintext would be used as is for encryption. If the context is set but:

1. there is no record present when transforming a given value or

2. the field is not present when transforming a given value,

   plaintext would be used as is for encryption.

   Note that case (1) is expected when an InfoTypeTransformation is applied to both structured and unstructured ContentItems.

.google.privacy.dlp.v2.FieldId context = 3;

Returns
Type	Description
boolean	Whether the context field is set.

hasCryptoKey()

public abstract boolean hasCryptoKey()

The key used by the encryption function. For deterministic encryption using AES-SIV, the provided key is internally expanded to 64 bytes prior to use.

.google.privacy.dlp.v2.CryptoKey crypto_key = 1;

Returns
Type	Description
boolean	Whether the cryptoKey field is set.

hasSurrogateInfoType()

public abstract boolean hasSurrogateInfoType()

The custom info type to annotate the surrogate with. This annotation will be applied to the surrogate by prefixing it with the name of the custom info type followed by the number of characters comprising the surrogate. The following scheme defines the format: {info type name}({surrogate character count}):{surrogate}

For example, if the name of custom info type is 'MY_TOKEN_INFO_TYPE' and the surrogate is 'abc', the full replacement value will be: 'MY_TOKEN_INFO_TYPE(3):abc'

This annotation identifies the surrogate when inspecting content using the custom info type 'Surrogate'. This facilitates reversal of the surrogate when it occurs in free text.

Note: For record transformations where the entire cell in a table is being transformed, surrogates are not mandatory. Surrogates are used to denote the location of the token and are necessary for re-identification in free form text.

In order for inspection to work properly, the name of this info type must not occur naturally anywhere in your data; otherwise, inspection may either

• reverse a surrogate that does not correspond to an actual identifier

• be unable to parse the surrogate and result in an error

  Therefore, choose your custom info type name carefully after considering what your data looks like. One way to select a name that has a high chance of yielding reliable detection is to include one or more unicode characters that are highly improbable to exist in your data. For example, assuming your data is entered from a regular ASCII keyboard, the symbol with the hex code point 29DD might be used like so: ⧝MY_TOKEN_TYPE.

.google.privacy.dlp.v2.InfoType surrogate_info_type = 2;

Returns
Type	Description
boolean	Whether the surrogateInfoType field is set.