知识卡片
企业共享治理插槽
统一流水线可预留安全与企业治理阶段,让新依赖风险出现时迅速向所有项目下发检查。触发条件应覆盖代码、模式、配置、依赖及治理规则自身变化。只在新提交时检查不能保证长期不构建的运行系统被覆盖,还需与实际部署资产核对。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
- · 企业共享治理插槽
原书出处 · 1 处
- Putting Evolutionary Architecture into Practice · 查看原书依据
In a world with automated governance, every project runs a deployment pipeline, and the security team has a “slot” in each team’s deployment pipeline where they can deploy fitness functions. Most of the time, these will be mundane checks for safeguards like preventing developers from storing passwords in databases and similar regular governance chores. However, when a zero-day exploit appears, having the same mechanism in
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第09章《Putting Evolutionary Architecture into Practice》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch09.html;段落定位:the security team has a “slot” in each team)
- 结论依据:原文对“企业共享治理插槽”的定义或案例,支撑“统一流水线可预留安全与企业治理阶段,让新依赖风险出现时迅速向所有项目下发检查”的归纳。据其上下文,触发条件应覆盖代码、模式、配置、依赖及治理规则自身变化。
- 原始内容:In a world with automated governance, every project runs a deployment pipeline, and the security team has a “slot” in each team’s deployment pipeline where they can deploy fitness functions. Most of the time, these will be mundane checks for safeguards like preventing developers from storing passwords in databases and similar regular governance chores. However, when a zero-day exploit appears, having the same mechanism in