教材原文段落
External Dependencies
When crafting a robust BCP, you need to understand and mitigate the risks
associated with external dependencies. These dependencies range from
technology vendors supplying critical hardware, software, and cloud services,
to legal and regulatory frameworks that shape your operational landscape. Each external factor carries potential risks that could, if unaddressed, disrupt
your business operations. Consequently, a comprehensive BCP doesn't just
look inward at the organization's processes, but also outward, ensuring that
external parties' roles and responsibilities are clearly understood and that
contingency plans are in place to tackle any disruptions in these areas.
Vendors
As you develop your BCP, it's crucial to consider the role of all technology
vendors, not just those offering cloud services. These vendors, encompassing
cloud service providers, hardware suppliers, and software developers, are
integral to your organization's operational resilience. Their own business
continuity arrangements can significantly impact your organization's ability
to maintain business operations during disruptive incidents. Consider, for example, a firm that outsources email and calendaring to a
third-party software-as-a-service (SaaS) provider.
Does the contract with that
provider include details about the provider's service-level agreement (SLA)
and commitments for restoring operations in the event of a disaster? Also, remember that a contract is not normally sufficient due diligence when
choosing a vendor. You should also verify that the vendor has the controls in
place to deliver on their contractual commitments. Although it may not be
possible for you to physically visit the vendor's facilities to verify their control
implementation, you can always do the next best thing—send someone else!
Now, before you go off identifying an emissary and booking flights, realize
that many of your vendor's customers are probably asking the same question. For this reason, the vendor may have already hired an independent auditing
firm to conduct an assessment of its controls. They can make the results of
this assessment available to you in the form of a System and Organization
Controls (SOC) report. We cover SOC reports in more detail in Chapter 15,
“Security Assessment and Testing.”
Keep in mind that there are three different versions of the SOC report. The
simplest of these, a SOC 1 report, covers only internal controls over financial
中文直译 / 整理
外部依赖
在制定稳健的业务连续性计划(BCP)时,您需要了解并缓解与外部依赖相关
的风险。 这些依赖关系涵盖从提供关键硬件、软件和云服务的技术供应商,到
塑造您运营环境的法律和监管框架。 每个外部因素都可能带来潜在风险,若未
加以应对,将导致您的业务运营中断。 因此,一个全面的BCP不仅关注组织内
部的流程,还需向外审视,确保明确理解外部方的角色与责任,并制定应急计
划以应对这些领域可能出现的中断。 供应商
在制定您的业务连续性计划(BCP)时,至关重要的是考虑所有技术供应商的
作用,而不仅仅是提供云服务的供应商。 这些供应商包括云服务提供商、硬件
供应商和软件开发商,它们对贵组织的运营韧性至关重要。 它们自身的业务连
续性安排会显著影响贵组织在发生中断事件时维持业务运营的能力。 例如,考虑一家将电子邮件和日历服务外包给第三方软件即服务(SaaS)提供
商的公司。 与该提供商签订的合同是否包含了有关其服务级别协议(SLA)以
及在灾难发生时恢复运营的承诺的详细信息? 此外,请记住,在选择供应商时,合同通常不足以作为充分的尽职调查。 您还
应核实供应商是否具备履行其合同承诺的控制措施。
尽管您可能无法亲自访问
供应商的设施以验证其控制措施的实施情况,但您总可以采取次优的方案——
派其他人去! 现在,在您开始识别使者并预订航班之前,请意识到您的供应商的许多客户可
能也在提出同样的问题。 因此,供应商可能已经聘请了一家独立的审计公司对
其控制措施进行评估。 他们可以以系统与组织控制(SOC)报告的形式向您提
供该评估结果。 我们将在第15章“安全评估与测试”中更详细地介绍SOC报告。 请记住,SOC 报告有三个不同的版本。 其中最简单的是 SOC 1 报告,仅涵盖财务
相关的内部控制
小白解释
场景先行:新员工入职后要登录系统。第一步是声明身份,第二步证明身份,第三步决定能访问哪些数据,最后系统要记录他做了什么。IAM 题就是围绕这条链条出题。
这一页真正想让你理解的是:供应商也要被合同、审计、评估和持续监控管理起来。
把它放进公司里看,关键不是背定义,而是判断:认证成功不代表什么都能做;离职、调岗、权限漂移都会造成越权。
你作为负责人可以这样想:把识别、认证、授权、审计分开看,再用最小权限和定期复核收口。
本页术语用人话说:
审计:审计记录主体行为,用于追责、复盘和取证。
尽职调查:尽职调查是持续检查、验证和监督是否做到了。
OSI 模型:OSI 用七层结构理解网络通信,从物理层到应用层。
审计:审计检查控制是否存在、是否有效、是否符合要求。
常见误区:不要把 authentication 和 authorization 混成一件事:前者证明你是谁,后者决定你能干什么。
读完后用一句话复述:如果我是IAM 管理员,我会先识别风险,再选择控制,并保留能证明判断合理的证据。
考点提醒
考题会把“第三方治理:外包不外包责任”包装成一个业务场景:有人要上线系统、处理事故、审供应商、分配权限或选择控制。
先抓题干里的角色和目标:这里更像是IAM 管理员在做判断。
最佳答案通常不是“最强工具”,而是能降低风险、符合职责、成本合理、还能留下证据的动作。
没有日志和身份绑定,就很难问责。
Due diligence 偏“确认事情被正确执行”。
网络题先定位层次,再判断协议、设备或攻击位置。
审计题关注独立性、证据、范围和报告。
日志要保护完整性、时间同步和访问控制。
排除法提醒:不要把 authentication 和 authorization 混成一件事:前者证明你是谁,后者决定你能干什么。