-
Storyboard
Configuration
- 1x F16
- 1x F16 intruder, Non-Adversarial, non-cooperative , fixed course and speed (2D only)(TBD perhaps have intruder make one CA maneuver?). TODO REVIEW
- 1x static …
-
It would be useful to have a column for machine-readable cpe's for each affected product version.
-
# Situation / Comment
> Status
>
> The invitation for public comments on the website
>
> https://docs.oasis-open.org/csaf/csaf/v2.0/csd01/csaf-v2.0-csd01.html
>
> directs to the TC page f…
-
There is the CSAF format and then there are procedures for those who are sharing CSAF files. These matters seem rather distinct. Also, the format seems to me a bit more baked than this section.
elear updated
3 years ago
-
# Situation
reference: https://docs.oasis-open.org/csaf/csaf/v2.0/csd01/csaf-v2.0-csd01.html#3236-vulnerabilities-property---involvements
The last sentence of the second paragraph reads:
> The…
-
implement in CSAF a recovery maneuver that completes the RTA for the end to end demo of CP 3.2
-
Storyboard
Configuration
- 1x F16
- 1x F16 intruder, Non-Adversarial, non-cooperative , fixed course and speed (2D only)(TBD perhaps have intruder make one CA maneuver?). TODO REVIEW
- 1x static …
-
Looks like CSAF schema is ever-evolving and changing. The new schema has dropped the previous fields such as "text" and made the "category field compulsory in many locations. The link to the latest…
-
# Situation / Comment
> 3.1.3.3 Full Product Name Type - Product Identification Helper
>
> We welcome the addition of new ways to identify products besides CPE. Two
issues we face in this regar…
-
We currently do not feel confident to implement 6.1.26 in Secvisogram, as it seems contractionary for us:
### How we understand the specification
6.1.26 states
> It **must** be tested that the…