<?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: OpenVMS Logs in Security</title>
    <link>https://community.splunk.com/t5/Security/OpenVMS-Logs/m-p/41090#M13796</link>
    <description>&lt;P&gt;I didn't know anyone else has faced this issue. &lt;/P&gt;

&lt;P&gt;The approach I have seen is drawn from:&lt;BR /&gt;
&lt;A href="https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04623140"&gt;https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04623140&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;It seems the OpenVMS system send a report via email (the conduit off the box) and then dropped somewhere splunk can pick it up from. &lt;/P&gt;

&lt;P&gt;From the OpenVMS manual (section 9.5.1)&lt;BR /&gt;
"The most common type of report to generate is a brief, daily listing of events.  You can create a command procedure that runs in a batch job every evening before midnight to generate a report of the day’s security event messages. "&lt;/P&gt;</description>
    <pubDate>Fri, 26 Jul 2019 00:46:03 GMT</pubDate>
    <dc:creator>danan5</dc:creator>
    <dc:date>2019-07-26T00:46:03Z</dc:date>
    <item>
      <title>OpenVMS Logs</title>
      <link>https://community.splunk.com/t5/Security/OpenVMS-Logs/m-p/41087#M13793</link>
      <description>&lt;P&gt;How are OpenVMS admins gettig logs into Splunk?&lt;/P&gt;

&lt;P&gt;Thanks in Advance.&lt;/P&gt;</description>
      <pubDate>Tue, 21 Aug 2012 19:36:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/OpenVMS-Logs/m-p/41087#M13793</guid>
      <dc:creator>dale_lakes</dc:creator>
      <dc:date>2012-08-21T19:36:00Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Logs</title>
      <link>https://community.splunk.com/t5/Security/OpenVMS-Logs/m-p/41088#M13794</link>
      <description>&lt;P&gt;Where I used to work we had syslog-ng listen for data that came from devices where the splunk forwarder could not be installed, we then replaced syslog-ng with splunk forwarders. We had OpenVMS Servers sending data to those machines aswell. (I'm not familiar with OpenVMS, I was the splunk admin).&lt;/P&gt;</description>
      <pubDate>Tue, 21 Aug 2012 20:47:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/OpenVMS-Logs/m-p/41088#M13794</guid>
      <dc:creator>chris</dc:creator>
      <dc:date>2012-08-21T20:47:26Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Logs</title>
      <link>https://community.splunk.com/t5/Security/OpenVMS-Logs/m-p/41089#M13795</link>
      <description>&lt;P&gt;We have a linux admin that wrote some scripting that produces some .txt files on a host from OpenVMS. Then the splunk forwarder on that host monitors the directory where the .txt files land.&lt;/P&gt;

&lt;P&gt;Pretty simple solution.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Jan 2019 22:47:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/OpenVMS-Logs/m-p/41089#M13795</guid>
      <dc:creator>joesrepsolc</dc:creator>
      <dc:date>2019-01-03T22:47:41Z</dc:date>
    </item>
    <item>
      <title>Re: OpenVMS Logs</title>
      <link>https://community.splunk.com/t5/Security/OpenVMS-Logs/m-p/41090#M13796</link>
      <description>&lt;P&gt;I didn't know anyone else has faced this issue. &lt;/P&gt;

&lt;P&gt;The approach I have seen is drawn from:&lt;BR /&gt;
&lt;A href="https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04623140"&gt;https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04623140&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;It seems the OpenVMS system send a report via email (the conduit off the box) and then dropped somewhere splunk can pick it up from. &lt;/P&gt;

&lt;P&gt;From the OpenVMS manual (section 9.5.1)&lt;BR /&gt;
"The most common type of report to generate is a brief, daily listing of events.  You can create a command procedure that runs in a batch job every evening before midnight to generate a report of the day’s security event messages. "&lt;/P&gt;</description>
      <pubDate>Fri, 26 Jul 2019 00:46:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/OpenVMS-Logs/m-p/41090#M13796</guid>
      <dc:creator>danan5</dc:creator>
      <dc:date>2019-07-26T00:46:03Z</dc:date>
    </item>
  </channel>
</rss>

