事件网格的 Azure 安全基线Azure security baseline for Event Grid

适用于 Azure 事件网格的 Azure 安全基线包含有助于改进部署安全状况的建议。The Azure Security Baseline for Azure Event Grid 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 Azure Security Baselines overview.

网络安全性Network security

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

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

指导:使用专用终结点,可以允许事件通过专用链接安全地从虚拟网络直接进入事件网格主题和域,而无需通过公共 Internet。Guidance: You can use private endpoints to allow ingress of events directly from your virtual network to your Event Grid topics and domains securely over a private link without going through the public internet. 为事件网格主题或域创建专用终结点时,它会在 VNet 上的客户端与事件网格资源之间提供安全连接。When you create a private endpoint for your Event Grid topic or domain, it provides secure connectivity between clients on your VNet and your Event Grid resource. 从虚拟网络的 IP 地址范围为专用终结点分配 IP 地址。The private endpoint is assigned an IP address from the IP address range of your virtual network. 专用终结点与事件网格服务之间的连接使用安全的专用链接。The connection between the private endpoint and the Event Grid service uses a secure private link.

对于将内容发布到主题和域的操作,Azure 事件网格还支持进行基于公共 IP 的访问控制。Azure Event Grid also supports public IP-based access controls for publishing to topics and domains. 使用基于 IP 的控制,可以将主题和域的发布者限制为一组经过批准的计算机和云服务。With IP-based controls, you can limit the publishers to a topic or domain to only a set of approved set of machines and cloud services. 此功能是对事件网格支持的身份验证机制的补充。This feature complements the authentication mechanisms supported by Event Grid.

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

责任:客户Responsibility: Customer

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

指导:使用 Azure 安全中心并遵循网络保护建议来保护 Azure 中的事件网格资源。Guidance: Use Azure Security Center and follow network protection recommendations to help secure your Event Grid resources in Azure. 如果使用 Azure 虚拟机来访问事件网格资源,请启用网络安全组 (NSG) 流日志,并将日志发送到存储帐户进行流量If using Azure virtual machines to access your Event Grid resources, enable network security group (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 应用程序。Guidance: Not applicable; this recommendation is intended for web applications running on Azure App Service or compute resources.

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

责任:不适用Responsibility: Not Applicable

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

指导:如果使用 Azure 虚拟机来访问事件网格资源,请启用网络安全组 (NSG) 流日志,并将日志发送到存储帐户进行流量审核。Guidance: If you are using Azure virtual machines to access your Event Grid resources, enable network security group (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.

请注意,为事件网格创建专用终结点时,默认情况下会禁用网络策略,因此以上工作流可能不起作用。Note network policies are disabled by default when private endpoints are created for Event Grid so above workflow may not work.

启用网络观察程序数据包捕获(如果调查异常活动时有此需要)。If necessary for investigating anomalous activity, enable 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 防火墙威胁情报。When payload inspection is not a requirement, Azure Firewall threat intelligence can be used. 使用基于 Azure 防火墙威胁情报的筛选功能,针对进出已知恶意 IP 地址和域的流量发出警报并/或阻止该流量。Azure Firewall threat intelligence-based filtering is used to alert on and/or block 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 block malicious traffic.

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

责任:客户Responsibility: Customer

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

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

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

责任:不适用Responsibility: Not Applicable

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

指导:对于虚拟网络中需要访问 Azure 事件网格资源的资源,请在网络安全组或 Azure 防火墙上使用虚拟网络服务标记来定义网络访问控制。Guidance: For resources in virtual networks that need access to your Azure Event Grid resources, 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. 通过在规则的相应源字段或目标字段中指定服务标记名(例如,AzureEventGrid),可以允许或拒绝相应服务的流量。By specifying the service tag name (for example, AzureEventGrid) in the appropriate source or destination field of a rule, you can allow or deny the traffic for the corresponding service. Microsoft 会管理服务标记包含的地址前缀,并会在地址发生更改时自动更新服务标记。Microsoft manages the address prefixes encompassed by the service tag and automatically updates the service tag as addresses change.

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

责任:客户Responsibility: Customer

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

指导:使用 Azure Policy 为与 Azure 事件网格命名空间关联的网络资源定义和实施标准安全配置。Guidance: Define and implement standard security configurations for network resources associated with your Azure Event Grid namespaces with Azure Policy. 在“Microsoft.EventGrid”和“Microsoft.Network”命名空间中使用 Azure Policy 别名创建自定义策略,以审核或强制实施事件网格资源的网络配置。Use Azure Policy aliases in the "Microsoft.EventGrid" and "Microsoft.Network" namespaces to create custom policies to audit or enforce the network configuration of your Event Grid resources.

你还可以使用与 Azure 事件网格相关的内置策略定义,例如:- Azure 事件网格域应使用专用链接;- Azure 事件网格主题应使用专用链接You may also make use of built-in policy definitions related to Azure Event Grid, such as:- Azure Event Grid domains should use private links- Azure Event Grid topics should use private linksAzure

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

责任:客户Responsibility: Customer

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

指导:对与 Azure 事件网格资源关联的网络资源使用标记,以便按逻辑将这些资源组织成某种分类。Guidance: Use tags for network resources associated with your Azure Event Grid resources in order to logically organize them into a taxonomy.

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 活动日志监视网络资源配置,并检测与 Azure 事件网格相关的网络资源的更改。Guidance: Use Azure Activity Log to monitor network resource configurations and detect changes for network resources related to Azure Event Grid. 在 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

有关详细信息,请参阅 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 Azure Event Grid. 在 Azure Monitor 中,使用 Log Analytics 工作区来查询和执行分析,并使用存储帐户进行长期/存档存储。Within the Azure Monitor, use Log Analytics workspace(s) to query and perform analytics, and use storage accounts for long-term/archival storage. 也可启用第三方安全信息和事件管理 (SIEM) 并将数据加入其中。Alternatively, you may enable, and on-board data to a third-party Security Incident and Event Management (SIEM).

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

责任:客户Responsibility: Customer

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

指导:事件网格用户可以通过诊断设置在以下任一位置捕获和查看“发布和传递失败”日志:存储帐户、事件中心或 Log Analytics 工作区。Guidance: Diagnostic settings allow Event Grid users to capture and view publish and delivery failure Logs in either a Storage account, an event hub, or a Log Analytics Workspace.

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

责任:客户Responsibility: Customer

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

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

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

责任:不适用Responsibility: Not Applicable

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

指导:在 Azure Monitor 中,根据组织的合规性规定,为与 Azure 事件网格资源关联的 Log Analytics 工作区设置日志保留期。Guidance: In Azure Monitor, set the log retention period for Log Analytics workspaces associated with your Azure Event Grid resources according to your organization's compliance regulations.

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

责任:客户Responsibility: Customer

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

指导:分析和监视日志中的异常行为,并定期审查来自 Azure 事件网格的结果。Guidance: Analyze and monitor logs for anomalous behavior and regularly review the results from Azure Event Grid. 使用 Azure Monitor 和 Log Analytics 工作区查看日志并对日志数据执行查询。Use Azure Monitor and a Log Analytics workspace to review logs and perform queries on log data.

也可以启用数据并将其加入第三方 SIEM。Alternatively, you can enable and on-board data to a third-party SIEM.

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

责任:客户Responsibility: Customer

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

指导:在事件网格上启用诊断设置,以便访问“发布和传递失败”日志。Guidance: Enable diagnostic settings on your event grid for access to publish and delivery failure logs. 活动日志自动可用,包括事件源、日期、用户、时间戳、源地址、目标地址和其他有用元素。Activity logs, which are automatically available, include event source, date, user, timestamp, source addresses, destination addresses, and other useful elements. 你可以将日志发送到 Log Analytics 工作区。You may send the logs to a Log Analytics workspace. 使用 Azure 安全中心和 Log Analytics 监视安全日志和事件中的异常活动并发出警报。Use Azure Security Center with Log Analytics for monitoring and alerting on anomalous activity found in security logs and events.

你还可以创建有关 Azure 事件网格指标和活动日志操作的警报。You can also create alerts on Azure Event Grid metrics and activity log operations. 可以针对 Azure 事件网格资源(主题和域)的发布和交付这两种指标创建警报。You can create alerts on both publish and delivery metrics for Azure Event Grid resources (topics and domains).

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

责任:客户Responsibility: Customer

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

指导:不适用;Azure 事件网格不会处理或生成与反恶意软件相关的日志。Guidance: Not applicable; Azure Event Grid does not process or produce anti-malware related logs.

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

责任:不适用Responsibility: Not Applicable

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

指导:不适用;Azure 事件网格不会处理或生成与 DNS 相关的日志。Guidance: Not applicable; Azure Event Grid does not process or produce DNS-related logs.

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

责任:不适用Responsibility: Not Applicable

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

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

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

责任:不适用Responsibility: Not Applicable

标识和访问控制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 事件网格,可以控制授予不同用户用来执行各种管理操作的访问级别,例如列出事件订阅、创建新的事件订阅及生成密钥。Guidance: Azure Event Grid allows you to control the level of access given to different users to do various management operations such as list event subscriptions, create new ones, and generate keys. 事件网格使用 Azure 基于角色的访问控制 (Azure RBAC)。Event Grid uses Azure role-based access control (Azure RBAC). 事件网格支持内置角色和自定义角色。Event Grid supports built-in roles as well as custom roles.

借助基于 Azure 角色的访问控制 (Azure RBAC),可以通过角色分配管理对 Azure 资源的访问。Azure role-based access control (Azure RBAC) allows you to manage access to Azure resources through role assignments. 可以将这些角色分配给用户、组服务主体和托管标识。You can assign these roles to users, groups service principals and managed identities. 某些资源具有预定义的内置角色,可以通过工具(例如 Azure CLI、Azure PowerShell 或 Azure 门户)来清点或查询这些角色。There are pre-defined built-in roles for certain resources, and these roles can be inventoried or queried through tools such as Azure CLI, Azure PowerShell or the Azure portal.

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

责任:客户Responsibility: Customer

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

指导:对事件网格资源的访问管理是通过 Azure Active Directory (AD) 控制的。Guidance: Access management to Event Grid resources is controlled through Azure Active Directory (AD). Azure AD 没有默认密码。Azure AD does not have the concept of default passwords.

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 AD Privileged Identity Management 和 Azure 资源管理器来启用即时访问权限。You can also enable a Just-In-Time access by using Azure AD Privileged Identity Management and Azure Resource Manager.

事件网格可以为 Azure 事件网格主题或域启用托管服务标识,并使用该标识将事件转发到支持的目标,如服务总线队列和主题、事件中心和存储帐户。Event Grid can enable a managed service identity for Azure event grid topics or domains and use it to forward events to supported destinations such as Service Bus queues and topics, event hubs, and storage accounts. 共享访问签名 (SAS) 令牌用于将事件发布到 Azure 事件网格。Shared Access Signature (SAS) token is used for publishing events to Azure Event Grid. 使用这些帐户创建有关事件访问、转发和发布的标准操作过程。Create standard operating procedure around event access, forwarding, and publishing with those accounts.

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

指导:不适用;事件网格服务不支持 SSO。Guidance: Not applicable; Event Grid service doesn't support SSO.

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

责任:不适用Responsibility: Not Applicable

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

指导:不适用;事件网格服务不使用多重身份验证Guidance: Not applicable; Event Grid service doesn't use multi-factor authentication

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

责任:不适用Responsibility: Not Applicable

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

指导:不适用;事件网格方案不需要特权访问工作站。Guidance: Not applicable; no Event Grid scenarios require Privileged Access Workstations.

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

责任:不适用Responsibility: Not Applicable

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

指导:使用 Azure Active Directory 安全报告和监视来检测环境中何时发生可疑活动或不安全的活动。Guidance: Use Azure Active Directory security reports and monitoring to detect 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 only from approved locations

指导:不适用。Guidance: Not applicable. 事件网格不使用 Azure AD 对事件发布客户端进行身份验证;它支持通过 SAS 密钥进行身份验证。Event Grid doesn’t use Azure AD for authenticating event publishing clients; it supports authentication via SAS keys.

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

责任:客户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 事件网格主题或域启用托管服务标识,并使用该标识将事件转发到支持的目标,如服务总线队列和主题、事件中心和存储帐户。Event Grid can enable a managed service identity for Azure event grid topics or domains and use it to forward events to supported destinations such as Service Bus queues and topics, event hubs, and storage accounts. 共享访问签名 (SAS) 令牌用于将事件发布到 Azure 事件网格。Shared Access Signature (SAS) token is used for publishing events to Azure Event Grid.

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

责任:客户Responsibility: Customer

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

指南:Azure AD 提供日志来帮助发现过时的帐户。Guidance: Azure AD provides logs to help discover stale accounts. 此外,请使用 Azure AD 标识和访问评审来有效管理组成员身份、对企业应用程序的访问以及角色分配。In addition, use Azure AD identity and 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 Active Directory (AD) Privileged Identity Management (PIM) 生成日志和警报。Use Azure Active Directory (AD) Privileged Identity Management (PIM) for generation of logs and alerts when suspicious or unsafe activity occurs in the environment.

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

责任:客户Responsibility: Customer

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

指导:你有权访问 Azure AD 登录活动、审核和风险事件日志源,因此可以与任何 SIEM/监视工具集成。Guidance: You have access to Azure AD sign-in activity, audit, and risk event log sources, which allow you to integrate with any 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.

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

责任:客户Responsibility: Customer

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

指导:不适用;事件网格服务目前不支持客户密码箱。Guidance: Not applicable; Event Grid service doesn't support Customer Lockbox currently.

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

责任:不适用Responsibility: Not Applicable

数据保护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 tags to assist in tracking Azure resources that store or process sensitive information.

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

责任:客户Responsibility: Customer

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

指导:使用单独的订阅和管理组对各个安全域(如环境类型和数据敏感度级别)实现隔离。Guidance: Implement isolation using separate subscriptions and management groups for individual security domains such as environment type and data sensitivity level. 你可以限制对应用程序和企业环境所需 Azure 资源的访问级别。You can restrict the level of access to your Azure resources that your applications and enterprise environments demand. 可以通过 Azure RBAC 来控制对 Azure 资源的访问。You can control access to Azure resources via Azure RBAC.

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

责任:客户Responsibility: Customer

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

指导:对于由 Microsoft 管理的基础平台,Microsoft 会将所有客户内容都视为敏感信息,竭尽全力防范客户数据丢失和泄露。Guidance: For the underlying platform, which is managed by Microsoft, Microsoft treats all customer content as sensitive and goes to great lengths to guard against customer data loss and exposure. 为了确保 Azure 中的客户数据保持安全,Microsoft 实施并维护了一套可靠的数据保护控制措施和功能。To ensure customer data within Azure remains secure, Microsoft has implemented and maintains a suite of robust data protection controls and capabilities.

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

责任:共享Responsibility: Shared

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

指导:Azure 事件网格需要使用 HTTPS 进行发布操作,并支持使用 HTTPS 将事件传递到 Webhook 终结点。Guidance: Azure Event Grid requires HTTPS for publishing and supports HTTPS for delivering events to a webhook endpoint. 在 Azure Global 中,事件网格支持 1.1 和 1.2 版本的 TLS,但我们强烈建议使用 1.2 版本。In Azure Global, Event Grid supports both 1.1 and 1.2 versions of TLS, but we strongly recommend that you use the 1.2 version. 在国家云(例如 Azure 政府和由中国的世纪互联运营的 Azure)中,事件网格仅支持 1.2 版本的 TLS。In national clouds such as Azure Government and Azure operated by 21Vianet in China, Event Grid supports only 1.2 version of TLS.

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

责任:客户Responsibility: Customer

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

指导:数据标识、分类和丢失防护功能尚不适用于 Azure 事件网格。Guidance: Data identification, classification, and loss prevention features are not yet available for Azure Event Grid. 可以根据合规性需要实施第三方解决方案。Implement third-party solution if necessary for compliance purposes.

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

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

责任:客户Responsibility: Customer

4.6:使用 Azure RBAC 管理对资源的访问4.6: Use Azure RBAC to manage access to resources

指导:Azure 事件网格支持使用 Azure Active Directory (AD) 对事件网格资源请求进行授权。Guidance: Azure Event Grid supports using Azure Active Directory (AD) to authorize requests to Event Grid resources. 可以通过 Azure AD 使用 Azure 基于角色的访问控制 (Azure RBAC) 向安全主体授予权限,该安全主体可能是用户,也可能是应用程序服务主体。With Azure AD, you can use Azure role-based access control (Azure RBAC) to grant permissions to a security principal, which may be a user, or an application service principal.

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 活动日志结合使用,以创建在 Azure 事件网格资源的生产实例和其他关键资源或相关资源发生更改时发出的警报。Guidance: Use Azure Monitor with the Azure Activity log to create alerts for when changes take place to production instances of Azure Event Grid resources and other critical or related resources.

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

责任:客户Responsibility: Customer

漏洞管理Vulnerability management

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

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

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

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

责任:不适用Responsibility: Not Applicable

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

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

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

责任:不适用Responsibility: Not Applicable

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

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

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

责任:不适用Responsibility: Not Applicable

库存和资产管理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

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

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

责任:不适用Responsibility: Not Applicable

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

指导:将标记应用到 Azure资源,以便有条理地将元数据组织成某种分类。Guidance: Apply tags to Azure 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: Define and maintain an inventory of approved Azure resources

指导:根据组织需求,创建已获批 Azure 资源以及已获批用于计算资源的软件的清单。Guidance: Create an inventory of approved Azure resources and approved software for compute 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 customer subscription(s) using the following built-in policy definitions:

  • 不允许的资源类型Not allowed resource types
  • 允许的资源类型Allowed resource types

此外,请使用 Azure Resource Graph 来查询/发现订阅中的资源。In addition, use the Azure Resource Graph to query/discover resources within the subscription(s).

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

责任:客户Responsibility: Customer

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

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

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

责任:不适用Responsibility: Not Applicable

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

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

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

责任:不适用Responsibility: Not Applicable

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

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

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 put restrictions on the type of resources that can be created in customer subscription(s) using the following built-in policy definitions:

  • 不允许的资源类型Not allowed resource types
  • 允许的资源类型Allowed resource types

此外,请使用 Azure Resource Graph 来查询/发现订阅中的资源。In addition, use the Azure Resource Graph to query/discover resources within the subscription(s).

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

责任:客户Responsibility: Customer

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

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

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

责任:不适用Responsibility: Not Applicable

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

指导:通过为“Azure 管理”应用配置“阻止访问”,使用 Azure AD 条件访问来限制用户与 Azure 资源管理器交互的能力。Guidance: Use Azure AD 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 in compute resources

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

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

责任:不适用Responsibility: Not Applicable

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

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

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

责任:不适用Responsibility: Not Applicable

安全配置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 事件网格服务定义和实现标准安全配置。Guidance: Define and implement standard security configurations for your Azure Event Grid service with Azure Policy. 使用“Microsoft.EventGrid”命名空间中的 Azure Policy 别名创建自定义策略,以审核或强制实施 Azure 事件网格服务的配置。Use Azure Policy aliases in the "Microsoft.EventGrid" namespace to create custom policies to audit or enforce the configuration of your Azure Event Grid services.

Azure 资源管理器能够以 JavaScript 对象表示法 (JSON) 格式导出模板,应该对其进行检查,以在部署前确保配置满足组织的安全要求。Azure Resource Manager has the ability to export the template in JavaScript Object Notation (JSON), which should be reviewed to ensure that the configurations meet the security requirements for your organization before deployments.

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

责任:客户Responsibility: Customer

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

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

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

责任:不适用Responsibility: Not Applicable

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

指南:使用 Azure Policy“[拒绝]”和“[不存在则部署]”对不同的 Azure 资源强制实施安全设置。Guidance: Use Azure Policy [deny] and [deploy if not exist] to enforce secure settings across your Azure resources. 此外,你可以使用 Azure 资源管理器模板维护组织所需的 Azure 资源的安全配置。In addition, you can use Azure Resource Manager templates to maintain the security configuration of your Azure resources required by your organization.

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

责任:客户Responsibility: Customer

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

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

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

责任:不适用Responsibility: Not Applicable

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

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

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

责任:不适用Responsibility: Not Applicable

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

指导:在“Microsoft.EventGrid”命名空间中使用 Azure Policy 别名创建自定义策略,以审核、强制实施系统配置并对其发出警报。Guidance: Use Azure Policy aliases in the "Microsoft.EventGrid" namespace to create custom policies 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 configuration management tools for operating systems

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

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

责任:不适用Responsibility: Not Applicable

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 警告和审核 Azure 资源配置。Additionally, use Azure Policy to alert and audit Azure resource configurations.

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

责任:客户Responsibility: Customer

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

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

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

责任:不适用Responsibility: Not Applicable

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

指导:事件网格使用共享访问签名 (SAS) 令牌将事件发布到事件网格主题或域中。Guidance: Event Grid uses Shared Access Signature (SAS) token for publishing events to Event Grid topics or domains. 生成只能访问在有限时间范围内需要的资源的 SAS 令牌。Generating SAS tokens with only access to the resources that are needed in a limited time window.

将托管标识与 Azure Key Vault 结合使用,以简化云应用程序的机密管理。Use managed identities in conjunction with Azure Key Vault to simplify secret management for your cloud applications.

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

责任:客户Responsibility: Customer

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

指导:事件网格可以为 Azure 事件网格主题或域启用托管服务标识。Guidance: Event Grid can enable a managed service identity for Azure event grid topics or domains. 使用它将事件转发到受支持的目标,如服务总线队列和主题、事件中心和存储帐户。Use it to forward events to supported destinations such as Service Bus queues and topics, event hubs, and storage accounts.

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

责任:客户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

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

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

指导:Microsoft 反恶意软件已在支持 Azure 服务(例如,Azure 事件网格)的基础主机上启用,但它不会针对客户内容运行。Guidance: Microsoft Anti-malware is enabled on the underlying host that supports Azure services (for example, Azure Event Grid), however it does not run on customer content.

你需要负责预先扫描要上传到非计算 Azure 资源的任何内容。It is your responsibility to pre-scan any content being uploaded to non-compute Azure resources. Microsoft 无法访问客户数据,因此无法代表你对客户内容执行反恶意软件扫描。Microsoft cannot access customer data, and therefore cannot conduct anti-malware scans of customer content on your behalf.

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

责任:客户Responsibility: Customer

数据恢复Data recovery

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

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

指导:事件网格可以针对新的和现有的所有域、主题和事件订阅提供元数据自动异地灾难恢复 (GeoDR) 功能。Guidance: Event Grid has an automatic geo disaster recovery (GeoDR) of meta-data not only for new, but all existing domains, topics, and event subscriptions. 在整个 Azure 区域出现故障时,事件网格已将所有与事件相关的基础结构元数据同步到配对的区域。If an entire Azure region goes down, Event Grid will already have all of your event-related infrastructure metadata synced to a paired region.

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

责任:客户Responsibility: Customer

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

指导:事件网格可以针对新的和现有的所有域、主题和事件订阅提供元数据自动异地灾难恢复 (GeoDR) 功能。Guidance: Event Grid has an automatic geo disaster recovery (GeoDR) of meta-data not only for new, but all existing domains, topics, and event subscriptions. 在整个 Azure 区域出现故障时,事件网格已将所有与事件相关的基础结构元数据同步到配对的区域。If an entire Azure region goes down, Event Grid will already have all of your event-related infrastructure metadata synced to a paired region.

目前,事件网格不支持客户管理的密钥。Currently, Event Grid doesn’t support customer-managed keys.

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

责任:客户Responsibility: Customer

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

指导:事件网格可以针对新的和现有的所有域、主题和事件订阅提供元数据自动异地灾难恢复 (GeoDR) 功能。Guidance: Event Grid has an automatic geo disaster recovery (GeoDR) of meta-data not only for new, but all existing domains, topics, and event subscriptions. 在整个 Azure 区域出现故障时,事件网格已将所有与事件相关的基础结构元数据同步到配对的区域。If an entire Azure region goes down, Event Grid will already have all of your event-related infrastructure metadata synced to a paired region.

目前,事件网格不支持客户管理的密钥。Currently, Event Grid doesn’t support customer-managed keys.

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

责任:客户Responsibility: Customer

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

指南:在 Key Vault 中启用软删除和清除保护,以防止意外删除或恶意删除密钥。Guidance: Enable soft delete and purge protection in Key Vault to protect keys against accidental or malicious deletion.

目前,事件网格不支持客户管理的密钥。Currently, Event Grid doesn’t support customer-managed keys.

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

责任:客户Responsibility: Customer

事件响应Incident response

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

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

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

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

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

责任:客户Responsibility: Customer

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

指导:定期执行演练来测试系统的事件响应功能,以帮助保护 Azure 资源。Guidance: Conduct exercises to test your systems' incident response capabilities on a regular cadence to help protect your Azure resources. 查明弱点和差距,并根据需要修改你的响应计划。Identify weak points and gaps and then revise your response 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) 发现数据被某方非法访问或未经授权访问,Microsoft 会使用安全事件联系信息联系用户。Guidance: Security incident contact information will be used by Microsoft to contact you if the Microsoft Security Response Center (MSRC) discovers that your 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: Not Applicable

责任:客户Responsibility: Customer

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

指导:使用连续导出功能导出 Azure 安全中心警报和建议,以便确定 Azure 资源的风险。Guidance: Export your Azure Security Center alerts and recommendations using the continuous export feature to help identify risks to Azure resources. 使用连续导出可以手动导出或者持续导出警报和建议。Continuous export allows you to export alerts and recommendations either manually or in an ongoing, continuous fashion.

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

责任:客户Responsibility: Customer

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

指导:使用 Azure 安全中心的工作流自动化功能,针对安全警报和建议自动触发响应,以保护 Azure 资源。Guidance: Use workflow automation feature Azure Security Center to automatically trigger responses to security alerts and recommendations to protect your Azure resources.

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

责任:客户Responsibility: Customer

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

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

责任:共享Responsibility: Shared

后续步骤Next steps