Snare Central can process a reasonably wide range of source data types. The Snare Central data acquisition software is generally tuned for particular versions of operating system or device logs, so if you encounter problems importing particular types of data, please contact your Snare Central support team, and be prepared to supply (sanitised if required) log samples.

Snort Sensor

Organisations that use the Snort network intrusion detection system can send data to Snare Central via the syslog protocol. Snare will be able to collect, interpret, and report on the events. The following information provides an overview of the steps required to configure the Snort sensor to send eventlog data back to Snare Central. Note that there is no configuration required on Snare Central.

Troubleshooting Snort

Checking for Snort Sensor errors:

• Look in /var/log/messages for errors.

• Run manually:

  • /usr/sbin/snort -D -i "ppp0" -c /etc/snort/snort.conf

• ..then look in /var/log/messages for errors

Collecting ACF2 Data

Snare Central is able to collect ACF2 processed reports, via FTP transfer. The processed reports need to be transferred to a particular directory on Snare Central, which will then be uploaded by Snare Central processes, on a daily basis.

The ACF2 processed reports are based on specific utilities, provided with the ACF2. The utilities produce formatted reports on the following activity on a mainframe, which can then be collected by Snare Central, and used for reporting:

• ACFRPTLL Logonid Modification Log

• ACFRPTRL Dataset Rule Modification Log

• ACFRPTEL Infostorate Modification Log

• ACFRPTDS Dataset Violation/Logging

• ACFRPTRV Resource Violation/Logging

• ACFRPTPW Invalid Password Authority Log

The end of this chapter contains a listing of an example JCL which could be used to run, extract and send the ACF2 processed reports to Snare Central. This sample job has been set up for the Logonid Modification Log report, but could easily be configured for all the reports listed above. Each step in the sample job below performs the following steps. Note that a fixed transfer library name is used because a reference to this library is stored in an FTP parm library which cannot be changed with each run. Some of the programs used in this job are defined below.

• Deletes previous day's FTP transfer library.

• Runs ACF2 report, placing output in a GDG (7 generations kept).

• Allocate new FTP transfer library and copy report from GDG created in previous step.

• FTP the transfer library to Snare Central. The 'snarexfer' FTP user must be used. This user defaults to the "/data/SnareCollect" directory on Snare Central. The ACF2 processed reports must be placed in the "ACF2Log" sub-directory. So the full path becomes: "/data/SnareCollect/ACF2Log". Member level security is used to protect the FTP lid password.

The IEBGENER program used in the sample job is an IBM-supplied utility program designed to generate copies of data sets when disk storage or tape is involved. The IKJEFT01 program is the TSO/E program, and is used to perform a TSO function within a batch job.

CSCSNR01

RACF Violation Logs

RACF resource violation logs can be batch-imported to Snare Central. In particular, ACCESS, DELRES, and JOBINIT logs are supported directly, .

RACF files should be in ASCII format, and transferred to the directory /data/SnareCollect/RACFLog via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

Tandem Logs

Tandom systems supply logs with the following fields:

• P-TIMEREP

• PS-SYSNAME

• PS-GUSER

• PS-GUSER

• PS-TERM

• P-OPERATIO

• P-OUTCOME

• PO-OWNUSER

• PO-OBJTYPE

• PO-OWNUSER

• PC-GUSER

• PC-TERM

Logs should be transferred to the directory /data/SnareCollect/TandemLog via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

Sidewinder Firewall Logs

Sidewinder firewall logs can be exported to CSV, and transferred to Snare Central for processing.

Snare Central, will utilise the following fields:

• date

• hostname

• user_name

• reason

• srcip

• srcport

• dstip

• dstport

• type

• event

• protocol

• auth_method

Logs should be transferred to the directory /data/SnareCollect/SidewinderLog via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

Content Keeper Logs

Content keeper logs can be transferred to the directory /data/SnareCollect/CKeeperLog via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

Snare expects logs to be comma delimited, and be composed of fields in the following order:

• Date/Time

• Ignored field

• Source IP Address

• User Name

• Bytes

• Status Code

• Content

• URL

• Policy

• Category

Checkpoint Firewall1 Logs

Checkpoint Firewall 1 firewalls can export log data to a CSV file. Snare is capable of coping with a range of formats, as long as the header line, specifying the log format, is included as the first line in each exported file.

A sample header line is:

• num,date,time,orig,type,action,alert,i/f_name,i/f_dir,proto,src,dst,service,s_port,len,rule,icmp-type,icmp-code,reason:,rpc_prog,IKE Log:,product,additionals:,sys_msgs

Snare will try and pull out the following information from the log data, and incorporate it into the Snare log archive:

• Date

• Time

• Action

• Interface

• Source IP Address

• Source Port

• Destination IP Address

• Destination Port

• Protocol

• Rule

• All other information will be included within a general 'Data' field.

Checkpoint Firewall logs can be transferred to the directory /data/SnareCollect/Firewall1Log via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

Gauntlet Firewall Logs

Gauntlet Firewall logs can be transferred to the directory /data/SnareCollect/GauntletFirewallLog/ via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

Content is assumed to be in ASCII format, and values are space separated.

OS400 Logs

OS400 logs can be transferred to the directory /data/SnareCollect/OS400Log via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

Snare is capable of coping with a range of log formats, as long as the header line, specifying the log format, is included as the first line in each exported file.

Snare understands the following fields:

• Journal Code (JournalCode)

• Journal Entry Code (JournalEntryCode)

• Journal Entry Date (Date)

• Journal Entry Time (Time)

• System name (System)

• Job Name (JobName)

• User Name (JobUser)

• Job Number (JobNumber)

• Program Accessing Object (Program)

• Object Failure Object Name (OFName)

• Object Failure Library Name (OFLibrary)

• Object Failure Object Type (OFType)

• Failed Login User (Strings)

• Failed Login Job (Strings)

• System Value name (Strings)

• Changed Value (Strings)

Squid Proxy Logs

Squid proxy logs (in the default squid log format) can be transferred to the directory /data/SnareCollect/SquidProxyLog via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

Apache Logs

Apache web server logs (in the default apache 'combined' format) can be transferred to the directory /data/SnareCollect/ApacheLog via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

Internet Information Server (IIS) Logs

IIS web server logs can be transferred to the directory /data/SnareCollect/IISWebLog via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

IIS logs should retain the header information, that includes the 'Fields' definition line.

Snare Central requires the following fields to be included:

• date

• time

• s-ip

• cs-method

• cs-uri-stem

• cs-uri-query

• s-port

• cs-username

• c-ip

• cs(User-Agent)

• sc-status

• sc-substatus

• sc-win32-status

Windows Event Logs (Exported from Snare Agents)

Snare for Windows agents are capable of exporting log data to a file on disk, rather than pushing the events back to a central server.

In situations where systems are air-gapped, or have sporadic internet connectivity, directly transferring the archived log data to Snare Central via FTP is possible.

Logs should be in standard Snare Agent tab-delimited text format, and can be transferred to the directory /data/SnareCollect/MSWinEventLog via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

Windows Event Logs (EVTX files)

Note: Only available in Snare Central version 7.1 or newer

EVTX files can be exported from windows machines, and transferred to a subdirectory within /data/SnareCollect/MSWinEVTX via FTP using the user 'snarexfer'. Logs will be processed daily, at around midnight.

There are several limitations of the EVTX format that need to be considered:

• String order may not match the order found in normal Snare agent logs.

  • Some existing Snare Central objectives may require strings to be in a particular order, to pull out information of particular interest, from the 'Strings' section of events, such as as user name.

• String names may not match those found in normal Snare agent logs.

  • The string "SubjectUserSid" in the EVTX file, is actually translated to "Subject: Security ID:" in many events.

  • The string "SubjectUserName" in the EVTX file may be "User Name" in some circumstances, or "Account Name" in others. There is no obvious consistency , and there does not seem to be a generally available lookup-table to hint at what translations are appropriate.

  • Snare Central will attempt to convert the 'CamelCase' string headers to space-included versions, which are more likely to match those displayed by the Windows event viewer (and therefore transmitted by Snare), however, case may be incorrect in some circumstances:

    • SubjectUserId may be translated as "Subject User Id", whereas the Windows event view will display it as "Subject User ID".

    • There are a few 'special cases' defined in the EVTX converter, that may fix the more obvious examples.

• The contents of the 'Data' field is not currently supported for conversion.

• Content that is usually interpreted at display-time in the Windows event viewer, or at transmission time in the Snare agents, will not be interpreted.

  • At event display-time, the Windows event viewer interrogates the registry, and sometimes native or third party DLL's, to try and resolve event template components to human readable text. The Snare for Windows agent does the same, when it converts the events to text-format prior to transmission.

  • These DLL's/registry entries are not guaranteed to be installed on all windows machines - for example, Internet Information Server template conversion DLL's will not be installed on a server that is not running IIS.

  • As such, information that is available to a Snare Agent on the source system, is NOT available to Snare Central when it attempts to convert the binary EVTX log data to text format.

  • Human-readable event descriptions that are often included within the strings section, will not be available.

• Date/Time values within the EVTX files are in UTC format, and the EVTX files do not contain UTC offset information for the source server.

• In general, the conversion tool may require assistance in determining the source of the source EVTX file (eg: Security, Application, System, etc).

  • The two points above, can be addressed with the assistance of file path hints.

  • Logs should be included in one of the following file paths, depending on the log type/source:

    • /data/SnareCollect/MSWinEVTX/Security

    • /data/SnareCollect/MSWinEVTX/Application

    • /data/SnareCollect/MSWinEVTX/System

  • Under these directories, if time zone conversion is required (highly recommended), a directory should be created with the textual representation of the time-zone (but with the forward-slash character switched out for a COLON)

    • For example:

      • /data/SnareCollect/MSWinEVTX/Security/America:New_York

      • /data/SnareCollect/MSWinEVTX/Security/Australia:Adelaide

Lotus Notes / Domino

Snare Central is able to connect to a Domino server to retrieve eventlog data from log.nsf. It can also retrieve user and group information, plus access controls. However, some of the default settings in Lotus Domino can cause problems with the Snare Agent; please modify the server as follows: From the Domino Administrator page, click the Configuration tab, expand the Web section and click Internet Sites.

1. Choose the log.nsf and click Edit Document.

2. Click the Domino Web Engine tab. Under "Conversion/Display" complete these fields:

   1. Default lines per view page: 250 (default 30)

   2. Maximum lines per view page: 0 (default 1000).