Vulnarex | Elite Cybersecurity Learning Platform

#The Architect's Dilemma: Form vs. Function#link

Throughout this course, we have analyzed TLS, SSH, IPsec, WPA3, OAuth, and SAML. In a real-world enterprise, you will never use just one. The challenge for a security architect is knowing which protocol solves a specific problem without introducing unnecessary complexity.

Mapping Requirements to Protocols

The choice of protocol depends on the 'entity' being secured: Is it a human, a machine, or a network tunnel?

callout

Wrong Protocol Choice $ o$ 'Security Friction.' If you use SAML for a machine-to-machine API call, your system will fail because there is no browser to handle the redirects.

Need	Recommended Protocol	Why?	Example
Employee Login to Web App	SAML / OIDC	Centralized Identity / SSO	Okta $ o$ Salesforce
Third-Party App Access	OAuth 2.0	Delegated Access / Scopes	Calendar App $ o$ Gmail
Remote Admin Access	SSH (Key-based)	Secure Shell / Tunneling	Dev $ o$ Ubuntu Server
Site-to-Site Network	IPsec VPN	Layer 3 Encryption	Branch Office $ o$ HQ
Public Guest Wi-Fi	OWE / WPA3	Passive Privacy	Airport Hotspot

As the table shows, the decision is driven by the 'Actor.' Humans interact with browsers (SAML/OIDC), admins interact with terminals (SSH), and routers interact with other routers (IPsec).

The Cost of Complexity

info

💡 Every added protocol increases the 'Attack Surface.' A system that uses SAML, OAuth, and IPsec simultaneously has three different sets of keys to manage and three different parsing libraries that could have bugs.

markdown

### Protocol Selection Logic
IF (Actor == 'User') AND (App == 'Web') $	o$ OIDC/SAML
IF (Actor == 'Service') AND (Target == 'API') $	o$ OAuth 2.0 (Client Creds)
IF (Actor == 'Network') AND (Target == 'Network') $	o$ IPsec

The logic above represents the mental model an architect uses to prevent 'Protocol Overkill'—the act of using a heavy enterprise protocol for a simple task.

Analyzing Protocol Overlap

STRICT SECURE AUDIT RULE

Beware of 'Protocol Shadowing,' where a secondary protocol is used to bypass the security of a primary one (e.g., using an insecure API key to bypass a strict OIDC login).

▪Define the actor (User vs. Machine)
▪Define the transport (Web vs. Tunnel vs. Air)
▪Select the protocol with the least friction that meets the security requirement
▪Audit the protocol's implementation for common flaws (e.g., XSW in SAML)

STRICT SECURE AUDIT RULE

The 'most secure' protocol is not always the best. If it's too hard to use, employees will find 'shadow IT' workarounds (like using personal Dropbox because the corporate SAML-VPN is too slow).

quiz BLOCK (★ 50 XP)

Your company needs to allow a third-party auditing service to read logs from your internal servers once a day. The auditor has no human user involved in the process. Which protocol is most appropriate?

Select your proof vectors above

challenge BLOCK (★ 100 XP)

The Architecture Conflict