Encryption in Transit
Engineer/DeveloperSecurity Specialist
No contributors yet. Be the first to contribute!
🔑 Key Takeaway: Data crossing networks must use modern encrypted transports (TLS, SSH, VPN as appropriate); cleartext remote admin and bulk HTTP are unacceptable for sensitive systems.
Encryption in transit protects confidentiality and integrity while data moves between systems. Without it, any on-path observer on the route can read or alter traffic.
Encryption in transit refers to how data is encrypted while it flows across networks. This is important as you don't want anyone eavesdropping on your traffic, and by following best practices such as the ones below, you can reduce the risk of that:
Best practices
- Ensure that all data transmitted over the internet is encrypted using TLS/SSL.
- Use secure VPNs to encrypt data transmitted over public networks such as public WiFi.
- Use SSH for secure remote access to servers and other infrastructure.
- Use encryption protocols such as S/MIME or PGP for email communications.
Further Reading
- Encryption overview: framework map and shared concepts
- NIST SP 800-175B: guideline for using cryptographic standards in the federal government (useful baseline references)
- OWASP Cryptographic Storage Cheat Sheet