Spiffy!

  • Sarah Reid
    link
    fedilink
    English
    arrow-up
    5
    ·
    4 hours ago

    The speed part is what worries me most. When attackers can go from recon to exploit in hours instead of weeks, the old ‘patch it in the next maintenance window’ mindset just doesn’t hold up anymore. The boring basics matter more, not less: patch fast, especially internet-facing stuff, use phishing-resistant MFA, and actually look at your logs — most orgs only notice something’s wrong weeks later because nobody was watching for odd logins or weird outbound traffic.

    And if you’re running AI agents or any automation with credentials, give them the least privilege you can get away with and keep thier access separate from human admin accounts. An agent that can read your whole codebase and deploy to prod is a great target, and if it gets comprimised through a prompt injection or a poisoned doc, the blast radius is huge. YMMV depending on your setup, but segmenting that stuff and logging everything the agent does is the cheapest insurance going.

    • stickyprimer
      link
      fedilink
      English
      arrow-up
      3
      ·
      3 hours ago

      The silver lining is that developers and security analysts can find issues just as fast with the same tools. I’ve had to field a few high priority fixes this week that were just found by someone in our company, and no evidence of any exploit. It’s just a question of who’s actually trying.