<?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: Vulnerabilities found in NSO 5.4 in NSO Developer Hub Discussions</title>
    <link>https://community.cisco.com/t5/nso-developer-hub-discussions/addressing-json-rpc-errors/m-p/4130649#M5545</link>
    <description>Can you please raise these as a TAC case. A best effort discussion forum is not the place to manage issues like this.&lt;BR /&gt;&lt;BR /&gt;NSO (and all Cisco products) is developed under the Cisco Secure Development Lifecycle&lt;BR /&gt;&lt;A href="http://www.cisco.com/c/en/us/about/security-center/security-programs/secure-development-lifecycle.html" target="_blank"&gt;http://www.cisco.com/c/en/us/about/security-center/security-programs/secure-development-lifecycle.html&lt;/A&gt;&lt;BR /&gt;and has undergone thorough security testing.&lt;BR /&gt;&lt;BR /&gt;When you are running security scanning then you are likely to encounter a number of false positive issues. Most of these relate to the overall system under test. Often it turns out that e.g. the operating system that NSO is installed on is not sufficiently hardened.&lt;BR /&gt;&lt;BR /&gt;We can of course not comment on whether the issues you have found fall into that category, or if they are genuine issues. If you raise your findings as TAC cases then they can be investigated and dealt with in an appropriate manner&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;KJ.&lt;BR /&gt;</description>
    <pubDate>Wed, 05 Aug 2020 08:43:05 GMT</pubDate>
    <dc:creator>KJ Rossavik</dc:creator>
    <dc:date>2020-08-05T08:43:05Z</dc:date>
    <item>
      <title>Addressing JSON rpc errors</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/addressing-json-rpc-errors/m-p/4130564#M5542</link>
      <description>&lt;P&gt;How to address JSON rpc errors?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Aug 2020 05:56:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/addressing-json-rpc-errors/m-p/4130564#M5542</guid>
      <dc:creator>sphoredd</dc:creator>
      <dc:date>2020-08-05T05:56:57Z</dc:date>
    </item>
    <item>
      <title>Re: Vulnerabilities found in NSO 5.4</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/addressing-json-rpc-errors/m-p/4130649#M5545</link>
      <description>Can you please raise these as a TAC case. A best effort discussion forum is not the place to manage issues like this.&lt;BR /&gt;&lt;BR /&gt;NSO (and all Cisco products) is developed under the Cisco Secure Development Lifecycle&lt;BR /&gt;&lt;A href="http://www.cisco.com/c/en/us/about/security-center/security-programs/secure-development-lifecycle.html" target="_blank"&gt;http://www.cisco.com/c/en/us/about/security-center/security-programs/secure-development-lifecycle.html&lt;/A&gt;&lt;BR /&gt;and has undergone thorough security testing.&lt;BR /&gt;&lt;BR /&gt;When you are running security scanning then you are likely to encounter a number of false positive issues. Most of these relate to the overall system under test. Often it turns out that e.g. the operating system that NSO is installed on is not sufficiently hardened.&lt;BR /&gt;&lt;BR /&gt;We can of course not comment on whether the issues you have found fall into that category, or if they are genuine issues. If you raise your findings as TAC cases then they can be investigated and dealt with in an appropriate manner&lt;BR /&gt;&lt;BR /&gt;Cheers,&lt;BR /&gt;KJ.&lt;BR /&gt;</description>
      <pubDate>Wed, 05 Aug 2020 08:43:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/addressing-json-rpc-errors/m-p/4130649#M5545</guid>
      <dc:creator>KJ Rossavik</dc:creator>
      <dc:date>2020-08-05T08:43:05Z</dc:date>
    </item>
    <item>
      <title>Re: Addressing JSON rpc errors</title>
      <link>https://community.cisco.com/t5/nso-developer-hub-discussions/addressing-json-rpc-errors/m-p/4132986#M5567</link>
      <description>&lt;P&gt;The question is too short and carries too little information in order for it to be answered.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please give more details, e.g. what is wanted to achieve, what input is given, what output is expected, what is actually received.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Aug 2020 11:01:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/nso-developer-hub-discussions/addressing-json-rpc-errors/m-p/4132986#M5567</guid>
      <dc:creator>perander</dc:creator>
      <dc:date>2020-08-10T11:01:31Z</dc:date>
    </item>
  </channel>
</rss>

