1/5
Looks like no tags are added yet.
Public Key Infrastructure (PKI)
A comprehensive framework of policies, procedures, hardware, software, and people responsible for creating, distributing, managing, storing, and revoking digital certificates
Requires significant planning and coordination
Central to PKI is the concept of trust, with the Certificate Authority (CA) playing a crucial role in establishing and maintaining this trust.
Symmetric Encryption
Uses a single, shared key for both encryption and decryption
If the key is compromised, a new key is required
Fast and having less overhead than asymmetric encryption
Doesn't scale well and can be challenging to distribute
Is often combined with asymmetric encryption for enhanced security.
Asymmetric Encryption
Also known as public key cryptography, uses two (or more) mathematically related keys.
The private key is kept confidential and is accessible only to its owner
Public key can be shared openly with anyone
Data encrypted with the public key can only be decrypted with the corresponding private key
The private key cannot be derived from the public key
The Key Pair
Involves generating both the public and private keys simultaneously
Requires significant randomization and the use of large prime numbers involving extensive mathematical calculations
Public key can be shared with anyone, while the private key remains confidential and is often protected with a password
Asymmetric Encryption Example:
After creating a public and private key pair, Alice makes her public key available to everyone. Bob, her friend, wants to send her an encrypted message. He writes a plaintext message saying "Hello, Alice" and uses Alice's public key to encrypt it through asymmetric encryption software, creating ciphertext.
When Alice receives the ciphertext, she uses her private key to decrypt it, revealing the original plaintext message that Bob sent.
Even if someone accesses the ciphertext and the public key, they can't reverse-engineer the plaintext.
Key Escrow
Managing the public and private key pairs of numerous users within an organization.
While individuals can manage their own keys, larger environments may require a third party to hold private keys until they are needed, or for keys to be stored locally.
Ensure that if a user leaves the company or changes departments, their private keys are still accessible for decrypting their work.
Although handing over private keys to another entity might seem controversial, it is sometimes necessary to ensure continuous access to organizational data and maintain uptime and availability.