Promptly Secured A security chief and his AI crew

blue asks Red about one more detail
péter publishes the post
red is scanning this week's news with an attacker's eye
blue is turning it into a plain-language checklist
péter reviews, adds context, signs off
red is filtering reports about leaked databases
blue cuts the advice down to three steps
péter checks the sources
red is checking what a scammer can learn from an order history
blue weeds out the jargon
péter cuts an overconfident sentence
red is collecting new phishing patterns from public alerts
blue checks whether a grandparent could do it too
péter adds his own experience
red is counting exposed controllers in public search engines
blue cross-checks the advice with official guidance
péter map[sends it back to Red:too technical]
red is replaying the logic of a known flaw in the lab
blue writes update instructions for home devices
péter map[sends it back to Blue:could be shorter]
red is working out why a scam text actually worked
blue writes what to do if you already clicked
péter asks how we actually know this
red reads CVE write-ups, never hands out working code
blue lists who to call when something goes wrong
péter picks the topic of the week
red is checking which old flaw is getting a second life
blue puts together a password-change checklist
péter makes coffee
red turns the attack into a mechanism, not a weapon
blue explains two-factor authentication
péter reads an original source from start to finish
red is mapping the script of fake refund calls
blue writes a small-business version as well
péter notes where the AI got it wrong
red is guessing what pretext a scammer would build
blue translates the advice into English
péter takes out the scaremongering
red is hunting for the week's most creative social engineering trick
blue checks that nothing in it is scaremongering
péter writes the closing note
red is mapping the attack chain to MITRE ATT&CK
blue formats the "what to do now" box
péter reads the whole thing one last time
red tells Blue that this one needs a plain-language version
blue asks Red about one more detail
péter publishes the post

Privacy

This site uses no cookies and runs no tracking code. It loads only one thing from a third party: embedded YouTube videos, on the posts that come with a video.

What the server logs

The hosting provider’s (Rackhost Zrt.) web server keeps the usual logs needed for operation and security: IP address, time, requested page and browser identifier. I don’t use this data to identify visitors.

Embedded YouTube videos

When a post includes a video, I embed it using YouTube’s privacy-enhanced mode (youtube-nocookie.com). Your browser then loads the video player from Google’s servers, so Google sees your IP address and the page you requested. YouTube stores no cookies before playback; once you start the video, Google’s privacy policy applies. If you’d rather avoid that, don’t start the video; the post is complete without it.

Contact

For privacy questions, use the contact details in the imprint.