So Long, And No Thanks for the Externalities: The Rational Rejection of Security Advice by Users
A research paper published under Microsoft Research by Cormac Herley, on why users reject much/most/all of the security education and advice given nowadays by security researchers and professionals alike.
Here're the links to the page, PDF [original] [mirror] and Google Docs viewer. What's below are just my summaries (of the paper) and thoughts on this, if it's of any interest anyway.
Weird outgoing IP accesses…
Found out by accident (plenty of "accident"s happening with me recently) that one of the home computers has been connecting out to some weird China IP amongst others, all of which are blacklisted according to robtex...
Starting to get quite concerned, since there was a lot of stuff that was previously installed, like those that you "need" to install in order to view online videos.
Will start to do some verbose logging to gather more info, but this isn't looking good so far. How this came up was because of the way the computer tried to connect to the site, apparently it tried to make too many connections at the same time, causing the router to think that there's a SYN flood attack going on lol.
Culprit #1 - 221.238.197.38 [robtex report]
Getting additional (IP/network/location) info along with your Splunk searches
Chanced upon some of the info by accident (smack at the bottom of one part of the Splunk documentation...), but I can't find it now. Going to share here anyway 
Some (or probably most/all) of your searches might involve public IP addresses, and more often than not we would want to have additional info along with the IP address to work with.
Three of the things that we could do in Splunk automatically would be to get IP-location info, or to reverse lookup an IP to a domain, or to lookup a domain to an IP.