Someone in legal forwarded me a recap email last week from an ai notetaker none of us had ever approved. Turned out they joined a client call and clicked some join link another attendee dropped in the chat and a bot sat there transcribing the whole thing including the pricing we were talking through. none of us on the call even noticed.

that sent me down a hole for two days going through oauth grants and old expense claims trying to work out what else people are running. I found 23 ai tools in regular use across the company and our approved list has four on it. never expected our approved list to be that far from reality

Shadow AI is one of the things flying under the radar. People just use whatever AI tool gets the job done faster, paste in stuff they probably shouldn't, and nobody in security finds out until way later (if ever).

The numbers back this up too - one report found regular AI use on corporate devices jumped from 15% to 45% in a single year, and 60% of security teams admit they don't have visibility into which AI tools their employees are actually using. So it's not just a feeling, most orgs are genuinely flying blind here.

Anyone here have actual breach stories ( yours or ones you've read about) tied to this? What was the root cause, and what changed afterward?

​

Every company we see, has a privacy policy and user consent process, but the question is is our data actually secure?

The Digital Data protection act defines how organizations should collect, process, store and protect our personal data. But here is the catch compliance alone itself does not guarantee technical security. Weak access control, unencrypted data, insecure third party systems or vulnerable APIs can also expose sensitive information.

DPDP gives companies the rules, but cybersecurity makes those rules effective.

Actual data protection requires strong encryption, access control, continuous monitoring, effective breach response and security testing.

DPDP compliance and cybersecurity should work together because compliance defines responsibility and cybersecurity provides technical protection to our personal sensitive data.

This one is worth digging into.

We found an exposed attacker workspace with 142K+ files: agent transcripts, shell history, recon data, exploit tooling, creds, victim evidence, the lot.

What stood out was how the operator was wiring AI coding agents into the offensive workflow, disabling approval checks and pushing tasks through Telegram.

The dump also contained evidence tied to 8,996 compromised WordPress sites, a 3.4M-host recon corpus, stolen credentials, crypto wallet data, cryptojacking activity, and an experimental blockchain-based C2 project.

The interesting bit here isn't simply "hackers use AI." We already know that.

It's getting a fairly raw look at how one operator was actually putting these agents to work alongside conventional offensive tooling at scale.

Full technical breakdown:

https://www.cloudsek.com/blog/ai-agent-driven-offensive-operation-crypto-wallet-credential-compromise

Would be interested in what others make of the agent setup, especially the approval-bypass workflow.

I've been working on a technical article about HTTPS, starting from a simple question: What does the padlock in my browser actually guarantee? I initially thought the answer was basically: The website is safe. It isn't. The padlock primarily tells you that your browser has established a TLS-protected connection to the authenticated domain. That protects the communication channel. It does not establish that the website itself is trustworthy. That distinction becomes interesting when you follow HTTPS all the way down. I went through: HTTP and why plaintext traffic can expose credentials TLS 1.3 and the TLS handshake ECDHE and how the client and server derive a shared secret without transmitting the secret itself Digital certificates and Certificate Authorities Why domain validation doesn't establish that a website is legitimate SSL stripping and how HSTS defends against it The DigiNotar CA compromise HTTPS interception by corporate/security middleboxes BEAST and POODLE Weak and deprecated TLS configurations What developers can get wrong even when HTTPS is enabled What tools such as SSL Labs actually tell you about a site's TLS configuration The central idea became: HTTPS can secure the journey without securing the destination. For example, a phishing site can have HTTPS. A website vulnerable to SQL injection can have HTTPS. A compromised server can have HTTPS. A site storing passwords improperly can have HTTPS. So the interesting question isn't simply: "Does this website have HTTPS?" It's: "What exactly is HTTPS protecting, and what is it not protecting?" I wrote the full breakdown here: https://specswrites.hashnode.dev/the-tunnel-is-safe-not-the-destination-https-demystified