If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...
If you have a not-so-usual solution for your problems but need to justify it to your boss...
If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...
...then 'No Bugs' Hare on Soft.ware might be the right place for you.
Your mileage may vary. Batteries not included

Developing secure software is a challenge. Writing really secure software is a real challenge.
Here are the articles which touch different security aspects of software, from “what cipher suites are not to be used with TLS”, to certain more or less novel things under ‘Security Research’ subcategory.

All Software Herecies about Security, page 1:

Bot Fighting 104. Known Bots and Environment Scans.

Quote: “Most of multi-million-dollar games have a special team dealing specifically with public and semi-private bots.”
Another Quote: “it might help to ensure that whatever-information-you-collect, DOES NOT leave the player’s box”
[]

Bot Fighting 203: (Re)Actors and Short Stacks

Quote: “there will be almost-zero information available via reading the stack frames.”
Another Quote: “If your game is NOT really time-critical – we can go all the way to the full-scale Tor-like network out of obfuscation-only (Re)Actors”
[]

Bot Fighting 202. Time-Based Protection

Quote: “Whenever we detect that the time spent within a piece-of-non-blocking-code, is more than a few seconds – then, either the system is hopelessly swapping, or we’re being debugged”
Another Quote: “What if we send not just a challenge, but a “challenge which includes some piece of code to be executed on the Client-Side”?”
[]

Bot Fighting 201. Part 4. Obfuscating Protocols. Versioning.

Quote: “we can handle several Client versions (each with its own obfuscation) with the very same Server.”
Another Quote: “Then, if/when a zero-day bug is encountered in TLS – our obfuscation does provide additional protection even before the attacker can reach the code with that zero-day vulnerability”
[]

Bot Fighting 201, part 3. ithare::obf: An Open Source Data+Source Randomized Obfuscation Library

Quote: “This is all what the-best-available-decompiler was able to do with our obfuscated code”
Another Quote: “Performance-wise, we can do A LOT of obfuscation per network tick”
[]

Bot Fighting 201: Declarative Data+Code Obfuscation with Build-Time Polymorphism in C++

Quote: “Technically, what we’re looking for here, is any kind of bijection; we’ll use this bijection to convert our data from one representation into another one (and as it is a bijection, we can revert it later).”
Another Quote: “As we’re not writing our obf<> classes manually (instead, we have a code generator doing it for us on each build), the sky is the limit to the obfuscations we can generate.”
[]