<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Vulnerability Management in Welcome</title>
    <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9716#M1088</link>
    <description>&lt;P&gt;Start with a software inventory of what you have and think about how often that software is used or exposed to risk. You cannot defend anything until you know what and where your responsibilities start and stop. Now look at your reports for high and medium risk items found in that first inventory. Common Vulnerabilities and Exploits (CVEs) range from 0-10 with 10 being the easiest or most destructive exploit. If at all possible patch and remediate those items first, no matter how painful they may seem at the time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Go down through your list from highest to lowest, red - yellow - green, however your reports are presented and continue to work through reducing your overall risk.&amp;nbsp; Ideally you will be able to look at the current state of patching and vulnerabilities in whole numbers today and compare them to next month, quarterly and annually to check your progress. We call this a baseline but for now allow yourself the luxury of learning the patching priority from both a technical and political standpoint. It's not uncommon for business (stakeholders) to put patching for for business reasons because "it's not broke" or convenience if not indifference. Concentrate on those things you can affect and warn against putting patching off for later.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These thing only look impossible when starting but once you get started will continue to build on itself. Doing much the same with a newer position myself.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just takes time to get your arms around it all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Good luck!&lt;/P&gt;</description>
    <pubDate>Tue, 24 Apr 2018 14:12:29 GMT</pubDate>
    <dc:creator>Beads</dc:creator>
    <dc:date>2018-04-24T14:12:29Z</dc:date>
    <item>
      <title>Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9704#M1083</link>
      <description>&lt;P&gt;Hi There, I'm a Security Analyst&amp;nbsp;and have just taken on a new role a few months ago.&amp;nbsp; I work for a small organisation (220 staff, 15 IT staff) and we have a variety&amp;nbsp;of apps that report on vulnerabilities.&amp;nbsp; To begin with I am trying to discover all our vulnerability sources, what vulnerabilities they currently have and their severity.&amp;nbsp; So I have exports of detections to date from a vulnerability scanner, endpoint protection tool, Pen tests results, Web Application Security Scanner and a manually created list of vulnerabilities in the admin tools that we use and including users as a vulnerability too.&amp;nbsp; My question is what is best practice in taking all&amp;nbsp;these data sources and managing them in one place that is not a spreadsheet?&amp;nbsp; Are there any free/low cost tools that can accept data from all these sources, display them and then allow me to track the remediation.&amp;nbsp; Qualys is a good tool for tracking remediation and reporting but I cannot import other data into it.&amp;nbsp; What do other people do?&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 11:50:03 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9704#M1083</guid>
      <dc:creator>Samclarke80</dc:creator>
      <dc:date>2018-04-24T11:50:03Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9705#M1084</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Qualys is a lot more than that. What about your ITSM software?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 12:07:59 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9705#M1084</guid>
      <dc:creator>Thalpius</dc:creator>
      <dc:date>2018-04-24T12:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9706#M1085</link>
      <description>&lt;P&gt;I suggest taking a look at threadfix by denim group.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 12:12:20 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9706#M1085</guid>
      <dc:creator>Markus_Miedaner</dc:creator>
      <dc:date>2018-04-24T12:12:20Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9713#M1086</link>
      <description>&lt;P&gt;Hi Thalpius, whilst that (Manage Engine Desktop Central) does provide reports of inventory and OS and third party software patching status, I cannot integrate Qualys reports into it or other manual vulnerability information.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 14:00:50 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9713#M1086</guid>
      <dc:creator>Samclarke80</dc:creator>
      <dc:date>2018-04-24T14:00:50Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9714#M1087</link>
      <description>&lt;P&gt;Thanks looks just like what I need, is it expensive though?&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 14:01:34 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9714#M1087</guid>
      <dc:creator>Samclarke80</dc:creator>
      <dc:date>2018-04-24T14:01:34Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9716#M1088</link>
      <description>&lt;P&gt;Start with a software inventory of what you have and think about how often that software is used or exposed to risk. You cannot defend anything until you know what and where your responsibilities start and stop. Now look at your reports for high and medium risk items found in that first inventory. Common Vulnerabilities and Exploits (CVEs) range from 0-10 with 10 being the easiest or most destructive exploit. If at all possible patch and remediate those items first, no matter how painful they may seem at the time.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Go down through your list from highest to lowest, red - yellow - green, however your reports are presented and continue to work through reducing your overall risk.&amp;nbsp; Ideally you will be able to look at the current state of patching and vulnerabilities in whole numbers today and compare them to next month, quarterly and annually to check your progress. We call this a baseline but for now allow yourself the luxury of learning the patching priority from both a technical and political standpoint. It's not uncommon for business (stakeholders) to put patching for for business reasons because "it's not broke" or convenience if not indifference. Concentrate on those things you can affect and warn against putting patching off for later.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These thing only look impossible when starting but once you get started will continue to build on itself. Doing much the same with a newer position myself.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just takes time to get your arms around it all.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Good luck!&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 14:12:29 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9716#M1088</guid>
      <dc:creator>Beads</dc:creator>
      <dc:date>2018-04-24T14:12:29Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9721#M1089</link>
      <description>&lt;P&gt;Also look at the CIS critical security controls and see if you are currently doing the top 6 well. If you are not even doing that well, no amount of pen tests, vulnerability management scans, etc. is going to do any long term good as you will be vulnerable because you do not have a good basic security posture. Then you can work on the foundational steps and then move on to the organizational portion of it. You may find that you need improvement in all areas, as most agencies do, but start with the basics.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 14:29:29 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9721#M1089</guid>
      <dc:creator>CISOScott</dc:creator>
      <dc:date>2018-04-24T14:29:29Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9730#M1090</link>
      <description>&lt;P&gt;Thanks, Beads.&amp;nbsp; Yes it does&amp;nbsp;look impossible good point on the responsibilities.&amp;nbsp; I now have a list of all our infrastructure, endpoint, web applications and software assets as well as a list of vulnerability detections on each one.&amp;nbsp; Next step to prioritise them!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Good luck to you too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sam&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 15:40:02 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9730#M1090</guid>
      <dc:creator>Samclarke80</dc:creator>
      <dc:date>2018-04-24T15:40:02Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9731#M1091</link>
      <description>&lt;P&gt;Thanks for the direction, Scott.&amp;nbsp; We have the inventory down, just moving onto the vulnerability management now as that is a basic requirement.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 15:46:19 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9731#M1091</guid>
      <dc:creator>Samclarke80</dc:creator>
      <dc:date>2018-04-24T15:46:19Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9733#M1092</link>
      <description>&lt;P&gt;I agree that it does take time to wrap your arms around it all.&amp;nbsp; What may be helpful is to utilize the API access from most of the tools you currently possess then customize them to fit your environment to get a better view (identification) and (response) alerting.&amp;nbsp; Later, develop a project with in-house talent to create a customized dashboard where you can import data.&amp;nbsp; Often the only way to stay within a budget is to leverage your current toolbox to your fullest capabilities.&amp;nbsp; I hope this helps!&lt;/P&gt;</description>
      <pubDate>Tue, 24 Apr 2018 15:51:45 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9733#M1092</guid>
      <dc:creator>canLG0501</dc:creator>
      <dc:date>2018-04-24T15:51:45Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9758#M1093</link>
      <description>&lt;P&gt;Thanks, yes perhaps an in house solution might be possible although our developers are flat out.&amp;nbsp; Exporting spreadsheets&amp;nbsp;is the way forward for now until I can&amp;nbsp;get agreement on extra resources or extra finances!&lt;/P&gt;</description>
      <pubDate>Wed, 25 Apr 2018 11:14:49 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9758#M1093</guid>
      <dc:creator>Samclarke80</dc:creator>
      <dc:date>2018-04-25T11:14:49Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9838#M1094</link>
      <description>&lt;P&gt;&lt;SPAN&gt;There is a free, open source tool that isn't very widely known yet, which solves some of your problems.&amp;nbsp; The best part is that it's extensible, so we can add parsers for any number of sources.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://sourceforge.net/projects/sagacity/" target="_blank"&gt;https://sourceforge.net/projects/sagacity/&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Please let me know if I can help in any way.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;- Jeff&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Jeff A. Odegard, CISSP, CPT, C|EH&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;jeff.odegard@CyberPerspectives.com&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Apr 2018 15:11:36 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9838#M1094</guid>
      <dc:creator>JeffOdegard</dc:creator>
      <dc:date>2018-04-26T15:11:36Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9843#M1095</link>
      <description>Hi Jeff, great thanks I will take a look. Sam</description>
      <pubDate>Thu, 26 Apr 2018 15:44:26 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9843#M1095</guid>
      <dc:creator>Samclarke80</dc:creator>
      <dc:date>2018-04-26T15:44:26Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9881#M1098</link>
      <description>&lt;P&gt;Hi Jeff,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looks great!&amp;nbsp; Before getting this&amp;nbsp;installed am I going to be able to add data from Manage Engine Desktop Central, Qualys Web Application Scanner and Qualys VM scanner data and add manual info from a Pen test report?&amp;nbsp; Even if I can only add info from Qualys and manually enter vulnerabilities that is going to be a great help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sam&lt;/P&gt;</description>
      <pubDate>Fri, 27 Apr 2018 11:37:44 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9881#M1098</guid>
      <dc:creator>Samclarke80</dc:creator>
      <dc:date>2018-04-27T11:37:44Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9887#M1099</link>
      <description>We don't have parsers for those products yet, but if you email me, we can discuss getting some sample data and building some parsers for you. It doesn't take long. - Jeff jeff.odegard@cyberperspectives.com</description>
      <pubDate>Fri, 27 Apr 2018 15:35:12 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/9887#M1099</guid>
      <dc:creator>JeffOdegard</dc:creator>
      <dc:date>2018-04-27T15:35:12Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerability Management</title>
      <link>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/10004#M1101</link>
      <description>&lt;P&gt;Hi Jeff,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Fantastic.&amp;nbsp; Ok I will go ahead and ask the IT guys to install and configure as per your video next week.&amp;nbsp; Will email you now.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sam&lt;/P&gt;</description>
      <pubDate>Wed, 02 May 2018 10:47:45 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Welcome/Vulnerability-Management/m-p/10004#M1101</guid>
      <dc:creator>Samclarke80</dc:creator>
      <dc:date>2018-05-02T10:47:45Z</dc:date>
    </item>
  </channel>
</rss>

