<?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: Customizing scanning policies with Vulnerability &amp;amp; Patch Manager in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/customizing-scanning-policies-with-vulnerability-amp-patch/m-p/3454215#M8593</link>
    <description>Hi Rob,&lt;BR /&gt;&lt;BR /&gt;Once I solved all my SSH issues, I still had trouble scanning initially because of the WBEM credentials.  The VPM documentation says that if you have VPM installed on different server than SIM, you should use WBEM credentials of the form DOMAIN/user.  However, I found that only when I used the local administrator account/password on the first line of WBEM credentials did I get a complete scan.&lt;BR /&gt;&lt;BR /&gt;Good luck,&lt;BR /&gt;- Steve&lt;BR /&gt;</description>
    <pubDate>Wed, 05 Jan 2005 10:21:21 GMT</pubDate>
    <dc:creator>Steve Kadish</dc:creator>
    <dc:date>2005-01-05T10:21:21Z</dc:date>
    <item>
      <title>Customizing scanning policies with Vulnerability &amp; Patch Manager</title>
      <link>https://community.hpe.com/t5/server-management-systems/customizing-scanning-policies-with-vulnerability-amp-patch/m-p/3454213#M8591</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I am running my first scans with VPM.  Some of the vulnerabilities it is flagging are less than entirely helpful, because while we might have addressed the issue already, we are not addressing it to the extent which Harris Stat would like to.&lt;BR /&gt;&lt;BR /&gt;For instance, we have the Password History on our servers set to less than 10, and therefore it is flagged.  In the "Solution" section of the report, it says that "Policy Options can be set on STAT Scanner by clicking on Edit | Options | Policy."  I appears that if we had the full version of Harris STAT Scanner, we could set this policy to a lower number which matches our current in-house policy.&lt;BR /&gt;&lt;BR /&gt;Is there any way to set such customizations in SIM?  The "Customize Vulnerability Scan Definitions" only allows one to turn a vulnerability check on or off.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;- Steve&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Jan 2005 14:33:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/customizing-scanning-policies-with-vulnerability-amp-patch/m-p/3454213#M8591</guid>
      <dc:creator>Steve Kadish</dc:creator>
      <dc:date>2005-01-03T14:33:58Z</dc:date>
    </item>
    <item>
      <title>Re: Customizing scanning policies with Vulnerability &amp; Patch Manager</title>
      <link>https://community.hpe.com/t5/server-management-systems/customizing-scanning-policies-with-vulnerability-amp-patch/m-p/3454214#M8592</link>
      <description>I just wish I could get it to scan the two licensed Servers I have! &lt;BR /&gt;It seems a bit like PMP in that you can't really tune it that finely.</description>
      <pubDate>Tue, 04 Jan 2005 20:45:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/customizing-scanning-policies-with-vulnerability-amp-patch/m-p/3454214#M8592</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2005-01-04T20:45:56Z</dc:date>
    </item>
    <item>
      <title>Re: Customizing scanning policies with Vulnerability &amp; Patch Manager</title>
      <link>https://community.hpe.com/t5/server-management-systems/customizing-scanning-policies-with-vulnerability-amp-patch/m-p/3454215#M8593</link>
      <description>Hi Rob,&lt;BR /&gt;&lt;BR /&gt;Once I solved all my SSH issues, I still had trouble scanning initially because of the WBEM credentials.  The VPM documentation says that if you have VPM installed on different server than SIM, you should use WBEM credentials of the form DOMAIN/user.  However, I found that only when I used the local administrator account/password on the first line of WBEM credentials did I get a complete scan.&lt;BR /&gt;&lt;BR /&gt;Good luck,&lt;BR /&gt;- Steve&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Jan 2005 10:21:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/customizing-scanning-policies-with-vulnerability-amp-patch/m-p/3454215#M8593</guid>
      <dc:creator>Steve Kadish</dc:creator>
      <dc:date>2005-01-05T10:21:21Z</dc:date>
    </item>
    <item>
      <title>Re: Customizing scanning policies with Vulnerability &amp; Patch Manager</title>
      <link>https://community.hpe.com/t5/server-management-systems/customizing-scanning-policies-with-vulnerability-amp-patch/m-p/3454216#M8594</link>
      <description>Steve,&lt;BR /&gt;Yeah I read that but got confused.&lt;BR /&gt;I have HPSIM &amp;amp; VPM on the same Server. But the Server I want to scan is separate.&lt;BR /&gt;&lt;BR /&gt;So, I just tried setting the WBEM credentials for the Remote (non HPSIM/VPM Server) to use a local admin account and it worked.&lt;BR /&gt;&lt;BR /&gt;So, yep, it seems you cannot use Domain Credentials with WBEM and get VPM to work.&lt;BR /&gt;This strikes me as being somewhat flawed.</description>
      <pubDate>Wed, 05 Jan 2005 14:55:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/customizing-scanning-policies-with-vulnerability-amp-patch/m-p/3454216#M8594</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2005-01-05T14:55:50Z</dc:date>
    </item>
  </channel>
</rss>

