知识卡片
负向测试验证真实隔离
正常租户查询成功只证明功能可用。隔离测试应保持租户1的受限权限,却故意尝试访问租户2的资源,预期为空或拒绝,并核查告警和日志。测试要在受控环境注入错误目标,验证边界,而不是把身份本身一起切成租户2后期待拒绝。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Tenant Isolation · 查看原书依据
belong to Tenant 1. However, in your test, you replace the tenant identifier in your request with the ID that belongs to Tenant 2. This should return no data or an error indicating that you’ve crossed a boundary. You may also add logs and operational policies that trigger alerts within your operations console, indicating that an attempt was made to
参考来源
- 位置:《Building Multi-Tenant SaaS Architectures》第09章《Tenant Isolation》(来源项目 a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Multi-Tenant SaaS Architectures/_epub-src/OEBPS/ch09.html)
- 结论依据:原文具体说明正常租户查询成功只证明功能可用;本卡据此归纳机制及适用边界。
- 原始内容:belong to Tenant 1. However, in your test, you replace the tenant identifier in your request with the ID that belongs to Tenant 2. This should return no data or an error indicating that you’ve crossed a boundary. You may also add logs and operational policies that trigger alerts within your operations console, indicating that an attempt was made to