<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>Fctr Blog</title>
  <subtitle>Identity threats and support operations.</subtitle>
  <link href="https://fctr.io/blog/" />
  <link href="https://fctr.io/blog/rss.xml" rel="self" type="application/atom+xml" />
  <id>https://fctr.io/blog/</id>
  <updated>2026-10-29T00:00:00.000Z</updated>
  
  <entry>
    <title>A Practical Guide to IT Caller Verification</title>
    <link href="https://fctr.io/blog/test-it-caller-verification/" />
    <id>https://fctr.io/blog/test-it-caller-verification/</id>
    <published>2026-10-20T00:00:00.000Z</published>
    <updated>2026-10-20T00:00:00.000Z</updated>
    <summary>Three practical checks for IT caller verification: can employees find the trusted app, complete the check, and stop safely when verification fails?</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>Introducing Netra: an AI agent for Microsoft Entra ID</title>
    <link href="https://fctr.io/blog/introducing-netra-ai-microsoft-entra-id/" />
    <id>https://fctr.io/blog/introducing-netra-ai-microsoft-entra-id/</id>
    <published>2026-10-11T00:00:00.000Z</published>
    <updated>2026-10-11T00:00:00.000Z</updated>
    <summary>Get answers about your Microsoft Entra ID tenant in plain English. Meet Netra AI, a self-hosted agent for directory questions, follow-ups, and CSV exports.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>IT caller verification: a takeaway from Okta Threat Intelligence.</title>
    <link href="https://fctr.io/blog/okta-mfa-downgrade-caller-verification/" />
    <id>https://fctr.io/blog/okta-mfa-downgrade-caller-verification/</id>
    <published>2026-10-07T00:00:00.000Z</published>
    <updated>2026-10-07T00:00:00.000Z</updated>
    <summary>Okta recommends a way to verify IT support callers as attackers push MFA downgrades. See how Fctr fits alongside strong authentication policies.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>Gartner reports deepfake social engineering during employee calls.</title>
    <link href="https://fctr.io/blog/gartner-deepfake-caller-verification/" />
    <id>https://fctr.io/blog/gartner-deepfake-caller-verification/</id>
    <published>2026-09-22T00:00:00.000Z</published>
    <updated>2026-09-23T00:00:00.000Z</updated>
    <summary>Gartner reports deepfake social engineering on employee calls. See how Fctr verifies callers and protects supported helpdesk actions using existing factors.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>ClickFix and fake IT support: before you run the fix.</title>
    <link href="https://fctr.io/blog/clickfix-fake-it-support/" />
    <id>https://fctr.io/blog/clickfix-fake-it-support/</id>
    <published>2026-09-16T00:00:00.000Z</published>
    <updated>2026-09-16T00:00:00.000Z</updated>
    <summary>ClickFix can turn fake IT support into malicious command execution. See how Fctr helps employees verify IT callers before following instructions.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>Microsoft Entra Verified ID was built for identity verification.</title>
    <link href="https://fctr.io/blog/microsoft-entra-verified-id-identity-verification/" />
    <id>https://fctr.io/blog/microsoft-entra-verified-id-identity-verification/</id>
    <published>2026-09-08T00:00:00.000Z</published>
    <updated>2026-09-08T00:00:00.000Z</updated>
    <summary>Learn how Microsoft Entra Verified ID differs from authentication factors, why it is practical for Microsoft environments, and how Fctr brings it into helpdesk workflows.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>A Microsoft Teams call is not proof that the caller is IT.</title>
    <link href="https://fctr.io/blog/spring-ring-microsoft-teams-vishing/" />
    <id>https://fctr.io/blog/spring-ring-microsoft-teams-vishing/</id>
    <published>2026-09-02T00:00:00.000Z</published>
    <updated>2026-10-29T00:00:00.000Z</updated>
    <summary>Microsoft and Unit 42 document IT support impersonation through Teams. Learn how to verify callers before remote access, with lessons from Spring Ring.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>The signals looked legitimate. The person was not verified.</title>
    <link href="https://fctr.io/blog/fake-it-support-verify-person-not-channel/" />
    <id>https://fctr.io/blog/fake-it-support-verify-person-not-channel/</id>
    <published>2026-08-27T00:00:00.000Z</published>
    <updated>2026-08-30T00:00:00.000Z</updated>
    <summary>ReliaQuest and Expel documented IT-impersonation attacks involving real MFA and Microsoft systems. McKesson later confirmed a separate data-exfiltration incident.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>Email bombing creates the crisis. Fake IT support arrives with the fix.</title>
    <link href="https://fctr.io/blog/email-bombing-fake-it-support-verification/" />
    <id>https://fctr.io/blog/email-bombing-fake-it-support-verification/</id>
    <published>2026-08-20T00:00:00.000Z</published>
    <updated>2026-10-29T00:00:00.000Z</updated>
    <summary>Email bombing can create urgency before an attacker impersonates IT in Teams and asks for Quick Assist. Verify the support caller before remote access begins.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>UNC6671 is calling employees at financial firms and posing as IT.</title>
    <link href="https://fctr.io/blog/helpdesk-caller-id-passkey-vishing/" />
    <id>https://fctr.io/blog/helpdesk-caller-id-passkey-vishing/</id>
    <published>2026-08-06T00:00:00.000Z</published>
    <updated>2026-10-29T00:00:00.000Z</updated>
    <summary>Mandiant tracks fake IT calls using passkey and MFA changes as a pretext. Canada&#39;s Cyber Centre now warns legal and financial firms to verify unexpected IT calls.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>The unlock button should come after verification.</title>
    <link href="https://fctr.io/blog/account-unlock-verification-workflow/" />
    <id>https://fctr.io/blog/account-unlock-verification-workflow/</id>
    <published>2026-08-05T00:00:00.000Z</published>
    <updated>2026-09-11T00:00:00.000Z</updated>
    <summary>Verify the employee before unlocking an account. See a helpdesk workflow using existing Entra ID or Okta factors, role checks, and connected audit evidence.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>The sign-in page was real. The caller wasn&#39;t.</title>
    <link href="https://fctr.io/blog/device-code-vishing-caller-verification/" />
    <id>https://fctr.io/blog/device-code-vishing-caller-verification/</id>
    <published>2026-08-05T00:00:00.000Z</published>
    <updated>2026-09-11T00:00:00.000Z</updated>
    <summary>Microsoft reports passkey-themed vishing that leads to device code phishing. Learn how to verify IT support callers before following sign-in instructions.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
  <entry>
    <title>Your mother&#39;s maiden name is not verification.</title>
    <link href="https://fctr.io/blog/security-questions-helpdesk-verification/" />
    <id>https://fctr.io/blog/security-questions-helpdesk-verification/</id>
    <published>2026-08-05T00:00:00.000Z</published>
    <updated>2026-09-11T00:00:00.000Z</updated>
    <summary>How should a helpdesk verify a caller before a password reset? Use a trusted employee record, an approved factor, and a policy-controlled recovery workflow.</summary>
    <author><name>Fctr Identity</name></author>
  </entry>
  
</feed>
