The best way to protect sensitive information is to not store it in the first place. Minimise the Storage of Sensitive Information ¶ For example, hardware level encryption is effective at protecting against the physical theft of the server, but will provide no protection if an attacker is able to compromise the server remotely. Which layer(s) are most appropriate will depend on the threat model. At the hardware level (e.g, encrypted RAID cards or SSDs).At the filesystem level (e.g, BitLocker or LUKS).At the database level (e.g, SQL Server TDE).Where to Perform Encryption ¶Įncryption can be performed on a number of levels in the application stack, such as: The Secrets Management Cheat Sheet contains further guidance on this topic. Note that many cloud environments provide these services, so these should be taken advantage of where possible. The use of dedicated secret or key management systems can provide an additional layer of security protection, as well as making the management of secrets significantly easier - however it comes at the cost of additional complexity and administrative overhead - so may not be feasible for all applications. This process should begin with considering the threat model of the application (i.e, who you are trying to protect that data against). The first step in designing any application is to consider the overall architecture of the system, as this will have a huge impact on the technical implementation. The Password Storage Cheat Sheet contains further guidance on storing passwords. Passwords should not be stored using reversible encryption - secure password hashing algorithms should be used instead. This article provides a simple model to follow when implementing solutions to protect data at rest. Insecure Direct Object Reference PreventionĬryptographic Storage Cheat Sheet ¶ Introduction ¶ Minimise the Storage of Sensitive Information
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |