Bug 13734

Summary: cumulative deployment features and fixes
Product: [Yocto Project Subprojects] Security Response Tool Reporter: David Reyna <david.reyna>
Component: GeneralAssignee: David Reyna <david.reyna>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Medium+    
Version: 3.1   
Target Milestone: 3.1 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: Yes (doc changes required)

Description David Reyna 2020-01-12 22:08:47 UTC
Cumulative SRTool changes to YP from Wind River, based on deployment enhancements.

New Features:
  * Publishing support to external/public databases
  * Ability to label products as "active", "inactive", "under development"
    Inactive (EOL) products appear but
      * Do not affect status propagation
      * Do not auto-create defects
    Development product status is not exported to pubic database
  * Extend NIST download range to 2002..2019
  * Extended audit history tracking and meta-data
  * Delete CVE records
  * Ability to do "OR" searches
  * Automated defect creation (Jira)
    If selected, creates customer defect for selected and active products
    Reuse existing defect if present for given product
 * Many small defects, sorting issues, readability, edge cases

Backups:
  * Add meta-data stamp file for each backup
  * Save daily backups with day name instead of day number
  * Preserve file dates when making copies to backup
  * Add list command

Automated Updates:
  * Fix report format
  * Add trial run test

Utilities:
  * Add 13 new database fixup procedures
    (Hopefully no one else should need to use them)

Database Schema:
  * Add "SRTool" class to wrap shared enumerations (e.g. Priority)
 * Add "Update" class to tag and track audit trail objects
  * Change Priority naming to match CVE model instead of JIRA
  * Add srt_created/srt_updated to CVE/Vul/Inv/Notify for improved updating and auditing
  * Add to Defect the SRT versions of Status, Priority, Outcome
    To distinguish these from the customer's defect system's values

Common Tools:
  * Fix new CVE auto-scoring to skip CVE's already scored (though still NEW)
  * Add automated propagation of Defects/Investigations status to parent Vulnerabilities
    See "srtool_common.py" for rule details

CVEs:
  * Add MITRE as an automatic upstream source
    This is to specifically capture all of the "RESERVED" CVE enumerations which
    will not appear in the MIST databases, and have the CVE records in place for
    internal investigations and transitions to "public" status.
  * Spell out the command argument in the NIST data source files for greater legibility
  * Change Priority naming to match CVE instead of JIRA
  * Add parallel status states for "inactive" products
    This specifically blocks state propagation from inactive objects to active objects

NIST management script:
  * Refactor file for greater clarity
    * Reorder methods to reflect workflow order
    * Fully spell out names of objects
    * Remove temporary holding class "CVE" in favor of dictionary objects
  * Debugging enhancements
    * Incremental update commands for stepped debugging
      For example, ability to fetch/update specific CVE(s)
    * Additional debugging flags
Comment 1 David Reyna 2020-01-13 04:11:17 UTC
commit 889781b5a04a7c9226e45161105ad4d6a95ad1e9