key_management/compromise

6 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Key compromise implications for confidentiality

Unauthorized disclosure of a key used for confidentiality protection via encryption means all information encrypted by that key could be exposed to unauthorized entities. Disclosure of a Certificate Authority's private signature key means an adversary can create fraudulent certificates and Certificate Revocation Lists (CRLs).

Key compromise implications for integrity

Compromise of key integrity means the key is incorrect - either modified deliberately or accidentally, or another key has been substituted including deletion (non-availability). Substitution or modification of a key providing integrity calls into question the integrity of all information protected by the key. This information could have been provided by or changed by an unauthorized entity knowing the key.

Key compromise implications for usage association

Compromise of a key's usage or application association means the key could be used for wrong purpose (e.g., key establishment instead of digital signatures) or wrong application, resulting in compromise of information protected by the key.

Key compromise implications for entity association

Compromise of a key's association with the owner or other entity means identity of the other entity cannot be assured (one does not know who the other entity really is) or information cannot be processed correctly (e.g., decrypted with correct key).

Key compromise implications for information association

Compromise of a key's association with other information means there is no association at all, or the association is with wrong information. This could cause cryptographic services to fail, information to be lost, or security of information to be compromised.

Key compromise protective measures

Protective measures to minimize likelihood or consequences of key compromise: (1) Limit the amount of time symmetric or private key is in plaintext form, (2) Prevent humans from viewing plaintext symmetric and private keys, (3) Restrict plaintext symmetric and private keys to physically protected containers (key generators, key-transport devices, key loaders, cryptographic modules, key-storage devices), (4) Use integrity checks to ensure key integrity and associations not compromised, (5) Use key wrapping to detect unauthorized modifications, (6) Employ key confirmation to ensure proper key was established, (7) Establish accountability system tracking each plaintext key access, (8) Provide cryptographic integrity check on key (MAC or digital signature), (9) Use trusted timestamps for signed data, (10) Destroy keys as soon as no longer needed.

Give your agent this brain