Skip to content

Latest commit

 

History

History
27 lines (18 loc) · 3.37 KB

security-architecture.md

File metadata and controls

27 lines (18 loc) · 3.37 KB
copyright lastupdated subcollection keywords
years
2024
2024-10-09
pattern-network-vrf-only

{{site.data.keyword.attribute-definition-list}}

Architecture decisions for security

{: #security-architecture}

The following are security architecture decisions for the hybrid cloud network for classic infrastructure disaster recovery pattern.

Architecture decisions for identity and access management

{: #ad-iam}

Architecture decision Requirement Options Decision Rationale
Privileged Access Management Ensure that all operator actions are run securely through a bastion host \n Implement session recording to track all activities and note any potential threats \n Manage access to resources and track commands issued - Bring Your Own bastion host \n - Jump server \n - Bring Your Own bastion host with Privileged Access Management (PAM) software Bring Your Own bastion host or jump server The bastion host or jump server is a Virtual Server instance that is provisioned through SSH over a private network to securely access resources within the {{site.data.keyword.Bluemix_notm}} private network. \n \n Using PAM software is recommended when session recording, tracking, and managing all access is required.
Identity Access & Role Management (IAM) Securely authenticate users for platform services and control access to resources consistently across {{site.data.keyword.Bluemix_notm}} {{site.data.keyword.iamshort}} {{site.data.keyword.iamshort}} Use IAM access policies to assign users, service IDs, and trusted profiles access to resources within the {{site.data.keyword.Bluemix_notm}} account.
{: caption="Classic data center security identity and access management architecture decisions"}