Skip to content
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

Migrate sec-scanner-configurations to support CheckmarxOne #2029

Open
5 tasks
lindnerby opened this issue Nov 14, 2024 · 0 comments
Open
5 tasks

Migrate sec-scanner-configurations to support CheckmarxOne #2029

lindnerby opened this issue Nov 14, 2024 · 0 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@lindnerby
Copy link
Member

lindnerby commented Nov 14, 2024

Description

As part of the migration plans to new Checkmarx, we need to adapt our components' security-scanner-configs to be picked up by new Cx mechanisms.

To be added:

kind: kcp / kyma  //depending on where the component is deployed
checkmarxOne:
  checkmarx_preset_golang

For lifecycle-manager and modulectl kind value of kcp should be used, for runtime-watcher and template-operator kind is kyma.

Reasons

Security compliance

Acceptance Criteria

Feature Testing

No response

Testing approach

No response

Attachments

No response

@lindnerby lindnerby added the kind/feature Categorizes issue or PR as related to a new feature. label Nov 14, 2024
@nesmabadr nesmabadr self-assigned this Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants