I would say those are non-issues in most deployments. Application caches are normally deployed within an isolated, trusted environment. TCP connections from un

I would say those are non-issues in most deployments. Application caches are normally deployed within an isolated, trusted environment. TCP connections from untrusted clients simply don't happen, so hardening is not needed at that level. I'm confused about what use-case you have in mind with this. Is your cache meant to be exposed to the general public, sort of like the things you can do with couchdb?