Security specialist, public speaker, consumer of all things #hacking related. VP of PM @TenableSecurity #infosec #Nessus

Cambridge, England
Joined March 2009
What the hell Tel Aviv, I thought I was going to get some cheeky winter sun. Chucking it down outside but having fun meeting up with the Israeli team at #cybertechtlv
2
805
Malware on Google Play store found to enable proxy on target device to route malicious traffic. Apparently 2M downloads of affected apps although one should assume some of those are to boost ratings rather than potential victims #infosec bleepingcomputer.com/news/se…
I’ve obviously been super quiet on Twitter for a while now. During the IPO I had to keep my head down to not cause any issues and just got out of the habit of posting. I’m starting up again but on Mastodon infosec.exchange/@Gmillard
4
5
So if you want to hear the latest stuff from my perspective, hit me up on Mastodon. By the looks of it, a lot of #infosec folks have already made the move over.
Which is a pity, as at my most twittery times, I met a lot of cool people and had awesome conversations.
I’ll probably cross post for a while but then shut this account down as it appears to have gone a tad downhill since I was last here.
On the advice of @CISAgov, you shouldn't be exposing UPS devices to the internet #infosec cisa.gov/uscert/ncas/current…
1
At a Greggs for lunch: "Could I have a sausage roll, coffee and whatever that new ESET thing is on the menu please" #infosec
1
Previously compromised Exchange servers being leveraged in IcedID phishing campaigns threatpost.com/exchange-serv… #infosec
1
Worth scanning your external attack surface with this plugin to get an accurate inventory of Sonicwall devices exposing the web interface to the world tenable.com/plugins/nessus/1…
1
Am I missing something? Apparently AI “caught” the use of a 6 month old gitlab vulnerability for crypto mining and it’s worthy of a press release. Lol. darkreading.com/attacks-brea… #infosec
2
1
We’ll be releasing detections for 2.17.0 #log4jRCE. Looks like it’s FAR less of an issue than #log4shell. Will be updating blog and community posts shortly. #infosec
Tenable research will be reviewing the latest on #Log4Shell and updating plugins as required. For our customers, any new plugins will be included in the new dynamic scan policy "Log4Shell vulnerability Ecosystem" #infosec
Erm the 2.15.0 #Log4Shell fix that had a piddly DoS issue addressed by 2.16.0 has apparently been upgraded to a limited RCE. Not good. Also, this logo was drawn by someone drowning their sorrows #infosec lunasec.io/docs/blog/log4j-z…