應用程序通過配置應確保 SSL 被用于所有的訪問受控頁面。
如果應用程序使用 SSL 來保證與客戶端瀏覽器之間的機密通信，那么應用程序的配置應該規定：如果不使用 SSL，就無法查看任何訪問受控頁面。
通常有以下三種方式來繞開 SSL：
－ 用戶手動輸入 URL，且該 URL 的類型是 "HTTP" 而不是 "HTTPS"。
－ 攻擊者故意將一個不安全的 URL 發送給用戶。
－ 程序員在應用程序中錯誤地創建了一個與頁面相關的鏈接，使之未能從 HTTP 轉換成 HTTPS。（這種情況很容易發生，尤其是在一個網站上，鏈接在公開區域與安全區域之間移動的時候。）
[1] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A10 Insecure Configuration Management
[2] Standards Mapping - OWASP Top 10 2007 - (OWASP 2007) A9 Insecure Communications
[3] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A9 Insufficient Transport Layer Protection
[4] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP3250.1 CAT I, APP3250.2 CAT I, APP3250.3 CAT II, APP3250.4 CAT II
[5] Standards Mapping - Security Technical Implementation Guide Version 3.4 - (STIG 3.4) APP3250.1 CAT I, APP3250.2 CAT I, APP3250.3 CAT II, APP3250.4 CAT II
[6] Standards Mapping - FIPS200 - (FISMA) CM, SC
[7] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 5
[8] Standards Mapping - Web Application Security Consortium 24 + 2 - (WASC 24 + 2) Information Leakage
[9] A. Taylor et al. J2EE & Java:Developing Secure Web Applications with Java Technology (Hacking Exposed) Osborne/McGraw-Hill
[10] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 - (PCI 1.2) Requirement 4.1, Requirement 6.3.1.4, Requirement 6.5.9
[11] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 4.1, Requirement 6.5.10
[12] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 - (PCI 2.0) Requirement 4.1, Requirement 6.5.4