Skip to content

Latest commit

 

History

History
38 lines (25 loc) · 5.78 KB

07_Protect-Data-in-Transit.md

File metadata and controls

38 lines (25 loc) · 5.78 KB

Protection of Data-in-Transit

(Back)

Objective

Protect data transiting networks through the use of appropriate encryption and network safeguards.

Applicable Service Models

IaaS, PaaS, SaaS

Mandatory Requirements

Activity Validation
  • Encrypt data in transit by default (for example, Transport Layer Security (TLS) 1.2) to protect the confidentiality and integrity of data, including for all publicly accessible sites and external communications, according to the GC Web Sites and Services Management Configuration Requirements, and wherever possible for internal zone communication.
  • Confirm that TLS 1.2 or above encryption is implemented for all cloud services (via Hypertext Transfer Protocol Secure (HTTPS), TLS or another mechanism).
  • Note: while this encryption setting is often the default, cloud platforms and cloud services often have configuration options to select the permitted TLS version.
  • Use CSE-approved cryptographic algorithms and protocols in accordance with ITSP.40.111 and ITSP.40.062.
  • Leverage cryptographic algorithms and protocols configurable by the user in accordance with ITSP.40.111 and ITSP.40.062.
  • Confirm that non-person entity certificates are issued from certificate authorities that align with GC recommendations for TLS server certificates.

Additional Considerations

None

References

Related security controls from ITSG-33

IA-7, SC-12, SC-13, SC-28, SC-28(1)