<?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: Pulling Logs via API in APIs</title>
    <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882453#M445</link>
    <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;We are using a 3rd party solution for that. take a look at skyformation. AFAIK they support any SIEM and also remove the need to parse and classify the events.&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Wed, 25 Apr 2018 15:50:21 GMT</pubDate>
    <dc:creator>janereed</dc:creator>
    <dc:date>2018-04-25T15:50:21Z</dc:date>
    <item>
      <title>Pulling Logs via API</title>
      <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882445#M437</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;My organization is coming up on our go-live for requiring Duo for a variety of platforms. We are trying to get auth, admin, and telephony logs to our SIEM (LogRhythm) prior to go-live. Since there is no connector/plugin for Duo that leaves the method of pulling the logs down via API and ingesting them as a flat file or csv format. I am aware of these resources for accomplishing this: &lt;A href="https://duo.com/docs/adminapi#logs" rel="nofollow noopener"&gt;https://duo.com/docs/adminapi#logs&lt;/A&gt; and &lt;A href="https://github.com/duosecurity" rel="nofollow noopener"&gt;https://github.com/duosecurity&lt;/A&gt;. However, the team that operates our SIEM does not have a strong scripting background and this process will live on their platform. Are there more resources I am missing that could help them get this going?&lt;/P&gt;
&lt;P&gt;The fact that Duo does not provide a more seamless process, or does not put more effort into working with SIEM vendors to make it seamless, IMO is a major drawback of the product. Any corporation with any compliance or regulatory restrictions will need to have these logs ingested into a SIEM. This should not be a manual, custom process that is prone to human error.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 12 Jul 2017 13:14:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882445#M437</guid>
      <dc:creator>Steve_M</dc:creator>
      <dc:date>2017-07-12T13:14:59Z</dc:date>
    </item>
    <item>
      <title>Re: Pulling Logs via API</title>
      <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882446#M438</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;I agree, but it may be useful to try the script here. You shouldn’t need significant background other than just installing python and changing a couple of variables. This will convert the logs to syslog to send to your SIEM. Our team uses something very similar.&lt;/P&gt;
&lt;ASIDE class="onebox whitelistedgeneric"&gt;
  &lt;HEADER class="source"&gt;
      &lt;IMG src="https://github.githubassets.com/favicons/favicon.svg" class="site-icon" width="32" height="32" /&gt;
      &lt;A href="https://github.com/libresec/Duo-Log-Grabber" target="_blank" rel="nofollow noopener"&gt;GitHub&lt;/A&gt;
  &lt;/HEADER&gt;
  &lt;ARTICLE class="onebox-body"&gt;
    &lt;IMG src="https://avatars2.githubusercontent.com/u/1238700?s=400&amp;amp;v=4" class="thumbnail onebox-avatar" width="400" height="400" /&gt;

&lt;H3&gt;&lt;A href="https://github.com/libresec/Duo-Log-Grabber" target="_blank" rel="nofollow noopener"&gt;libresec/duo-log-grabber&lt;/A&gt;&lt;/H3&gt;

&lt;P&gt;Grabs the administrator and authentication logs from the Duo Security API and sends CEF-formatted syslog. - libresec/duo-log-grabber&lt;/P&gt;


  &lt;/ARTICLE&gt;
  &lt;DIV class="onebox-metadata"&gt;
    
    
  &lt;/DIV&gt;
  &lt;DIV style="clear: both"&gt;&lt;/DIV&gt;
&lt;/ASIDE&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 12 Jul 2017 14:07:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882446#M438</guid>
      <dc:creator>rhys_samson</dc:creator>
      <dc:date>2017-07-12T14:07:21Z</dc:date>
    </item>
    <item>
      <title>Re: Pulling Logs via API</title>
      <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882447#M439</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;Thank you &lt;A class="mention" href="https://community.duo.com/u/rhys_samson"&gt;@rhys_samson&lt;/A&gt;. I will forward this on to my team and hopefully it helps them.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 12 Jul 2017 14:32:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882447#M439</guid>
      <dc:creator>Steve_M</dc:creator>
      <dc:date>2017-07-12T14:32:34Z</dc:date>
    </item>
    <item>
      <title>Re: Pulling Logs via API</title>
      <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882448#M440</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;We are working to improve Duo’s integration with SIEMs. For example, we released a &lt;A href="https://duo.com/docs/splunkapp"&gt;Splunk connector&lt;/A&gt; earlier this year.&lt;/P&gt;
&lt;P&gt;We’ll prioritize exploring integrations with specific SIEM vendors based on customer interest, so if you haven’t already done so please contact &lt;A href="https://duo.com/support"&gt;Duo Support&lt;/A&gt; or your Duo Customer Success Manager to submit a feature request for a LogRhythm connector or integration.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 13 Jul 2017 18:49:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882448#M440</guid>
      <dc:creator>DuoKristina</dc:creator>
      <dc:date>2017-07-13T18:49:13Z</dc:date>
    </item>
    <item>
      <title>Re: Pulling Logs via API</title>
      <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882449#M441</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;We have a similar need for Sumologic.&lt;BR /&gt;
Can I run libresec/Duo-Log-Grabber on AWS? If so do you have any document which can assist with the config?&lt;BR /&gt;
Thanks,&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 04 Dec 2017 04:51:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882449#M441</guid>
      <dc:creator>avs1</dc:creator>
      <dc:date>2017-12-04T04:51:58Z</dc:date>
    </item>
    <item>
      <title>Re: Pulling Logs via API</title>
      <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882450#M442</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;Can I run this on AWS? What are the requirements?&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Sun, 10 Dec 2017 00:14:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882450#M442</guid>
      <dc:creator>avs1</dc:creator>
      <dc:date>2017-12-10T00:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: Pulling Logs via API</title>
      <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882451#M443</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;Hello avs,&lt;/P&gt;
&lt;P&gt;If you have specific questions about &lt;A href="https://github.com/libresec/duo-log-grabber"&gt;libresec’s Duo-Log-Grabber&lt;/A&gt; utility you may wish to direct them to &lt;A href="https://github.com/libresec"&gt;libresec&lt;/A&gt; himself on GitHub.&lt;/P&gt;
&lt;P&gt;You can probably run it on an Amazon Linux AWS instance (or any other Linux) with Python, then &lt;A href="https://github.com/libresec/duo-log-grabber/blob/master/README.md"&gt;follow the install instructions&lt;/A&gt;.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 11 Dec 2017 14:52:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882451#M443</guid>
      <dc:creator>DuoKristina</dc:creator>
      <dc:date>2017-12-11T14:52:38Z</dc:date>
    </item>
    <item>
      <title>Re: Pulling Logs via API</title>
      <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882452#M444</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;It would be nice if there were more of a push feature. Maybe write out to AWS SQS or even s3 buckets?&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 14 Mar 2018 16:23:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882452#M444</guid>
      <dc:creator>gimmic</dc:creator>
      <dc:date>2018-03-14T16:23:44Z</dc:date>
    </item>
    <item>
      <title>Re: Pulling Logs via API</title>
      <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882453#M445</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;We are using a 3rd party solution for that. take a look at skyformation. AFAIK they support any SIEM and also remove the need to parse and classify the events.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Wed, 25 Apr 2018 15:50:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882453#M445</guid>
      <dc:creator>janereed</dc:creator>
      <dc:date>2018-04-25T15:50:21Z</dc:date>
    </item>
    <item>
      <title>Re: Pulling Logs via API</title>
      <link>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882454#M446</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;This is very outdated solution . Do we have anyhting to integrate with elastic search&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 20 Feb 2020 07:43:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/apis/pulling-logs-via-api/m-p/4882454#M446</guid>
      <dc:creator>Pranav_Jariwala</dc:creator>
      <dc:date>2020-02-20T07:43:09Z</dc:date>
    </item>
  </channel>
</rss>

