Weak WS-SecurityPolicy: Insecure Transport

ABSTRACT

應用程序配置應確保使用 HTTPS 傳輸所有敏感信息。

EXPLANATION

如果處理敏感信息的應用程序不使用消息級加密方式，則應只允許其通過加密的傳輸通道進行通信。

例 1：以下傳輸綁定使用 HTTP 而不是 HTTPS：

<sp:TransportBinding>
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpToken/>
</wsp:Policy>
</sp:TransportToken>
    ...
</sp:TransportBinding>

REFERENCES

[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 254

[8] Standards Mapping - SANS Top 25 2009 - (SANS 2009) Insecure Interaction - CWE ID 319

[9] Standards Mapping - Web Application Security Consortium 24 + 2 - (WASC 24 + 2) Insufficient Authentication

[10] Standards Mapping - SANS Top 25 2010 - (SANS 2010) Porous Defenses - CWE ID 311

[11] Standards Mapping - SANS Top 25 2011 - (SANS Top 25 2011) Porous Defenses - CWE ID 311

[12] 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

[13] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 4.1, Requirement 6.5.10

[14] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 - (PCI 2.0) Requirement 4.1, Requirement 6.5.4

[15] SALT WSSP 1.2 Policy File Example Oracle

[16] WS-SecurityPolicy 1.2 OASIS

97av