<?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: Api PSIRT update by date range issue in Services Discussions</title>
    <link>https://community.cisco.com/t5/services-discussions/api-psirt-update-by-date-range-issue/m-p/3495279#M152</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is, that api didn't detect this change when we called by date range, so to get this update we had to make a call to get all PSIRTs. The issue is not with data, but api mechanism.&lt;BR /&gt;Could you investigate this why it has happened?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 31 Oct 2017 14:38:48 GMT</pubDate>
    <dc:creator>cisco_api_cco</dc:creator>
    <dc:date>2017-10-31T14:38:48Z</dc:date>
    <item>
      <title>Api PSIRT update by date range issue</title>
      <link>https://community.cisco.com/t5/services-discussions/api-psirt-update-by-date-range-issue/m-p/3495277#M150</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When we call &lt;A href="https://api.cisco.com/security/advisories/cvrf/all/lastpublished?xxx"&gt;https://api.cisco.com/security/advisories/cvrf/all/lastpublished?xxx&lt;/A&gt; to get last updated items, we spotted there are some missing updates.&lt;/P&gt;&lt;P&gt;When we called initially on 2017-08-22 for all we got related software versions for advisories in attached excel.&lt;/P&gt;&lt;P&gt;Then we recently called again for all and for the same advisories software versions gone.&lt;/P&gt;&lt;P&gt;It means it was silent update inside nested xml(we get this link inside cvrf xml for each advisory), for example”&lt;/P&gt;&lt;P&gt;&lt;A href="https://tools.cisco.com/security/center/contentxml/CiscoSecurityAdvisory/cisco-sa-20170802-ise/cvrf/cisco-sa-20170802-ise_cvrf.xml"&gt;https://tools.cisco.com/security/center/contentxml/CiscoSecurityAdvisory/cisco-sa-20170802-ise/cvrf/cisco-sa-20170802-ise_cvrf.xml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Also, for those advisories last update date is not change and for cisco-sa-20170802-ise is 2017-08-02, it looks like no changes has been detected for that advisory.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it something you can fix on your side, or we should stop using date range and update always for all?&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 Oct 2017 14:38:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/api-psirt-update-by-date-range-issue/m-p/3495277#M150</guid>
      <dc:creator>cisco_api_cco</dc:creator>
      <dc:date>2017-10-30T14:38:16Z</dc:date>
    </item>
    <item>
      <title>Re: Api PSIRT update by date range issue</title>
      <link>https://community.cisco.com/t5/services-discussions/api-psirt-update-by-date-range-issue/m-p/3495278#M151</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We had to remove the versions of the results due to data inconsistency issues. Currently, detailed version information is supported for IOS and IOS-XE high and critical advisories. We are working on expanding this functionality to medium severity advisories and also other operating systems like NXOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks! Omar&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Oct 2017 14:08:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/api-psirt-update-by-date-range-issue/m-p/3495278#M151</guid>
      <dc:creator>Omar Santos</dc:creator>
      <dc:date>2017-10-31T14:08:39Z</dc:date>
    </item>
    <item>
      <title>Re: Api PSIRT update by date range issue</title>
      <link>https://community.cisco.com/t5/services-discussions/api-psirt-update-by-date-range-issue/m-p/3495279#M152</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi ,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The problem is, that api didn't detect this change when we called by date range, so to get this update we had to make a call to get all PSIRTs. The issue is not with data, but api mechanism.&lt;BR /&gt;Could you investigate this why it has happened?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 31 Oct 2017 14:38:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/services-discussions/api-psirt-update-by-date-range-issue/m-p/3495279#M152</guid>
      <dc:creator>cisco_api_cco</dc:creator>
      <dc:date>2017-10-31T14:38:48Z</dc:date>
    </item>
  </channel>
</rss>

