Skip to content

Adding security policy - #13

Open
CsatariGergely wants to merge 1 commit into
kptdev:mainfrom
nokia:add-security-policy
Open

Adding security policy#13
CsatariGergely wants to merge 1 commit into
kptdev:mainfrom
nokia:add-security-policy

Conversation

@CsatariGergely

Copy link
Copy Markdown
Contributor

No description provided.

Signed-off-by: Gergely Csatari <gergely.csatari@nokia.com>
Copilot AI lite review requested due to automatic review settings September 9, 2026 15:05

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Pull request overview

Adds a repository security policy describing supported versions, how to report vulnerabilities via GitHub Security Advisories, and expectations around disclosure timing.

Changes:

  • Introduces SECURITY.md with vulnerability reporting guidance and disclosure process
  • Documents supported versions policy (n-1) and communication channels
  • Adds a per-repository table linking to Security Advisories pages

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread SECURITY.md
Comment on lines +31 to +33
### Please use the process below to report a vulnerability the repositories in the kpt organization

Vulnerabilities reported as new security advisory to the repository affected by the vulnerability.
Comment thread SECURITY.md
Comment on lines +35 to +45
| Repository | Advisory Reporting |
|------------|--------------------|
| kpt | [In the kpt repository](https://github.com/kptdev/kpt/security/advisories/) |
| porch | [In the porch repository](https://github.com/kptdev/porch/security/advisories/) |
| krm-functions-catalog | [In the krm-functions-catalog repository](https://github.com/kptdev/krm-functions-catalog/security/advisories/) |
| krm-functions-sdk | [In the krm-functions-sdk repository](https://github.com/kptdev/krm-functions-sdk/security/advisories/) |
| kpt-samples | [In the kpt-samples repository](https://github.com/kptdev/kpt-samples/security/advisories/) |
| kpt-backstage-plugins | [In the kpt-backstage-plugins repository](https://github.com/kptdev/kpt-backstage-plugins/security/advisories) |
| governance | [In the governance repository](https://github.com/kptdev/governance/security/advisories/) |
| .github | [In the .github repository](https://github.com/kptdev/.github/security/advisories) |
| .project | [In the .project repository](https://github.com/kptdev/.project/security/advisories) |
Comment thread SECURITY.md
@@ -0,0 +1,84 @@
# Security Policy for the kpt organisation
Comment thread SECURITY.md

## Supported Versions

The kpt community has *n - 1* version support policy for all artefacts released.
Comment thread SECURITY.md

## Reporting a Vulnerability

### When should you?
Comment thread SECURITY.md
- You think you discovered a vulnerability in a dependency of kpt. For those projects, please leverage their reporting
policy.

### When you should not?
Comment thread SECURITY.md
| .project | [In the .project repository](https://github.com/kptdev/.project/security/advisories) |


1. Open the new Security Advisory
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants