知识卡片
容器不等于用户代码沙箱
执行用户脚本或把参数拼入脚本,会把输入升级为可执行能力。即使装进普通容器,代码仍可能访问内部网络和注入的凭据,因此还要审计隔离边界、限制环境并考虑专门沙箱。SQL注入可用恰当库与参数处理防护,但“使用容器”不能代替对任意用户代码的威胁分析。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 宏观架构中的安全 · 查看原书依据
Even when we are running the user code as containers, the code has access to the internal network, which is a security threat. Also, all credentials provided to containers can be accessed via code running inside, which could let an attacker sneak into the system.
参考来源
- 位置:《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)
- 结论依据:所引连续原文给出本卡机制或取舍;条件与示例结合本节已读上下文解释。
- 原始内容:Even when we are running the user code as containers, the code has access to the internal network, which is a security threat. Also, all credentials provided to containers can be accessed via code running inside, which could let an attacker sneak into the system.