for device to device communication. Protection.33 Authenticator Feedback The organization DHS 2.15.13 obscure the feedback of authentication information during the authentication process. Protection.34 Cryptographic Module The DM system DHS 2.15.14 Authentication components shall employ cryptographic module authentication for authenticating users and devices. Protection.35 Information Flow The organization enforces DHS 2.15.15 Enforcement the flow of information within the DM system based on applicable policy. Organizations shall place software or hardware firewalls at designated network segment boundaries that serve as choke points for filtering information across field and central devices. Protection.36 Password Management The system provides the DHS 2.15.16 necessary capabilities to enforce the use of strong passwords, in accordance with FIPS 112, and to protect passwords from potential exposure. This includes: 1. Ensuring that passwords never cross component boundaries in the clear. 2. Ensuring that all stored passwords are encrypted in accordance with FIPS 140-2 or hashed using a cryptographic one-way hash function in accordance with FIPS 180-2. 3. Ensuring that passwords are never included in or allowed to be embedded into tools,
for device to device communication. Protection.33 Authenticator Feedback The organization obscure the feedback of authentication information during the authentication process. DHS 2.15.13 Protection.34 Cryptographic Module Authentication The DM system components shall employ cryptographic module authentication for authenticating users and devices. DHS 2.15.14 Protection.35 Information Flow Enforcement The organization enforces the flow of information within the DM system based on applicable policy. Organizations shall place software or hardware firewalls at designated network segment boundaries that serve as choke points for filtering information across field and central devices. DHS 2.15.15 Protection.36 Password Management The system provides the necessary capabilities to enforce the use of strong passwords, in accordance with FIPS 112, and to protect passwords from potential exposure. This includes: 1. Ensuring that passwords never cross component boundaries in the clear. 2. Ensuring that all stored passwords are encrypted in accordance with FIPS 140-2 or hashed using a cryptographic one-way hash function in accordance with FIPS 180-2. 3. Ensuring that passwords are never included in or allowed to be embedded into tools, DHS 2.15.16
DM%20Security%20Profile%20-%20v1_0%20-%2020120220.docx