You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -105,9 +69,9 @@ The following tables reflect the latest available profiles in the Compliance Ope
105
69
106
70
|===
107
71
[.small]
108
-
1. The `ocp4-cis` and `ocp4-cis-node` profiles maintain the most up-to-date version of the CIS benchmark as it becomes available in the Compliance Operator. If you want to adhere to a specific version, such as CIS v1.4.0, use the `ocp4-cis-1-4` and `ocp4-cis-node-1-4` profiles.
72
+
1. The `ocp4-cis` and `ocp4-cis-node` profiles maintain the most up-to-date version of the CIS benchmark as it becomes available in the Compliance Operator. If you want to adhere to a specific version, such as CIS v1.7.0, use the `ocp4-cis-1-7` and `ocp4-cis-node-1-7` profiles.
109
73
2. Node profiles must be used with the relevant Platform profile. For more information, see _Compliance Operator profile types_.
110
-
3. CIS v1.4.0 is superceded by CIS v1.5.0. It is recommended to apply the latest profile to your environment.
74
+
3. All earlier CIS profiles are superceded by CIS v1.7.0. It is recommended to apply the latest profile to your environment.
111
75
4. To locate the CIS {product-title} v4 Benchmark, go to link:https://www.cisecurity.org/benchmark/kubernetes[CIS Benchmarks] and click *Download Latest CIS Benchmark*, where you can then register to download the benchmark.
112
76
113
77
[id="bsi-profiles_{context}"]
@@ -152,6 +116,21 @@ The following tables reflect the latest available profiles in the Compliance Ope
152
116
|`x86_64`
153
117
|
154
118
119
+
|rhcos4-bsi ^[3]^
120
+
|BSI IT-Grundschutz (Basic Protection) Building Block SYS.1.6 and APP.4.4
1. The `ocp4-bsi` and `ocp4-bsi-node` profiles maintain the most up-to-date version of the BSI Basic Protection Profile as it becomes available in the Compliance Operator. If you want to adhere to a specific version, such as BSI 2022, use the `ocp4-bsi-2022` and `ocp4-bsi-node-2022` profiles.
@@ -390,6 +369,7 @@ Applying automatic remedations to any profile, such as `rhcos4-stig`, that uses
390
369
|link:https://www.pcisecuritystandards.org/document_library?document=pci_dss[PCI Security Standards ® Council Document Library]
391
370
|`x86_64`
392
371
`ppc64le`
372
+
`aarch64`
393
373
|
394
374
395
375
|ocp4-pci-dss-3-2 ^[3]^
@@ -399,6 +379,7 @@ Applying automatic remedations to any profile, such as `rhcos4-stig`, that uses
399
379
|`x86_64`
400
380
`ppc64le`
401
381
`s390x`
382
+
`aarch64`
402
383
|
403
384
404
385
|ocp4-pci-dss-4-0
@@ -407,6 +388,7 @@ Applying automatic remedations to any profile, such as `rhcos4-stig`, that uses
407
388
|link:https://www.pcisecuritystandards.org/document_library?document=pci_dss[PCI Security Standards ® Council Document Library]
408
389
|`x86_64`
409
390
`ppc64le`
391
+
`aarch64`
410
392
|
411
393
412
394
|ocp4-pci-dss-node ^[1]^
@@ -415,6 +397,7 @@ Applying automatic remedations to any profile, such as `rhcos4-stig`, that uses
415
397
|link:https://www.pcisecuritystandards.org/document_library?document=pci_dss[PCI Security Standards ® Council Document Library]
416
398
|`x86_64`
417
399
`ppc64le`
400
+
`aarch64`
418
401
|{product-rosa} with {hcp} (ROSA HCP)
419
402
420
403
|ocp4-pci-dss-node-3-2 ^[3]^
@@ -424,6 +407,7 @@ Applying automatic remedations to any profile, such as `rhcos4-stig`, that uses
424
407
|`x86_64`
425
408
`ppc64le`
426
409
`s390x`
410
+
`aarch64`
427
411
|{product-rosa} with {hcp} (ROSA HCP)
428
412
429
413
|ocp4-pci-dss-node-4-0
@@ -432,6 +416,7 @@ Applying automatic remedations to any profile, such as `rhcos4-stig`, that uses
432
416
|link:https://www.pcisecuritystandards.org/document_library?document=pci_dss[PCI Security Standards ® Council Document Library]
433
417
|`x86_64`
434
418
`ppc64le`
419
+
`aarch64`
435
420
|{product-rosa} with {hcp} (ROSA HCP)
436
421
|===
437
422
@@ -460,95 +445,48 @@ Applying automatic remedations to any profile, such as `rhcos4-stig`, that uses
460
445
|Supported platforms
461
446
462
447
|ocp4-stig ^[1]^
463
-
|Defense Information Systems Agency Security Technical Implementation Guide (DISA STIG) for Red Hat Openshift
448
+
|Defense Information Systems Agency Security Technical Implementation Guide (DISA STIG) for Red Hat Openshift^[3]^
@@ -557,9 +495,9 @@ Applying automatic remedations to any profile, such as `rhcos4-stig`, that uses
557
495
558
496
|===
559
497
[.small]
560
-
1. The `ocp4-stig`, `ocp4-stig-node` and `rhcos4-stig` profiles maintain the most up-to-date version of the DISA-STIG benchmark as it becomes available in the Compliance Operator. If you want to adhere to a specific version, such as DISA-STIG V2R1, use the `ocp4-stig-v2r1` and `ocp4-stig-node-v2r1` profiles.
498
+
1. The `ocp4-stig`, `ocp4-stig-node` and `rhcos4-stig` profiles maintain the most up-to-date version of the DISA-STIG benchmark as it becomes available in the Compliance Operator. If you want to adhere to a specific version, such as DISA-STIG V2R3, use the `ocp4-stig-v2r3` and `ocp4-stig-node-v2r3` profiles.
561
499
2. Node profiles must be used with the relevant Platform profile. For more information, see _Compliance Operator profile types_.
562
-
3. DISA-STIG V1R1 is superceded by DISA-STIG V2R1. It is recommended to apply the latest profile to your environment.
500
+
3. DISA-STIG V1R2 is superceded by DISA-STIG V2R3. It is recommended to apply the latest profile to your environment.
0 commit comments