network profile
| bio | website | sencedev.com |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 5 months |
| seen | Dec 29 '11 at 5:30 | |
| stats | profile views | 7 |
|
Dec 5 |
awarded | Popular Question |
|
Dec 19 |
awarded | Scholar |
|
Dec 19 |
accepted | Creating a “key server” (HIPAA compliance with AWS) |
|
Dec 16 |
comment |
Creating a “key server” (HIPAA compliance with AWS) fair enough (thanks for all your answers by the way)... is there an industry best practice for keeping keys safe then? |
|
Dec 16 |
comment |
Creating a “key server” (HIPAA compliance with AWS) Presumably there would be authentication and authorization controls so that only people authenticated through the application server could retrieve data from the encryption server. From what I have read key management is a real issue (like leaving your key in your car door after you lock it if not protected properly) so I'm trying to abstract key management into a separate service so that they keys aren't either hardcoded into my application code or stored in my database alongside the encrypted data. |
|
Dec 16 |
comment |
Creating a “key server” (HIPAA compliance with AWS) So basically from a "compliance" standpoint I don't actually have to be all that secure.. however from a moral/technical point of view is the system as described above fairly secure? |
|
Dec 15 |
awarded | Student |
|
Dec 15 |
asked | Creating a “key server” (HIPAA compliance with AWS) |
