-
Notifications
You must be signed in to change notification settings - Fork 40
Issues: oasis-tcs/csaf
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Question about multi-layered or nested relationship structure
#852
opened Dec 24, 2024 by
chripluEri
Clearly state what not mentioning a product in
product_status
means
tc-discussion-needed
#850
opened Dec 18, 2024 by
tschmidtb51
Date of First Known Exploitation (
first_known_exploitation_date
)
tc-discussion-needed
#849
opened Dec 18, 2024 by
santosomar
Update traffic light protocol (TLP) support to include version 2.0 of TLP
user-question
#848
opened Dec 17, 2024 by
e-shreve-ti
Correct default open csaf 2.1 work
motion_passed
A motion has passed
serial_numbers
and model_numbers
csaf 2.1
#847
opened Dec 16, 2024 by
tschmidtb51
explanation of test 6.3.10 (product_version_range)
user-question
#845
opened Dec 16, 2024 by
jaccoNCSCNL
How to provide advisories in different parallel CSAF versions?
csaf 2.1
csaf 2.1 work
documentation
editorial
mostly nits and consistency
FAQ
tc-discussion-needed
#843
opened Dec 15, 2024 by
sthagen
Ensure the implications of the scores-to-metrics change are made explicit
csaf 2.1
csaf 2.1 work
documentation
editorial
mostly nits and consistency
FAQ
#842
opened Dec 15, 2024 by
sthagen
Editorial
csaf 2.1
csaf 2.1 work
editorial
mostly nits and consistency
#841
opened Dec 11, 2024 by
tschmidtb51
4 tasks
Description of test 6.1.34 needs clarification
documentation
editorial
mostly nits and consistency
question
#840
opened Dec 8, 2024 by
oxisto
[Exclude from changes list] Changes from previous version collector
csaf 2.1
csaf 2.1 work
editorial
mostly nits and consistency
#838
opened Dec 1, 2024 by
sthagen
Need real examples of VEX based on actual products and known vulnerabilities, such as Log4J
call_to_action
a call to action has been send out
user-question
#832
opened Nov 20, 2024 by
rjb4standards
Clarify csaf.data.security.domain.ltd in Requirement 10: DNS path
csaf 2.1
csaf 2.1 work
editorial
mostly nits and consistency
#831
opened Nov 20, 2024 by
sonnyvanlingen
Clarification on why test case 6-1-31-12 in CSAF2.0 is supposed to be valid
csaf 2.0
csaf 2.0 work
csaf 2.1
csaf 2.1 work
editor-revision
already worked on in the editor revision
editorial
mostly nits and consistency
#825
opened Nov 9, 2024 by
oxisto
Provide patched documents of CSAF v2.0 including ERRATA 01 to fix docs.oasis-open.org
bug
documentation
oasis_tc_process
OASIS TC process action
#823
opened Nov 4, 2024 by
sthagen
Ensure VEX minimum requirements with CSAF
csaf 2.1
csaf 2.1 work
#818
opened Oct 30, 2024 by
tschmidtb51
Clearly state hardware/software separation in csaf 2.1 work
motion_passed
A motion has passed
product_tree
csaf 2.1
#817
opened Oct 30, 2024 by
tschmidtb51
Add test data for 6.1.7: duplicate items
csaf 2.0
csaf 2.0 work
csaf 2.1
csaf 2.1 work
test
related to tests in this repo
#815
opened Oct 30, 2024 by
tschmidtb51
Enforce csaf 2.1 work
enhancement
format
validation
csaf 2.1
#813
opened Oct 25, 2024 by
tschmidtb51
Add test: Consistent PIH
csaf 2.1
csaf 2.1 work
motion_passed
A motion has passed
#812
opened Oct 25, 2024 by
tschmidtb51
Include support for SSVC
csaf 2.1
csaf 2.1 work
motion_passed
A motion has passed
#803
opened Oct 23, 2024 by
justmurphy
Clarify requirement 19: ASCII vs. Binary signature
csaf 2.1
csaf 2.1 work
editor-revision
already worked on in the editor revision
editorial
mostly nits and consistency
#797
opened Oct 17, 2024 by
tschmidtb51
Previous Next
ProTip!
no:milestone will show everything without a milestone.