An adversary-in-the-middle attack puts an attacker between a person and the service they are trying to access. The attacker may relay a sign-in, capture credentials or an authenticated session, and try to use that access. Your organization should assess its exposure by reviewing sign-in routes, device controls, session protections, and its ability to respond.
In This Article
What happens during an adversary-in-the-middle attack?

“John brought the right knowledge to my issue and resolved it in about a reasonable amount of time. I walked away confident the problem was actually fixed.”
A user thinks they are signing in to a familiar service. The attacker has placed an intermediary in the connection, often by directing the user to a deceptive sign-in page or through another redirection.
The intermediary can relay the sign-in exchange as it happens. If the user enters a password and responds to a multifactor authentication (MFA) prompt, the attacker may capture the resulting session token. That token can represent an already authenticated session, so the attacker may try to use it without repeating the original sign-in.
This differs from simply guessing a password. The exposure depends on how identity, devices, and sessions are managed, as well as what an account can reach after sign-in. MFA remains an important control, but its presence alone does not show whether sessions are protected against interception or misuse.
Review both the account and the resources it can access. A compromised session could expose email, files, administrative functions, or connected business applications, depending on the account's permissions. The business impact therefore depends not only on how the attacker obtained access, but also on the account's privileges and the information or processes it can reach.
Security teams should distinguish between stolen credentials and misuse of a session that has already passed authentication. The distinction helps determine which evidence to review and which containment steps may be needed. For example, changing a password may not be the only action to consider if an active session could remain valid.
Assess two points in the access path: the sign-in and the session that follows.
Takeaway: Check what happens before and after authentication, not only whether MFA is enabled.
How could an attacker get between a user and a service?
An attacker may direct a user to an intermediary that looks like part of an ordinary sign-in. A link in a message, a lookalike page, or a redirection can create the opening. The method varies, so examine how users reach sign-in pages and how browsers and devices establish trusted connections.
Access conditions differ across managed devices, personal devices, public networks, and corporate networks. Each setting provides a different level of visibility and control. Review the ways employees actually connect, including remote access and devices that the organization does not manage.
Check which signals your identity platform can use to control access, such as device condition or sign-in risk. Also identify which applications accept the same identity session and whether sensitive actions call for additional verification. Document exceptions as well as standard policies: a control that applies to most users may not cover every account or access route.
A connection that appears technically valid does not, by itself, establish that a sign-in is safe. Know how your team detects unusual activity, handles suspicious sessions, and tells affected users what to do. Staff should have a simple way to report a prompt they did not initiate without having to decide whether an attack succeeded.
Include third-party and business-critical applications in the review when they use the same identity provider. An account may have access to information outside the main email or file platform, and that access may be governed by a separate application owner. Confirm who can review the relevant records and revoke access if needed.
Takeaway: Map the routes employees use to reach business systems, including less-managed access.
What should an organization assess first?
Start by listing identity providers, business applications, privileged accounts, and sign-in methods. Mark the services that contain sensitive information or support important workflows, then record how employees and administrators access them.
Review the rules that govern access after sign-in. Confirm where MFA is required, what additional protections apply to privileged accounts, and whether your team can revoke sessions promptly. Make sure the people responsible for those decisions are known and available during an incident.
Check the devices and browsers employees use, how they are maintained, and what guidance staff receive about suspicious links and sign-in prompts. The help desk should have a clear process for reporting a possible account compromise and escalating it to the right people.
Then exercise the response process without attempting an unapproved live attack. In a tabletop exercise, walk through a report of a suspected stolen session: who validates it, who can restrict access, who reviews activity, and who makes business decisions? Record gaps, owners, and follow-up actions.
Make the review practical by noting the evidence available to the people who will respond. Can they see recent sign-ins, application access, authentication changes, and session activity? Are those records available to the right responders, and do they know how to preserve them? A written answer is useful only if it matches the tools and permissions people actually have.
- Inventory identity systems, applications, privileged accounts, and access routes.
- Review MFA, session controls, device requirements, and access to sensitive services.
- Confirm that staff know how to report suspicious prompts and sign-in activity.
- Walk through the response process and assign owners to any gaps.
Prioritize findings by the business processes and information at risk, not simply by the number of controls listed. An administrative account, for example, deserves attention based on what it can reach and who can act if it is compromised. Give each finding an owner and a next step so the assessment can lead to a measurable improvement.
An assessment is useful when it connects controls to people who can act and response steps the organization has practiced.
What signs could point to session or account misuse?
An unfamiliar sign-in or a single alert does not prove that an adversary-in-the-middle attack occurred. Check the surrounding activity, especially if a user reports an unexpected MFA prompt, a sign-in reached through an unusual link, or a session they do not recognize.
Review sign-ins that do not fit the user's normal work, changes to authentication methods, new forwarding rules, unfamiliar application permissions, or access to resources the user does not typically use. Each signal can have a legitimate explanation. Compare it with the user's work and the available audit records before drawing a conclusion.
Ask the affected person what they saw and when. Do not ask them to send passwords or session tokens. Preserve relevant logs and notes according to your incident procedures, and avoid deleting evidence during an initial cleanup.
Keep a timeline of what was reported, what records were reviewed, and which containment decisions were made. That record helps responders coordinate their work and gives business leaders a clearer view of what is known, what remains uncertain, and what needs follow-up.
A professional services client, Madhav, described the value of clear communication during technical support: "John brought the right knowledge to my issue and resolved it in about a reasonable amount of time. I walked away confident the problem was actually fixed." In a security review, explaining what was checked and what remains open gives decision-makers a clearer basis for action.
Takeaway: Treat unusual activity as a reason to validate the evidence, not as a diagnosis on its own.
What should we do if we suspect an intercepted session?
Follow your incident response process and involve the people responsible for identity, security, and business operations. If a session may still be active, use approved identity controls to remove access. Depending on the situation, that may mean revoking sessions or disabling the affected account.
Reset credentials through the trusted identity service, not through a link in a suspicious message. Coordinate any changes to authentication methods, application permissions, or forwarding rules with the incident lead, and preserve relevant evidence before making changes that could affect the investigation.
Review activity during the suspected exposure period. Determine which resources the account accessed, whether other accounts or systems may be involved, and whether the business needs temporary safeguards. If a privileged account is affected, assess the systems it could reach before treating the incident as contained.
Coordinate recovery with the owners of affected systems. Restricting access can disrupt work, so balance containment with the needs of staff, customers, and critical services. Keep business owners informed as the scope becomes clearer.
After access is contained, confirm that the user can return to work through a trusted sign-in route and that any required credentials or authentication methods have been reset safely. Review the cause and update access policies, user guidance, or response procedures where the investigation identifies a gap. Close the loop with affected stakeholders so they understand what was done and what remains to monitor.
GDS Technology helps organizations assess cybersecurity risks and plan for incidents. Its work can connect with broader cybersecurity services, IT compliance support, and disaster recovery planning. The team works with clients across Georgia, Indiana, and nationwide.
Takeaway: Contain access, preserve evidence, and coordinate recovery with the owners of affected business processes.
Frequently Asked Questions
Does multifactor authentication stop adversary-in-the-middle attacks?
MFA makes account access harder when a password alone is exposed, but it does not by itself eliminate the risk of an intercepted session. Some attacks relay a user's authentication in real time and attempt to capture the resulting session. Review identity, device, and session controls alongside MFA, and make sure the response team can revoke access quickly.
Should a small organization assess this risk?
Yes, if staff use cloud accounts, remote access, or business applications that rely on sign-in sessions. Begin with the systems that support sensitive information, payments, administration, or daily operations. A focused review can identify who owns access decisions, what controls are in place, and how the organization would respond to a suspected compromised account.
What is the first action after a suspicious sign-in?
Report it through the organization's established security or IT channel and avoid interacting further with suspicious links or prompts. The incident lead should validate the activity using trusted identity and audit records, then decide whether to revoke sessions, reset credentials, or restrict access. Preserve relevant evidence and coordinate any interruption with affected business owners.
Can changing a password alone end a suspected session compromise?
Do not assume a password change alone has removed every possible avenue of access. The response lead should use the identity provider's approved controls to revoke sessions where appropriate, review authentication methods and connected applications, and inspect activity for signs of continued access. Coordinate the steps with the incident process and confirm that the affected user can sign in safely afterward.
Follow GDS Technology on Facebook, and subscribe on YouTube for new videos.