|  | 
| 2 | 2 | 
 | 
| 3 | 3 | copyright: | 
| 4 | 4 |   years: 2024 | 
| 5 |  | -lastupdated: "2024-09-06" | 
|  | 5 | +lastupdated: "2024-11-19" | 
| 6 | 6 | 
 | 
| 7 | 7 | subcollection: deployable-reference-architectures | 
| 8 | 8 | 
 | 
| @@ -30,7 +30,7 @@ industry: SoftwareAndPlatformApplications, Technology, Banking, FinancialSector | 
| 30 | 30 | 
 | 
| 31 | 31 | compliance: CIS Benchmarks | 
| 32 | 32 | 
 | 
| 33 |  | -docs: https://cloud.ibm.com/docs/security-services | 
|  | 33 | +docs: https://cloud.ibm.com/docs/security-hub | 
| 34 | 34 | 
 | 
| 35 | 35 | content-type: reference-architecture | 
| 36 | 36 | 
 | 
| @@ -80,20 +80,19 @@ The following diagram represents the architecture for the IBM Cloud Essential Se | 
| 80 | 80 | 
 | 
| 81 | 81 | {: caption="Figure 1. Architecture diagram" caption-side="bottom"}{: external download="core-security-services-architecture.svg"} | 
| 82 | 82 | 
 | 
| 83 |  | -The architecture is anchored by three fundamental services: {{site.data.keyword.keymanagementserviceshort}}, {{site.data.keyword.secrets-manager_short}}, and IBM Cloud Security Services and {{site.data.keyword.sysdigsecure_full_notm}}. These services provide integration endpoints for any customer workload that is hosted on {{site.data.keyword.cloud_notm}}. | 
|  | 83 | +The architecture is anchored by three fundamental services: {{site.data.keyword.keymanagementserviceshort}}, {{site.data.keyword.secrets-manager_short}}, and {{site.data.keyword.compliance_short}}. These services provide integration endpoints for any customer workload that is hosted on {{site.data.keyword.cloud_notm}}. | 
| 84 | 84 | 
 | 
| 85 | 85 | 1. {{site.data.keyword.keymanagementserviceshort}} | 
| 86 | 86 | 
 | 
| 87 |  | -{{site.data.keyword.keymanagementserviceshort}} is responsible for centrally managing the lifecycle of encryption keys that are used by {{site.data.keyword.cos_full_notm}} buckets, {{site.data.keyword.secrets-manager_short}}, and event notification resources. Additionally, it can manage encryption keys for any customer workload that requires protection. | 
|  | 87 | +  {{site.data.keyword.keymanagementserviceshort}} is responsible for centrally managing the lifecycle of encryption keys that are used by {{site.data.keyword.cos_full_notm}} buckets, {{site.data.keyword.secrets-manager_short}}, and event notification resources. Additionally, it can manage encryption keys for any customer workload that requires protection. | 
| 88 | 88 | 
 | 
| 89 | 89 | 2. {{site.data.keyword.secrets-manager_short}} | 
| 90 | 90 | 
 | 
| 91 |  | -{{site.data.keyword.secrets-manager_short}} securely stores and manages sensitive information, including API keys, credentials, and certificates. It uses encryption keys from {{site.data.keyword.keymanagementserviceshort}} to encrypt sensitive data and to seal and unseal vaults that hold the secrets. It is preconfigured to send events to the {{site.data.keyword.en_short}} service, allowing customers to set up email or SMS notifications. Moreover, it is automatically configured to forward all API logs to the customer's logging instance. | 
|  | 91 | +  {{site.data.keyword.secrets-manager_short}} securely stores and manages sensitive information, including API keys, credentials, and certificates. It uses encryption keys from {{site.data.keyword.keymanagementserviceshort}} to encrypt sensitive data and to seal and unseal vaults that hold the secrets. It is preconfigured to send events to the {{site.data.keyword.en_short}} service, allowing customers to set up email or SMS notifications. Moreover, it is automatically configured to forward all API logs to the customer's logging instance. | 
| 92 | 92 | 
 | 
| 93 |  | -3. Security Compliance Center | 
| 94 |  | - | 
| 95 |  | -The Security Compliance Center instance is preconfigured to scan all resources provisioned by the reference architecture. It can be expanded to accommodate the unique workloads of customers. | 
|  | 93 | +3. {{site.data.keyword.compliance_short}} | 
| 96 | 94 | 
 | 
|  | 95 | +  The Security Compliance Center instance is preconfigured to scan all resources provisioned by the reference architecture. It can be expanded to include {{site.data.keyword.sysdigsecure_full_notm}} to accomodate the unique workloads of customers. | 
| 97 | 96 | 
 | 
| 98 | 97 | {{site.data.keyword.cos_full_notm}} buckets are set up to receive logs from logging and alerting services. Each bucket is configured to encrypt data at rest by using encryption keys managed by {{site.data.keyword.keymanagementserviceshort}}. | 
| 99 | 98 | 
 | 
|  | 
0 commit comments