You need to make a frequently requested authenticated resource cacheable at CDN edge, but avoid IDOR/caching cross-contamination. Which is the best safe approach?
Cache everything and rely on short TTLs so the impact is minimal
Disable compression to make poisoning harder
Use a cache key that includes a signed token or user identifier that the CDN cannot forge, and validate it server-side
Remove authentication so caching is simpler
This question is part of this quiz :
Cyber Quiz Day 34