JSON Web Encryption (JWE)

Overview

JSON Web Encryption is a JOSE standard for representing encrypted content with protected metadata in compact or JSON-based serialization formats. Encryption provides confidentiality and integrity for the protected content, but correct security depends on algorithm selection, key strength, nonce handling, and validation of protected headers. JWE protects plaintext using authenticated encryption and represents the necessary parameters as structured, base64url-encoded parts. JWE encrypts and integrity-protects content for intended recipients; it should not be confused with JWS signing or with the broader JWT claims profile. Applications must verify issuer, audience, purpose, and freshness separately where relevant, while avoiding sensitive information in unprotected headers. For JSON Web Encryption (JWE), identifiers and timestamps should remain stable enough to trace the technical action to its final business outcome.

Implementations should use maintained JOSE libraries, allow only explicitly approved algorithms, validate every cryptographic result, and rotate keys safely. It separates key management from content encryption and can support one or multiple recipients depending on the serialization. A JWE does not automatically establish who created the content unless the surrounding protocol provides identity or a signature.

The production contract for JSON Web Encryption (JWE) should state the supported principals, credentials, keys, scopes, claims, requests, verification results, and revocation state, required and optional fields, types and units, validation rules, state preconditions, version, permissions, limits, errors, and compatibility guarantees. The production boundary for JSON Web Encryption (JWE) should identify the authoritative system, responsible owner, accepted states, and recovery path. Evidence for JSON Web Encryption (JWE) should preserve the input, configuration version, actor or service, decision, downstream reference, and final outcome.