Skip to content

Commit c4c0744

Browse files
authored
Merge pull request #39950 from lpettyjo/OSDOCS-2809_Rev2
OSDOCS-2809_Rev2: remove hardened SRE support pod info
2 parents fc9a916 + 1dc8bfd commit c4c0744

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/rosa-policy-identity-access-management.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ For a list of the available subprocessors, see the link:https://access.redhat.co
1515
== SRE access to all {product-title} clusters
1616
SREs access {product-title} clusters through the web console or command-line tools. Authentication requires multi-factor authentication (MFA) with industry-standard requirements for password complexity and account lockouts. SREs must authenticate as individuals to ensure auditability. All authentication attempts are logged to a Security Information and Event Management (SIEM) system.
1717

18-
SREs access private clusters using an encrypted tunnel through a hardened SRE support pod running in the cluster. Connections to the SRE support pod are permitted only from a secured Red Hat network using an IP allow-list. In addition to the cluster authentication controls described above, authentication to the SRE support pod is controlled by using SSH keys. SSH key authorization is limited to SRE staff and automatically synchronized with Red Hat corporate directory data. Corporate directory data is secured and controlled by HR systems, including management review, approval, and audits.
18+
SREs access private clusters using an encrypted HTTP connection. Connections are permitted only from a secured Red Hat network using either an IP allowlist or a private cloud provider link.
1919

2020
[id="rosa-policy-privileged-access-control_{context}"]
2121
== Privileged access controls in {product-title}

0 commit comments

Comments
 (0)