Uploaded image for project: 'Chat Solution'
  1. Chat Solution
  2. CSN-5844

Schedule the Vulnerability Report on Confluence

    XMLWordPrintable

Details

    • Story
    • Status: Resolved
    • Minor
    • Resolution: Done
    • None
    • None
    • None
    • Software (SOFTWARE)
    • Sprint# 65 (Jan 19 - Feb 1), Sprint# 66 (Feb 2 - Feb 15)
    • 5

    Description

      Scheduling the Report Generation Process for

      – Updating the Vulnerability Report to Confluence
      – Report with Critical Score added
      – Alert to the DevOps Group for any Critical

      the script will publish a number of critical, normal, low, high counts through Anchore Engine and trivy on Confluence

      confluence page link :
      https://docs.expertflow.com/display/EKB/Expertflow+Component+Vulnerability+Report

      1) place these two files (image-tag.txt + script.py) on the machine where trivy and anchore engine is installed

      2) create a temp folder in the directory and copy the path of the temp folder by using the PWD command and paste the path in script line 66 variable named folder_path = "temp folder path"

      3) please run this script on anchore engine VM
      command to run the script :
      *python3 filename.py -l images-file.txt *

      4)commands to verify the counts by passing the name of an "imagetag-anchore.txt". These files are created in a folder named temp
      *gawk 'NR>1

      { print $3 }

      ' filename.txt | uniq -c *

      5)Make sure that you have installed the installed this module named httplib2 by using this command pip3 install httplib2

      6) the script also sends the critical count to alter in google chat space "Expertflow Component Vulnerability Report"

      Attachments

        1. 3-15-0.txt
          2 kB
        2. 3-19-0.txt
          2 kB
        3. newscanscript.py
          28 kB

        Issue Links

          Activity

            People

              aqsa.naeem Aqsa Naeem
              nasir.mehmood Nasir Mehmood
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - Not Specified
                  Not Specified
                  Logged:
                  Time Spent - 4 days, 1 hour, 45 minutes
                  4d 1h 45m