Sync: add container security notes
This commit is contained in:
44
wiki/log.md
44
wiki/log.md
@@ -1,3 +1,47 @@
|
||||
## [2026-04-24] ingest | CTP Topic 49 Container Lifecycle Hardening Standards
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/07_Security/ctp-topic-49-container-lifecycle-hardening-standards.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Micro Focus 产品安全小组 Ashish 主讲,容器镜像构建阶段 11 条安全加固标准——基础镜像选择、Init 系统(tini 防止僵尸进程)、只读根文件系统(readOnlyRootFilesystem: true)、emptyDir Volume、禁用 Kubernetes API 自动挂载(automountServiceAccountToken: false)、私有服务账号+RBAC、避免 hostNetwork/hostPort
|
||||
- Concepts created: [[Container-Lifecycle-Hardening]], [[Pod-Security-Context]], [[emptyDir-Volume]]
|
||||
- Entities created: [[Ashish]], [[Product-Security-Group]], [[tini]]
|
||||
- Source page: wiki/sources/ctp-topic-49-container-lifecycle-hardening-standards.md
|
||||
- Notes: 与 [[ctp-topic-39-implementing-eks-in-the-aws-lab-landing-zone]] 就 hostNetwork 配置存在场景冲突(Topic 39 Lab 环境特例 vs Topic 49 通用最佳实践);检测到 3 个潜在概念(Container-Lifecycle-Hardening/Pod-Security-Context/emptyDir-Volume)和 3 个实体(Ashish/Product-Security-Group/tini),均已创建 Entity/Concept 页面;overview.md 已更新
|
||||
|
||||
## [2026-04-14] ingest | CTP Topic 21 Supply Chain Security in Micro Focus
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/07_Security/ctp-topic-21-supply-chain-security-in-micro-focus.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: Micro Focus 软件供应链安全新方法——供应链(产品层面)涵盖 SCM/CI/CD 全环节;驱动因素:SolarWinds 攻击事件、美国网络安全行政命令、AWS/SaaS 迁移风险;安全观念转变:从 99% 关注研发安全转向全生命周期防护;供应链安全成为 SDL 第五支柱,强调 CI 和 CD 过程完整性
|
||||
- Concepts identified: [[Supply Chain Security(供应链安全)]], [[SolarWinds Hack]], [[CI/CD Security]], [[SDL(Security Development Lifecycle)]], [[Executive Order on Cybersecurity]], [[Lateral Movement]]
|
||||
- Entities identified: [[Micro Focus]], [[Shlomi Ben-Hur]]
|
||||
- Source page: wiki/sources/ctp-topic-21-supply-chain-security-in-micro-focus.md
|
||||
- Notes: 无冲突检测;Micro Focus 已在多处来源提及但无独立 Entity 页面,本次补充创建;SolarWinds/Shlomi Ben-Hur 仅出现一次,不满足 Entity 创建条件
|
||||
|
||||
## [2026-04-24] ingest | CTP Topic 52 3 Lines of Defence (3LoD) Framework Cloud Security Posture Management
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/07_Security/ctp-topic-52-3-lines-of-defence-3lod-framework-cloud-security-posture-management.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: 3LoD 安全治理框架落地(业务单元→集团职能部门→审计三层责任分层)+ Cloud Guard CSPM 工具选型(态势管理/资产管理/网络可视化/事件管理/威胁情报)+ 新账户创建流程中自动纳入 Cloud Guard
|
||||
- Concepts identified: [[Three Lines of Defence(3LoD)]], [[Cloud Security Posture Management(CSPM)]]
|
||||
- Source page: wiki/sources/ctp-topic-52-3-lines-of-defence-3lod-framework-cloud-security-posture-management.md
|
||||
- Notes: 无冲突内容;3LoD/CSPM 均属行业通用概念,已有 CSPM 相关内容于 cloud-security.md;Cloud Guard 为该组织专用 CSPM 工具,暂不单独建 Entity 页面
|
||||
|
||||
## [2026-04-24] ingest | CTP Topic 55 AWS Firewall Manager
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/07_Security/ctp-topic-55-aws-firewall-manager.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: AWS Firewall Manager 在 Grand Torque 多 Landing Zone 环境中的集中化安全策略管理实践——跨 RLABS/R&D/SAS/CAT 多个 Landing Zone 统一部署基线安全组;三种策略类型(通用/审计强制/清理冗余);通过 AWS Config + Lambda 实现自动修复;RAM 前缀列表跨账户共享规则;独立 Firewall Manager 账户支持跨 LZ 部署;Demo 展示 EC2 实例安全组的自动附加与移除
|
||||
- Concepts identified: [[Security-Group]], [[Prefix-List]], [[Auto-Remediation]], [[WAF-Rules-Management]]
|
||||
- Entities identified: [[AWS-Firewall-Manager]], [[Landing-Zones]], [[QALIS]], [[Checkpoint-Firewall]]
|
||||
- Source page: wiki/sources/ctp-topic-55-aws-firewall-manager.md
|
||||
- Notes: 无冲突检测;与 [[ctp-topic-10-aws-landing-zone-lz-data-collection-tagging-related-security]] 中的 Checkpoint 方案属互补关系(网络边界防火墙 vs 实例级安全组基线),已于 Contradictions 节记录
|
||||
|
||||
## [2026-04-30] ingest | CTP Topic 37 Secrets Certificates Management
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/07_Security/ctp-topic-37-secrets-certificates-management.md
|
||||
- Status: ✅ 成功摄入
|
||||
- Summary: 云转型计划密钥与证书管理解决方案选型与实施——30天试点对比 AWS Secrets Manager 与 HashiCorp Vault,AWS Secrets Manager 以更低成本和更简实施胜出;实施阶段从 Control Tower 开始,从 CI/CD 流程清除明文密钥,集中化管理。
|
||||
- Concepts identified: [[Secrets-Management]], [[AWS-Secrets-Manager]]
|
||||
- Entities identified: [[Micro-Focus]], [[CCLE]](CCLE 在 2022 年 3 月负责评估工作,关键组织角色)
|
||||
- Source page: wiki/sources/ctp-topic-37-secrets-certificates-management.md
|
||||
- Notes: 无冲突;与 [[ctp-topic-62-aws-secrets-manager]] 的关系记录于 Contradictions 节(Topic 37 试点结论 + Topic 62 深度实践,属补充关系而非冲突)
|
||||
|
||||
## [2026-04-30] ingest | CTP Topic 62 AWS Secrets Manager
|
||||
- Source file: Cloud & DevOps/Public-Cloud-Learning-Sessions/07_Security/ctp-topic-62-aws-secrets-manager.md
|
||||
- Status: ✅ 成功摄入
|
||||
|
||||
Reference in New Issue
Block a user