Talk:Man-in-the-middle attack

Skip to table of contents

This is the talk page for discussing improvements to the Man-in-the-middle attack article.
This is not a forum for general discussion of the subject of the article.

Add new text under old text.
New to Wikipedia? Welcome! Learn to edit; get help.

Start a new topic

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Archives: 1, 2: 3 months

This article is rated C-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

Cryptography: Computer science Mid‑importance

	This article is within the scope of WikiProject Cryptography, a collaborative effort to improve the coverage of Cryptography on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.CryptographyWikipedia:WikiProject CryptographyTemplate:WikiProject CryptographyCryptography
Mid	This article has been rated as Mid-importance on the importance scale.
	This article is supported by WikiProject Computer science (assessed as Mid-importance).

Computer security: Computing Mid‑importance

This article is within the scope of WikiProject Computer security, a collaborative effort to improve the coverage of computer security on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.Computer securityWikipedia:WikiProject Computer securityTemplate:WikiProject Computer securityComputer security

Mid This article has been rated as Mid-importance on the project's importance scale.

This article is supported by WikiProject Computing (assessed as Mid-importance).

Things you can help WikiProject Computer security with:

How you can help:

Add to your watchlist the project talk page! Post there for help with articles or to suggest articles that need work.
Request editing suggestions on your talk page by entering WikiProject_Computer_security into this template.
Check the article alerts to participate in deletion discussions, review Good Article nominees, and review draft articles.
Edit any articles that interest you. Recommended:
- Most popular articles that need the most work (last refreshed 1 August 2026)
- Popular articles (monthly top articles by views)
- High-importance stub-quality articles
- High-importance start-quality articles
- Mid-importance stub-quality articles
- Mid-importance start-quality articles
- Unknown-importance stub-quality articles
- Unknown-importance start-quality articles
Review changes to popular articles or changes to talk pages.
Replace deprecated archival service links.
Recategorize articles in Category:Security to more specific categories
Fix something on the list of articles that need cleanup, including:
- Clarification needed
- Rewrite needed
- Expansion needed
- Style editing needed
- Update needed
- Orphaned (add links from other articles to these articles)
- Conflict of interest
- Original research
- Promotional tone
- Biographies of living persons (BLP) articles lacking sources
- Cites no sources
- Cites unreliable sources
Review unreviewed articles, if you're a new pages patroller.

Of the 3667 articles in this project 2049 or 56% are marked for cleanup, with 4257 issues in total.

Editing resources:

Biometrics are no more secure, deleted...

Latest comment: 8 months ago1 comment1 person in discussion

Most biometrics don't change; if they do, a secure-channel transfer must be made...since they are unchanging, they don't add any extra authentication security. They can just be relayed along as-is. It is generally impractical to do more than one secure channel transfer, so real-time biometrics are out. The only example I can think of that works is voice, but that is unreliable, easy to fool in only a few tries, and would rely on strings of randomly chosen words. Also, if your voice is hoarse, etc., it will lock you out. Eyes don't change, fingerprints don't change, etc. --Pokeme444 22:11, Mar 20 2010 (UTC)

https://developers.googleblog.com/upcoming-security-changes-to-googles-oauth-20-authorization-endpoint-in-embedded-webviews/ ~2026-38072 (talk) 21:08, 2 January 2026 (UTC)Reply

Any thoughts on updating the title to match industry standards?

Latest comment: 8 months ago1 comment1 person in discussion

Proposal to rename this article to better reflect modern industry standards. While "Man-in-the-middle" remains a common historical term, leading cybersecurity frameworks have transitioned to more descriptive and technically accurate terminology. Specifically, the MITRE ATT&CK framework now categorizes this technique as Adversary-in-the-middle (AiTM)^[1], while the CAPEC list identifies it as Adversary in the Middle^[2]. Additionally, "On-path attack" is frequently utilized in academic and technical documentation.^[3]. This change would align Wikipedia with the evolving nomenclature used by NIST, CISA, and major industry vendors.

Requesting community feedback on whether Adversary-in-the-middle attack or On-path attack is the more appropriate title for the primary entry. The current title would remain as a redirect to ensure historical continuity and searchability.

Please provide your rationale for either preference below to help reach a consensus.

I personally feel like it makes more sense to use Adversary-in-the-middle, as the impression I get is that it more widely used term within the cyber security community.

--Cktom (talk) 04:22, 31 January 2026 (UTC) Cktom (talk) 04:22, 31 January 2026 (UTC)Reply

References

↑ MITRE ATT&CK. "Adversary-in-the-Middle." https://attack.mitre.org/techniques/T1557/
↑ CAPEC. "CAPEC-94: Adversary in the Middle." https://capec.mitre.org/data/definitions/94.html
↑ NIST Computer Security Resource Center. "On-path Attack." https://csrc.nist.gov/glossary/term/on_path_attack

[1] MITRE ATT&CK. "Adversary-in-the-Middle." https://attack.mitre.org/techniques/T1557/

[2] CAPEC. "CAPEC-94: Adversary in the Middle." https://capec.mitre.org/data/definitions/94.html

[3] NIST Computer Security Resource Center. "On-path Attack." https://csrc.nist.gov/glossary/term/on_path_attack

[1]

[2]

[3]