Noise Protocol Framework

Noise defines a formal language of interactive patterns that specify the sequence of ephemeral and static Diffie-Hellman operations. Each pattern—such as IK, XX, or N—is a strict recipe dictating which keys are exchanged and when. This deterministic structure eliminates the ambiguity of traditional protocol design, allowing implementers to select a pattern that precisely matches their trust model, whether mutual authentication is required or one party remains anonymous.

The foundational mathematical primitive upon which the Noise Protocol Framework is built. It allows two parties to jointly establish a shared secret over an insecure channel without prior secrets.

• Elliptic Curve Diffie-Hellman (ECDH): The modern variant used in Noise, typically with Curve25519.
• Static-Static (SS): Both parties use long-term keys; provides mutual authentication.
• Ephemeral-Ephemeral (EE): Both parties generate one-time keys; provides forward secrecy but no authentication.
• Static-Ephemeral (SE, ES): One party uses a long-term key, the other a one-time key; provides unilateral authentication.

Noise handshake patterns are defined by the sequence and direction of these DH operations.

Authenticated Encryption with Associated Data is the symmetric cipher mode used in Noise transport messages. It provides three guarantees simultaneously:

• Confidentiality: The plaintext is encrypted and unreadable to attackers.
• Integrity: Any modification to the ciphertext is detected.
• Authenticity: The message is verified to come from the holder of the symmetric key.

Noise typically uses AES-256-GCM or ChaCha20-Poly1305. The associated data component binds encrypted payloads to the session context, preventing attackers from splicing ciphertexts between different sessions.

A critical security property enforced by Noise handshake patterns. Forward secrecy ensures that the compromise of a party's long-term static private key does not reveal the plaintext of previously recorded sessions.

• Achieved by incorporating ephemeral key pairs in the handshake.
• After the handshake completes, ephemeral private keys are securely erased.
• An attacker who later steals the static key cannot retroactively decrypt past traffic.

Patterns like Noise_IK and Noise_XX provide forward secrecy. Patterns relying solely on static-static DH (like Noise_NK) do not. This is a non-negotiable requirement for agent-to-agent communication in zero-trust architectures.

A privacy-preserving property where a party's static public key is not transmitted in cleartext to passive eavesdroppers. Noise achieves this through careful handshake design.

• Sender Identity Hiding: The initiator's static public key is encrypted using a key derived from the responder's ephemeral key before transmission.
• Responder Identity Hiding: The responder's static public key is encrypted using a key derived from the initiator's ephemeral key.
• Patterns like Noise_XK hide the initiator's identity from passive observers.
• Patterns like Noise_IX hide the responder's identity.

This is crucial for agent mesh networks operating in hostile network environments where revealing agent identities could enable targeted attacks.

Noise defines a compact language for specifying the sequence of cryptographic operations in a protocol. Each pattern is a pre-defined sequence of tokens representing DH operations and message payloads.

• -> e: Initiator sends an ephemeral public key.
• <- e, ee: Responder sends an ephemeral public key and performs an EE DH operation.
• -> s, se: Initiator sends a static public key and performs an SE DH operation.

Common patterns include:

• NN: No authentication, pure forward secrecy (like unauthenticated TLS).
• XX: Mutual authentication with identity hiding for both parties.
• IK: Initiator knows responder's static key; ideal for client-server agent architectures.
• KK: Both parties know each other's static keys; minimal latency for reconnecting agents.

While Noise provides forward secrecy, it does not inherently provide post-compromise security (PCS)—the ability to recover security after a key compromise. PCS requires continuous key ratcheting.

• Noise can be composed with the Double Ratchet Algorithm (from the Signal Protocol) to achieve PCS.
• Each message advances a symmetric ratchet, deriving a new key from the previous one.
• An attacker who compromises a single message key cannot derive past or future keys.
• For long-lived agent communication channels, implementing a ratcheting layer on top of Noise transport messages is recommended.

This hybrid approach combines Noise's flexible handshake authentication with Signal's robust ongoing channel security.