Create Security Policy for the Devfiles Org #1461
Labels
area/alizer
Enhancement or issue related to the alizer repo
area/api
Enhancement or issue related to the api/devfile specification
area/landing-page
Issues with the Landing Page
area/library
Common devfile library for interacting with devfiles
area/registry
Devfile registry for stacks and infrastructure
kind/epic
A high level requirement that can/should be split into smaller issues
kind/user-story
User story for new enhancement
/kind user-story
/kind epic
Which area this user story is related to?
/area api
/area library
/area registry
/area alizer
/area landing-page
User Story
As part of the CNCF Defender EPIC it is recommended to add a security-policy. As part of the security policy it is also recommended to add:
security-artifacts
inside theSECURITY-INSIGHTS.yaml
of each repo. The thread model can be the same for every devfile org repo. An example threat model is here: https://github.com/cncf/financial-user-group/blob/main/projects/k8s-threat-model/README.mdBoth the threat model and the vulnerability report process can be part of a more generic
Security.md
file which also can define additional policies and procedures followed by the devfile org.Acceptance Criteria
devfile/api
#1629The text was updated successfully, but these errors were encountered: