1.4 Cryptographic Solutions

Public Key Infrastructure (PKI) is the framework of technology, policies, and procedures used to create, distribute, store, and revoke digital certificates and manage public-key encryption.

Asymmetric Cryptography Fundamentals PKI is built on asymmetric encryption, which uses a mathematically related key pair to deliver security services. - Key pairs: a public key shared openly with anyone, and a private key kept strictly secret by the owner. - Directional property: data encrypted with the public key can only be decrypted by the matching private key, and vice versa. - Scalability: each user needs only one key pair to talk to anyone, while symmetric encryption needs N(N-1)/2 keys for N users. - Key exchange: PKI solves the key-distribution problem — public keys can travel over insecure channels like the Internet without exposing the private key.

Core PKI Operations PKI supports three goals through specific key-usage patterns: - Confidentiality: the sender encrypts with the recipient's public key; only the recipient's private key can decrypt it. - Digital signatures: the sender encrypts a hash of the message with their own private key, giving non-repudiation (they cannot deny sending it) and integrity (the message has not changed). - Authentication: the recipient verifies a signature with the sender's public key, confirming the sender's identity.

Digital Certificates and Trust To stop an attacker from substituting a bogus public key, PKI binds keys to identities with certificates. - Certificate Authority (CA): the trusted third party that issues and signs certificates, binding a public key to a verified identity. - Trust anchor: the Root CA certificate that all other certificates ultimately chain back to. - Validation: when a browser opens an HTTPS site, it checks that the server's certificate was signed by a trusted CA and belongs to the legitimate owner.

Quick recall - Encrypt for secrecy → use the recipient's public key. - Sign for identity → use the sender's private key. - Decrypt → use your own private key. - Verify a signature → use the sender's public key. - Digital signature → provides authentication, integrity, and non-repudiation. - Scalability → asymmetric beats symmetric for large groups because it avoids the N(N-1)/2 key-management overhead.