-
Notifications
You must be signed in to change notification settings - Fork 706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CMP-2456: PCI-DSS v4 Requirement 4 #12002
Conversation
🤖 A k8s content image for this PR is available at: Click here to see how to deploy itIf you alread have Compliance Operator deployed: Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and: |
/test |
@rhmdnd: The
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Kicking the tires on some new CI we have for ROSA: /test 4.15-e2e-rosa-ocp4-cis-node |
/hold for test |
/unhold |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good to me. Just one question on if we need to include a couple additional rules for encrypting network traffic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I'll keep my comment open since @xiaojiey has a valid question there, too.
Following my comment on #12002 (comment) I have removed the |
/retest |
/lgtm |
@yuumasato: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
@yuumasato I noticed this error in the ci jobs. Do we need to drop this rule? |
7fd6368
to
b8bb32d
Compare
@xiaojiey There was a typo in the rule. Should be fixed now. |
/lgtm |
b8bb32d
to
f855af6
Compare
Rebased on top of latest master. |
This req is defining processes and creating documentation.
OpenShift uses and provides strong cryptography and secure protocols, but it is still up to the applications to leverage them.
- Add api_server_tls_cert rule - Tweak note on requirement 4.2.1
The rule api_server_tls_security_profile sets up a custom security profile, without specifying ciphers. So we also need to select api_server_tls_security_profile. Removing etcd cipher rule, it is not related to transission on public networks.
f855af6
to
00cfb09
Compare
Code Climate has analyzed commit 00cfb09 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 59.4% (0.0% change). View more on Code Climate. |
@rhmdnd @Vincent056 CI is happy now, :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Description:
4.1
is not applicableDocumentation and processes are not be created and maintained at in OpenShift.
4.2
is partially applicableWhile OCP uses and can provide support for secure cryptography and protocols, the application / workload needs correctly to leverage them.