知识卡片

普通读书笔记卡 · 3131.a

PII分离降低集中泄漏面

理解等级:高级

先审计哪些数据敏感,再让日志、分析和交易记录尽量以不直接标识个人的ID关联,把个人身份信息PII集中在受更强保护的独立系统。需要保存的PII应加密,并让解密密钥与数据分开管理。删除或隔离PII不应破坏所有业务记录;但UUID是关联标识,不会因改名就自动彻底匿名。此处保留架构原则,不替代具体法规评估。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 宏观架构中的安全 · 查看原书依据

      The best practice is to store all sensitive data as UUIDs (for example, system or activity logs, audits, or transactions) and keep PIIs only in your IAM system. This approach limits PII storage to IAM, which you can guard with many layers of security.

    参考来源

    - 位置:《Software Architecture and Decision-Making》第08章《宏观架构中的安全》(来源项目:book-sources;源文件:extracted/Software Architecture and Decision-Making Leveraging Leadership, Technology, and Product Management to Build Great Products… (Srinath Perera)/_epub-src/ch08.xhtml) - 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。 - 原始内容:The best practice is to store all sensitive data as UUIDs (for example, system or activity logs, audits, or transactions) and keep PIIs only in your IAM system. This approach limits PII storage to IAM, which you can guard with many layers of security.