{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifxjx4lur3wesplwgzd54t3mabp6h2truspzczxh7grd2p2dmmy3u",
    "uri": "at://did:plc:gapzbf5nl5wxaqkqoecaeawh/app.bsky.feed.post/3mpc52iequdj2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreif2mtuzf6mdtnnsfm24ck3zgojvpzmhikx53ksriodev227mggxdq"
    },
    "mimeType": "image/webp",
    "size": 24880
  },
  "path": "/from-phishing-to-vishing-why-devsecops-must-rethink-communication-security/",
  "publishedAt": "2026-06-26T21:42:29.000Z",
  "site": "https://devops.com",
  "tags": [
    "Blogs",
    "Contributed Content",
    "DevSecOps",
    "Social - Facebook",
    "Social - LinkedIn",
    "Social - X",
    "AI security",
    "CI/CD",
    "devsecops",
    "social engineering",
    "Vishing",
    "zero-trust"
  ],
  "textContent": "Key Takeaways: Vishing is the new frontline threat: Attackers are shifting from emails to phone-based scams, using AI and social engineering to bypass traditional security controls. DevSecOps must expand its scope: Securing code is no longer enough; communication channels like voice, chat, and messaging must be integrated into threat models and security pipelines. Human and […]",
  "title": "From Phishing to Vishing: Why DevSecOps Must Rethink Communication Security"
}