Pinned Tweet
Security work keeps growing, but security teams don't.
We've spent years getting better at finding security problems. It's everything that happens after that where most teams are feeling the pressure.
Contabo reset every customer’s VNC password after an intrusion on Nov 14.
That console sits below the OS, so whoever has it can bypass your SSH config and firewall rules entirely.
What to check on your servers today👇
secure.com/news/contabo-secu…
2
17
Google just documented an AI system that reads a vendor’s patch, works out what it fixed, writes the exploit, and runs it, with no human steering any of it.
Every patch you haven’t deployed yet is now a set of instructions.
The response side has to move at the same speed, and for most teams it’s still a ticket queue.
It’s the problem we’ve been building Secure.com’s AI Teammates around: connecting a new advisory to the systems it actually affects, so the response starts when the patch drops.
secure.com/?utm_source=x&utm…
9
What actually helps: knowing which of your internet-facing systems a new advisory affects on the day it drops, and watching those systems closely until they’re patched. Speeding up patching alone won’t close a gap that’s now measured in hours.
7
For context, the system Google found compares code before and after a vendor ships a patch, works out which bug the patch closed, and then writes and launches the exploit. Most of its targets already had fixes available, which is why the gap between “patch released” and “patch deployed” matters so much now.
14
Secure.com retweeted
Microsoft's global outage exposed how shared cloud infrastructure can disrupt multiple services at once. In this op-ed, @Securedotcom's Waseem Ahmed urges stronger continuity plans and vigilance against recovery scams. #cybersecurity #CISO #infosec bit.ly/4ABwBRv
The November 17 blackout rumor clearly shows how social engineering works: a real event, a familiar reference, and a date to create urgency.
FYI, phishing campaigns follow the same pattern every day.
Every trust signal the cybersecurity industry spent a decade teaching people to check got used against them this month.
The padlock, the blue check, the signed installer, the provenance badge, the real login page.
The real test is what happens after the click, and that’s where most teams can see the least right now
Most security content covers the breach and the tools. Very little covers what practitioners actually do in the minutes and hours after the alert fires.
So we started After The Alert, a weekly series where security leaders walk through the investigation, the call, and the fix.
Episode 1: Gabriel Podolan, Director of InfoSec at Ariat International, on alert fatigue at AI speed and what he’d trust AI to do alone.
youtube.com/watch?v=Va2Sn8pz…
2
16
Attackers aren’t breaking into financial firms anymore. They walk in through the people and approvals around the money.
Joining @ZIGFinance in London on 12 Nov to get in on it.
Banking, fintech, Web3 → come say hi.
luma.com/ZIGFinancexSecure.c…
1
13
It usually means the response team is assuming the attacker can see email, chat, or the ticketing system. Ransomware crews have been caught sitting in a victim’s chat, watching the response unfold
1
1
24
Secure.com retweeted
As AI changes how financial firms are targeted, protecting capital means securing the people and approvals behind every transaction.
On 12 November, we're co-hosting a conversation in London with @Securedotcom, bringing together leaders across banking, fintech and Web3 to discuss what it takes to protect capital against the next generation of cyber threats.
Join us: luma.com/ZIGFinancexSecure.c…
Vulns this week, ranked by how hard they made us laugh:
1. Alpine: a really long password gets you in (under the right conditions)
2. Barracuda: the timezone field runs as root
3. MS Paint: has a network attack surface now
4. WordPress: updating is the dangerous part
5. Rails: ImageMagick, again
Anyway, go patch stuff
Us, realizing all of these could live on one page 👇
secure.com/cve?utm_source=x&…
2
81
Three HIPAA cloud myths that get teams fined:
1. A signed BAA makes you compliant
2. Cloud apps are exempt because no ePHI is on site
3. There’s an official HIPAA cloud certification
All three are wrong. Your data, user access, and evidence stay with you in every cloud model.
1
1
100
2,828 new CVEs were published this week, and 5 were added to CISA’s exploited list.
We built CVE Radar so you can see which ones those are at a glance, with every new CVE’s CVSS, KEV status, and EPSS score on one page, updated hourly:
secure.com/CVE?utm_source=x&…
1
66
What actually tells you what to patch first:
1. Is it on CISA KEV? Someone is exploiting it right now.
2. What’s the EPSS score? That’s how likely it is to be exploited soon.
3. Is it reachable in your environment?
1
14




