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

容器实例的 Azure 安全基线包含可帮助你改进部署安全态势的建议。The Azure Security Baseline for Container Instances contains recommendations that will help you improve the security posture of your deployment.

此服务的基线摘自 Azure 安全基准版本 1.0,其中提供了有关如何根据我们的最佳做法指导保护 Azure 上的云解决方案的建议。The baseline for this service is drawn from the Azure Security Benchmark version 1.0, which provides recommendations on how you can secure your cloud solutions on Azure with our best practices guidance.

有关详细信息,请参阅 Azure 安全基线概述For more information, see the Azure security baselines overview.

网络安全性Network security

有关详细信息,请参阅安全控制:网络安全For more information, see Security control: Network security.

1.1:在虚拟网络中使用网络安全组或 Azure 防火墙保护资源1.1: Protect resources using Network Security Groups or Azure Firewall on your Virtual Network

指导:Azure 虚拟网络为 Azure 资源和本地资源提供安全的专用网络。Guidance: Azure Virtual Network provides secure, private networking for your Azure and on-premises resources. 将 Azure 容器实例中的容器组与 Azure 虚拟网络集成。Integrate your container groups in Azure Container Instances with an Azure virtual network.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

1.2:监视和记录 VNet、子网和 NIC 的配置与流量1.2: Monitor and log the configuration and traffic of Vnets, Subnets, and NICs

指导:使用 Azure 安全中心并修正网络保护建议来帮助保护 Azure 中的网络资源。Guidance: Use Azure Security Center and remediate network protection recommendations to help protect your network resources in Azure. 启用 NSG 流日志,并将日志发送到存储帐户中进行流量审核。Enable NSG flow logs and send logs into a Storage Account for traffic audit.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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

指导:在 Azure 容器实例中托管的关键 Web 应用程序前部署 Azure Web 应用程序防火墙 (WAF),以对传入的流量进行额外的检查。Guidance: Deploy Azure Web Application Firewall (WAF) in front of critical web applications hosted in Azure Container Instances for additional inspection of incoming traffic. 启用 WAF 的诊断设置,并将日志引入存储帐户、事件中心或 Log Analytics 工作区。Enable Diagnostic Setting for WAF and ingest logs into a Storage Account, Event Hub, or Log Analytics Workspace.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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

指导:在 Azure 虚拟网络上启用 DDoS 标准保护,以防范 DDoS 攻击。Guidance: Enable DDoS Standard protection on your Azure Virtual Networks to guard against DDoS attacks. 使用 Azure 安全中心的集成式威胁情报功能拒绝与已知的恶意 IP 地址通信。Use Azure Security Center Integrated Threat Intelligence to deny communications with known malicious 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 地址。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 配置。Use Azure Security Center Adaptive Network Hardening to recommend NSG configurations that limit ports and source IPs based on actual traffic and threat intelligence.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

1.5:记录网络数据包和流日志1.5: Record network packets and flow logs

指导:如果将网络安全组 (NSG) 与虚拟网络实现一起使用,请为附加到委派给 Azure 容器实例的子网的 NSG 启用 NSG 流日志。Guidance: If using Network Security Groups (NSGs) with your virtual network implementation, enable NSG flow logs for the NSG attached to the subnet delegated to Azure Container Instances. 将 NSG 流日志记录到 Azure 存储帐户中,以生成流记录。Record the NSG flow logs into an Azure Storage Account to generate flow records. 如果需要调查异常活动,请启用 Azure 网络观察程序数据包捕获。If required for investigating anomalous activity, enable Azure Network Watcher packet capture.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:目前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

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

指导:为 Web 应用程序部署 Azure 应用程序网关,并为受信任的证书启用 HTTPS/SSL。Guidance: Deploy Azure Application Gateway for web applications with HTTPS/SSL enabled for trusted certificates.

Azure 安全中心监视:目前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

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

指导:在网络安全组或 Azure 防火墙中使用虚拟网络服务标记来定义网络访问控制。Guidance: Use Virtual Network Service Tags 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. 在规则的相应源或目标字段中指定服务标记名称(例如 ApiManagement),可以允许或拒绝相应服务的流量。By specifying the service tag name (e.g., ApiManagement) 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.

还可使用应用程序安全组来帮助简化复杂的安全配置。You may also use Application Security Groups to help simplify complex security configuration. 使用应用程序安全组可将网络安全性配置为应用程序结构的固有扩展,从而可以基于这些组将虚拟机分组以及定义网络安全策略。Application security groups enable you to configure network security as a natural extension of an application's structure, allowing you to group virtual machines and define network security policies based on those groups.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

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

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

1.10:阐述流量配置规则1.10: Document traffic configuration rules

指导:将标记用于 NSG 以及其他与网络安全和流量流有关的资源。Guidance: Use Tags for NSGs and other resources related to network security and traffic flow. 对于单个 NSG 规则,请使用“说明”字段针对允许流量传入/传出网络的任何规则指定业务需求和/或持续时间等。For individual NSG rules, use the "Description" field to specify business need and/or duration (etc.) for any rules that allow traffic to/from a network.

使用标记相关的任何内置 Azure 策略定义(例如“需要标记及其值”)来确保使用标记创建所有资源,并在有现有资源不带标记时发出通知。Use any of the built-in Azure policy definitions related to tagging, such as "Require tag and its value" to ensure that all resources are created with Tags and to notify you of existing untagged resources.

可以使用 Azure PowerShell 或 Azure CLI 根据资源的标记查找资源或对其执行操作。You may use Azure PowerShell or Azure CLI to look-up or perform actions on resources based on their Tags.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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 instances. 在 Azure Monitor 中创建当关键网络资源发生更改时触发的警报。Create alerts within Azure Monitor that will trigger when changes to critical network resources take place.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

日志记录和监视Logging and monitoring

有关详细信息,请参阅安全控制:日志记录和监视For more information, see Security control: Logging and monitoring.

2.1:使用批准的时间同步源2.1: Use approved time synchronization sources

指导:Azure 维护 Azure 资源的时间源,但是,你可以选择管理计算资源的时间同步设置。Guidance: Azure maintains time sources for Azure resources, however, you have the option to manage the time synchronization settings for your compute resources. 例如,在正在运行的容器中运行时间同步命令。For example, run a time synchronization command in a running container.

Azure 安全中心监视:目前不可用Azure Security Center monitoring: Currently not available

责任:AzureResponsibility: Azure

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 group. 在 Azure Monitor 中,使用 Log Analytics 工作区来查询和执行分析,并使用 Azure 存储帐户进行长期/存档存储。Within Azure Monitor, use Log Analytics Workspace(s) to query and perform analytics, and use Azure Storage Accounts for long-term/archival storage.

Azure 安全中心监视:当前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

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 in your registry. Azure 容器实例提供内置支持,支持将容器组日志和事件数据以及容器日志发送到 Azure Monitor 日志。Azure Container Instances includes built-in support for sending container group logs and event data, and container logs, to Azure Monitor logs.

Azure 安全中心监视:当前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

2.4:从操作系统收集安全日志2.4: Collect security logs from operating systems

指导:不适用。Guidance: Not applicable. 此项指导适用于 IaaS 计算资源。This guideline is intended for IaaS compute resources.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:不适用Responsibility: Not applicable

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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

2.6:监视和审查日志2.6: Monitor and review Logs

指导:分析和监视日志中的异常行为,并定期查看结果。Guidance: Analyze and monitor 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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:使用 Log Analytics 工作区监视安全日志和事件中的异常活动并发出警报。Guidance: Use Log Analytics Workspace for monitoring and alerting on anomalous activity found in security logs and events.

Azure 安全中心监视:当前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

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

指导:如果需要,请提供你自己的反恶意软件解决方案和事件集合以在容器中运行。Guidance: Provide your own anti-malware solution and event collection if needed to run in a container.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:如果需要,请提供你自己的解决方案以在容器中查询 DNS 日志。Guidance: Provide your own solution if needed to query DNS logs in a container.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

2.10:启用命令行审核日志记录2.10: Enable command-line audit logging

指导:如果需要,请在正在运行的容器实例中配置控制台日志记录。Guidance: If needed, configure console logging in a running container instance.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not Applicable

责任:客户Responsibility: Customer

标识和访问控制Identity and access control

有关详细信息,请参阅安全控制:标识和访问控制For more information, see Security control: 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 you use an 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.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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 you use an 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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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 you use an 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.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

3.4:将单一登录 (SSO) 与 Azure Active Directory 配合使用3.4: Use single sign-on (SSO) with Azure Active Directory

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

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

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

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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

指南:将 PAW(特权访问工作站)与为登录和配置 Azure 资源而配置的 MFA 结合使用。Guidance: Use PAWs (privileged access workstations) with MFA configured to log into and configure Azure resources.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

3.7:记录来自管理帐户的可疑活动并对其发出警报3.7: Log and alert on suspicious activity 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.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:目前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

3.11:监视访问已停用帐户的企图3.11: Monitor attempts to access deactivated accounts

指导:你有权访问 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 Active Directory 用户帐户创建诊断设置,并将审核日志和登录日志发送到 Log Analytics 工作区,来简化此过程。You can streamline this process by creating Diagnostic Settings for Azure Active Directory 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.

Azure 安全中心监视:目前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

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

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

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:不适用Responsibility: Not applicable

数据保护Data protection

有关详细信息,请参阅安全控制:数据保护For more information, see Security control: Data protection.

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

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

对容器映像进行标记和版本控制,以帮助跟踪用于存储或处理敏感信息的映像。Tag and version container images, to assist in tracking images that store or process sensitive information.

Azure 安全中心监视:目前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

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

指导:为开发、测试和生产实施单独的订阅和/或管理组。Guidance: Implement separate subscriptions, and/or management groups for development, test, and production. 资源应当按 VNet/子网进行分隔,相应地进行标记,并由 NSG 或 Azure 防火墙提供保护。Resources should be separated by VNet/Subnet, tagged appropriately, and secured by an NSG or Azure Firewall. 存储或处理敏感数据的资源应当充分隔离。Resources storing or processing sensitive data should be sufficiently isolated.

Azure 安全中心监视:目前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

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. 监视并阻止从 Azure 文件共享和其他装载到容器实例的卷传输未经授权的信息。Monitor and block unauthorized information transfer from Azure file shares and other volumes mounted to container instances.

对于 Microsoft 管理的底层平台,Azure 会将所有客户内容视为敏感数据,并会全方位地防范客户数据丢失和泄露。For the underlying platform which is managed by Microsoft, Azure treats all customer content 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.

Azure 安全中心监视:目前不可用Azure Security Center monitoring: Currently not available

责任:共享Responsibility: Shared

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

指导:确保连接到 Azure 容器组的任何客户端能够协商 TLS 1.2 或更高版本。Guidance: Ensure that any clients connecting to your Azure container groups 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.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:共享Responsibility: Shared

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

指导:数据标识、分类和丢失防护功能目前不可用于 Azure 容器实例。Guidance: Data identification, classification, and loss prevention features are not currently available for Azure Container Instances. 标记可能正在处理敏感信息的容器组,如果需要出于合规性目的使用这些功能,请实施第三方解决方案。Tag container groups that may be processing sensitive information as such and implement third-party solution if required for compliance purposes.

对于 Microsoft 管理的底层平台,Azure 会将所有客户内容视为敏感数据,并会全方位地防范客户数据丢失和泄露。For the underlying platform which is managed by Microsoft, Azure treats all customer content 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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:共享Responsibility: Shared

4.6:使用 Azure RBAC 控制对资源的访问4.6: Use Azure RBAC to control access to resources

指导:使用 Azure 基于角色的访问控制 (Azure RBAC) 来控制对 Azure 容器实例数据和资源的访问。Guidance: Use Azure role-based access control (Azure RBAC) to control access to Azure Container Instances data and resources.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:不适用;此建议适用于 IaaS 计算资源。Guidance: Not applicable; this recommendation is intended for IaaS compute resources.

对于 Microsoft 管理的底层平台,Azure 会将所有客户内容视为敏感数据,并会全方位地防范客户数据丢失和泄露。For the underlying platform which is managed by Microsoft, Azure treats all customer content 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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:共享Responsibility: Shared

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

指导:默认情况下,Azure 容器实例中的所有部署数据都使用 Azure 托管密钥进行静态加密。Guidance: By default, all deployment data in Azure Container Instances is encrypted at rest using Azure-managed keys. 你可以选择使用自己的密钥(客户管理的密钥)管理加密。Optionally, manage the encryption with your own key (customer-managed key).

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:将 Azure Monitor 与 Azure 活动日志结合使用,可创建在容器组和容器实例发生更改时发出的警报。Guidance: Use Azure Monitor with the Azure Activity Log to create alerts for when changes take place to your container groups and container instances.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

漏洞管理Vulnerability management

有关详细信息,请参阅安全控制:漏洞管理For more information, see Security control: Vulnerability management.

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

指导:实施解决方案以扫描专用注册表中的容器映像并识别潜在漏洞。Guidance: Implement solutions to scan container images in a private registry and identify potential vulnerabilities. 遵循 Azure 安全中心关于对存储在 Azure 容器注册表中的容器映像执行漏洞评估的建议。Follow recommendations from Azure Security Center on performing vulnerability assessments on container images stored in Azure Container Registry. (可选)从 Azure 市场部署第三方解决方案,用于执行映像漏洞评估。Optionally deploy third-party solutions from Azure Marketplace to perform image vulnerability assessments.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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.

使用自定义或第三方解决方案修补容器映像。Use a custom or third party solution to patch container images. 如果将容器映像存储在 Azure 容器注册表中,可以运行 Azure 容器注册表任务,根据基础 OS 映像中的安全修补程序或其他更新自动更新容器注册表中的应用程序映像。If you store container images in Azure Container Registry, run Azure Container Registry tasks to automate updates to application images in a container registry based on security patches or other updates in base OS images.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:共享Responsibility: Shared

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

指导:使用自定义或第三方解决方案修补容器映像。Guidance: Use a custom or third party solution to patch container images. 如果将容器映像存储在 Azure 容器注册表中,可以运行 Azure 容器注册表任务,根据基础 OS 映像中的安全修补程序或其他更新自动更新容器注册表中的应用程序映像。If you store container images in Azure Container Registry, run Azure Container Registry tasks to automate updates to application images in a container registry based on security patches or other updates in base OS images.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:以一致的间隔导出映像扫描结果,并比较结果以验证漏洞是否已修复。Guidance: Export image scanning results at consistent intervals and compare the results to verify that vulnerabilities have been remediated. 如果将容器映像存储在 Azure 容器注册表中,则将注册表与 Azure 安全中心集成,以便定期扫描容器映像中的漏洞。If you store container images in Azure Container Registry, integrate your registry 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.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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

指导:如果将容器映像存储在 Azure 容器注册表中,则将注册表与 Azure 安全中心集成,以便定期扫描容器映像中的漏洞并对风险进行分类。Guidance: If you store container images in Azure Container Registry, integrate your registry 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.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

库存和资产管理Inventory and asset management

有关详细信息,请参阅安全控制:清单和资产管理For more information, see Security control: Inventory and asset management.

6.1:使用 Azure 资产发现6.1: Use Azure Asset Discovery

指导:使用 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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:将标记应用到提供元数据的 Azure 容器实例和相关资源,以便按逻辑将其组织到分类中。Guidance: Apply tags to Azure Container Instances and related resources giving metadata to logically organize them into a taxonomy.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:在适用的情况下,请使用标记、管理组和单独的订阅来组织和跟踪资产。Guidance: Use tagging, management groups, and separate subscriptions, where appropriate, to organize and track assets. 定期核对清单,确保及时地从订阅中删除未经授权的资源。Reconcile inventory on a regular basis and ensure unauthorized resources are deleted from the subscription in a timely manner.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

6.4:维护已批准的 Azure 资源和软件标题的清单6.4: Maintain an inventory of approved Azure resources and software titles

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

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:实施你自己的解决方案或第三方解决方案,以便为已批准的容器化应用程序清点软件。Guidance: Implement your own solution, or a third-party solution, to inventory software for approved containerized applications.

实施解决方案以扫描专用注册表中的容器映像并识别潜在漏洞。Implement solutions to scan container images in a private registry and identify potential vulnerabilities. 遵循 Azure 安全中心关于对存储在 Azure 容器注册表中的容器映像执行漏洞评估的建议。Follow recommendations from Azure Security Center to perform vulnerability assessments on container images stored in Azure Container Registry. (可选)从 Azure 市场部署第三方解决方案,用于执行映像漏洞评估。Optionally deploy third-party solutions from Azure Marketplace to perform image vulnerability assessments.

监视 Azure 容器实例日志中的异常行为,并定期查看结果。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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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 and software applications.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:对容器映像进行标记和版本控制,以帮助跟踪运行已批准应用程序的映像。Guidance: Tag and version container images, to assist in tracking images that run approved applications.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:不适用Responsibility: Not applicable

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

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

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

6.10:实施已批准的应用程序列表6.10: Implement approved application list

指导:对容器映像进行标记和版本控制,以帮助跟踪运行已批准应用程序的映像。Guidance: Tag and version container images, to assist in tracking images that run approved applications.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:不适用Responsibility: Not applicable

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

指导:通过为“Azure 管理”应用配置“阻止访问”,使用 Azure 条件访问来限制用户与 Azure 资源管理器交互的能力。Guidance: Use Azure Conditional Access to limit users' ability to interact with Azure Resources Manager by configuring "Block access" for the "Azure Management" App.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:所有有权访问 Azure 容器实例的用户都可以在容器内执行脚本。Guidance: All users with access to Azure Container Instances can execute scripts within containers.

使用不同的 Azure 订阅或管理组来管理和查看对 Azure 容器实例资源的访问,或者使用虚拟网络和 NSG 或 Azure 防火墙隔离资源。Manage and review access to Azure Container Instances resources by using different Azure subscriptions or management groups, or isolate resources using virtual networks and NSGs or Azure Firewall.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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 network and sufficiently secured with either an Azure Firewall or Network Security Group.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

安全配置Secure configuration

有关详细信息,请参阅安全控制:安全配置For more information, see Security control: Secure configuration.

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

指导:通过使用 Azure 资源管理器模板或导出为 YAML 文件,维护批准的容器组配置。Guidance: Maintain an approved container group configuration by using an Azure Resource Manager template or exporting to a YAML file. 使用 Azure Policy 维护相关 Azure 资源的安全配置。Use Azure Policy to maintain security configurations for related Azure resources.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:使用自定义或第三方解决方案修补容器映像。Guidance: Use a custom or third party solution to patch container images. 如果将容器映像存储在 Azure 容器注册表中,可以运行 Azure 容器注册表任务,根据基础 OS 映像中的安全修补程序或其他更新自动更新容器注册表中的应用程序映像。If you store container images in Azure Container Registry, run Azure Container Registry tasks to automate updates to application images in a container registry based on security patches or other updates in base OS images.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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

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

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:实施解决方案以扫描专用注册表中的容器映像,并识别 OS 配置中的潜在漏洞。Guidance: Implement solutions to scan container images in a private registry and identify potential vulnerabilities in OS configurations. 遵循 Azure 安全中心关于对存储在 Azure 容器注册表中的容器映像执行漏洞评估的建议。Follow recommendations from Azure Security Center to perform vulnerability assessments on container images stored in Azure Container Registry. (可选)从 Azure 市场部署第三方解决方案,用于执行映像漏洞评估。Optionally deploy third-party solutions from Azure Marketplace to perform image vulnerability assessments.

使用自定义或第三方解决方案修补容器映像。Use a custom or third party solution to patch container images. 如果将容器映像存储在 Azure 容器注册表中,可以运行 Azure 容器注册表任务,根据基础 OS 映像中的安全修补程序或其他更新自动更新容器注册表中的应用程序映像。If you store container images in Azure Container Registry, run Azure Container Registry tasks to automate updates to application images in a container registry based on security patches or other updates in base OS images.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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

指导:在源代码管理中安全地存储和管理 ARM 模板、YAML 文件和自定义 Azure 策略定义。Guidance: Store and manage ARM templates, YAML files, and custom Azure policy definitions securely in source control.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:将容器映像存储在 Azure 容器注册表中,并利用 Azure RBAC 确保只有授权用户才能访问这些映像。Guidance: Store container images in Azure Container Registry and leverage Azure RBAC to ensure only authorized users may access the images.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

7.7:部署系统配置管理工具7.7: Deploy system configuration management tools

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

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

指导:不适用;此项指导适用于 IaaS 计算资源。Guidance: Not applicable; this guideline is intended for IaaS compute resources.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:不适用Responsibility: Not applicable

7.9:为 Azure 服务实施自动配置监视7.9: Implement automated configuration monitoring for Azure services

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

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

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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

指导:如果使用 Azure 容器注册表存储容器映像,请使用 Azure 安全中心对 OS 和容器的 Docker 设置执行基线扫描。Guidance: If you use Azure Container Registry to store container images, use Azure Security Center to perform baseline scans for OS and Docker settings for containers.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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

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

Azure 安全中心监视:目前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

恶意软件防护Malware defense

有关详细信息,请参阅安全控制:恶意软件防护For more information, see Security control: Malware defense.

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

指导:不适用;此项指导适用于 IaaS 计算资源。Guidance: Not applicable; this guideline is intended for IaaS compute resources.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:不适用Responsibility: Not applicable

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 content.

预扫描任何上传到非计算 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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

步骤 8.3:确保反恶意软件和签名已更新8.3: Ensure anti-malware software and signatures are updated

指导:不适用;此建议适用于 IaaS 计算资源。Guidance: Not applicable; this recommendation is intended for IaaS compute resources.

在支持 Azure 服务(例如 Azure 容器实例)的基础主机上已启用 Azure 反恶意软件,但是,该软件不会针对客户内容运行。Azure anti-malware is enabled on the underlying host that supports Azure services (for example, Azure Container Instances), however it does not run on customer content.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:不适用Responsibility: Not applicable

数据恢复Data recovery

有关详细信息,请参阅安全控制:数据恢复For more information, see Security control: Data recovery.

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

指导:启用 Azure 备份并配置备份源(例如装载到容器组的文件共享)以及所需的频率和保持期。Guidance: Enable Azure Backup and configure the backup source (such as a file share mounted to container groups), as well as the desired frequency and retention period.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

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

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

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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

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

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:目前不可用Azure Security Center monitoring: Currently not available

责任:客户Responsibility: Customer

事件响应Incident response

有关详细信息,请参阅安全控制:事件响应For more information, see Security control: 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.

客户还可以利用 NIST 的“计算机安全事件处理指南”来制定他们自己的事件响应计划。Customer may also leverage NIST's Computer Security Incident Handling Guide to aid in the creation of their own incident response plan.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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.

此外,请明确标记订阅(例如Additionally, clearly mark subscriptions (for example. 生产、非生产),并创建命名系统来对 Azure 资源进行明确标识和分类。production, non-production) and create a naming system to clearly identify and categorize Azure resources.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:是Azure Security Center monitoring: Yes

责任:客户Responsibility: Customer

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 安全中心数据连接器将警报流式传输到 Sentinel。You may use the Azure Security Center data connector to stream the alerts Sentinel.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:客户Responsibility: Customer

渗透测试和红队练习Penetration tests and red team exercises

有关详细信息,请参阅安全控制:渗透测试和红队演练For more information, see Security control: Penetration tests and red team exercises.

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

指导:遵循 Azure 互动规则,确保你的渗透测试不违反 Azure 政策。Guidance: Follow the Azure 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.

Azure 安全中心监视:不适用Azure Security Center monitoring: Not applicable

责任:共享Responsibility: Shared

后续步骤Next steps