Nope - they are pretty raw, we leave that up to the person installing the kit - Tyk isn't a service, it's a piece of software to run on your own infrastructure so that your sysops can lock it down however they see fit, like NGinX. You could go meta and put Tyk in front of the Tyk API's, and lock that layer down. though I'm not sure what that would achieve...