scandale-project is also meant to monitor constituencies' actions after being notified about security issues. The idea is to timestamp scan results with a Time Stamp Authority to have a clear and indisputable incident timeline following a notification. The aim is to nudge constituencies to take action and also give them leverage on non-cooperating suppliers. No infrastructure change or patch after repeated notifications is not a good trajectory to be on--hence the name, scandale :)
Shameless plug: I wrote a small poc module to use hashlookup's bloom filter (https://github.com/hashlookup/a-ray-grass/) in yara (https://github.com/VirusTotal/yara). The idea is to easily discard files that are known to be safe and so to avoid launching thousands of yara rules on a file for nothing. One can also use it to keep track of some files that meet certain conditions for instance. The module can store any string in these filters so I see a lot of useful use-cases for this little thingy :)
edit: forgot the link duh.
Actually IEEE 802.11u implements something like EAP-UNAUTH-TLS where the client auths the server but the server does not auths the client.
After that, the best would be to push the whole traffic throug tor (Or even to run a tor exit node, if nobody can say from which side of the network the requezst comes from ...).
"Pour des raisons de sécurité, l’ensemble des services IRC (à titre non-exhaustif : bots, proxy, bouncer,
etc.), services de navigation anonyme (généralement appelés proxy), nœuds TOR, ne sont pas autorisés
sur le réseau OVH sauf autorisation écrite d’OVH. OVH se réserve le droit de suspendre tout serveur sur
lequel ces éléments seraient utilisés sans autorisation préalable d’OVH."
It looks like anything looking like a proxy is forbidden now. Including tor nodes :/