<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>/</loc>
    <changefreq>weekly</changefreq>
    <priority>1.0</priority>
  </url>
  <url>
    <loc>/services</loc>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>/threat-frameworks</loc>
    <changefreq>monthly</changefreq>
    <priority>0.9</priority>
  </url>
  <url>
    <loc>/industries</loc>
    <changefreq>monthly</changefreq>
    <priority>0.7</priority>
  </url>
  <url>
    <loc>/blog</loc>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
  <url>
    <loc>/about</loc>
    <changefreq>monthly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/contact</loc>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/privacy</loc>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>/terms</loc>
    <changefreq>yearly</changefreq>
    <priority>0.3</priority>
  </url>
  <url>
    <loc>/blog/the-recent-disclosed-voice-cloning-attack-on-a-us-senator-s-office</loc>
    <lastmod>2026-03-30</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/a-reading-list-on-ai-communications-security</loc>
    <lastmod>2026-03-13</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-to-tell-your-board-about-ai-voice-risk</loc>
    <lastmod>2026-03-01</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/why-webform-intake-is-the-most-neglected-channel</loc>
    <lastmod>2026-02-26</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/chat-widget-abuse-and-the-new-front-door</loc>
    <lastmod>2026-02-22</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/email-spoofing-has-not-stopped-being-a-problem</loc>
    <lastmod>2026-02-09</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-quiet-threat-of-sms-pumping-in-customer-workflows</loc>
    <lastmod>2026-01-31</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/a-framework-for-categorizing-communications-threats</loc>
    <lastmod>2026-01-29</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/when-ai-agent-logs-become-discovery-evidence</loc>
    <lastmod>2026-01-23</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-the-recent-change-healthcare-aftermath-taught-about-communications-recovery</loc>
    <lastmod>2026-01-22</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-an-executive-communications-risk-brief-should-contain</loc>
    <lastmod>2026-01-09</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/conversational-prompt-exploitation-in-practice</loc>
    <lastmod>2026-01-03</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/why-you-should-stress-test-your-ai-agent-quarterly</loc>
    <lastmod>2026-01-01</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-underdiscussed-risk-of-ai-agent-memory-across-calls</loc>
    <lastmod>2025-12-22</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/how-restoration-companies-can-harden-their-first-notice-of-loss</loc>
    <lastmod>2025-12-10</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/disaster-surge-plans-that-account-for-ai-channel-failure</loc>
    <lastmod>2025-12-07</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/a-practical-approach-to-verified-identity-manipulation-defense</loc>
    <lastmod>2025-12-03</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-insurance-carriers-should-ask-their-ai-vendors</loc>
    <lastmod>2025-11-20</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-limits-of-voice-biometrics-in-2026</loc>
    <lastmod>2025-11-10</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/why-multi-location-brands-need-centralized-intake-security</loc>
    <lastmod>2025-11-08</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-recent-wave-of-vishing-attacks-on-help-desks-has-not-slowed</loc>
    <lastmod>2025-11-04</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-ivr-as-an-untrusted-boundary</loc>
    <lastmod>2025-11-02</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/how-surge-aware-routing-reduces-fraud-exposure</loc>
    <lastmod>2025-10-20</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-case-for-a-dedicated-communications-soc-function</loc>
    <lastmod>2025-10-13</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/tabletop-exercises-for-ai-era-communications-incidents</loc>
    <lastmod>2025-10-11</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-happens-when-your-chatbot-becomes-a-witness</loc>
    <lastmod>2025-10-02</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/a-vendor-risk-checklist-for-ai-voice-providers</loc>
    <lastmod>2025-09-19</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-quiet-erosion-of-trust-in-inbound-phone-channels</loc>
    <lastmod>2025-09-15</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-an-ai-agent-pen-test-should-actually-cover</loc>
    <lastmod>2025-09-13</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-recent-ransomware-disclosure-at-a-major-retailer-was-a-communications-test</loc>
    <lastmod>2025-09-12</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-underrated-risk-of-voicebot-outbound-campaigns</loc>
    <lastmod>2025-08-31</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-recent-ferrari-deepfake-attempt-and-the-discipline-of-the-skeptical-question</loc>
    <lastmod>2025-08-26</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/voice-cloning-has-crossed-an-affordability-threshold</loc>
    <lastmod>2025-08-20</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/designing-fallback-to-human-in-ai-first-workflows</loc>
    <lastmod>2025-08-18</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-compliance-case-for-ai-intake-logging</loc>
    <lastmod>2025-08-12</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/why-contact-center-qa-programs-miss-fraud-indicators</loc>
    <lastmod>2025-07-30</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/cross-channel-pivots-how-one-email-becomes-a-voice-attack</loc>
    <lastmod>2025-07-22</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/when-ai-agents-promise-things-they-cannot-deliver</loc>
    <lastmod>2025-07-20</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-difference-between-ai-safety-and-ai-security-in-customer-channels</loc>
    <lastmod>2025-07-11</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-a-modern-communications-threat-model-looks-like</loc>
    <lastmod>2025-06-28</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-financial-services-wire-verification-conversation</loc>
    <lastmod>2025-06-23</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/how-home-services-companies-get-targeted-by-lead-fraud</loc>
    <lastmod>2025-06-21</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-the-snowflake-linked-customer-breaches-say-about-vendor-communications-risk</loc>
    <lastmod>2025-06-15</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/legal-intake-lines-are-an-underestimated-attack-surface</loc>
    <lastmod>2025-06-10</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/healthcare-intake-and-the-new-class-of-ai-risks</loc>
    <lastmod>2025-05-29</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-insurance-industry-s-quiet-vishing-problem</loc>
    <lastmod>2025-05-26</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/designing-escalation-paths-that-survive-surge-events</loc>
    <lastmod>2025-05-21</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/why-verified-caller-frameworks-still-leave-gaps</loc>
    <lastmod>2025-05-08</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-quiet-risk-of-voicemail-to-text-in-intake-workflows</loc>
    <lastmod>2025-04-29</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/how-to-prepare-contact-centers-for-ai-era-abuse</loc>
    <lastmod>2025-04-27</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/ai-impersonation-across-phone-email-and-chat</loc>
    <lastmod>2025-04-19</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/lessons-from-the-recent-wave-of-ai-generated-voice-scams-targeting-families</loc>
    <lastmod>2025-04-09</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/why-traditional-cybersecurity-misses-voice-risk</loc>
    <lastmod>2025-04-06</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/intake-fraud-in-restoration-and-emergency-services</loc>
    <lastmod>2025-03-31</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/securing-franchise-communication-networks</loc>
    <lastmod>2025-03-29</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/how-to-audit-an-ai-voice-agent-before-deployment</loc>
    <lastmod>2025-03-18</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-executive-case-for-communications-resilience</loc>
    <lastmod>2025-03-06</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/social-engineering-against-virtual-agents</loc>
    <lastmod>2025-03-03</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/prompt-injection-risks-in-customer-intake</loc>
    <lastmod>2025-02-27</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/how-ai-receptionists-can-be-manipulated</loc>
    <lastmod>2025-02-14</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-hong-kong-deepfake-wire-transfer-and-what-it-changes</loc>
    <lastmod>2025-02-10</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/building-a-communications-security-program</loc>
    <lastmod>2025-02-04</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/why-omnichannel-fraud-is-hard-to-detect</loc>
    <lastmod>2025-02-02</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/synthetic-identity-attacks-in-service-businesses</loc>
    <lastmod>2025-01-26</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-problem-with-trusting-caller-id</loc>
    <lastmod>2025-01-13</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/ai-agent-red-teaming-for-voice-and-chat-systems</loc>
    <lastmod>2025-01-06</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/contact-center-resilience-during-disaster-surge-events</loc>
    <lastmod>2025-01-04</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/how-fraudsters-exploit-emergency-intake-workflows</loc>
    <lastmod>2024-12-25</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/human-ai-handoff-failure-in-customer-service</loc>
    <lastmod>2024-12-12</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/why-sms-email-chat-and-voice-must-be-secured-together</loc>
    <lastmod>2024-12-08</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/deepfake-callers-and-the-future-of-identity-verification</loc>
    <lastmod>2024-12-05</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/voice-denial-of-service-the-next-contact-center-threat</loc>
    <lastmod>2024-11-23</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-t-mobile-sim-swap-settlement-and-the-sms-trust-problem</loc>
    <lastmod>2024-11-21</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-hidden-risk-of-ai-only-customer-intake</loc>
    <lastmod>2024-11-13</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/how-contact-centers-become-attack-surfaces</loc>
    <lastmod>2024-11-11</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/why-ai-voice-agents-create-a-new-security-perimeter</loc>
    <lastmod>2024-11-05</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-is-synthetic-caller-injection</loc>
    <lastmod>2024-10-23</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-the-internet-archive-breach-tells-us-about-communications-trust</loc>
    <lastmod>2024-10-22</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-mgm-and-caesars-vishing-playbook-one-year-later</loc>
    <lastmod>2024-08-14</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/what-the-crowdstrike-outage-revealed-about-communications-surge-capacity</loc>
    <lastmod>2024-07-22</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/the-ascension-health-outage-was-a-communications-continuity-failure</loc>
    <lastmod>2024-05-17</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
  <url>
    <loc>/blog/air-canada-and-the-new-liability-of-hallucinated-ai-intake</loc>
    <lastmod>2024-02-20</lastmod>
    <changefreq>yearly</changefreq>
    <priority>0.6</priority>
  </url>
</urlset>