Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Datastream for Db2 7.1.

SMF 80 statement


SMF type 80 records are written for security events. Security events include both problems such as a user attempting to log on with an invalid password as well as non-problem events such as RACF’s granting access to a particular resource to a particular user.

SMF-80.png


For information about filterSpecifications , see FILTER-and-MATCH-parameters.

The statement described here is for RACF. For CA Top Secret SMF type 80 formatting, see SMF-TSS80-statement.

Warning

Note

Your installation might have customized RACF to suppress the writing of records on certain events.

You might want to monitor. type 80 records to keep track of security events. The SMF 80 statement indicates that type 80 records are to be collected and forwarded to your syslog console. If you code an SMF 80 statement, then by default all SMF type 80 records are forwarded to your BMC Defender Server or syslog console with a facility of Security (4) and a severity of informational, except for those records where RACF sets bit 0 (the event is a violation) or bit 3 (the event is a warning) in the field SMF80DES. Those records are forwarded by default with a severity of Error or Warning respectively.

Warning

Note

Certain z/OS subsystems might have generated a very large volume of RACF events with event and qualifier code of 1.12 (Successful RACINIT initiation) and 1.13 (Successful RACINIT delete).

These events have non-zero qualifier codes that are routine and benign (as the description successful indicates). You might want to suppress these events by coding EVENTS(1.12 1.13 SEV(SUP)) on your SMF 80 statement.

If you code more than one SMF 80 statement, then a subsequent SMF 80 statement replaces any SMF 80 statements that came before.

Parameter

Description

SMF 80

Must be specified as shown.

DESCription

The description parameter is depreciated and is accepted only for compatibility purposes.

EVENTs

One or more SMF record type 80 event codes and the syslog severity to be assigned to them

Specify the event code or codes in one or more of the following formats. For all of the formats, eventCode must be in the range 1 to 255 and qualifier must be in the range 0 to 63.

Format

Description

eventCode

Single event code

For example, EVENT(1 SEV(ERR)) specifies that event code 1 events (all qualifiers) are forwarded with a severity of Error.

.qualifier

Single qualifier for all events

For example, if you code EVENT( .0 SEV(SUP)), then event code and qualifier 1.0, 2.0, 3.0, etc. is suppressed.

The primary intent of the .qualifier syntax is to allow you to suppress or push down the severity of dot zero events (these all indicate some sort of successful access) but qualifier might be used with any valid qualifier number.

eventCode.qualifier

Single event code and qualifier

For example, EVENT(7.0 SEV(INFO)) specifies that all event code 7 qualifier 0 records are forwarded with severity Informational.

eventCode.qualifier:qualifier

Specifies a range of qualifiers of a single event code

For example, EVENT(5.2:4 SEV(WARN)) specifies that qualifier 2, 3, and 4 of event code 5 are forwarded with a severity of Warning.

eventCode:eventCode

Specifies a range of event codes

For example, EVENT(5:9 SEV(NOTICE)) specifies that all event code 5, 6, 7, 8, and 9 records are forwarded with a severity of Notice.


Warning

Note

The event code or codes can be specified more than once.

For example, EVENT(8 10.2 6:2:3 12:14 SEV(WARN)) specifies that event codes 8, 12, 13, and 14, and event code/qualifiers 10.2, 6.2, and 6.3 are to be forwarded with a severity of Warning.

SEVERITY(severity) specifies the syslog severity for the event code. See Syslog-facilities-and-severities. There are two operands of SEVERITY that are not RFC 3164 severities:

  • SUPPRESS indicates that the specified event records are not to be forwarded to the syslog server at all.
  • DEFAULT restores the default severity processing based on the SMF80DES bit flags as described.

For example, you could code EVENT(2 SEV(NOTICE) EVENT(2.1:5 SEV(DEFAULT)) to indicate that code 2 events were to have a severity of Notice except for qualifiers 1 through 5 that are to have a default severity.

If TRACE(PARM) is specified on the options statement, then the specified severity for each event and qualifier where there is an event map entry and displays in message CZA0242I.

INHibit

Specifies that the writing of the SMF record type 80 to the SMF data sets or log stream is to be inhibited by BMC AMI Defender

SMF record type 80 is processed by BMC AMI Defender, but then inhibited from further processing by SMF.

FACILITY(facilityName)

Specifies the RFC 3164 facility that is to be indicated as the origin of the syslog records corresponding to SMF type 80 records. If you omit this parameter, it defaults to SECURITY4

If you would like a different facility indicated, code one of the RFC 3164 facility names as listed in Syslog-facilities-and-severities.

FIELDs(fieldName…)

Specifies the names of the SMF type 80 record fields that are to be transmitted to the BMC Defender Server or other syslog console, and the order where they are to appear in the message

Specify one or more of the fields as described in SMF-80-fields.

filterSpecification

For information about filterSpecification, see FILTER-and-MATCH-parameters.

LOG | LOG(HEX)

Specifies that the selected SMF records are to be logged on CZAPRINT and optionally dumped in hexadecimal and character format

This parameter is intended primarily for diagnostic purposes. Use care in specifying LOG(HEX) as it might generate a large volume of print records, especially if BMC AMI Defender is left running for several hours or more.

PROCess(‘processTag’)

Specifies the tag that appears at the start of SMF 80 syslog messages, following the priority, timestamp and hostname, and preceding the formatted fields

Specify the exact process tag that you want to include in syslog messages including any spaces and punctuation. Process-tag might be any length from the null string (‘’) to 32 characters. If SMF 80 PROCess is omitted, it defaults to RACF followed by the leading delimiter from OPTIONS DELIM.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Defender for Db2 6.1