So this made me laugh... For two reasons:
I imagined the elevator pitch: "So our product is called Node-able and it's like twitter, for like sysadmins and... their servers"
Because it's crazy/quirky enough that it may actually work
I am *technically* supposed to work in the near future on a project that will devise some kind of organisational structure that will correlate security events in order to generate actionable/understandable data/information. Of course the technical solutions I have been exposed so far are "serious" software, they create pie charts and bar graphs and all kinds of excel grade visual information. Those are really useful but in reality mostly for reporting to powers that be because I guarantee you that the sec team don't give a fuck, they have fires to put out, audits to conduct and presentations to deliver... But! What if it the information were <140 text message? Well then it's different, you have several stakeholders accross your IT team, I&O people, Strat people, Info Sec people, R&D maybe, Architecture, etc... They all more or less have important "stakes" in security, well those "stakes" look like #hashtags, and those "stakes" can be directly correlated to assets (like *we*say in infosec-speek) and guess what, if your asset is an electronic device or is tracked/monitored by one, you can make it @username identifying it in your network.
So now that you have @ITperson + @machine + #securityEvents you can effectively monitor your network security, with a granularity and a simplicity that even allows bi-directional interaction (e.g.: @CISO asking @ExchangeServer about #LoadBalancing in real time or @FW warning @NetManager of possible #DDoS from ip 192.168.0.0). You can track specific types of #events too...










