知识卡片

普通读书笔记卡 · 2277.p.9

安全功能可推迟质量不可降

理解等级:高级

可以推迟当前不用的安全功能,但每个已发布功能都应有充分安全设计,不能先用有漏洞的简单方案再等下版。团队技能不足时应引入专家和成熟产品,保留对IAM替换、成本及权限模型的考虑。领导者还需平衡安全、用户体验与试验成本,例如错误提示应说明密码哪条规则未满足,而不是让用户盲猜。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

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

      In summary, handling security in a macro architecture is a complicated topic and deviates from other topics we discussed. The main idea is that it may be OK to delay the additional security features, but whichever feature you choose to support requires a deep security design. It is best to adopt a CIAM or IAM solution and build on top of that, but you must get it right the first time and enlist external expertise if you must.

    参考来源

    - 位置:《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) - 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。 - 原始内容:In summary, handling security in a macro architecture is a complicated topic and deviates from other topics we discussed. The main idea is that it may be OK to delay the additional security features, but whichever feature you choose to support requires a deep security design. It is best to adopt a CIAM or IAM solution and build on top of that, but you must get it right the first time and enlist external expertise if you must.