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

Add CLE specification #3

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add CLE specification #3

wants to merge 1 commit into from

Conversation

noqcks
Copy link
Collaborator

@noqcks noqcks commented Feb 5, 2025

Continuing on from our PR here which added CLE constraints, we're now adding the specification.

The Rationale (this PR). The rationale document describes the goals and constraints of the specification.
The Technical Choices. The technical choices should be very easy to understand given the constraints and goals defined in the Rationale document.
An Example Spec. Once we have the constraints and the technical choices, we can make an example specification.

We were supposed to do a Technical Choices document, but I found that it was somewhat unnecessary. Happy to add it though if we feel like its needed.

There are some places in this specification where I have a TODO which I would like to discuss in the tg3 wg

Original CLE google doc is here.

Signed-off-by: Benji Visser <[email protected]>
Comment on lines +86 to +89
#### endOfSupport
*Category: Version Event*

Indicates when the manufacturer ceases any and all support of a component or service. This point in time marks a transfer of risk from the manufacturer to the consuming organisation or user of the component or service, encompassing all cybersecurity knowledge and known vulnerabilities, with no further assistance provided by the manufacturer.

Choose a reason for hiding this comment

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

This has probably been discussed before, but if endOfSupport means that the manufacturer stops accepting vulnerability reports and will not publish any new CVEs, how do you mark the "end of security updates"? There is a certain number of vulnerability reports, which are "UNSUPPORTED WHEN ASSIGNED". These are published, but the manufacturer will never fix them.

Maybe endOfSupport should not exonerate the manufacturer from accepting vulnerability reports, which would be published until endOfLife is announced.

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