<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>13734</bug_id>
          
          <creation_ts>2020-01-12 22:08:47 +0000</creation_ts>
          <short_desc>cumulative deployment features and fixes</short_desc>
          <delta_ts>2020-01-13 04:11:17 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Yocto Project Subprojects</classification>
          <product>Security Response Tool</product>
          <component>General</component>
          <version>3.1</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Medium+</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>3.1 M2</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="David Reyna">david.reyna</reporter>
          <assigned_to name="David Reyna">david.reyna</assigned_to>
          
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Yes (doc changes required)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>86028</commentid>
    <comment_count>0</comment_count>
    <who name="David Reyna">david.reyna</who>
    <bug_when>2020-01-12 22:08:47 +0000</bug_when>
    <thetext>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 &quot;active&quot;, &quot;inactive&quot;, &quot;under development&quot;
    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 &quot;OR&quot; 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 &quot;SRTool&quot; class to wrap shared enumerations (e.g. Priority)
 * Add &quot;Update&quot; 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&apos;s defect system&apos;s values

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

CVEs:
  * Add MITRE as an automatic upstream source
    This is to specifically capture all of the &quot;RESERVED&quot; CVE enumerations which
    will not appear in the MIST databases, and have the CVE records in place for
    internal investigations and transitions to &quot;public&quot; 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 &quot;inactive&quot; 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 &quot;CVE&quot; 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</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>86029</commentid>
    <comment_count>1</comment_count>
    <who name="David Reyna">david.reyna</who>
    <bug_when>2020-01-13 04:11:17 +0000</bug_when>
    <thetext>commit 889781b5a04a7c9226e45161105ad4d6a95ad1e9</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>