-
As discussed in the CSAF TC September 2020 monthly meeting, this issue has been opened to help the TC review the CSAF 2.0 Documentation Draft "Conformance" Section (section 5).
I have included the …
-
The following error is produced with a CSAF file that never-the-less validates against the CSAF schema online:
Errors:
/vulnerabilities/0/product_status/known_not_affected/0: no suitable i…
elear updated
2 years ago
-
Here is a checker run, which encountered a ROLIE document with
```json
{
"updated" : "2022-02-22T00:00Z"
}
```
which is a valid ISO 8601 format (see second paragraph in https://en.wikipedia.or…
-
Just to have a clear logging scheme, I propose these log-level meanings:
- **Critical** - Converter encountered a case which it can not handle and exits immediately without producing any output, ex…
-
Part of EPIC #10
## [CVRF 1.1 view](https://github.com/csaf-tools/CVRF-CSAF-Converter/issues/6#issuecomment-984599492)
 does not. This can be fixed by either reducing the …
elear updated
2 years ago
-
As a very first test, we would like to convert `Document Publisher` alone from CVRF 1.2 to CSAF, by establishing a general read / write workflow.
- [x] Create first entrypoint for `cvrf2csaf.py` (`…
-
### Description
This issue is part of Epic #13760.
The analysis in #13826 described some types of common vulnerabilities feed formats but it concluded that the matching engine would require a di…
-
- [x] Invite members from DTSEC and BSI
- [x] Setup organization csaf-tools
- [x] Create repository with sufficient rights