New doc: GDPR support in ASP.NET Core #6516
Conversation
|
Recommended Ordering:
|
aspnetcore/security/gdpr.md
Outdated
|
|
||
| ## Essential cookies | ||
|
|
||
| If tracking is disabled, only cookies marked essential are sent to the browser. The following code makes a cookie essential: |
There was a problem hiding this comment.
If consent has not been given...
|
Don't mention encryption, until I have a sample I'm happy with. We'll use that to create a document all on it's own. You could however add a paragraph like the following, Some databases or storage mechanisms allow for encryption at rest, encrypting your stored data with no work needed for any software that accesses the data. This is, by far, the easiest and safest option, let the database manage keys and encryption for you. For example, Microsoft SQL and Azure SQL provide Transparent Data Encryption (TDE), and Azure has encrypted SQL database by default since May 2017, as well as encrypting blobs, files, tables and queue storage since August 2017. For databases that don't provide built-in encryption at rest you may be able to use disk encryption, such as Bitlocker to provide the same protections. Linux has encrypted file systems so as eCryptfs and EncFS. |
|
Should we highlight that the delete and download only touch the default identity data, and needs to be extended out as soon as you start storing other things? Also mention cascading deletes - https://github.com/aspnet/Identity/issues/1797#issuecomment-391052520 |
Fixes #5400
Review URL