<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://protocolreport.com/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/discord-alternatives/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/openai-hugging-face-agent-incident-investigation/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/cloud-foundry-uaa-zone-collation-bypass/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/netscaler-authentication-bypass-patch-boundary/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/sakura-internet-account-data-incident/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/zimbra-snmp-smtp-kev-response/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/entra-id-cve-exploitation-correction/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/trueconf-server-phantomcore-incident-response/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/telegram-mini-app-local-storage-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/atlassian-august-2026-dependency-patch-triage/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/whatsapp-scam-alert-on-device-privacy/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/cisco-secure-workload-hardening-upgrade/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/ray-cve-2025-62593-kev-response/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/gitlab-graphql-public-project-patch/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/threema-ddos-outage-messaging-continuity/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/safepal-order-tracking-data-breach/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/google-cloud-pqc-tls-rollout/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/ringcentral-contact-data-breach-response/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/pass-ta-key-google-synced-passkey-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/macos-screen-sharing-cve-2026-65400-exploitation/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/sap-commerce-cloud-cve-2026-58231-redeploy/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/zoom-annotation-rce-client-patch-boundary/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/wpmanageninja-plugin-update-compromise-recovery/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/trezor-shipmonk-customer-data-breach/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/vcenter-cve-2026-59310-incident-response/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/metabase-cve-2026-72898-incident-response/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/cisco-asa-ftd-cve-2026-20349-vpn-dos/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/windows-afd-cve-2026-68820-active-exploitation/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/microsoft-teams-august-2026-security-boundaries/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/loadmaster-cve-2026-8037-active-exploitation/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/teamcity-cve-2026-63077-active-exploitation/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/n-central-cve-2026-18577-incident-response/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/aisi-agent-evaluation-egress-incident/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/hollowgraph-microsoft-365-calendar-c2/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/openssl-hollowbyte-memory-exhaustion/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/entra-passkey-default-sms-voice-retirement/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/cross-platform-rcs-encryption-rollout/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/avi-load-balancer-control-plane-patch/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/signal-vs-whatsapp-privacy-comparison/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/fortisandbox-active-exploitation-response/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/ey-support-ticket-tax-data-breach/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/zoom-windows-account-takeover-patch/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/sharefile-storage-zones-emergency-patch-recovery/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/sonicwall-sma1000-exploitation-forensic-triage/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/eu-eprivacy-encrypted-chat-vote/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/sharepoint-cve-2026-56164-active-exploitation/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/adfs-dkm-acl-zero-day-hardening/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/russian-router-snmp-hygiene-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/vpn-kill-switch-failure-mode-testing/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/moveit-transfer-july-2026-security-fixes/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/cisco-ise-july-2026-patch-gap/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/slash-commands-authorization-boundary/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/guest-accounts-expiration-access-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/screen-sharing-collaboration-data-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/chat-exports-community-data-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/webhook-signatures-community-integration-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/break-glass-admin-accounts-community-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/mobile-app-logs-chat-privacy-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/oauth-redirect-uri-community-app-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/russian-messaging-phishing-backup-key-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/bot-token-rotation-community-security/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/whatsapp-usernames-contact-boundary-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/disappearing-messages-retention-policy-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/mfa-push-prompts-identity-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/rate-limits-community-bot-security/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/presence-read-receipts-chat-metadata/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/moderation-logs-community-security-data/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/chat-attachments-storage-boundary/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/vpn-dns-leaks-resolver-policy/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/dkve-key-verification-social-graph-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/mls-group-chat-protocol-integration-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/push-notifications-secure-chat-platform-boundary/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/split-tunnel-vpn-routing-access-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/cisco-sdwan-manager-zero-day-control-plane-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/stockstay-turla-endpoint-messaging-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/external-collaboration-channel-boundary/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/scim-deprovisioning-community-access-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/webmcp-tool-metadata-trust-boundary/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/oauth-consent-community-app-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/post-quantum-tls-certificate-gap/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/age-assurance-community-identity-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/infinitered-redcap-workspace-exfiltration/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/autojack-agent-localhost-control-plane-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/linked-devices-chat-endpoint-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/meeting-transcripts-collaboration-record-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/apple-intelligence-token-replay-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/chat-bridges-private-room-trust-boundary/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/rogueplanet-defender-zero-day-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/link-previews-chat-fetch-surface/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/telegram-neet-editing-restriction-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/searchleak-copilot-enterprise-search-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/encrypted-chat-backups-recovery-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/private-community-invite-links-access-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/chrome-v8-zero-day-session-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/oracle-peopletools-rce-patch-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/fable-mythos-access-suspension-ai-safety/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/yellowkey-bitlocker-physical-access-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/webhook-urls-community-secret-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/encrypted-spaces-e2ee-collaboration-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/token-gated-discord-signature-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/bot-permissions-community-admin-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/wallet-token-approval-drainer-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/whatsapp-nso-spyware-phishing-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/check-point-vpn-ikev1-auth-bypass/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/gemini-notification-injection-agent-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/codex-ui-token-theft-ai-supply-chain/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/instagram-password-reset-leak-patched/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/silent-ransom-group-it-impersonation/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/hp-poly-voip-cve-2026-0826/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/microsoft-365-android-token-flaw/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/cisco-unified-cm-webdialer-ssrf/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/zcash-orchard-forgery-opus-48/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/github-dev-token-theft-browser-ide-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/http2-bomb-header-limits-availability-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/red-hat-npm-provenance-gap/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/android-linux-kev-patch-triage/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/dashlane-brute-force-vault-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/storm-2949-sspr-cloud-breach/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/passkeys-account-recovery-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/post-quantum-messaging-migration/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/discord-e2ee-voice-video-default/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/instagram-encrypted-dms-removed/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/globalprotect-cookie-bypass-vpn-risk/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/composio-ai-connector-token-incident/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/glassworm-developer-botnet-takedown/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/google-workspace-dbsc-session-cookie-theft/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/github-enterprise-signing-key-rotation/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/whatsapp-encryption-lawsuit-privacy-claims/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/kali365-microsoft-365-oauth-token-phishing/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/privage-vs-discord-security-privacy-comparison/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/end-to-end-encryption-failing-ux-test/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/slack-vs-signal-enterprise-security-review/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/best-discord-alternatives-communities-teams-private-groups/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/zero-log-claims-under-pressure-2024-server-seizure-report/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/misconfigured-s3-buckets-automated-exploitation-crisis/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/blog/bypassing-biometrics-synthetic-identity-injections/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/comparisons/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/methodology/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/about/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/contact/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/editorial-process/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/legal/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/privacy/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/terms/</loc>
  </url>
  <url>
    <loc>https://protocolreport.com/reviews/slack-vs-signal/</loc>
  </url>
</urlset>
