Security notes / data-at-rest encryption: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
Line 1: | Line 1: | ||
{{SecurityRelated}} | {{SecurityRelated}} | ||
{{stub}} | |||
Data at rest, | |||
====Data at rest, or data in flight==== | |||
Encryption generally protects either data only at rest, or data only in flight (e.g. HTTP / TLS). | |||
Why not both? While you ''could'' base both on much the same underlying code, they are different purposes, and have practicalities different enough in the security and privacy implications, and how to use them well for those purposes. | |||
You might as well have two different specializations. | |||
Revision as of 11:43, 25 September 2023
Security related stuff.
Securing services
Unsorted - · Anonymization notes · website security notes · integrated security hardware · Glossary · unsorted |
✎ This article/section is a stub — some half-sorted notes, not necessarily checked, not necessarily correct. Feel free to ignore, or tell me about it.
Data at rest, or data in flight
Encryption generally protects either data only at rest, or data only in flight (e.g. HTTP / TLS).
Why not both? While you could base both on much the same underlying code, they are different purposes, and have practicalities different enough in the security and privacy implications, and how to use them well for those purposes.
You might as well have two different specializations.
On hard drive encryption
Do I need it?
For a practical view, see Security notes - security for the everyday person