Menu

Partitioned Cookies Limit Cross-Site Reuse, Not Cross-Site Risk
📰

Partitioned Cookies Limit Cross-Site Reuse, Not Cross-Site Risk

DEV Community: security·StarkMan·8 days ago
#gaoDZRew
#devtosecurity#devto#dev#cookie#partitioned
Reading 0:00
15s threshold

Partitioned Cookies Limit Cross-Site Reuse, Not Cross-Site Risk

Cookies Having Independent Partitioned State, usually called CHIPS, gives a cookie a second key based on the top-level site. A service embedded in two different sites gets separate cookie jars for those embedding contexts. MDN describes the storage key as the host key plus a partition key derived from the top-level URL. The feature addresses cross-site tracking and cross-site state reuse. It does not make the embedded application trustworthy.

With the Partitioned attribute, a cookie must also be Secure . A typical header looks like Set-Cookie: __Host-example=...; SameSite=None; Secure; Path=/; Partitioned . The __Host prefix is recommended when the cookie does not need to be shared between subdomains. That combination gives the cookie a host binding and a top-level-site partition.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.