-
Notifications
You must be signed in to change notification settings - Fork 696
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-2459: PCI-DSS 4 Requirement 7 #12090
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: |
Code Climate has analyzed commit f786e0b 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. |
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
/hold for review |
/hold for test |
/lgtm |
Verification pass with ghcr.io/complianceascode/k8scontent:12090:
|
/unhold |
Description:
7.1
- not applicableManaging and protecting access to card holder data is a responsibility of the payment entity.
7.2
- inherently met based on the single requirement that is applicableAssessing whether a user has legit access need to a system componetn is resposibility of the payment entity.
7.3
- inherently metOpenShift supports and enforces RBAC by default.