Monitoring deep, dark and surface web to detect exposure of your sensitive data, secret projects and initiatives, privileged users, critical systems, IT infrastructure, and more.
Monitoring and alerting of third party data breaches impacting your employees’ emails, usernames, and personally identifiable information.
Assess the risk footprint and security posture of key business relationships to get a handle on external risk introduced through your extended attack surface.

Sign Up for Updates

Digital risk monitoring of key personnel with telemetry and risk metrics. VIPRecon provides broad coverage of social media, deep and dark web, as well as physical threat assessments.
Our Ransomware Response Readiness Assessment, Playbook and Table Top Exercise gives your organization the best chance to survive and recover.
Gain visibility of your digital footprint by reaching into the most active areas of the cyber underground.
Fully managed and tailored Threat Intelligence services that becomes an extension of your current security processes and provides real-time visibility on new threats.
Providing research and investigations into known threats, to save security teams time and stress during a cyber emergency.

Sign Up for Updates

GroupSense offers a comprehensive package of services for assessing and responding to ransomware attacks, including negotiations with threat actors.
Actively researching and monitoring threats from vendors or third-party companies that can affect organizational security.
Monitoring for threats to elections, VIPs, and more on social media to proactively prevent or mitigate digital risk.
Focusing on the threats and risks that matter to your security processes and providing intelligence and insights to prevent or mitigate digital risk.
Taking the next step in security services, by proactively taking down phishing sites or anonymously interacting with threat actors to provide better intelligence.
Active monitoring of your brand's digital assets to protect its reputation and stop further brand abuse from targeting unsuspecting victims.

Sign Up for Updates

Combining your cyber and fraud programs to effectively fight threat actors continually scamming or threatening assets within an organization.
Executives are prime targets for fraudulent activities, but with a proactive approach, any attacks or threats can be neutralized before causing any damage.
Governments, political parties and candidates must all act now to activate cyber threat intelligence services to harden their information security and get ahead of inevitable cyber threats to the election process.
3 min read

Breached Passwords and Legacy Protocols Still Defeat Azure MFA

Sep 3, 2020 10:04:24 AM

In August 2020, Microsoft posted an article focused on email authentication utilizing their Azure Active Directory (AD) authentication and the use of Multi-Factor Authentication (MFA).

The issue is in order to support legacy email protocols such as SMTP, IMAP, MAPI and POP, MFA is not supported and thus, not utilized even in an organization with Azure AD MFA required.   

This permits threat actors to log into those email accounts using single-factor authentication, bypassing any MFA security safeguards.  According to the article, the authentication protocols identified as “legacy” in Azure include:

  • Authenticated SMTP - Used by POP and IMAP clients to send email messages.
  • Autodiscover - Used by Outlook and EAS clients to find and connect to mailboxes in Exchange Online.
  • Exchange ActiveSync (EAS) - Used to connect to mailboxes in Exchange Online.
  • Exchange Online PowerShell - Used to connect to Exchange Online with remote PowerShell. If you block basic authentication for Exchange Online PowerShell, you need to use the Exchange Online PowerShell Module to connect. (For instructions, see Connect to Exchange Online PowerShell using multi-factor authentication.)
  • Exchange Web Services (EWS) - A programming interface used by Outlook, Outlook for Mac, and third-party apps.
  • IMAP4 - Used by IMAP email clients.
  • MAPI over HTTP (MAPI/HTTP) - Used by Outlook 2010 and later.
  • Offline Address Book (OAB) - A copy of address list collections downloaded and used by Outlook.
  • Outlook Anywhere (RPC over HTTP) - Used by Outlook 2016 and earlier.
  • Outlook Service - Used by the Mail and Calendar apps for Windows 10.
  • POP3 - Used by POP email clients.
  • Reporting Web Services - Used to retrieve report data in Exchange Online.
  • Other clients - Other protocols identified as utilizing legacy authentication.

This issue came to light when an organization with MFA in place received a number of spearphishing emails from an internal email address.  An investigation revealed a user from Russia logged in to the user’s email account via a legacy protocol using breached credentials.  The threat actor then had unrestricted access to the employee’s email, as only single-factor authentication was required.  The threat actor began sending spearphishing emails to organization employees.

Pre-Attack Phase

During the pre-attack phase, the organization noticed a number of failed authentication attempts using legacy protocols. This was to establish whether those protocols were supported, which would clear the way for a single-factor authentication entry into the victim’s account. 

Attack Phase

Threat actors were able to log in and access email using single-factor authentication via breached credentials. They were able to send emails under the employee’s account; this  could have resulted in significant brand damage and fraud focused on both employees and customers.

Determining if legacy authentication protocols are in use

  1. Navigate to the Azure portal > Azure Active Directory > Sign-ins.
  2. Add the Client App column if it is not shown by clicking on Columns > Client App.
  3. Add filters > Client App > select all of the legacy authentication protocols. Select outside the filtering dialog box to apply your selections and close the dialog box.

Applying this filter will permit you to review which users are utilizing legacy protocols to authenticate.  You can view additional details about the authentication by clicking on the individual users in the interface and reviewing the authentication protocol available in the Client App field.


Mitigating the risk can take two forms, directly or indirectly blocking the use of legacy authentication protocols. The process for each technique and the user impact is covered on the Microsoft advisory page.

Topics: Blog

Written by Editorial Team