若為簽名加密失敗，會提高強力攻擊的成功機率。
MessageProtectionOrder 屬性允許您指定應用簽名和加密的順序（以及是否應對簽名進行加密）。將 MessageProtectionOrder 屬性設為 SignBeforeEncryptAndEncryptSignature 以外的任何其他值，都會構成潛在的安全問題。
下面列出了 SignBeforeEncryptAndEncryptSignature 可能的替代設置及其相關問題。
SignBeforeEncrypt - 對未加密的消息應用簽名，但不對簽名本身進行加密。
EncryptBeforeSign - 對消息的內容進行加密，然后簽名。
采用低熵密鑰（例如密碼）進行簽名的消息，更容易受到強力攻擊。
[1] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A10 Insecure Configuration Management
[2] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A6 Security Misconfiguration
[3] Standards Mapping - OWASP Top 10 2007 - (OWASP 2007) A8 Insecure Cryptographic Storage
[4] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP3150.1 CAT II
[5] Standards Mapping - Security Technical Implementation Guide Version 3.4 - (STIG 3.4) APP3150.1 CAT II
[6] Standards Mapping - FIPS200 - (FISMA) CM
[7] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 311
[8] Standards Mapping - Web Application Security Consortium 24 + 2 - (WASC 24 + 2) Information Leakage
[9] MessageProtectionOrder Enumeration Microsoft
[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 6.3.1.3, Requirement 6.5.8
[13] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 6.5.10
[14] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 - (PCI 2.0) Requirement 6.5.3