容器实例的 Azure 安全基线Azure security baseline for Container Instances

此安全基线对容器实例应用 Azure 安全基准版本 1.0 中的指导。This security baseline applies guidance from the Azure Security Benchmark version1.0 to Container Instances. Azure 安全基准提供有关如何在 Azure 上保护云解决方案的建议。The Azure Security Benchmark provides recommendations on how you can secure your cloud solutions on Azure. 内容分为 Azure 安全基准定义的 安全控制 和适用于容器实例的相关指导。The content is grouped by the security controls defined by the Azure Security Benchmark and the related guidance applicable to Container Instances. 排除了不适用于容器实例或属于 Azure 职责范围的控制措施。Controls not applicable to Container Instances, or for which the responsibility is Azure's, have been excluded.

若要了解容器实例如何完全映射到 Azure 安全基准,请参阅完整的容器实例安全基线映射文件To see how Container Instances completely maps to the Azure Security Benchmark, see the full Container Instances security baseline mapping file.

网络安全Network Security

有关详细信息,请参阅 Azure 安全基线: 网络安全性For more information, see the Azure Security Benchmark: Network Security.

1.1:保护虚拟网络中的 Azure 资源1.1: Protect Azure resources within virtual networks

指导:将 Azure 容器实例中的容器组与 Azure 虚拟网络集成。Guidance: Integrate your container groups in Azure Container Instances with an Azure virtual network. 使用 Azure 虚拟网络可将多个 Azure 资源(例如容器组)置于无法通过 Internet 路由的网络中。Azure virtual networks allow you to place many of your Azure resources, such as container groups, in a non-internet routable network.

使用 Azure 防火墙控制从委托给 Azure 容器实例的子网进行的出站网络访问。Control outbound network access from a subnet delegated to Azure Container Instances by using Azure Firewall.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

1.2:监视并记录虚拟网络、子网和网络接口的配置与流量1.2: Monitor and log the configuration and traffic of virtual networks, subnets, and network interfaces

指导:使用 Azure 安全中心并遵循网络保护建议来帮助保护 Azure 中的网络资源。Guidance: Use Azure Security Center and follow network protection recommendations to help secure your network resources in Azure. 启用 NSG 流日志,并将日志发送到存储帐户以进行流量审核。Enable NSG flow logs and send logs into a Storage Account for traffic audit. 还可以将 NSG 流日志发送到 Log Analytics 工作区,并使用流量分析来提供有关 Azure 云中流量流的见解。You may also send NSG flow logs to a Log Analytics Workspace and use Traffic Analytics to provide insights into traffic flow in your Azure cloud. 流量分析的优势包括能够可视化网络活动、识别热点、识别安全威胁、了解流量流模式,以及查明网络不当配置。Some advantages of Traffic Analytics are the ability to visualize network activity and identify hot spots, identify security threats, understand traffic flow patterns, and pinpoint network misconfigurations.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

1.3:保护关键 Web 应用程序1.3: Protect critical web applications

指导:不适用。Guidance: Not applicable. 基准适用于 Azure 应用服务或托管 Web 应用程序的计算资源。Benchmark is intended for Azure App Service or compute resources hosting web applications.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

1.4:拒绝与已知恶意的 IP 地址进行通信1.4: Deny communications with known-malicious IP addresses

指导:在虚拟网络上启用 DDoS 标准保护,以防范 DDoS 攻击。Guidance: Enable DDoS Standard protection on your virtual networks for protections from DDoS attacks. 根据 Azure 安全中心集成的威胁情报进行判断,拒绝与已知恶意的或未使用过的 Internet IP 地址通信。Use Azure Security Center Integrated Threat Intelligence to deny communications with known malicious or unused Internet IP addresses. 在组织的每个网络边界上部署 Azure 防火墙,启用威胁情报并将其配置为针对恶意网络流量执行“发出警报并拒绝”操作。Deploy Azure Firewall at each of the organization's network boundaries with Threat Intelligence enabled and configured to "Alert and deny" for malicious network traffic.

可以使用 Azure 安全中心实时网络访问,将 NSG 配置为只能在有限时间内将终结点公开给已批准的 IP 地址。You may use Azure Security Center Just In Time Network access to configure NSGs to limit exposure of endpoints to approved IP addresses for a limited period. 另请使用 Azure 安全中心自适应网络强化,推荐基于实际流量和威胁情报限制端口和源 IP 的 NSG 配置。Also , use Azure Security Center Adaptive Network Hardening to recommend NSG configurations that limit Ports and Source IPs based on actual traffic and threat intelligence.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

1.5:记录网络数据包1.5: Record network packets

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),可对附加到用于保护 Azure 容器注册表的子网的 NSG 启用网络安全组 (NSG) 流日志。Guidance: If using a cloud-based private registry like Azure container registry with Azure Container Instances, you can enable network security group (NSG) flow logs for the NSG attached to the subnet being used to protect your Azure container registry. 你可以将 NSG 流日志记录到 Azure 存储帐户中,以生成流记录。You can record the NSG flow logs into a Azure Storage Account to generate flow records. 如果需要调查异常活动,请启用 Azure 网络观察程序数据包捕获。If required for investigating anomalous activity, enable Azure Network Watcher packet capture.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

1.6:部署基于网络的入侵检测/入侵防护系统 (IDS/IPS)1.6: Deploy network-based intrusion detection/intrusion prevention systems (IDS/IPS)

指导:从 Azure 市场中选择一种产品/服务,该产品/服务应支持包含有效负载检查功能的 ID/IPS 功能。Guidance: Select an offer from the Azure Marketplace that supports IDS/IPS functionality with payload inspection capabilities. 如果不需要基于有效负载检查的入侵检测和/或防护,则可以使用包含威胁情报功能的 Azure 防火墙。If intrusion detection and/or prevention based on payload inspection is not a requirement, Azure Firewall with Threat Intelligence can be used. 基于 Azure 防火墙威胁情报的筛选功能可以发出警报,并拒绝传入和传出已知恶意 IP 地址和域的流量。Azure Firewall Threat intelligence-based filtering can alert and deny traffic to and from known malicious IP addresses and domains. IP 地址和域源自 Microsoft 威胁智能源。The IP addresses and domains are sourced from the Microsoft Threat Intelligence feed.

在组织的每个网络边界上部署所选的防火墙解决方案,以检测和/或拒绝恶意流量。Deploy the firewall solution of your choice at each of your organization's network boundaries to detect and/or deny malicious traffic.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

1.7:管理发往 Web 应用程序的流量1.7: Manage traffic to web applications

指导:不适用。Guidance: Not applicable. 基准适用于在 Azure 应用服务或计算资源上运行的 Web 应用程序。Benchmark is intended for web applications running on Azure App Service or compute resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

1.8:最大程度地降低网络安全规则的复杂性和管理开销1.8: Minimize complexity and administrative overhead of network security rules

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),对于需要访问容器注册表的资源,请使用 Azure 容器注册表服务的虚拟网络服务标记,来定义网络安全组或 Azure 防火墙中的网络访问控制。Guidance: If using a cloud-based private registry like Azure container registry with Azure Container Instances, for resources that need access to your container registry, use virtual network service tags for the Azure Container Registry service to define network access controls on Network Security Groups or Azure Firewall. 创建安全规则时,可以使用服务标记代替特定的 IP 地址。You can use service tags in place of specific IP addresses when creating security rules. 在规则的相应源或目标字段中指定服务标记名称“AzureContainerRegistry”,可以允许或拒绝相应服务的流量。By specifying the service tag name "AzureContainerRegistry" in the appropriate source or destination field of a rule, you can allow or deny the traffic for the corresponding service. Azure 会管理服务标记包含的地址前缀,并会在地址发生更改时自动更新服务标记。Azure manages the address prefixes encompassed by the service tag and automatically updates the service tag as addresses change.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

1.9:维护网络设备的标准安全配置1.9: Maintain standard security configurations for network devices

指导:在 Azure 容器实例中使用 Azure 容器注册表时,我们建议对与 Azure 容器注册表关联的网络资源定义并实施标准安全配置。Guidance: When using Azure Container Registry with Azure Container Instances, we recommend that you define and implement standard security configurations for network resources associated with your Azure container registry.

Microsoft.ContainerRegistryMicrosoft.Network 命名空间中使用 Azure Policy 别名创建自定义策略,以审核或强制实施你的容器注册表的网络配置。Use Azure Policy aliases in the Microsoft.ContainerRegistry and Microsoft.Network namespaces to create custom policies to audit or enforce the network configuration of your container registries.

可以使用 Azure 蓝图,通过在单个蓝图定义中打包关键环境项目(例如 Azure 资源管理器模板、Azure RBAC 控制措施和策略定义),来简化大规模的 Azure 部署。You can use Azure Blueprints to simplify large-scale Azure deployments by packaging key environment artifacts, such as Azure Resource Manager templates, Azure RBAC controls, and policy definitions into a single blueprint definition. 轻松将蓝图应用到新的订阅,并通过版本控制来微调控制措施和管理。Easily apply the blueprint to new subscriptions and fine-tune control and management through versioning.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

1.11:使用自动化工具来监视网络资源配置和检测更改1.11: Use automated tools to monitor network resource configurations and detect changes

指导:使用 Azure 活动日志监视网络资源配置,并检测与容器注册表相关的网络资源的更改。Guidance: Use Azure Activity Log to monitor network resource configurations and detect changes for network resources related to your container registries. 在 Azure Monitor 中创建当关键网络资源发生更改时触发的警报。Create alerts within Azure Monitor that will trigger when changes to critical network resources take place.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

日志记录和监视Logging and Monitoring

有关详细信息,请参阅 Azure 安全基线: 日志记录和监视For more information, see the Azure Security Benchmark: Logging and Monitoring.

2.2:配置中心安全日志管理2.2: Configure central security log management

指导:通过 Azure Monitor 引入日志来聚合由 Azure 容器实例生成的安全数据。Guidance: Ingest logs via Azure Monitor to aggregate security data generated by an Azure container Instance. 在 Azure Monitor 中,使用 Log Analytics 工作区来查询和执行分析,并使用 Azure 存储帐户进行长期/存档存储。Within Azure Monitor, use a Log Analytics workspace to query and perform analytics, and use Azure Storage Accounts for long-term/archival storage.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

2.3:为 Azure 资源启用审核日志记录2.3: Enable audit logging for Azure resources

指导:Azure Monitor 针对用户驱动事件收集资源日志(前称为诊断日志)。Guidance: Azure Monitor collects resource logs (formerly called diagnostic logs) for user-driven events. 收集并使用这些数据来审核容器身份验证事件,并提供有关项目(例如拉取和推送事件)的完整活动跟踪,以便诊断容器组的安全问题。Collect and consume this data to audit container authentication events and provide a complete activity trail on artifacts such as pull and push events so you can diagnose security issues with your container group.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

2.5:配置安全日志存储保留期2.5: Configure security log storage retention

指导:在 Azure Monitor 中,根据组织的合规性规章设置 Log Analytics 工作区保留期。Guidance: Within Azure Monitor, set your Log Analytics workspace retention period according to your organization's compliance regulations. 使用 Azure 存储帐户进行长期/存档存储。Use Azure Storage Accounts for long-term/archival storage.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

2.6:监视和查看日志2.6: Monitor and review logs

指导:分析并监视 Azure 容器实例日志以确定其是否存在异常行为,并定期评审结果。Guidance: Analyze and monitor Azure Container Instances logs for anomalous behavior and regularly review results. 使用 Azure Monitor 的 Log Analytics 工作区查看日志并对日志数据执行查询。Use Azure Monitor's Log Analytics workspace to review logs and perform queries on log data.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

2.7:针对异常活动启用警报2.7: Enable alerts for anomalous activities

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),请使用 Azure Log Analytics 工作区来监视与 Azure 容器注册表相关的安全日志和事件中的异常活动并相应地发出警报。Guidance: If using a cloud-based private registry like Azure container registry with Azure Container Instances, use Azure Log Analytics workspace for monitoring and alerting on anomalous activities in security logs and events related to your Azure container registry.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

2.8:集中管理反恶意软件日志记录2.8: Centralize anti-malware logging

指导:不适用。Guidance: Not applicable. 如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),Azure 容器注册表不会处理或生成反恶意软件相关的日志。If using a cloud-based private registry like Azure container registry with Azure Container Instances, Azure container registry does not process or produce anti-malware related logs.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

2.9:启用 DNS 查询日志记录2.9: Enable DNS query logging

指导:不适用。Guidance: Not applicable. 如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),Azure 容器注册表将是一个终结点且不会发起通信,服务不会查询 DNS。If using a cloud-based private registry like Azure container registry with Azure Container Instances, Azure container registry is an endpoint and does not initiate communication, and the service does not query DNS.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

标识和访问控制Identity and Access Control

有关详细信息,请参阅 Azure 安全基线: 标识和访问控制For more information, see the Azure Security Benchmark: Identity and Access Control.

3.1:维护管理帐户的清单3.1: Maintain an inventory of administrative accounts

指导:Azure Active Directory (Azure AD) 具有必须显式分配且可查询的内置角色。Guidance: Azure Active Directory (Azure AD) has built-in roles that must be explicitly assigned and are queryable. 使用 Azure AD PowerShell 模块执行即席查询,以发现属于管理组成员的帐户。Use the Azure AD PowerShell module to perform ad hoc queries to discover accounts that are members of administrative groups.

如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),对于每个 Azure 容器注册表,请跟踪内置的管理员帐户是处于启用状态还是禁用状态。If using a cloud-based private registry like Azure container registry with Azure Container Instances, for each Azure container registry, track whether the built-in admin account is enabled or disabled. 不使用该帐户时请将其禁用。Disable the account when not in use.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.2:在适用的情况下更改默认密码3.2: Change default passwords where applicable

指导:Azure Active Directory (Azure AD) 没有默认密码的概念。Guidance: Azure Active Directory (Azure AD) does not have the concept of default passwords. 其他需要密码的 Azure 资源会强制创建具有复杂性要求和最小密码长度要求的密码,这些要求因服务而异。Other Azure resources requiring a password force a password to be created with complexity requirements and a minimum password length, which differ depending on the service. 你对可能使用默认密码的第三方应用程序和市场服务负责。You are responsible for third-party applications and Marketplace services that may use default passwords.

如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),并且启用了 Azure 容器注册表的默认管理员帐户,则会自动创建复杂密码并对其进行轮换。If using a cloud-based private registry like Azure container registry with Azure Container Instances, if the default admin account of an Azure container registry is enabled, complex passwords are automatically created and should be rotated. 不使用该帐户时请将其禁用。Disable the account when not in use.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.3:使用专用管理帐户3.3: Use dedicated administrative accounts

指南:围绕专用管理帐户的使用创建标准操作程序。Guidance: Create standard operating procedures around the use of dedicated administrative accounts. 使用 Azure 安全中心标识和访问管理来监视管理帐户的数量。Use Azure Security Center Identity and Access Management to monitor the number of administrative accounts.

如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),请创建相关过程来启用容器注册表的内置管理员帐户。If using a cloud-based private registry like Azure container registry with Azure Container Instances, create procedures to enable the built-in admin account of a container registry. 不使用该帐户时请将其禁用。Disable the account when not in use.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.4:使用 Azure Active Directory 单一登录 (SSO)3.4: Use Azure Active Directory single sign-on (SSO)

指导:请尽可能使用 Azure Active Directory (Azure AD) SSO,而不是为每个服务配置单个独立凭据。Guidance: Wherever possible, use Azure Active Directory (Azure AD) SSO instead of configuring individual stand-alone credentials per-service. 请使用 Azure 安全中心标识和访问管理建议。Use Azure Security Center Identity and Access Management recommendations.

如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),那么请使用与 Azure AD 集成的单独登录来单独访问容器注册表。If using a cloud-based private registry like Azure container registry with Azure Container Instances, for individual access to the container registry, use individual sign inintegrated with Azure AD.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.5:对所有基于 Azure Active Directory 的访问使用多重身份验证3.5: Use multi-factor authentication for all Azure Active Directory-based access

指导:启用 Azure Active Directory (Azure AD) 多重身份验证,并遵循 Azure 安全中心标识和访问管理的建议。Guidance: Enable Azure Active Directory (Azure AD) multifactor authentication and follow Azure Security Center Identity and Access Management recommendations.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.6:对所有管理任务使用专用计算机(特权访问工作站)3.6: Use dedicated machines (Privileged Access Workstations) for all administrative tasks

指导:使用配置了多重身份验证的 PAW(特权访问工作站)来登录和配置 Azure 资源。Guidance: Use PAWs (privileged access workstations) with multifactor authentication configured to log into and configure Azure resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.7:记录来自管理帐户的可疑活动并对其发出警报3.7: Log and alert on suspicious activities from administrative accounts

指导:当环境中出现可疑或不安全的活动时,请使用 Azure Active Directory (Azure AD) 安全报告来生成日志和警报。Guidance: Use Azure Active Directory (Azure AD) security reports for generation of logs and alerts when suspicious or unsafe activity occurs in the environment. 使用 Azure 安全中心监视标识和访问活动。Use Azure Security Center to monitor identity and access activity.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.8:仅从批准的位置管理 Azure 资源3.8: Manage Azure resources from only approved locations

指南:使用条件访问命名位置,仅允许从 IP 地址范围或国家/地区的特定逻辑分组进行访问。Guidance: Use Conditional Access Named Locations to allow access from only specific logical groupings of IP address ranges or countries/regions.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.9:使用 Azure Active Directory3.9: Use Azure Active Directory

指导:使用 Azure Active Directory (Azure AD) 作为中心身份验证和授权系统。Guidance: Use Azure Active Directory (Azure AD) as the central authentication and authorization system. Azure AD 通过对静态数据和传输中数据使用强加密来保护数据。Azure AD protects data by using strong encryption for data at rest and in transit. Azure AD 还会对用户凭据进行加盐、哈希处理和安全存储操作。Azure AD also salts, hashes, and securely stores user credentials.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.10:定期审查和协调用户访问3.10: Regularly review and reconcile user access

指导:Azure Active Directory (Azure AD) 提供日志来帮助发现过时的帐户。Guidance: Azure Active Directory (Azure AD) provides logs to help discover stale accounts. 此外,请使用 Azure 标识访问评审来有效管理组成员身份、对企业应用程序的访问和角色分配。In addition, use Azure Identity Access Reviews to efficiently manage group memberships, access to enterprise applications, and role assignments. 可以定期评审用户的访问权限,确保只有适当的用户才持续拥有访问权限。User access can be reviewed on a regular basis to make sure only the right Users have continued access.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.11:监视尝试访问已停用凭据的行为3.11: Monitor attempts to access deactivated credentials

指导:你有权访问 Azure Active Directory (Azure AD) 登录活动、审核和风险事件日志源,因此可以与任何安全信息和事件管理 (SIEM) /监视工具集成。Guidance: You have access to Azure Active Directory (Azure AD) sign in Activity, Audit and Risk Event log sources, which allow you to integrate with any Security Information and Event Management (SIEM) /Monitoring tool.

可以通过为 Azure AD 用户帐户创建诊断设置,并将审核日志和登录日志发送到 Log Analytics 工作区,来简化此过程。You can streamline this process by creating Diagnostic Settings for Azure AD user accounts and sending the audit logs and sign in logs to a Log Analytics Workspace. 你可以在 Log Analytics 工作区中配置所需的警报。You can configure desired Alerts within Log Analytics Workspace.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

3.13:在支持场合下为 Azure 提供对相关客户数据的访问权限3.13: Provide Azure with access to relevant customer data during support scenarios

指导:不适用;Azure 容器实例目前不支持客户密码箱。Guidance: Not available; Customer Lockbox not currently supported for Azure Container Instances.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

数据保护Data Protection

有关详细信息,请参阅 Azure 安全基线: 数据保护For more information, see the Azure Security Benchmark: Data Protection.

4.1:维护敏感信息的清单4.1: Maintain an inventory of sensitive Information

指导:使用资源标记可以帮助跟踪用于存储或处理敏感信息的 Azure 容器注册表。Guidance: Use resource tags to assist in tracking Azure container registries that store or process sensitive information.

在注册表中对容器映像或其他项目进行标记和版本控制并锁定映像或存储库,以便跟踪可存储或处理敏感信息的映像。Tag and version container images or other artifacts in a registry, and lock images or repositories, to assist in tracking images that store or process sensitive information.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

4.2:隔离存储或处理敏感信息的系统4.2: Isolate systems storing or processing sensitive information

指导:为开发、测试和生产实现单独的容器注册表、订阅和/或管理组。Guidance: Implement separate container registries, subscriptions, and/or management groups for development, test, and production. 存储或处理敏感数据的资源应当充分隔离。Resources storing or processing sensitive data should be sufficiently isolated.

资源应当按虚拟网络或子网进行分隔,相应地进行标记,并由网络安全组 (NSG) 或 Azure 防火墙提供保护。Resources should be separated by virtual network or subnet, tagged appropriately, and secured by an network security group (NSG) or Azure Firewall.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

4.3:监视和阻止未经授权的敏感信息传输4.3: Monitor and block unauthorized transfer of sensitive information

指导:在网络外围部署一个自动化工具,用于监视敏感信息的未授权传输,并阻止此类传输,同时提醒信息安全专业人员。Guidance: Deploy an automated tool on network perimeters that monitors for unauthorized transfer of sensitive information and blocks such transfers while alerting information security professionals.

对于 Microsoft 管理的底层平台,Azure 会将所有客户数据视为敏感数据,并会全方位地防范客户数据丢失和泄露。For the underlying platform which is managed by Microsoft, Azure treats all customer data as sensitive and goes to great lengths to guard against customer data loss and exposure. 为了确保 Azure 中的客户数据保持安全,Azure 已实施并维护一套可靠的数据保护控制机制和功能。To ensure customer data within Azure remains secure, Azure has implemented and maintains a suite of robust data protection controls and capabilities.

责任:共享Responsibility: Shared

Azure 安全中心监视:无Azure Security Center monitoring: None

4.4:加密传输中的所有敏感信息4.4: Encrypt all sensitive information in transit

指导:确保连接到 Azure 容器注册表的任何客户端能够协商 TLS 1.2 或更高版本。Guidance: Ensure that any clients connecting to your Azure Container Registry are able to negotiate TLS 1.2 or greater. 默认情况下,Azure 资源会协商 TLS 1.2。Azure resources negotiate TLS 1.2 by default.

请按照 Azure 安全中心的建议,了解静态加密和传输中加密(如果适用)。Follow Azure Security Center recommendations for encryption at rest and encryption in transit, where applicable.

责任:共享Responsibility: Shared

Azure 安全中心监视:无Azure Security Center monitoring: None

4.5:使用有效的发现工具识别敏感数据4.5: Use an active discovery tool to identify sensitive data

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),请注意,数据标识、分类和丢失防护功能尚不适用于 Azure 容器注册表。Guidance: If using a cloud-based private registry like Azure container registry with Azure Container Instances, data identification, classification, and loss prevention features are not yet available for Azure Container Registry. 如果需要出于合规性目的使用这些功能,请实施第三方解决方案。Implement third-party solution if required for compliance purposes.

对于 Microsoft 管理的底层平台,Azure 会将所有客户数据视为敏感数据,并会全方位地防范客户数据丢失和泄露。For the underlying platform which is managed by Microsoft, Azure treats all customer data as sensitive and goes to great lengths to guard against customer data loss and exposure. 为了确保 Azure 中的客户数据保持安全,Azure 已实施并维护一套可靠的数据保护控制机制和功能。To ensure customer data within Azure remains secure, Azure has implemented and maintains a suite of robust data protection controls and capabilities.

责任:共享Responsibility: Shared

Azure 安全中心监视:无Azure Security Center monitoring: None

4.6:使用基于角色的访问控制来控制对资源的访问4.6: Use Role-based access control to control access to resources

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),请使用 Azure 基于角色的访问控制 (Azure RBAC) 来管理对 Azure 容器注册表中数据和资源的访问。Guidance: If using a cloud-based private registry like Azure Container Registry with Azure Container Instances, use Azure role-based access control (Azure RBAC) manage access to data and resources in an Azure container registry.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

4.7:使用基于主机的数据丢失防护来强制实施访问控制4.7: Use host-based data loss prevention to enforce access control

指导:如果需要在计算资源上确保符合性,则实施第三方工具(如基于主机的自动数据丢失防护解决方案),以便对数据强制实施访问控制,即使数据从系统复制也是如此。Guidance: If required for compliance on compute resources, implement a third-party tool, such as an automated host-based data loss prevention solution, to enforce access controls to data even when data is copied off a system.

对于 Microsoft 管理的底层平台,Azure 会将所有客户数据视为敏感数据,并会全方位地防范客户数据丢失和泄露。For the underlying platform which is managed by Microsoft, Azure treats all customer data as sensitive and goes to great lengths to guard against customer data loss and exposure. 为了确保 Azure 中的客户数据保持安全,Azure 已实施并维护一套可靠的数据保护控制机制和功能。To ensure customer data within Azure remains secure, Azure has implemented and maintains a suite of robust data protection controls and capabilities.

责任:共享Responsibility: Shared

Azure 安全中心监视:无Azure Security Center monitoring: None

4.8:静态加密敏感信息4.8: Encrypt sensitive information at rest

指导:在所有 Azure 资源上使用静态加密。Guidance: Use encryption at rest on all Azure resources. 如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),默认情况下,将使用 Azure 管理的密钥对 Azure 容器注册表中的所有数据进行静态加密。If using a cloud-based private registry like Azure container registry with Azure Container Instances, by default, all data in an Azure container registry is encrypted at rest using Azure-managed keys.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

4.9:记录对关键 Azure 资源的更改并对此类更改发出警报4.9: Log and alert on changes to critical Azure resources

指导:Log Analytics 工作区提供了一个集中的位置,用于存储和查询来自 Azure 资源、本地资源以及其他云中的资源的日志数据。Guidance: Log Analytics workspaces provide a centralized location for storing and querying log data not only from Azure resources, but also on-premises resources and resources in other clouds. Azure 容器实例提供内置支持,支持将日志和事件数据发送到 Azure Monitor 日志。Azure Container Instances includes built-in support for sending logs and event data to Azure Monitor logs.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

漏洞管理Vulnerability Management

有关详细信息,请参阅 Azure 安全基线: 漏洞管理。For more information, see the Azure Security Benchmark: Vulnerability Management.

5.1:运行自动漏洞扫描工具5.1: Run automated vulnerability scanning tools

指导:利用解决方案来扫描专用注册表中的容器映像并识别潜在漏洞。Guidance: Take advantage of solutions to scan container images in a private registry and identify potential vulnerabilities. 必须了解不同解决方案提供的威胁检测深度。It's important to understand the depth of threat detection that the different solutions provide. 遵循 Azure 安全中心的在容器映像上执行漏洞评估的建议。Follow recommendations from Azure Security Center on performing vulnerability assessments on your container images. (可选)从 Azure 市场部署第三方解决方案,用于执行映像漏洞评估。Optionally deploy third-party solutions from Azure Marketplace to perform image vulnerability assessments.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

5.2:部署自动操作系统修补管理解决方案5.2: Deploy automated operating system patch management solution

指导:Azure 对支持正在运行的容器的基础系统执行修补管理。Guidance: Azure performs patch management on the underlying systems that support running containers.

当检测到来自操作系统和其他修补程序的基础映像更新时,将自动执行容器映像更新。Automate container image updates when updates to base images from operating system and other patches are detected.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

5.3:为第三方软件部署自动修补程序管理解决方案5.3: Deploy automated patch management solution for third-party software titles

指导:可以使用第三方解决方案来修补应用程序映像。Guidance: You can use a third party solution to patch application images. 此外,如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),可以运行 Azure 容器注册表任务,基于基础映像中的安全修补程序或其他更新自动对容器注册表中的应用程序映像进行更新。Also, if using a cloud-based private registry like Azure container registry with Azure Container Instances, you can run Azure Container Registry tasks to automate updates to application images in a container registry based on security patches or other updates in base images.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

5.4:比较连续进行的漏洞扫描5.4: Compare back-to-back vulnerability scans

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),请将 Azure 容器注册表 (ACR) 与 Azure 安全中心集成,以便能够定期扫描容器映像中的漏洞。Guidance: If using a cloud-based private registry like Azure container registry with Azure Container Instances, integrate Azure container registry (ACR) with Azure Security Center to enable periodic scanning of container images for vulnerabilities. (可选)从 Azure 市场部署第三方解决方案,用于执行定期的映像漏洞扫描。Optionally deploy third-party solutions from Azure Marketplace to perform periodic image vulnerability scans.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

5.5:使用风险评级过程来确定已发现漏洞的修正措施的优先级5.5: Use a risk-rating process to prioritize the remediation of discovered vulnerabilities

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表),请将 Azure 容器注册表 (ACR) 与 Azure 安全中心集成,以便能够定期扫描容器映像中的漏洞并将风险分类。Guidance: If using a cloud-based private registry like Azure container registry with Azure Container Instances, integrate Azure Container Registry (ACR) with Azure Security Center to enable periodic scanning of container images for vulnerabilities and to classify risks. (可选)从 Azure 市场部署第三方解决方案,用于执行定期的映像漏洞扫描和风险分类。Optionally deploy third-party solutions from Azure Marketplace to perform periodic image vulnerability scans and risk classification.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

清单和资产管理Inventory and Asset Management

有关详细信息,请参阅 Azure 安全基线: 清单和资产管理For more information, see the Azure Security Benchmark: Inventory and Asset Management.

6.1:使用自动化资产发现解决方案6.1: Use automated asset discovery solution

指导:使用 Azure Resource Graph 查询/发现订阅中的所有资源(例如计算、存储、网络、端口和协议等)。Guidance: Use Azure Resource Graph to query/discover all resources (such as compute, storage, network, ports, and protocols etc.) within your subscription(s). 确保租户中具有适当的(读取)权限,并枚举所有 Azure 订阅以及订阅中的资源。Ensure appropriate (read) permissions in your tenant and enumerate all Azure subscriptions as well as resources within your subscriptions.

尽管可以通过 Resource Graph 发现经典 Azure 资源,但我们强烈建议你今后还是创建并使用 Azure 资源管理器资源。Although classic Azure resources may be discovered via Resource Graph, it is highly recommended to create and use Azure Resource Manager resources going forward.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.2:维护资产元数据6.2: Maintain asset metadata

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表(ACR)),ACR 将在注册表中保留元数据(包括映像的标记和清单)。Guidance: If using a cloud-based private registry like Azure Container Registry (ACR) with Azure Container Instances, ACR maintains metadata including tags and manifests for images in a registry. 请遵循用于标记项目的建议做法。Follow recommended practices for tagging artifacts.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.3:删除未经授权的 Azure 资源6.3: Delete unauthorized Azure resources

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表(ACR)),ACR 将在注册表中保留元数据(包括映像的标记和清单)。Guidance: If using a cloud-based private registry like Azure Container Registry (ACR) with Azure Container Instances, ACR maintains metadata including tags and manifests for images in a registry. 请遵循用于标记项目的建议做法。Follow recommended practices for tagging artifacts.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.4:定义并维护已批准的 Azure 资源的清单6.4: Define and maintain inventory of approved Azure resources

指导:你需要根据组织需求创建已批准的 Azure 资源的清单。Guidance: You will need to create an inventory of approved Azure resources as per your organizational needs.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.5:监视未批准的 Azure 资源6.5: Monitor for unapproved Azure resources

指导:使用 Azure Policy 对可以在订阅中创建的资源类型施加限制。Guidance: Use Azure Policy to put restrictions on the type of resources that can be created in your subscription(s).

使用 Azure Resource Graph 查询/发现订阅中的资源。Use Azure Resource Graph to query/discover resources within their subscription(s). 确保环境中的所有 Azure 资源均已获得批准。Ensure that all Azure resources present in the environment are approved.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.6:监视计算资源中未批准的软件应用程序6.6: Monitor for unapproved software applications within compute resources

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表 (ACR)),请分析并监视 Azure 容器注册表日志以确定是否存在异常行为,并定期评审结果。Guidance: If using a cloud-based private registry like Azure Container Registry (ACR) with Azure Container Instances, analyze and monitor Azure Container Registry logs for anomalous behavior and regularly review results. 使用 Azure Monitor 的 Log Analytics 工作区来查看日志并执行针对日志数据的查询。Use Azure Monitor's Log Analytics Workspace to review logs and perform queries on log data.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.7:删除未批准的 Azure 资源和软件应用程序6.7: Remove unapproved Azure resources and software applications

指导:可以通过 Azure 自动化在工作负荷和资源的部署、操作和解除授权过程中进行完全的控制。Guidance: Azure Automation provides complete control during deployment, operations, and decommissioning of workloads and resources. 你可以实施自己的解决方案来删除未经授权的 Azure 资源。You can implement your own solution for removing unauthorized Azure resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.8:仅使用已批准的应用程序6.8: Use only approved applications

指导:不适用。Guidance: Not applicable. 基准设计用于计算资源。Benchmark is designed for compute resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.9:仅使用已批准的 Azure 服务6.9: Use only approved Azure services

指导:利用 Azure Policy 限制可在环境中预配的服务。Guidance: Leverage Azure Policy to restrict which services you can provision in your environment.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.10:维护已获批软件的清单6.10: Maintain an inventory of approved software titles

指导:不适用。Guidance: Not applicable. 基准设计用于计算资源。Benchmark is designed for compute resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.11:限制用户与 Azure 资源管理器进行交互的能力6.11: Limit users' ability to interact with Azure Resource Manager

指导:使用特定于操作系统的配置或第三方资源来限制用户在 Azure 计算资源中执行脚本的能力。Guidance: Use operating system-specific configurations or third-party resources to limit users' ability to execute scripts within Azure compute resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.12:限制用户在计算资源中执行脚本的功能6.12: Limit users' ability to execute scripts within compute resources

指导:使用特定于操作系统的配置或第三方资源来限制用户在 Azure 计算资源中执行脚本的能力。Guidance: Use operating system specific configurations or third-party resources to limit users' ability to execute scripts within Azure compute resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

6.13:以物理或逻辑方式隔离高风险应用程序6.13: Physically or logically segregate high risk applications

指导:业务运营所需的软件可能会给组织带来更高的风险,应将其隔离在自己的虚拟机和/或虚拟网络中,并通过 Azure 防火墙或网络安全组进行充分的保护。Guidance: Software that is required for business operations, but may incur higher risk for the organization, should be isolated within its own virtual machine and/or virtual network and sufficiently secured with either an Azure Firewall or Network Security Group.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

安全配置Secure Configuration

有关详细信息,请参阅 Azure 安全基线: 安全配置For more information, see the Azure Security Benchmark: Secure Configuration.

7.1:为所有 Azure 资源建立安全配置7.1: Establish secure configurations for all Azure resources

指导:使用 Azure Policy 或 Azure 安全中心来维护所有 Azure 资源的安全配置。Guidance: Use Azure Policy or Azure Security Center to maintain security configurations for all Azure Resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.2:建立安全的操作系统配置7.2: Establish secure operating system configurations

指导:利用 Azure 安全中心建议“修复虚拟机上安全配置中的漏洞”,维护所有计算资源上的安全配置。Guidance: Utilize Azure Security Center recommendation "Remediate Vulnerabilities in Security Configurations on your Virtual Machines" to maintain security configurations on all compute resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.3:维护安全的 Azure 资源配置7.3: Maintain secure Azure resource configurations

指导:使用 Azure Policy“[拒绝]”和“[不存在则部署]”效果对不同的 Azure 资源强制实施安全设置。Guidance: Use Azure policy [deny] and [deploy if not exist] effects to enforce secure settings across your Azure resources.

如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表 (ACR)),请使用 Azure Policy 审核 Azure 容器注册表的合规性。If using a cloud-based private registry like Azure Container Registry (ACR) with Azure Container Instances, audit compliance of Azure container registries using Azure Policy:.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.4:维护安全的操作系统配置7.4: Maintain secure operating system configurations

指导:不适用;此控制措施适用于计算资源。Guidance: Not applicable; this control is intended for compute resources.

责任:共享Responsibility: Shared

Azure 安全中心监视:无Azure Security Center monitoring: None

7.5:安全存储 Azure 资源的配置7.5: Securely store configuration of Azure resources

指导:如果使用自定义的 Azure Policy 定义,请使用 Azure Repos 安全地存储和管理代码。Guidance: If using custom Azure policy definitions, use Azure Repos to securely store and manage your code.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.6:安全存储自定义操作系统映像7.6: Securely store custom operating system images

指导:不适用;此控制措施仅适用于计算资源。Guidance: Not applicable; this control only applies to compute resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.7:部署 Azure 资源的配置管理工具7.7: Deploy configuration management tools for Azure resources

指导:使用 Azure 策略针对系统配置发出警报,以及审核和强制实施系统配置。Guidance: Use Azure Policy to alert, audit, and enforce system configurations. 另外,开发一个用于管理策略例外的流程和管道。Additionally, develop a process and pipeline for managing policy exceptions.

如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表 (ACR)),请使用 Azure Policy 审核 Azure 容器注册表的合规性。If using a cloud-based private registry like Azure Container Registry (ACR) with Azure Container Instances, audit compliance of Azure container registries using Azure Policy:.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.8:部署操作系统的配置管理工具7.8: Deploy configuration management tools for operating systems

指导:不适用。Guidance: Not applicable. 基准适用于计算资源。Benchmark applies to compute resources.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.9:为 Azure 资源实施自动配置监视7.9: Implement automated configuration monitoring for Azure resources

指导:使用 Azure 安全中心对 Azure 资源执行基线扫描。Guidance: Use Azure Security Center to perform baseline scans for your Azure Resources.

应用 Azure Policy 以便对可以在订阅中创建的资源类型施加限制。Apply Azure Policy to put restrictions on the type of resources that can be created in your subscriptions.

如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表 (ACR)),请使用 Azure Policy 审核 Azure 容器注册表的合规性。If using a cloud-based private registry like Azure Container Registry (ACR) with Azure Container Instances, audit compliance of Azure container registries using Azure Policy:.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.10:为操作系统实施自动配置监视7.10: Implement automated configuration monitoring for operating systems

指导:使用 Azure 安全中心对 OS 和容器的 Docker 设置执行基线扫描。Guidance: Use Azure Security Center to perform baseline scans for OS and Docker Settings for containers.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.11:安全管理 Azure 机密7.11: Manage Azure secrets securely

指导:将托管服务标识与 Azure Key Vault 结合使用,以便简化和保护云应用程序的机密管理。Guidance: Use Managed Service Identity in conjunction with Azure Key Vault to simplify and secure secret management for your cloud applications.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.12:安全自动管理标识7.12: Manage identities securely and automatically

指导:使用托管标识在 Azure Active Directory (Azure AD) 中为 Azure 服务提供一个自动托管的标识。Guidance: Use Managed Identities to provide Azure services with an automatically managed identity in Azure Active Directory (Azure AD). 使用托管标识可以向支持 Azure AD 身份验证的任何服务(包括 Azure 密钥保管库)进行身份验证,无需在代码中放入任何凭据。Managed Identities allows you to authenticate to any service that supports Azure AD authentication, including Azure Key Vault, without any credentials in your code.

如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表 (ACR)),请使用 Azure Policy 审核 Azure 容器注册表的合规性。If using a cloud-based private registry like Azure Container Registry (ACR) with Azure Container Instances, audit compliance of Azure container registries using Azure Policy:.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

7.13:消除意外的凭据透露7.13: Eliminate unintended credential exposure

指南:实施凭据扫描程序来识别代码中的凭据。Guidance: Implement Credential Scanner to identify credentials within code. 凭据扫描程序还会建议将发现的凭据转移到更安全的位置,例如 Azure Key Vault。Credential Scanner will also encourage moving discovered credentials to more secure locations such as Azure Key Vault.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

恶意软件防护Malware Defense

有关详细信息,请参阅 Azure 安全基线: 恶意软件防护For more information, see the Azure Security Benchmark: Malware Defense.

8.1:使用集中管理的反恶意软件8.1: Use centrally-managed anti-malware software

指导:使用适用于 Azure 云服务和虚拟机的 Microsoft Antimalware 来持续监视和保护资源。Guidance: Use Microsoft Antimalware for Azure Cloud Services and Virtual Machines to continuously monitor and defend your resources. 对于 Linux,请使用第三方反恶意软件解决方案。For Linux, use third party antimalware solution.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

8.2:预先扫描要上传到非计算 Azure 资源的文件8.2: Pre-scan files to be uploaded to non-compute Azure resources

指导:在支持 Azure 服务(例如 Azure 容器实例)的底层主机上已启用 Microsoft Antimalware,但是,该软件不会针对客户数据运行。Guidance: Microsoft Antimalware is enabled on the underlying host that supports Azure services (for example, Azure Container Instances), however it does not run on customer data.

预扫描任何上传到非计算 Azure 资源(例如应用服务、Data Lake Storage、Blob 存储等)的文件。Pre-scan any files being uploaded to non-compute Azure resources, such as App Service, Data Lake Storage, Blob Storage, etc.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

数据恢复Data Recovery

有关详细信息,请参阅 Azure 安全基线: 数据恢复For more information, see the Azure Security Benchmark: Data Recovery.

9.1:确保定期执行自动备份9.1: Ensure regular automated back-ups

指导:如果在 Azure 容器实例中使用基于云的专用注册表(例如 Azure 容器注册表 (ACR)),则始终会自动复制 Azure 容器注册表中的数据,以确保持久性和高可用性。Guidance: If using a cloud-based private registry like Azure Container Registry (ACR) with Azure Container Instances, the data in your Azure container registry is always automatically replicated to ensure durability and high availability. Azure 容器注册表会复制你的数据,以便在发生计划内和计划外事件时保护你的数据。Azure Container Registry copies your data so that it is protected from planned and unplanned events.

(可选)异地复制容器注册表,以在多个 Azure 区域中维护注册表副本。Optionally geo-replicate a container registry to maintain registry replicas in multiple Azure regions.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

9.2:执行完整系统备份,并备份客户管理的所有密钥9.2: Perform complete system backups and backup any customer-managed keys

指导:(可选)通过将容器映像从一个注册表导入到另一个注册表来备份它们。Guidance: Optionally back up container images by importing from one registry to another.

使用 Azure 命令行工具或 SDK 在 Azure Key Vault 中备份客户管理的密钥。Back up customer-managed keys in Azure Key Vault using Azure command-line tools or SDKs.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

9.3:验证所有备份,包括客户管理的密钥9.3: Validate all backups including customer-managed keys

指导:使用 Azure 命令行工具或 SDK 在 Azure 密钥保管库中测试已备份的客户管理的密钥的还原。Guidance: Test restoration of backed up customer-managed keys in Azure Key Vault using Azure command-line tools or SDKs.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

9.4:确保保护备份和客户管理的密钥9.4: Ensure protection of backups and customer-managed keys

指导:你可以在 Azure Key Vault 中启用“软删除”,以防止意外删除或恶意删除密钥。Guidance: You may enable Soft-Delete in Azure Key Vault to protect keys against accidental or malicious deletion.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

事件响应Incident Response

有关详细信息,请参阅 Azure 安全基线: 事件响应For more information, see the Azure Security Benchmark: Incident Response.

10.1:创建事件响应指导10.1: Create an incident response guide

指南:为组织制定事件响应指南。Guidance: Build out an incident response guide for your organization. 确保在书面的事件响应计划中定义人员职责,以及事件处理/管理从检测到事件后审查的各个阶段。Ensure that there are written incident response plans that define all roles of personnel as well as phases of incident handling/management from detection to post-incident review.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

10.2:创建事件评分和优先级设定过程10.2: Create an incident scoring and prioritization procedure

指导:Azure 安全中心为每条警报分配严重性,方便你根据优先级来确定应该最先调查的警报。Guidance: Azure Security Center assigns a severity to each alert to help you prioritize which alerts should be investigated first. 严重性取决于安全中心在发出警报时所依据的检测结果和分析结果的置信度,以及导致发出警报的活动的恶意企图的置信度。The severity is based on how confident Security Center is in the finding or the analytic used to issue the alert as well as the confidence level that there was malicious intent behind the activity that led to the alert.

此外,使用标记来标记订阅,并创建命名系统来对 Azure 资源进行标识和分类,特别是处理敏感数据的资源。Additionally, mark subscriptions using tags and create a naming system to identify and categorize Azure resources, especially those processing sensitive data. 你的责任是根据发生事件的 Azure 资源和环境的关键性确定修正警报的优先级。It's your responsibility to prioritize the remediation of alerts based on the criticality of the Azure resources and environment where the incident occurred.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

10.3:测试安全响应过程10.3: Test security response procedures

指导:定期执行演练来测试系统的事件响应功能。Guidance: Conduct exercises to test your systems' incident response capabilities on a regular cadence. 识别弱点和差距,并根据需要修改计划。Identify weak points and gaps and revise plan as needed.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

10.4:提供安全事件联系人详细信息,并针对安全事件配置警报通知10.4: Provide security incident contact details and configure alert notifications for security incidents

指导:如果 Microsoft 安全响应中心 (MSRC) 发现非法或未经授权的某方访问了客户的数据,Azure 将使用安全事件联系人信息与你取得联系。Guidance: Security incident contact information will be used by Azure to contact you if the Microsoft Security Response Center (MSRC) discovers that the customer's data has been accessed by an unlawful or unauthorized party. 事后审查事件,确保问题得到解决。Review incidents after the fact to ensure that issues are resolved.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

10.5:将安全警报整合到事件响应系统中10.5: Incorporate security alerts into your incident response system

指导:使用连续导出功能导出 Azure 安全中心警报和建议。Guidance: Export your Azure Security Center alerts and recommendations using the Continuous Export feature. 使用连续导出可以手动导出或者持续导出警报和建议。Continuous Export allows you to export alerts and recommendations either manually or in an ongoing, continuous fashion. 可以使用 Azure 安全中心数据连接器将警报流式传输到 Azure Sentinel。You may use the Azure Security Center data connector to stream the alerts to Azure Sentinel.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

10.6:自动响应安全警报10.6: Automate the response to security alerts

指导:使用 Azure 安全中心内的工作流自动化功能可以通过“逻辑应用”针对安全警报和建议自动触发响应。Guidance: Use the Workflow Automation feature in Azure Security Center to automatically trigger responses via "Logic Apps" on security alerts and recommendations.

责任:客户Responsibility: Customer

Azure 安全中心监视:无Azure Security Center monitoring: None

渗透测试和红队练习Penetration Tests and Red Team Exercises

有关详细信息,请参阅 Azure 安全基线: 渗透测试和红队演练For more information, see the Azure Security Benchmark: Penetration Tests and Red Team Exercises.

11.1:定期对 Azure 资源执行渗透测试,确保修正所有发现的关键安全问题11.1: Conduct regular penetration testing of your Azure resources and ensure remediation of all critical security findings

指导:请遵循 Microsoft 云渗透测试互动规则,确保你的渗透测试不违反 Azure 政策。Guidance: Follow the Microsoft Cloud Penetration Testing Rules of Engagement to ensure your penetration tests are not in violation of Azure policies. 使用 Azure 红队演练策略和执行,并针对 Azure 托管云基础结构、服务和应用程序执行现场渗透测试。Use Azure's strategy and execution of Red Teaming and live site penetration testing against Azure-managed cloud infrastructure, services, and applications.

责任:共享Responsibility: Shared

Azure 安全中心监视:无Azure Security Center monitoring: None

后续步骤Next steps