<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Social-Engineering on microsegment.io</title>
    <link>https://microsegment.io/tags/social-engineering/</link>
    <description>Recent content in Social-Engineering on microsegment.io</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 25 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://microsegment.io/tags/social-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Login Worked. The Breach Did Not.</title>
      <link>https://microsegment.io/post/2026-08-25-the-login-worked-the-breach-did-not/</link>
      <pubDate>Tue, 25 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://microsegment.io/post/2026-08-25-the-login-worked-the-breach-did-not/</guid>
      <description>&lt;p&gt;On August 22, 2026, a threat actor convinced a ReliaQuest employee to enter a password into a fake single sign-on page and approve an MFA push.&lt;/p&gt;&#xA;&lt;p&gt;The login worked.&lt;/p&gt;&#xA;&lt;p&gt;The attacker received a brief session on the identity dashboard. But the session had view-only access. Attempts to open applications were denied because the device did not meet ReliaQuest&amp;rsquo;s trust requirements. ReliaQuest then terminated the sessions, expired the password, and reset every authentication factor.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
