...
Note that this rule lacks any assumptions about the integrity of the data being sent down a socket. For information about ensuring data integrity, see rule SER02-J. Sign then seal sensitive objects before sending them outside a trust boundary.
Noncompliant Code Example
This noncompliant code example shows the use of regular sockets for a server application that fails to protect sensitive information in transit. The insecure code for the corresponding client application follows the server's code.
...
Note that the sockets are properly closed in accordance with rule ERR05-J. Do not let checked exceptions escape from a finally block.
Compliant Solution
This compliant solution uses SSLSocket to protect packets using the SSL/TLS security protocols.
...
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="52c10914eee2be94-bd6e833a-474544dd-9c62abcf-608fccddeb0a2713f211ff7e"><ac:plain-text-body><![CDATA[ | [[API 2006 | AA. References#API 06]] |
| ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="bbc2b2bf7846f7aa-e39ba3bd-43c74d5f-a39f9a06-cef9897cca00b13b9e900058"><ac:plain-text-body><![CDATA[ | [[Gong 2003 | AA. References#Gong 03]] | 11.3.3, Securing RMI Communications | ]]></ac:plain-text-body></ac:structured-macro> |
<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="cf798d75c69f0910-2139540f-483340c1-979a8a16-8c2be51e13a960825c24856c"><ac:plain-text-body><![CDATA[ | [[Ware 2008 | AA. References#Ware 08]] |
| ]]></ac:plain-text-body></ac:structured-macro> |
...