SIEM Plan

SIEM Plan provides access to a database of hundreds of predefined correlation rules and sets of ready-made visualizations and dashboards that give a quick overview of the organizations security status. At the same time, the system still provides a great flexibility in building your own correlation rules and visualizations exactly as required by your organization.

System responds to the needs of today’s organizations by allowing identification of threats on the basis of a much larger amount of data, not always related to the security area as it is provided by traditional SIEM systems.

Alert Module

Enabling the Alert Module

SMTP server configuration

To configuring STMP server for email notification you should:

  • edit /opt/alert/config.yml and add the following section:

    # email conf
    smtp_host: "mail.example.conf"
    smtp_port: 587
    smtp_ssl: false
    from_addr: "siem@example.com"
    smtp_auth_file: "/opt/alert/smtp_auth_file.yml"
    
  • add the new /opt/alert/smtp_auth_file.yml file:

    user: "user"
    password: "password"
    
  • restart alert service:

    systemctl restat alert
    

Creating Alerts

To create the alert, click the “Alerts” button from the main menu bar.

../_images/image93.png

We will display a page with tree tabs: Create new alerts in „Create alert rule”, manage alerts in „Alert rules List” and check alert status „Alert Status”.

In the alert creation windows we have an alert creation form:

../_images/image92.PNG

  • Name - the name of the alert, after which we will recognize and search for it.
  • Index pattern - a pattern of indexes after which the alert will be searched.
  • Role - the role of the user for whom an alert will be available
  • Type - type of alert
  • Description - description of the alert.
  • Example - an example of using a given type of alert. Descriptive field
  • Alert method - the action the alert will take if the conditions are met (sending an email message or executing a command)
  • Any - additional descriptive field.# List of Alert rules #

The “Alert Rule List” tab contain complete list of previously created alert rules:

../_images/image94.png

In this window, you can activate / deactivate, delete and update alerts by clicking on the selected icon with the given alert: ../_images/image63.png.

Alerts status

In the “Alert status” tab, you can check the current alert status: if it activated, when it started and when it ended, how long it lasted, how many event sit found and how many times it worked.

../_images/image95.png

Also, on this tab, you can recover the alert dashboard, by clicking the “Recovery Alert Dashboard” button.

Alert Types

The various Rule Type classes, defined in Energy Logserver. An instance is held in memory for each rule, passed all of the data returned by querying Elasticsearch with a given filter, and generates matches based on that data.

Any

The any rule will match everything. Every hit that the query returns will generate an alert.

Blacklist

The blacklist rule will check a certain field against a blacklist, and match if it is in the blacklist.

Whitelist

Similar to blacklist, this rule will compare a certain field to a whitelist, and match if the list does not contain the term.

Change

This rule will monitor a certain field and match if that field changes.

Frequency

This rule matches when there are at least a certain number of events in a given time frame.

Spike

This rule matches when the volume of events during a given time period is spike_height times larger or smaller than during the previous time period.

Flatline

This rule matches when the total number of events is under a given threshold for a time period.

New Term

This rule matches when a new value appears in a field that has never been seen before.

Cardinality

This rule matches when a the total number of unique values for a certain field within a time frame is higher or lower than a threshold.

Metric Aggregation

This rule matches when the value of a metric within the calculation window is higher or lower than a threshold.

Percentage Match

This rule matches when the percentage of document in the match bucket within a calculation window is higher or lower than a threshold.

Unique Long Term

This rule matches when there are values of compare_key in each checked timeframe.

Find Match

Rule match when in defined period of time, two correlated documents match certain strings.

Consecutive Growth

Rule matches for value difference between two aggregations calculated for different periods in time.

Logical

Rule matches when a complex, logical criteria is met. Rule can be use for alert data correlation.

An example of using the Logical rule type.

../_images/image149.png

Alerts that must occur for the rule to be triggered:

  • Switch - Port is off-line - the alert must appear 5 times.
    • OR
  • Switch - Port is on-line - the alert must appear 5 times.

If both of the above alerts are met within no more than 5 minutes and the values of the “port_number” field are related to each other, the alert rule is triggered. It is possible to use logical connectives such as: OR, AND, NOR, NAND, XOR.

Chain

Rule matches when a complex, logical criteria is met. Rule can be use for alert data correlation.

An example of using the Chain rule type.

../_images/image148.png

Alerts that must occur for the rule to be triggered:

  • Linux - Login Failure - the alert must appear 10 times.
  • AND
  • Linux - Login Success - 1 time triggered alert.

If the sequence of occurrence of the above alerts is met within 5 minutes and the values of the “username” field are related to each other, the alert rule is triggered. The order in which the component alerts occur is important.

Difference

This rule calculates percentage difference between aggregations for two non-overlapping time windows.

Let’s assume x represents the current time (i.e. when alert rule is run) then the relation between historical and present time windows is described by the inequality:

<x – agg_min – delta_min; x – delta_min> <= <x – agg_min; x>; where x – delta_min <= x – agg_min => delta_min >= agg_min

The percentage difference is then described by the following equation:

d = | avg_now – avg_history | / max(avg_now, avg_history) * 100; for (avg_now – avg_history != 0; avg_now != 0; avg_history != 0)
d = 0; (in other cases)

avg_now is the arithmetic mean of <x agg_min; x> avg_history is the arithmetic mean of <x agg_min delta_min; x delta_min>

Required parameters:

  • Enable the rule by setting type field. type: difference
  • Based on the compare_key field aggregation is calculated. compare_key: value
  • An alert is triggered when the percentage difference between aggregations is higher than the specified value. threshold_pct: 10
  • The difference in minutes between calculated aggregations. delta_min: 3
  • Aggregation bucket (in minutes). agg_min: 1

Optional parameters:

If present, for each unique query_key aggregation is calculated (it needs to be of type keyword). query_key: hostname

Alert Methods

When the alert rule is fulfilled, the defined action is performed - the alert method. The following alert methods have been predefined in the system:

  • email;
  • commands;
  • user;

Email

Method that sends information about an alert to defined email addresses.

User

Method that sends information about an alert to defined system users.

Command

A method that performs system tasks. For example, it triggers a script that creates a new event in the customer ticket system.

Below is an example of an alert rule definition that uses the “command” alert method to create and recover an ticket in the client’s request system:

index: op5-*
name: change-op5-hoststate
type: change

compare_key: hoststate
ignore_null: true
query_key: hostname

filter:
- query_string:
    query: "_exists_: hoststate AND datatype: \"HOSTPERFDATA\" AND _exists_: hostname"

realert:
  minutes: 0
alert: "command"
command: ["/opt/alert/send_request_change.sh", "5", "%(hostname)s", "SYSTEM_DOWN", "HOST", "Application Collection", "%(hoststate)s", "%(@timestamp)s"]

The executed command has parameters which are the values of the fields of the executed alert. Syntax: %(fields_name).

The Hive

The alert module can forward information about the alert to Security Incident Response Platform TheHive.

The configuration of the Hive Alert should be done in the definition of the Rule Definition alert using the following options:

  • hive_alert_config_type: classic - allows the use of variables to build The Hive alert
  • hive_alert_config:
    • title (text) : title of the alert (ignored in classic config type)
    • description (text) : description of the alert (ignored in classic config type)
    • severity (number) : severity of the alert (1: low; 2: medium; 3: high) default=2
    • date (date) : date and time when the alert was raised default=now
    • tags (multi-string) : case tags default=empty
    • tlp (number) : TLP (0: white; 1: green; 2: amber; 3: red) default=2
    • status (AlertStatus) : status of the alert (New, Updated, Ignored, Imported) default=New
    • type (string) : type of the alert (read only)
    • source (string) : source of the alert (read only)
    • sourceRef (string) : source reference of the alert (read only)
    • artifacts (multi-artifact) : artifact of the alert. It is a array of JSON object containing artifact attributes default=empty
    • follow (boolean) : if true, the alert becomes active when updated default=true
  • hive_observable_data_mapping - mapping field values to the The Hive alert.

Note: When use: hive_alert_config_type: classic the following parameters are ignored:

hive_alert_config:
    title: title of the alert
    description: description of the alert

and you should use:

alert_subject: "title of the alert"
alert_text: "description of the alert"

Example of configuration:

hive_alert_config_type: classic

hive_alert_config:
  type: 'test'
  source: 'elastalert-{rule[name]}'
  severity: 3
  tags: ['malicious behavior']
  tlp: 2
  status: 'New'
  follow: True

hive_observable_data_mapping:
  - ip: "{match[field1]}"
  - source: "{match[field2]}"

RSA Archer

The alert module can forward information about the alert to the risk management platfrorm RSA Archer.

The alert rule must be configure to use Command alert method witch execute the following scripts ucf.sh or ucf2.sh

Configuration steps:

  1. Copy and save on the Energy Logserver server the following scripts to appropriate location, for example /opt/alert/bin:

    • ucf.sh - for SYSLOG

      #!/usr/bin/env bash
      base_url = "http://localhost/Archer" ##set the appropriate Archer URL
      
      logger -n $base_url -t logger -p daemon.alert -T "CEF:0|EnergyLogServer|EnergyLogServer|${19}|${18}| TimeStamp=$1 DeviceVendor/Product=$2-$3 Message=$4 TransportProtocol=$5 Aggregated:$6 AttackerAddress=$7 AttackerMAC=$8 AttackerPort=$9 TargetMACAddress=${10} TargetPort=${11} TargetAddress=${12} FlexString1=${13} Link=${14} ${15} $1 ${16} $7 ${17}"
      
    • ucf2.sh - for REST API

      #!/usr/bin/env bash
      base_url = "http://localhost/Archer" ##set the appropriate Archer URL
      instance_name = "Archer"
      username = "apiuser"
      password = "Archer"
      
      curl -k -u $username:$password -H "Content-Type: application/xml" -X POST "$base_url:50105/$instance_name" -d {
      "CEF":"0","Server":"EnergyLogServer","Version":"${19}","NameEvent":"${18}","TimeStamp":"$1","DeviceVendor/Product":"$2-$3","Message""$4","TransportProtocol":"$5","Aggregated":"$6","AttackerAddress":"$7","AttackerMAC":"$8","AttackerPort":"$9","TargetMACAddress":"${10}","TargetPort":"${11}","TargetAddress":"${12}","FlexString1":"${13}","Link":"${14}","EventID":"${15}","EventTime":"${16}","RawEvent":"${17}"
      }
      
  2. Alert rule definition:

    • Index Pattern: alert*

    • Name: alert-sent-to-rsa

    • Rule Type: any

    • Rule Definition:

      filter:
      - query:
          query_string:
            query: "_exists_: endTime AND _exists_: deviceVendor AND _exists_: deviceProduct AND _exists_: message AND _exists_: transportProtocol AND _exists_: correlatedEventCount AND _exists_: attackerAddress AND _exists_: attackerMacAddress AND _exists_: attackerPort AND _exists_: targetMacAddress AND _exists_: targetPort AND _exists_: targetAddress AND _exists_: flexString1 AND _exists_: deviceCustomString4 AND _exists_: eventId AND _exists_: applicationProtocol AND _exists_: rawEvent"
      
      include:
      - endTime
      - deviceVendor
      - deviceProduct
      - message
      - transportProtocol
      - correlatedEventCount
      - attackerAddress
      - attackerMacAddress
      - attackerPort
      - targetMacAddress
      - targetPort
      - targetAddress
      - flexString1
      - deviceCustomString4
      - eventId
      - applicationProtocol
      - rawEvent
      
      realert:
        minutes: 0
      
    • Alert Method: command

    • Path to script/command: /opt/alert/bin/ucf.sh

Alert Content

There are several ways to format the body text of the various types of events. In EBNF::

rule_name           = name
alert_text          = alert_text
ruletype_text       = Depends on type
top_counts_header   = top_count_key, ":"
top_counts_value    = Value, ": ", Count
top_counts          = top_counts_header, LF, top_counts_value
field_values        = Field, ": ", Value

Similarly to alert_subject, alert_text can be further formatted using standard Python formatting syntax. The field names whose values will be used as the arguments can be passed with alert_text_args or alert_text_kw. You may also refer to any top-level rule property in the alert_subject_args, alert_text_args, alert_missing_value, and alert_text_kw fields. However, if the matched document has a key with the same name, that will take preference over the rule property.

By default::

body                = rule_name

                      [alert_text]

                      ruletype_text

                      {top_counts}

                      {field_values}

With alert_text_type: alert_text_only::

body                = rule_name

                      alert_text

With alert_text_type: exclude_fields::

body                = rule_name

                      [alert_text]

                      ruletype_text

                      {top_counts}

With alert_text_type: aggregation_summary_only::

body                = rule_name

                      aggregation_summary

ruletype_text is the string returned by RuleType.get_match_str.

field_values will contain every key value pair included in the results from Elasticsearch. These fields include “@timestamp” (or the value of timestamp_field), every key in include, every key in top_count_keys, query_key, and compare_key. If the alert spans multiple events, these values may come from an individual event, usually the one which triggers the alert.

When using alert_text_args, you can access nested fields and index into arrays. For example, if your match was {"data": {"ips": ["127.0.0.1", "12.34.56.78"]}}, then by using "data.ips[1]" in alert_text_args, it would replace value with "12.34.56.78". This can go arbitrarily deep into fields and will still work on keys that contain dots themselves.

Example of rules

Unix - Authentication Fail

  • index pattern:

      syslog-*
    
  • Type:

      Frequency
    
  • Alert Method:

      Email
    
  • Any:

      num_events: 4
      timeframe:
        minutes: 5
    
    
      filter:
      - query_string:
          query: "program: (ssh OR sshd OR su OR sudo) AND message: \"Failed password\""
    

Windows - Firewall disable or modify

  • index pattern:

      beats-*
    
  • Type:

      Any
    
  • Alert Method:

      Email
    
  • Any:

filter:

	- query_string:
	       query: "event_id:(4947 OR 4948 OR 4946 OR 4949 OR 4954 OR 4956 OR 5025)"

SIEM Rules

Beginning with version 6.1.7, the following SIEM rules are delivered with the product.

| Nr. | Architecture/Application | Rule Name                                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | Index name   | Requirements                                     | Source                       | Time definition            | Threashold |
|-----|--------------------------|--------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------|--------------------------------------------------|------------------------------|----------------------------|------------|
| 1   | Windows                  | Windows - Admin night logon                                  | Alert on Windows login events when detected outside business hours                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 2   | Windows                  | Windows - Admin task as user                                 | Alert when admin task is initiated by regular user.  Windows event id 4732 is verified towards static admin list. If the user does not belong to admin list AND the event is seen than we generate alert. Static Admin list is a logstash  disctionary file that needs to be created manually. During Logstash lookup a field user.role:admin is added to an event.4732: A member was added to a security-enabled local group                                                                                                                                                                                                                                       | winlogbeat-* | winlogbeatLogstash admin dicstionary lookup file | Widnows Security Eventlog    | Every 1min                 | 1          |
| 3   | Windows                  | Windows - diff IPs logon                                     | Alert when Windows logon process is detected and two or more different IP addressed are seen in source field.  Timeframe is last 15min.Detection is based onevents 4624 or 1200.4624: An account was successfully logged on1200: Application token success                                                                                                                                                                                                                                                                                                                                                                                                          | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min, for last 15min | 1          |
| 4   | Windows                  | Windows - Event service error                                | Alert when Windows event 1108 is matched1108: The event logging service encountered an error                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 5   | Windows                  | Windows - file insufficient privileges                       | Alert when Windows event 5145 is matched5145: A network share object was checked to see whether client can be granted desired accessEvery time a network share object (file or folder) is accessed, event 5145 is logged. If the access is denied at the file share level, it is audited as a failure event. Otherwise, it considered a success. This event is not generated for NTFS access.                                                                                                                                                                                                                                                                       | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min, for last 15min | 50         |
| 6   | Windows                  | Windows - Kerberos pre-authentication failed                 | Alert when Windows event 4625 or 4771 is matched 4625: An account failed to log on 4771: Kerberos pre-authentication failed                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 7   | Windows                  | Windows - Logs deleted                                       | Alert when Windows event 1102 OR 104 is matched1102: The audit log was cleared104: Event log cleared                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 8   | Windows                  | Windows - Member added to a security-enabled global group    | Alert when Windows event 4728 is matched4728: A member was added to a security-enabled global group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 9   | Windows                  | Windows - Member added to a security-enabled local group     | Alert when Windows event 4732 is matched4732: A member was added to a security-enabled local group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 10  | Windows                  | Windows - Member added to a security-enabled universal group | Alert when Windows event 4756 is matched4756: A member was added to a security-enabled universal group                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 11  | Windows                  | Windows - New device                                         | Alert when Windows event 6414 is matched6416: A new external device was recognized by the system                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 12  | Windows                  | Windows - Package installation                               | Alert when Windows event 4697 is matched 4697: A service was installed in the system                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 13  | Windows                  | Windows - Password policy change                             | Alert when Windows event 4739 is matched4739: Domain Policy was changed                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 14  | Windows                  | Windows - Security log full                                  | Alert when Windows event 1104 is matched1104: The security Log is now full                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 15  | Windows                  | Windows - Start up                                           | Alert when Windows event 4608 is matched 4608: Windows is starting up                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 16  | Windows                  | Windows - Account lock                                       | Alert when Windows event 4740 is matched4740: A User account was Locked out                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 17  | Windows                  | Windows - Security local group was changed                   | Alert when Windows event 4735 is matched4735: A security-enabled local group was changed                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 18  | Windows                  | Windows - Reset password attempt                             | Alert when Windows event 4724 is matched4724: An attempt was made to reset an accounts password                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 19  | Windows                  | Windows - Code integrity changed                             | Alert when Windows event 5038 is matched5038: Detected an invalid image hash of a fileInformation:    Code Integrity is a feature that improves the security of the operating system by validating the integrity of a driver or system file each time it is loaded into memory.    Code Integrity detects whether an unsigned driver or system file is being loaded into the kernel, or whether a system file has been modified by malicious software that is being run by a user account with administrative permissions.    On x64-based versions of the operating system, kernel-mode drivers must be digitally signed.The event logs the following information: | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 20  | Windows                  | Windows - Application error                                  | Alert when Windows event 1000 is matched1000: Application error                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     | winlogbeat-* | winlogbeat                                       | Widnows Application Eventlog | Every 1min                 | 1          |
| 21  | Windows                  | Windows - Application hang                                   | Alert when Windows event 1001 OR 1002 is matched1001: Application fault bucket1002: Application hang                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                | winlogbeat-* | winlogbeat                                       | Widnows Application Eventlog | Every 1min                 | 1          |
| 22  | Windows                  | Windows - Audit policy changed                               | Alert when Windows event 4719 is matched4719: System audit policy was changed                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 23  | Windows                  | Windows - Eventlog service stopped                           | Alert when Windows event 6005 is matched6005: Eventlog service stopped                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 24  | Windows                  | Windows - New service installed                              | Alert when Windows event 7045 OR 4697 is matched7045,4697: A service was installed in the system                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 25  | Windows                  | Windows - Driver loaded                                      | Alert when Windows event 6 is matched6: Driver loadedThe driver loaded events provides information about a driver being loaded on the system. The configured hashes are provided as well as signature information. The signature is created asynchronously for performance reasons and indicates if the file was removed after loading.                                                                                                                                                                                                                                                                                                                             | winlogbeat-* | winlogbeat                                       | Widnows System Eventlog      | Every 1min                 | 1          |
| 26  | Windows                  | Windows - Firewall rule modified                             | Alert when Windows event 2005 is matched2005: A Rule has been modified in the Windows firewall Exception List                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 27  | Windows                  | Windows - Firewall rule add                                  | Alert when Windows event 2004 is matched2004: A firewall rule has been added                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |
| 28  |                          | Windows - Firewall rule deleted                              | Alert when Windows event 2006 or 2033 or 2009 is matched2006,2033,2009: Firewall rule deleted                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       | winlogbeat-* | winlogbeat                                       | Widnows Security Eventlog    | Every 1min                 | 1          |

Playbooks

Energy Logserver has a set of predefined set of rules and activities (called Playbook) that can be attached to a registered event in the Alert module. Playbooks can be enriched with scripts that can be launched together with Playbook.

Create Playbook

To add a new playbook, go to the Alert module, select the Playbook tab and then Create Playbook

../_images/image116.png

In the Name field, enter the name of the new Playbook.

In the Text field, enter the content of the Playbook message.

In the Script field, enter the commands to be executed in the script.

To save the entered content, confirm with the Submit button.

Playbooks list

To view saved Playbook, go to the Alert module, select the Playbook tab and then Playbooks list:

../_images/image117.png

To view the content of a given Playbook, select the Show button.

To enter the changes in a given Playbook or in its script, select the Update button. After making changes, select the Submit button.

To delete the selected Playbook, select the Delete button.

Linking Playbooks with alert rule

You can add a Playbook to the Alert while creating a new Alert or by editing a previously created Alert.

To add Palybook to the new Alert rule, go to the Create alert rule tab and in the Playbooks section use the arrow keys to move the correct Playbook to the right window.

To add a Palybook to existing Alert rule, go to the Alert rule list tab with the correct rule select the Update button and in the Playbooks section use the arrow keys to move the correct Playbook to the right window.

Playbook verification

When creating an alert or while editing an existing alert, it is possible that the system will indicate the most-suited playbook for the alert. For this purpose, the Validate button is used, which starts the process of searching the existing playbook and selects the most appropriate ones.

../_images/image132.png

Risks

Energy Logserver allows you to estimate the risk based on the collected data. The risk is estimated based on the defined category to which the values from 0 to 100 are assigned.

Information on the defined risk for a given field is passed with an alert and multiplied by the value of the Rule Importance parameter.

Create category

To add a new risk Category, go to the Alert module, select the Risks tab and then Create Cagtegory.

../_images/image118.png

Enter the Name for the new category and the category Value.

Category list

To view saved Category, go to the Alert module, select the Risks tab and then Categories list:

../_images/image119.png

To view the content of a given Category, select the Show button.

To change the value assigned to a category, select the Update button. After making changes, select the Submit button.

To delete the selected Category, select the Delete button.

Create risk

To add a new playbook, go to the Alert module, select the Playbook tab and then Create Playbook

../_images/image120.png

In the Index pattern field, enter the name of the index pattern. Select the Read fields button to get a list of fields from the index. From the box below, select the field name for which the risk will be determined.

From the Timerange field, select the time range from which the data will be analyzed.

Press the Read valules button to get values from the previously selected field for analysis.

Next, you must assign a risk category to the displayed values. You can do this for each value individually or use the check-box on the left to mark several values and set the category globally using the Set global category button. To quickly find the right value, you can use the search field.

../_images/image122.png

After completing, save the changes with the Submit button.

List risk

To view saved risks, go to the Alert module, select the Risks tab and then Risks list:

../_images/image121.png

To view the content of a given Risk, select the Show button.

To enter the changes in a given Risk, select the Update button. After making changes, select the Submit button.

To delete the selected Risk, select the Delete button.

Linking risk with alert rule

You can add a Risk key to the Alert while creating a new Alert or by editing a previously created Alert.

To add Risk key to the new Alert rule, go to the Create alert rule tab and after entering the index name, select the Read fields button and in the Risk key field, select the appropriate field name. In addition, you can enter the validity of the rule in the Rule Importance field (in the range 1-100%), by which the risk will be multiplied.

To add Risk key to the existing Alert rule, go to the Alert rule list, tab with the correct rule select the Update button. Use the Read fields button and in the Risk key field, select the appropriate field name. In addition, you can enter the validity of the rule in the Rule Importance.

Risk calculation algorithms

The risk calculation mechanism performs the aggregation of the risk field values. We have the following algorithms for calculating the alert risk (Aggregation type):

  • min - returns the minimum value of the risk values from selected fields;
  • max - returns the maximum value of the risk values from selected fields;
  • avg - returns the average of risk values from selected fields;
  • sum - returns the sum of risk values from selected fields;
  • custom - returns the risk value based on your own algorithm

Adding a new risk calculation algorithm

The new algorithm should be added in the ./elastalert_modules/playbook_util.py file in the calculate_risk method. There is a sequence of conditional statements for already defined algorithms:

#aggregate values by risk_key_aggregation for rule
if risk_key_aggregation == "MIN":
    value_agg = min(values)
elif risk_key_aggregation == "MAX":
    value_agg = max(values)
elif risk_key_aggregation == "SUM":
    value_agg = sum(values)
elif risk_key_aggregation == "AVG":
    value_agg = sum(values)/len(values)
else:
    value_agg = max(values)

To add a new algorithm, add a new sequence as shown in the above code:

elif risk_key_aggregation == "AVG":
    value_agg = sum(values)/len(values)
elif risk_key_aggregation == "AAA":
    value_agg = BBB
else:
    value_agg = max(values)

where AAA is the algorithm code, BBB is a risk calculation function.

Using the new algorithm

After adding a new algorithm, it is available in the GUI in the Alert tab.

To use it, add a new rule according to the following steps:

  • Select the custom value in the Aggregation type field;
  • Enter the appropriate value in the Any field, e.g. risk_key_aggregation: AAA

The following figure shows the places where you can call your own algorithm:

../_images/image123.png

Additional modification of the algorithm (weight)

Below is the code in the calcuate_risk method where category values are retrieved - here you can add your weight:

        #start loop by tablicy risk_key
        for k in range(len(risk_keys)):
            risk_key = risk_keys[k]
            logging.info(' >>>>>>>>>>>>>> risk_key: ')
            logging.info(risk_key)
            key_value = lookup_es_key(match, risk_key)
            logging.info(' >>>>>>>>>>>>>> key_value: ')
            logging.info(key_value)
            value = float(self.get_risk_category_value(risk_key, key_value))
            values.append( value )
            logging.info(' >>>>>>>>>>>>>> risk_key values: ')
            logging.info(values)
        #finish loop by tablicy risk_key
        #aggregate values by risk_key_aggregation form rule
        if risk_key_aggregation == "MIN":
            value_agg = min(values)
        elif risk_key_aggregation == "MAX":
            value_agg = max(values)
        elif risk_key_aggregation == "SUM":
            value_agg = sum(values)
        elif risk_key_aggregation == "AVG":
            value_agg = sum(values)/len(values)
        else:
            value_agg = max(values)

Risk_key is the array of selected risk key fields in the GUI. A loop is made on this array and a value is collected for the categories in the line:

value = float(self.get_risk_category_value(risk_key, key_value))

Based on, for example, Risk_key, you can multiply the value of the value field by the appropriate weight. The value field value is then added to the table on which the risk calculation algorithms are executed.

Incidents

The Incident module allows you to handle incidents created by triggered alert rules.

media/media/image154.PNG

Incident handling allows you to perform the following action:

  • Show incident - shows the details that generated the incident;
  • Verify - checks the IP addresses of those responsible for causing an incident with the system reputation lists;
  • Preview - takes you to the Discover module and to the raw document responsible for generating the incident;
  • Update - allows you to change the Incident status or transfer the incident handling to another user. Status list: New, Ongoing, False, Solved.
  • Playbooks - enables handling of Playbooks assigned to an incident;
  • Note - User notes about the incident;

Incident Escalation

The alarm rule definition allows an incident to be escalated if the incident status does not change (from New to Ongoing) after a defined time.

Configuration parameter

  • escalate_users - an array of users who get an email alert about the escalation;
  • escalate_after - the time after which the escalation is triggered;

Example of configuration:

escalate_users:["user2", "user3"] 
escalate_after:
	- hours: 6

Context menu for Alerts::Incidents

In this section, you will find steps and examples that will allow you to add custom items in the actions context menu for the Incidents table. This allows you to expand on the functionalities of the system.

Important file paths
  • /usr/share/kibana/plugins/alerts/public/reactui/incidenttab.js
  • /usr/share/kibana/optimize/bundles/
List element template
{
  name: 'Name of the Action to add',
  icon: 'Name of the chosen icon',
  type: 'icon',
  onClick: this.runActionFunction,
}

You should pick the icon from available choices. After listing ls /usr/share/kibana/built_assets/dlls/icon* if you want to use:

  • icon.editor_align_center-js.bundle.dll.jsThe for icon: you should set:
  • editorAlignCenterUse the same transformation for each icon.
Action function template
runActionFunction = item => {
  // Functino logic to run => information from "item" object can be used here
};

Object “item” contains information about the incident that action was used on.

Steps to add the first custom action to the codebase
  1. Create backup of a file you are about to modify:

    cp /usr/share/kibana/plugins/alerts/public/reactui/incidenttab.js ~/incidenttab.js.bak
    
  2. Working example for the onClick function and action item:

    showMyLocation = () => {
      const opt = {
        enableHighAccuracy: true,
        timeout: 5000,
        maximumAge: 0
      };
      const success = pos => {
        const crd = pos.coords;
        alert(`Your current position is:\nLatitude: ${
          crd.latitude
        }\nLongitude: ${
          crd.longitude
        }\nMore or less ${
          crd.accuracy
        } meters.`);
      }
      const err = err => {
        alert(`ERROR(${err.code}): ${err.message}`);
      }
      navigator.geolocation.getCurrentPosition(success, err, opt);
    }
    
    const customActions = [
      {
        name: 'Show my location',
        icon: 'broom',
        type: 'icon',
        onClick: this.showMyLocation,
      }
    ];
    incidentactions.push(...customActions);
    
  3. The “showMyLocation” function code should be placed in /usr/share/kibana/plugins/alerts/public/reactui/incidenttab.js under:

      showIncidentModal = incident => {
        const updateIncident = incident;
        this.setState({ showIncidentModal: true, updateIncident });
      };
    
      // paste function here
    
      render() {
    
  4. Custom action with a push function should be placed:

          {
            name: 'Note',
            icon: 'pencil',
            type: 'icon',
            isPrimary: true,
            color: 'danger',
            onClick: this.note,
          },
        ];
    
        // insert HERE your action with function 'push'
    
        const incidentcolumns = [
    
  5. For the changes to take effect run below commands on the client serwer (as root or with sudo):

    systemctl stop kibana
    rm -rf /usr/share/kibana/optimize/bundles
    systemctl start kibana
    # verify that process runs correctly afterwards
    journalctl -fu kibana
    # in case of errors restore backup
    
  6. You should now be able to see an additional item in the action context menu in GUI Alerts::Incidents:

    ../_images/image202.png

  7. Running the action will resolve into an alert:

    ../_images/image203.png

Steps to add a second and subsequent custom actions
  1. Execute identicly as in the last section.

  2. Example of a function that uses item object. It will open a new tab in the browser with the default [Alert] dashboard with a custom filter and time set, based on information from the passed item variable:

    openAlertDashboardWithFilter = item => {
      const ruleName = `"${item.rule_name}"`;
      const startT = new Date(item.match_time);
      startT.setHours(0);
      const endT = new Date(item.match_time);
      endT.setHours(24);
      const alertDashboardPath =
        '/app/kibana#/dashboard/777ace50-d200-11e8-98f8-31520a7f9701';
      const timeQuery = 
        `_g=(time:(from:'${startT.toISOString()}',to:'${endT.toISOString()}'))`;
      const nameQuery = 
        `_a=(query:(language:lucene,query:'rule_name:${encodeURIComponent(
          ruleName
        )}'))`;
      const dashboardLocation = `${alertDashboardPath}?${timeQuery}&${nameQuery}`;
      window.open(dashboardLocation, '_blank');
    };
    
  3. Execute identicly as in the last section.

  4. The difference in adding subsequent action is that you append a new one to customActions array variable. The rest should stay the same:

    const customActions = [
      {
        name: 'Show my location',
        icon: 'broom',
        type: 'icon',
        onClick: this.showMyLocation,
      },
      {
        name: 'Show on Dashboard',
        icon: 'arrowRight',
        type: 'icon',
        onClick: this.openAlertDashboardWithFilter,
      },
    ];
    incidentactions.push(...customActions);
    
  5. Execute identicly as in the last section.

  6. Now both actions should be present on the context menu:

    ../_images/image204.png

  7. Using it will open dashboard in new tab:

    ../_images/image205.png

System update

When updating the system your changes might be overwritten. You should in that case save a backup of your changes and restore them after the update with the use of this instruction. Or for instance, with vimdiff compare your changes with the original file:

vimdiff ~/incidenttab.js.bak /usr/share/kibana/plugins/alerts/public/reactui/incidenttab.js

Indicators of compromise (IoC)

Energy Logserver has the Indicators of compromise (IoC) functionality, which is based on the Malware Information Sharing Platform (MISP). IoC observes the logs sent to the system and marks documents if their content is in MISP signature. Based on IoC markings, you can build alert rules or track incident behavior.

Configuration

Bad IP list update

To update bad reputation lists and to create .blacklists index, you have to run following scripts:

/etc/logstash/lists/bin/misp_threat_lists.sh
Scheduling bad IP lists update

This can be done in cron (host with Logstash installed):

0 6 * * * logstash /etc/logstash/lists/bin/misp_threat_lists.sh

or with Kibana Scheduller app (only if Logstash is running on the same host).

  • Prepare script path:
/bin/ln -sfn /etc/logstash/lists/bin /opt/ai/bin/lists
chown logstash:kibana /etc/logstash/lists/
chmod g+w /etc/logstash/lists/
  • Log in to Energy Logserver GUI and go to Scheduler app. Set it up with below options and push “Submit” button:
Name:           MispThreatList
Cron pattern:   0 1 * * *
Command:        lists/misp_threat_lists.sh
Category:       logstash

After a couple of minutes check for blacklists index:

curl -sS -u user:password -XGET '127.0.0.1:9200/_cat/indices/.blacklists?s=index&v'
health status index       uuid                   pri rep docs.count docs.deleted store.size pri.store.size
green  open   .blacklists Mld2Qe2bSRuk2VyKm-KoGg   1   0      76549            0      4.7mb          4.7mb

Calendar function

The alert rule can be executed based on a schedule called Calendar.

Create a calendar

The configuration of the Calendar Function should be done in the definition of the Rule Definition alert using the calendar and scheduler options, in Crontab format.

For example, we want to have an alert that:

  • triggers only on working days from 8:00 to 16:00;
  • only triggers on weekends;
calendar:
  schedule: "* 8-15 * * mon-fri"

If aggregation is used in the alert definition, remember that the aggregation schedule should be the same as the defined calendar.

Windows Events ID repository

+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Category           | Subcategory                   | Event ID | Dashboard                              | Type             | Event Log | Describe                                                                     | Event ID for Windows 2003 |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Object             | Access                        | 561      |  AD DNS Changes                        | Success          | Security  | Handle Allocated                                                                                         |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| System             | Security State Change         | 4608     | [AD] Event Statistics                  | Success          | Security  | Windows is starting up                                                       | 512                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| System             | Security System Extension     | 4610     | [AD] Event Statistics                  | Success          | Security  | An authentication package has been loaded by the Local Security Authority    | 514                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| System             | System Integrity              | 4612     | [AD] Event Statistics                  | Success          | Security  | Internal resources allocated for the queuing of audit                        | 516                       |
|                    |                               |          |                                        |                  |           | messages have been exhausted, leading to the loss of some audits             |                           |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| System             | System Integrity              | 4615     | [AD] Event Statistics                  | Success          | Security  | Invalid use of LPC port                                                      | 519                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| System             | Security State Change         | 4616     | [AD] Servers Audit                     | Success          | Security  | The system time was changed.                                                 | 520                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Logon/Logoff       | Logon                         | 4624     | [AD] Total Logins -> AD Login   Events | Success          | Security  | An account was successfully logged on                                        | 528 , 540                 |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Logon/Logoff       | Logon                         | 4625     | [AD] Inventory, [AD] Failed Logins ->  | Failure          | Security  | An account failed to log on                                                  | 529, 530, 531, 532, 533,  |
|                    |                               |          | AD Failed Login Events                 |                  |           |                                                                              | 534, 535, 536, 537, 539   |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Object Access      | File System, Registry, SAM,   | 4656     | [AD] Removable Device Auditing         | Success, Failure | Security  | A handle to an object was requested                                          | 560                       |
|                    | Handle Manipulation,          |          |                                        |                  |           |                                                                              |                           |
|                    | Other Object Access Events    |          |                                        |                  |           |                                                                              |                           |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Object Access      | File System, Registry,        | 4663     | [AD] Removable Device Auditing         | Success          | Security  | An attempt was made to access an object                                      | 567                       |
|                    | Kernel Object, SAM,           |          |                                        |                  |           |                                                                              |                           |
|                    | Other Object Access Events    |          |                                        |                  |           |                                                                              |                           |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Object Access      | File System, Registry,        | 4670     | [AD] GPO Objects Overview              | Success          | Security  | Permissions on an object were   changed                                                                  |
|                    | Policy Change,                |          |                                        |                  |           |                                                                                                          |
|                    | Authorization Policy Change   |          |                                        |                  |           |                                                                                                          |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4720     | [AD] Accounts Overview ->              | Success          | Security  |  A user account was created                                                  | 624                       |
|                    |                               |          | [AD] A user account was created        |                  |           |                                                                              |                           |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4722     | [AD] Accounts Overview ->              | Success          | Security  | A user account was enabled                                                   | 626                       |
|                    |                               |          | [AD] A user account was disabled       |                  |           |                                                                              |                           |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4723     | [AD] Accounts Overview ->              | Success          | Security  | An attempt was made to change an account's password                          | 627                       |
|                    |                               |          | [AD] An attempt was made               |                  |           |                                                                              |                           |
|                    |                               |          | to change an account's password        |                  |           |                                                                              |                           |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4724     | [AD] Accounts Overview ->              | Success          | Security  | An attempt was made to reset an accounts password                            | 628                       |
|                    |                               |          | [AD] An attempt was made               |                  |           |                                                                              |                           |
|                    |                               |          | to change an account's password        |                  |           |                                                                              |                           |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4725     | [AD] Accounts Overview ->              | Success          | Security  | A user account was disabled                                                  | 629                       |
|                    |                               |          | [AD] A user account was disabled       |                  |           |                                                                              |                           |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4726     | [AD] Accounts Overview ->              | Success          | Security  | A user account was deleted                                                   | 630                       |
|                    |                               |          | [AD] A user account was deleted        |                  |           |                                                                              |                           |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4727     | [AD] Security Group Change History     | Success          | Security  | A security-enabled global group was created                                  | 631                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4728     | [AD] Organizational Unit               | Success          | Security  | A member was added to a security-enabled global group                        | 632                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4729     | [AD] Organizational Unit               | Success          | Security  | A member was removed from a security-enabled global group                    | 633                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4730     | [AD] Organizational Unit               | Success          | Security  | A security-enabled global group was deleted                                  | 634                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4731     | [AD] Organizational Unit               | Success          | Security  | A security-enabled local group was created                                   | 635                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4732     | [AD] Organizational Unit               | Success          | Security  | A member was added to a security-enabled local group                         | 636                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4733     | [AD] Organizational Unit               | Success          | Security  | A member was removed from a security-enabled local group                     | 637                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4734     | [AD] Organizational Unit               | Success          | Security  | A security-enabled local group was deleted                                   | 638                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4738     | [AD] Accounts Overview                 | Success          | Security  | A user account was changed                                                   | 642                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4740     | [AD] Accounts Overview ->              | Success          | Security  | A user account was locked out                                                | 644                       |
|                    |                               |          | AD   Account - Account Locked          |                  |           |                                                                              |                           |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Computer Account Management   | 4741     | [AD] Computer Account Overview         | Success          | Security  | A computer account was created                                               | 645                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Computer Account Management   | 4742     | [AD] Computer Account Overview         | Success          | Security  | A computer account was changed                                               | 646                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Computer Account Management   | 4743     | [AD] Computer Account Overview         | Success          | Security  | A computer account was deleted                                               | 647                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4744     | [AD] Organizational Unit               | Success          | Security  | A security-disabled local group was created                                  | 648                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4746     | [AD] Security Group Change History     | Success          | Security  | A member was added to a security-disabled local group                        | 650                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4747     | [AD] Security Group Change History     | Success          | Security  | A member was removed from a security-disabled local group                    | 651                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4748     | [AD] Organizational Unit               | Success          | Security  | A security-disabled local group was deleted                                  | 652                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4749     | [AD] Organizational Unit               | Success          | Security  | A security-disabled global group was created                                 | 653                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4751     | [AD] Security Group Change History     | Success          | Security  | A member was added to a security-disabled global group                       | 655                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4752     | [AD] Security Group Change History     | Success          | Security  | A member was removed from a security-disabled global group                   | 656                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4753     | [AD] Organizational Unit               | Success          | Security  | A security-disabled global group was deleted                                 | 657                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4754     | [AD] Organizational Unit               | Success          | Security  | A security-enabled universal group was created                               | 658                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4755     | [AD] Organizational Unit               | Success          | Security  | A security-enabled universal group was changed                               | 659                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4756     | [AD] Organizational Unit               | Success          | Security  | A member was added to a security-enabled universal group                     | 660                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4757     | [AD] Organizational Unit               | Success          | Security  | A member was removed from a security-enabled universal group                 | 661                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4758     | [AD] Organizational Unit               | Success          | Security  | A security-enabled universal group was deleted                               | 662                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4759     | [AD] Security Group Change History     | Success          | Security  | A security-disabled universal group was created                              | 663                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4761     | [AD] Security Group Change History     | Success          | Security  | A member was added to a security-disabled universal group                    | 655                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Distribution Group Management | 4762     | [AD] Security Group Change History     | Success          | Security  | A member was removed from a security-disabled universal group                | 666                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | Security Group Management     | 4764     | [AD] Organizational Unit               | Success          | Security  | A groups type was changed                                                    | 668                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4765     | [AD] Accounts Overview ->              | Success          | Security  | SID History was added to an account                                                                      |
|                    |                               |          | AD Account - Account History           |                  |           |                                                                                                          |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+----------------------------------------------------------------------------------------------------------+
| Account Management | User Account Management       | 4766     | [AD] Accounts Overview ->              | Failure          | Security  | An attempt to add SID History to an   account failed                                                     |
|                    |                               |          | AD Account - Account History           |                  |           |                                                                                                          |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4767     | [AD] Accounts Overview                 | Success          | Security  | A computer account was changed                                               | 646                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Logon      | Credential Validation         | 4776     | [AD] Failed Logins                     | Success, Failure | Security  | The domain controller attempted to validate the credentials for an   account | 680, 681                  |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Account Management | User Account Management       | 4781     | [AD] Accounts Overview                 | Success          | Security  | The name of an account was changed                                           | 685                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Directory Service  | Directory Service Changes     | 5136     | [AD] Organizational Unit               | Success          | Security  | A directory service object was modified                                      | 566                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Directory Service  | Directory Service Changes     | 5137     | [AD] Organizational Unit               | Success          | Security  | A directory service object was created                                       | 566                       |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+------------------------------------------------------------------------------+---------------------------+
| Directory Service  | Directory Service Changes     | 5138     | [AD] Organizational Unit               | Success          | Security  | A directory service object was   undeleted                                                               |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+----------------------------------------------------------------------------------------------------------+
| Directory Service  | Directory Service Changes     | 5139     | [AD] Organizational Unit               | Success          | Security  | A directory service object was moved                                                                     |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+----------------------------------------------------------------------------------------------------------+
| Object Access      | File Share                    | 5140     | [AD] File Audit                        | Success          | Security  | A network share object was accessed                                                                      |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+----------------------------------------------------------------------------------------------------------+
| Directory Service  | Directory Service Changes     | 5141     | [AD] Organizational Unit               | Failure          | Security  | A directory service object was   deleted                                                                 |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+----------------------------------------------------------------------------------------------------------+
| Object Access      | File Share                    | 5142     | [AD] File Audit                        | Success          | Security  | A network share object was added.                                                                        |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+----------------------------------------------------------------------------------------------------------+
| Object Access      | Detailed File Share           | 5145     | [AD] File Audit                        | Success, Failure | Security  | A network share object was checked   to see whether client can be granted desired access                 |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+----------------------------------------------------------------------------------------------------------+
| Process Tracking   |  Plug and Play                | 6416     | [AD] Removable Device Auditing         | Success          | Security  |  A new external device was   recognized by the system.                                                   |
+--------------------+-------------------------------+----------+----------------------------------------+------------------+-----------+----------------------------------------------------------------------------------------------------------+

Netflow analyzis

The Logstash collector receives and decodes Network Flows using the provided decoders. During decoding, IP address reputation analysis is performed and the result is added to the event document.

Installation

Install/update logstash codec plugins for netflox and sflow
/usr/share/logstash/bin/logstash-plugin install file:///etc/logstash/plugins/logstash-codec-sflow-2.1.3.gem.zip
/usr/share/logstash/bin/logstash-plugin install file:///etc/logstash/plugins/logstash-codec-netflow-4.2.1.gem.zip
/usr/share/logstash/bin/logstash-plugin install file:///etc/logstash/plugins/logstash-input-udp-3.3.4.gem.zip
/usr/share/logstash/bin/logstash-plugin update logstash-input-tcp
/usr/share/logstash/bin/logstash-plugin update logstash-filter-translate
/usr/share/logstash/bin/logstash-plugin update logstash-filter-geoip
/usr/share/logstash/bin/logstash-plugin update logstash-filter-dns

Configuration

Enable Logstash pipeline
vim /etc/logstash/pipeline.yml

- pipeline.id: flows
  path.config: "/etc/logstash/conf.d/netflow/*.conf"
Elasticsearch template installation
curl -XPUT -H 'Content-Type: application/json' -u logserver:logserver 'http://127.0.0.1:9200/_template/netflow' -d@/etc/logstash/templates.d/netflow-template.json
Importing Kibana dashboards
curl -k -X POST -ulogserver:logserver "https://localhost:5601/api/kibana/dashboards/import" -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d@overview.json
curl -k -X POST -ulogserver:logserver "https://localhost:5601/api/kibana/dashboards/import" -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d@security.json
curl -k -X POST -ulogserver:logserver "https://localhost:5601/api/kibana/dashboards/import" -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d@sources.json
curl -k -X POST -ulogserver:logserver "https://localhost:5601/api/kibana/dashboards/import" -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d@history.json
curl -k -X POST -ulogserver:logserver "https://localhost:5601/api/kibana/dashboards/import" -H 'kbn-xsrf: true' -H 'Content-Type: application/json' -d@destinations.json
Enable reverse dns lookup

To enbled revere DNS lookup set the USE_DNS:false to USE_DNS:true in 13-filter-dns-geoip.conf

Optionally set both dns servers ${DNS_SRV:8.8.8.8} to your local dns

Security rules

MS Windows SIEM rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Windows

Windows - Admin night logon

Alert on Windows login events when detected outside business hours

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:(4624 OR 1200) AND user.role:admin AND event.hour:(20 OR 21 OR 22 OR 23 0 OR 1 OR 2 OR 3)"

2

Windows

Windows - Admin task as user

Alert when admin task is initiated by regular user. Windows event id 4732 is verified towards static admin list. If the user does not belong to admin list AND the event is seen than we generate alert. Static Admin list is a logstash disctionary file that needs to be created manually. During Logstash lookup a field user.role:admin is added to an event. 4732: A member was added to a security-enabled local group

winlogbeat-*

winlogbeat Logstash admin dicstionary lookup file

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4732 AND NOT user.role:admin"

3

Windows

Windows - diff IPs logon

Alert when Windows logon process is detected and two or more different IP addressed are seen in source field. Timeframe is last 15min. Detection is based onevents 4624 or 1200. 4624: An account was successfully logged on 1200: Application token success

winlogbeat-*

winlogbeat

Widnows Security Eventlog

cardinality

max_cardinality: 1 timeframe: minutes: 15 filter: - query_string: query: "event_id:(4624 OR 1200) AND NOT _exists_:user.role AND NOT event_data.IpAddress:\"-\" " query_key: username

4

Windows

Windows - Event service error

Alert when Windows event 1108 is matched 1108: The event logging service encountered an error

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:1108"

5

Windows

Windows - file insufficient privileges

Alert when Windows event 5145 is matched 5145: A network share object was checked to see whether client can be granted desired access Every time a network share object (file or folder) is accessed, event 5145 is logged. If the access is denied at the file share level, it is audited as a failure event. Otherwise, it considered a success. This event is not generated for NTFS access.

winlogbeat-*

winlogbeat

Widnows Security Eventlog

frequency

query_key: "event_data.IpAddress" num_events: 50 timeframe: minutes: 15 filter: - query_string: query: "event_id:5145"

6

Windows

Windows - Kerberos pre-authentication failed

Alert when Windows event 4625 or 4771 is matched 4625: An account failed to log on 4771: Kerberos pre-authentication failed

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4625 OR event_id:4771"

7

Windows

Windows - Logs deleted

Alert when Windows event 1102 OR 104 is matched 1102: The audit log was cleared 104: Event log cleared

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: 'event_desc:"1102 The audit log was cleared"'

8

Windows

Windows - Member added to a security-enabled global group

Alert when Windows event 4728 is matched 4728: A member was added to a security-enabled global group

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4728"

9

Windows

Windows - Member added to a security-enabled local group

Alert when Windows event 4732 is matched 4732: A member was added to a security-enabled local group

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4732"

10

Windows

Windows - Member added to a security-enabled universal group

Alert when Windows event 4756 is matched 4756: A member was added to a security-enabled universal group

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4756"

11

Windows

Windows - New device

Alert when Windows event 6414 is matched 6416: A new external device was recognized by the system

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:6416"

12

Windows

Windows - Package installation

Alert when Windows event 4697 is matched 4697: A service was installed in the system

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4697"

13

Windows

Windows - Password policy change

Alert when Windows event 4739 is matched 4739: Domain Policy was changed

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4739"

14

Windows

Windows - Security log full

Alert when Windows event 1104 is matched 1104: The security Log is now full

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:1104"

15

Windows

Windows - Start up

Alert when Windows event 4608 is matched 4608: Windows is starting up

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4608"

16

Windows

Windows - Account lock

Alert when Windows event 4740 is matched 4740: A User account was Locked out

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4740"

17

Windows

Windows - Security local group was changed

Alert when Windows event 4735 is matched 4735: A security-enabled local group was changed

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4735"

18

Windows

Windows - Reset password attempt

Alert when Windows event 4724 is matched 4724: An attempt was made to reset an accounts password

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4724"

19

Windows

Windows - Code integrity changed

Alert when Windows event 5038 is matched 5038: Detected an invalid image hash of a file Information: Code Integrity is a feature that improves the security of the operating system by validating the integrity of a driver or system file each time it is loaded into memory. Code Integrity detects whether an unsigned driver or system file is being loaded into the kernel, or whether a system file has been modified by malicious software that is being run by a user account with administrative permissions. On x64-based versions of the operating system, kernel-mode drivers must be digitally signed. The event logs the following information:

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:5038"

20

Windows

Windows - Application error

Alert when Windows event 1000 is matched 1000: Application error

winlogbeat-*

winlogbeat

Widnows Application Eventlog

any

filter: - query_string: query: "event_id:1000"

21

Windows

Windows - Application hang

Alert when Windows event 1001 OR 1002 is matched 1001: Application fault bucket 1002: Application hang

winlogbeat-*

winlogbeat

Widnows Application Eventlog

any

filter: - query_string: query: "event_id:1002 OR event_id:1001"

22

Windows

Windows - Audit policy changed

Alert when Windows event 4719 is matched 4719: System audit policy was changed

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:4719"

23

Windows

Windows - Eventlog service stopped

Alert when Windows event 6005 is matched 6005: Eventlog service stopped

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:6005"

24

Windows

Windows - New service installed

Alert when Windows event 7045 OR 4697 is matched 7045,4697: A service was installed in the system

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:7045 OR event_id:4697"

25

Windows

Windows - Driver loaded

Alert when Windows event 6 is matched 6: Driver loaded The driver loaded events provides information about a driver being loaded on the system. The configured hashes are provided as well as signature information. The signature is created asynchronously for performance reasons and indicates if the file was removed after loading.

winlogbeat-*

winlogbeat

Widnows System Eventlog

any

filter: - query_string: query: "event_id:6"

26

Windows

Windows - Firewall rule modified

Alert when Windows event 2005 is matched 2005: A Rule has been modified in the Windows firewall Exception List

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: 'event_desc:"4947 A change has been made to Windows Firewall exception list. A rule was modified"'

27

Windows

Windows - Firewall rule add

Alert when Windows event 2004 is matched 2004: A firewall rule has been added

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:2004"

28

Windows

Windows - Firewall rule deleted

Alert when Windows event 2006 or 2033 or 2009 is matched 2006,2033,2009: Firewall rule deleted

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: "event_id:2006 OR event_id:2033 OR event_id:2009"

29

Windows

Windows - System has been shutdown

This event is written when an application causes the system to restart, or when the user initiates a restart or shutdown by clicking Start or pressing CTRL+ALT+DELETE, and then clicking Shut Down.

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: 'event_id:"1074"'

30

Windows

Windows - The system time was changed

The system time has been changed. The event describes the old and new time.

winlogbeat-*

winlogbeat

Widnows Security Eventlog

any

filter: - query_string: query: 'event_id:"4616"'

Network Switch SIEM rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Switch

Switch - Blocked by LACP

ports: port <nr> is Blocked by LACP

syslog-*

syslog

any

filter: - query_string: query: “message:"Blocked by LACP"”

2

Switch

Switch - Blocked by STP

ports: port <nr> is Blocked by STP

syslog-*

syslog

any

filter: - query_string: query: “message:"Blocked by STP"”

3

Switch

Switch - Port state changed

Port state changed to down or up

syslog-*

syslog

any

filter: - query_string: query: “message:"changed state to"”

4

Switch

Switch - Configured from console

Configurations changes from console

syslog-*

syslog

any

filter: - query_string: query: “message:"Configured from console"”

5

Switch

Switch - High collision or drop rate

syslog-*

syslog

any

filter: - query_string: query: “message:"High collision or drop rate"”

6

Switch

Switch - Invalid login

auth: Invalid user name/password on SSH session

syslog-*

syslog

any

filter: - query_string: query: “message:"auth: Invalid user name/password on SSH session"”

7

Switch

Switch - Logged to switch

syslog-*

syslog

any

filter: - query_string: query: “message:" mgr: SME SSH from"”

8

Switch

Switch - Port is offline

ports: port <nr> is now off-line

syslog-*

syslog

any

filter: - query_string: query: “message:" is now off-line"”

9

Switch

Switch - Port is online

ports: port <nr> is now on-line

syslog-*

syslog

any

filter: - query_string: query: “message:" is now on-line"”

Cisco ASA devices SIEM rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Cisco ASA

Cisco ASA - Device interface administratively up

Device interface administratively up

syslog-*

syslog from Cisco ASA devices

any

filter: - query_string: query: ‘cisco.id:”%ASA-4-411003”’

2

Cisco ASA

Cisco ASA - Device configuration has been changed or reloaded

Device configuration has been changed or reloaded

syslog-*

syslog from Cisco ASA devices

any

filter: - query_string: query: ‘cisco.id:(“%ASA-5-111007” OR “%ASA-5-111008”)’

3

Cisco ASA

Cisco ASA - Device interface administratively down

Device interface administratively down

syslog-*

syslog from Cisco ASA devices

any

filter: - query_string: query: ‘cisco.id:”%ASA-4-411004”’

4

Cisco ASA

Cisco ASA - Device line protocol on Interface changed state to down

Device line protocol on Interface changed state to down

syslog-*

syslog from Cisco ASA devices

any

filter: - query_string: query: ‘cisco.id:”%ASA-4-411002”’

5

Cisco ASA

Cisco ASA - Device line protocol on Interface changed state to up

Device line protocol on Interface changed state to up

syslog-*

syslog from Cisco ASA devices

any

filter: - query_string: query: ‘cisco.id:”%ASA-4-411001”’

6

Cisco ASA

Cisco ASA - Device user executed shutdown

Device user executed shutdown

syslog-*

syslog from Cisco ASA devices

any

filter: - query_string: query: ‘cisco.id:”%ASA-5-111010”’

7

Cisco ASA

Cisco ASA - Multiple VPN authentication failed

Multiple VPN authentication failed

syslog-*

syslog from Cisco ASA devices

frequency

query_key: “src.ip” num_events: 10 timeframe: minutes: 240 filter: - query_string: query: “cisco.id:"%ASA-6-113005"”

8

Cisco ASA

Cisco ASA - VPN authentication failed

VPN authentication failed

syslog-*

syslog from Cisco ASA devices

any

filter: - query_string: query: “cisco.id:"%ASA-6-113005"”

9

Cisco ASA

Cisco ASA - VPN authentication successful

VPN authentication successful

syslog-*

syslog from Cisco ASA devices

any

filter: - query_string: query: “cisco.id:"%ASA-6-113004"”

10

Cisco ASA

Cisco ASA - VPN user locked out

VPN user locked out

syslog-*

syslog from Cisco ASA devices

any

filter: - query_string: query: “cisco.id:"%ASA-6-113006"”

Linux Mail SIEM rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Mail Linux

Mail - Flood Connect from

Connection flood, possible DDOS attack

syslog-*

syslog

frequency

filter: - query_string: query: “message:"connect from"” query_key: host timeframe: hours: 1 num_events: 50

2

Mail Linux

Mail - SASL LOGIN authentication failed

User authentication failure

syslog-*

syslog

frequency

filter: - query_string: query: “message:"SASL LOGIN authentication failed: authentication failure"” query_key: host timeframe: hours: 1 num_events: 30

3

Mail Linux

Mail - Sender rejected

Sender rejected

syslog-*

syslog

frequency

filter: - query_string: query: “message:"NOQUEUE: reject: RCPT from"” query_key: host timeframe: hours: 1 num_events: 20

Linux DNS Bind SIEM Rules

1 DNS DNS - Anomaly in geographic region DNS anomaly detection in geographic region filebeat-* filebeat spike query_key: geoip.country_code2 threshold_ref: 500 spike_height: 3 spike_type: “up” timeframe: minutes: 10 filter: - query_string: query: “NOT geoip.country_code2:(US OR PL OR NL OR IE OR DE OR FR OR GB OR SK OR AT OR CZ OR NO OR AU OR DK OR FI OR ES OR LT OR BE OR CH) AND _exists_:geoip.country_code2 AND NOT domain:(*.outlook.com OR *.pool.ntp.org)”

2

DNS

DNS - Domain requests

Domain requests

filebeat-*

filebeat

frequency

query_key: “domain” num_events: 1000 timeframe: minutes: 5 filter: - query_string: query: “NOT domain:(/.*localdomain/) AND _exists_:domain”

3

DNS

DNS - Domain requests by source IP

Domain requests by source IP

filebeat-*

filebeat

cadrinality

query_key: “src_ip” cardinality_field: “domain” max_cardinality: 3000 timeframe: minutes: 10 filter: - query_string: query: “(NOT domain:(/.*.arpa/ OR /.*localdomain/ OR /.*office365.com/) AND _exists_:domain”

4

DNS

DNS - Resolved domain matches IOC IP blacklist

Resolved domain matches IOC IP blacklist

filebeat-*

filebeat

blacklist-ioc

compare_key: “domain_ip” blacklist-ioc: - “!yaml /etc/logstash/lists/misp_ip.yml”

Fortigate Devices SIEM rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

FortiOS 6.x

Fortigate virus

fortigate*

FortiOS with Antivirus, IPS, Fortisandbox modules, Logstash KV filter, default-base-template

syslog from Forti devices

Any

filter: - query_string: query: “subtype:virus and action:blocked”

2

FortiOS 6.x

Fortigate http server attack by destination IP

fortigate*

FortiOS with waf, IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

frequency

query_key: “dst_ip” num_events: 10 timeframe: hours: 1 filter: - query_string: query: “level:alert and subtype:ips and action:dropped and profile:protect_http_server”

3

FortiOS 6.x

Fortigate forward deny by source IP

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

frequency

query_key: “src_ip” num_events: 250 timeframe: hours: 1 filter: - query_string: query: “subtype:forward AND action:deny”

4

FortiOS 6.x

Fortigate failed login

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

Any

filter: - query_string: query: “action:login and status:failed”

5

FortiOS 6.x

Fortigate failed login same source

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

frequency

query_key: “src_ip” num_events: 18 timeframe: minutes: 45 filter: - query_string: query: “action:login and status:failed”

6

FortiOS 6.x

Fortigate device configuration changed

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

any

filter: - query_string: query:”"Configuration is changed in the admin session"”

7

FortiOS 6.x

Fortigate unknown tunneling setting

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

any

filter: - query_string: query:”"http_decoder: HTTP.Unknown.Tunnelling"”

8

FortiOS 6.x

Fortigate multiple tunneling same source

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

frequency

query_key: “src_ip” num_events: 18 timeframe: minutes: 45 filter: - query_string: query: “"http_decoder: HTTP.Unknown.Tunnelling"”

9

FortiOS 6.x

Fortigate firewall configuration changed

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

any

filter: - query_string: query:”action:Edit”

10

FortiOS 6.x

Fortigate SSL VPN login fail

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

any

filter: - query_string: query:”ssl-login-fail”

11

FortiOS 6.x

Fortigate Multiple SSL VPN login failed same source

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

frequency

query_key: “src_ip” num_events: 18 timeframe: minutes: 45 filter: - query_string: query: “ssl-login-fail”

12

FortiOS 6.x

Fortigate suspicious traffic

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

any

filter: - query_string: query:”type:traffic AND status:high”

13

FortiOS 6.x

Fortigate suspicious traffic same source

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

frequency

query_key: “src_ip” num_events: 18 timeframe: minutes: 45 filter: - query_string: query: “type:traffic AND status:high”

14

FortiOS 6.x

Fortigate URL blocked

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

any

filter: - query_string: query:”action:blocked AND status:warning”

15

FortiOS 6.x

Fortigate multiple URL blocked same source

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

frequency

query_key: “src_ip” num_events: 18 timeframe: minutes: 45 filter: - query_string: query: “action:blocked AND status:warning”

16

FortiOS 6.x

Fortigate attack detected

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

any

filter: - query_string: query:”attack AND action:detected”

17

FortiOS 6.x

Fortigate attack dropped

fortigate*

FortiOS with IPS, modules, Logstash KV filter, default-base-template

syslog from Forti devices

any

filter: - query_string: query:”attack AND action:dropped”

Linux Apache SIEM rules

Table caption
Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Apache

HTTP 1xx peak

Response status 1xx

httpd*

Apache logs

spike

threshold_cur: 100 timeframe: hours: 2 spike_height: 5 spike_type: “up” filter: - query: query_string: query: “response.status.code:1*” - type: value: “_doc”

2

Apache

HTTP 2xx responses for unwanted URLs

Requests for URLS like: - /phpMyAdmin, /wpadmin, /wp-login.php, /.env, /admin, /owa/auth/logon.aspx, /api, /license.txt, /api/v1/pods, /solr/admin/info/system, /backup/, /admin/config.php, /dana-na, /dbadmin/, /myadmin/, /mysql/, /php-my-admin/, /sqlmanager/, /mysqlmanager/, config.php

httpd*

Apache logs

blacklist

compare_key: http.request ignore_null: true blacklist: - /phpMyAdmin - /wpadmin - /wp-login.php - /.env - /admin - /owa/auth/logon.aspx - /api - /license.txt - /api/v1/pods - /solr/admin/info/system - /backup/ - /admin/config.php - /dana-na - /dbadmin/ - /myadmin/ - /mysql/ - /php-my-admin/ - /sqlmanager/ - /mysqlmanager/ - config.php

3

Apache

HTTP 2xx spike

httpd*

Apache logs

spike

threshold_cur: 100 timeframe: hours: 2 spike_height: 5 spike_type: “up” filter: - query: query_string: query: “response.status.code:2*” - type: value: “_doc”

4

Apache

HTTP 3x spike

Response status 3xx

httpd*

Apache logs

any

threshold_cur: 100 timeframe: hours: 2 spike_height: 5 spike_type: “up” filter: - query: query_string: query: “response.status.code:3*” - type: value: “_doc”

5

Apache

HTTP 4xx spike

Response status 4xx

httpd*

Apache logs

spike

threshold_cur: 100 timeframe: hours: 2 spike_height: 5 spike_type: “up” filter: - query: query_string: query: “response.status.code:4*” - type: value: “_doc”

6

Apache

HTTP 5xx spike

Response status 5xx

httpd*

Apache logs

spike

threshold_cur: 100 timeframe: hours: 2 spike_height: 5 spike_type: “up” filter: - query: query_string: query: “response.status.code:5*” - type: value: “_doc”

RedHat / CentOS system SIEM rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Linux

Linux - Group Change

syslog-*

Syslog

any

filter: - query_string: query: “message:"added by root to group"”

2

Linux

Linux - Group Created

syslog-*

Syslog

any

filter: - query_string: query: “message:"new group: "”

3

Linux

Linux - Group Removed

syslog-*

Syslog

any

filter: - query_string: query: “message:"removed group: " OR message:"removed shadow group: "”

4

Linux

Linux - Interrupted Login

syslog-*

Syslog

any

filter: - query_string: query: “message:"Connection closed by"”

5

Linux

Linux -Login Failure

syslog-*

Syslog

any

filter: - query_string: query: “message:"Failed password for"”

6

Linux

Linux - Login Success

syslog-*

Syslog

any

filter: - query_string: query: “message:"Accepted password for"”

7

Linux

Linux - Out of Memory

syslog-*

Syslog

any

filter: - query_string: query: “message:"killed process"”

8

Linux

Linux - Password Change

syslog-*

Syslog

any

filter: - query_string: query: “message:"password changed"”

9

Linux

Linux - Process Segfaults

syslog-*

Syslog

any

filter: - query_string: query: “message:segfault”

10

Linux

Linux - Process Traps

syslog-*

Syslog

any

filter: - query_string: query: “message:traps”

11

Linux

Linux - Service Started

syslog-*

Syslog

any

filter: - query_string: query: “message:Started”

12

Linux

Linux - Service Stopped

syslog-*

Syslog

any

filter: - query_string: query: “message:Stopped”

13

Linux

Linux - Software Erased

syslog-*

Syslog

any

filter: - query_string: query: “message:"Erased: "”

14

Linux

Linux - Software Installed

syslog-*

Syslog

any

filter: - query_string: query: “message:"Installed: "”

15

Linux

Linux - Software Updated

syslog-*

Syslog

any

filter: - query_string: query: “message:"Updated: "”

16

Linux

Linux - User Created

syslog-*

Syslog

any

filter: - query_string: query: “message:"new user: "”

17

Linux

Linux - User Removed

syslog-*

Syslog

any

filter: - query_string: query: “message:"delete user"”

Checkpoint devices SIEM rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

VPN-1 & FireWall-1

Checkpoint - Drop a packet by source IP

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Frequency

query_key: “src” num_events: 10 timeframe: hours: 1 filter: - query_string: query: “action:drop” use_count_query: true doc_type: doc

2

VPN-1 & FireWall-1

Checkpoint - Reject by source IP

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Frequency

query_key: “src” num_events: 10 timeframe: hours: 1 filter: - query_string: query: “action:reject” use_count_query: true doc_type: doc

3

VPN-1 & FireWall-1

Checkpoint - User login

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Any

query_key: “user” filter: - query_string: query: “auth_status:"Successful Login"” use_count_query: true doc_type: doc

4

VPN-1 & FireWall-1

Checkpoint - Failed Login

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Any

query_key: “user” filter: - query_string: query: “auth_status:"Failed Login"” use_count_query: true doc_type: doc

5

VPN-1 & FireWall-1

Checkpoint - Application Block by user

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Frequency

query_key: “user” num_events: 10 timeframe: hours: 1 filter: - query_string: query: “action:block AND product:"Application Control"” use_count_query: true doc_type: doc

6

VPN-1 & FireWall-1

Checkpoint - URL Block by user

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Frequency

query_key: “user” num_events: 10 timeframe: hours: 1 filter: - query_string: query: “action:block AND product:"URL Filtering"” use_count_query: true doc_type: doc

7

VPN-1 & FireWall-1

Checkpoint - Block action with user

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Any

query_key: “user” filter: - query_string: query: “action:block” use_count_query: true doc_type: doc

8

VPN-1 & FireWall-1

Checkpoint - Encryption keys were created

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Any

filter: - query_string: query: “action:keyinst” use_count_query: true doc_type: doc

9

VPN-1 & FireWall-1

Checkpoint - Connection was detected by Interspect

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Any

filter: - query_string: query: “action:detect” use_count_query: true doc_type: doc

10

VPN-1 & FireWall-1

Checkpoint - Connection was subject to a configured protections

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Any

filter: - query_string: query: “action:inspect” use_count_query: true doc_type: doc

11

VPN-1 & FireWall-1

Checkpoint - Connection with source IP was quarantined

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Any

query_key: “src” filter: - query_string: query: “action:quarantine” use_count_query: true doc_type: doc

12

VPN-1 & FireWall-1

Checkpoint - Malicious code in the connection with source IP was replaced

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Any

query_key: “src” filter: - query_string: query: “action:"Replace Malicious code"” use_count_query: true doc_type: doc

13

VPN-1 & FireWall-1

Checkpoint - Connection with source IP was routed through the gateway acting as a central hub

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Any

query_key: “src” filter: - query_string: query: “action:"VPN routing"” use_count_query: true doc_type: doc

14

VPN-1 & FireWall-1

Checkpoint - Security event with user was monitored

checkpoint*

Checkpoint devices, fw1-grabber ( https://github.com/certego/fw1-loggrabber )

Checkpoint firewall, OPSEC Log Export APIs (LEA)

Frequency

query_key: “user” num_events: 10 timeframe: hours: 1 filter: - query_string: query: “action:Monitored” use_count_query: true doc_type: doc

Cisco ESA devices SIEM rule

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Cisco ESA

ESA - Attachments exceeded the URL scan

syslog-*

Cisco ESA

any

filter: - query_string: query: ‘message:”attachments exceeded the URL scan”’

2

Cisco ESA

ESA - Extraction Failure

syslog-*

Cisco ESA

any

filter: - query_string: query: ‘message:”Extraction Failure”’

3

Cisco ESA

ESA - Failed to expand URL

syslog-*

Cisco ESA

any

filter: - query_string: query: ‘message:”Failed to expand URL”’

4

Cisco ESA

ESA - Invalid host configured

syslog-*

Cisco ESA

any

filter: - query_string: query: ‘message:”Invalid host configured”’

5

Cisco ESA

ESA - Marked unscannable due to RFC Violation

syslog-*

Cisco ESA

any

filter: - query_string: query: ‘message:”was marked unscannable due to RFC Violation”’

6

Cisco ESA

ESA - Message was not scanned for Sender Domain Reputation

syslog-*

Cisco ESA

any

filter: - query_string: query: ‘message:”Message was not scanned for Sender Domain Reputation”’

7

Cisco ESA

ESA - URL Reputation Rule

syslog-*

Cisco ESA

any

filter: - query_string: query: ‘message:”URL Reputation Rule”’

Forcepoint devices SIEM rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Forcepoint HIGH

All high alerts

syslog-dlp*

any

alert_text_type: alert_text_only alert_text: “Forcepoint HIGH alert\n\n When: {}\n Analyzed by: {}\n User name: {}\n Source: {}\nDestination: {}\n\n{}\n” alert_text_args: - timestamp_timezone - Analyzed_by - user - Source - Destination - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “Severity:HIGH”

2

Forcepoint MEDIUM

All medium alerts

syslog-dlp*

any

alert_text_type: alert_text_only alert_text: “Forcepoint MEDIUM alert\n\n When: {}\n Analyzed by: {}\n User name: {}\n Source: {}\nDestination: {}\n\n{}\n” alert_text_args: - timestamp_timezone - Analyzed_by - user - Source - Destination - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “Severity:MEDIUM”

3

Forcepoint LOW

All low alerts

syslog-dlp*

any

alert_text_type: alert_text_only alert_text: “Forcepoint LOW alert\n\n When: {}\n Analyzed by: {}\n User name: {}\n Source: {}\nDestination: {}\n\n{}\n” alert_text_args: - timestamp_timezone - Analyzed_by - user - Source - Destination - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “Severity:LOW”

4

Forcepoint blocked email

Email was blocked by forcepoint

syslog-dlp*

any

alert_text_type: alert_text_only alert_text: “Email blocked\n\n When: {}\n Analyzed by: {}\n File name: {}\n Source: {}\nDestination: {}\n\n{}\n” alert_text_args: - timestamp_timezone - Analyzed_by - File_Name - Source - Destination - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “Action:Blocked and Channel:Endpoint Email”

5

Forcepoint removables

Forcepoint blocked data transfer to removeable device

syslog-dlp*

any

alert_text_type: alert_text_only alert_text: “Data transfer to removable device blocked\n\n When: {}\n Analyzed by: {}\n File name: {}\n Source: {}\nDestination: {}\n\n{}\n” alert_text_args: - timestamp_timezone - Analyzed_by - File_Name - Source - Destination - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “Action:Blocked and Channel:Endpoint Removable Media”

Oracle Database Engine SIEM rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Oracle DB

Oracle - Allocate memory ORA-00090

Failed to allocate memory for cluster database

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00090”

2

Oracle DB

Oracle logon denied ORA-12317

logon to database (link name string)

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-12317”

3

Oracle DB

Oracle credential failed ORA-12638

Credential retrieval failed

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 num_events: 10 filter: - term: oracle.code: “ora-12638”

4

Oracle DB

Oracle client internal error ORA-12643

Client received internal error from server

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 num_events: 10 filter: - term: oracle.code: “ora-12643”

5

Oracle DB

ORA-00018: maximum number of sessions exceeded

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00018”

6

Oracle DB

ORA-00019: maximum number of session licenses exceeded

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00019”

7

Oracle DB

ORA-00020: maximum number of processes (string) exceeded

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00020”

8

Oracle DB

ORA-00024: logins from more than one process not allowed in single-process mode

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00024”

9

Oracle DB

ORA-00025: failed to allocate string ( out of memory )

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00025”

10

Oracle DB

ORA-00055: maximum number of DML locks exceeded

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00055”

11

Oracle DB

ORA-00057: maximum number of temporary table locks exceeded

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00057”

12

Oracle DB

ORA-00059: maximum number of DB_FILES exceeded

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00059”

13

Oracle DB

Oracle - Deadlocks ORA - 0060

Deadlock detected while waiting for resource

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00060”

14

Oracle DB

ORA-00063: maximum number of log files exceeded

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00063”

15

Oracle DB

ORA-00064: object is too large to allocate on this O/S

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 filter: - term: oracle.code: “ora-00064”

16

Oracle DB

ORA-12670: Incorrect role password

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 num_events: 10 filter: - term: oracle.code: “ora-12670”

17

Oracle DB

ORA-12672: Database logon failure

oracle-*

Filebeat

Oracle Alert Log

any

timeframe: minutes: 15 num_events: 10 filter: - term: oracle.code: “ora-12672”

Paloalto devices SIEM rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Paloalto - Configuration changes failed

Config changes Failed

paloalto-*

frequency

timeframe: minutes: 15 num_events: 10 filter: - term: pan.type: CONFIG - term: result: Failed

2

Paloalto - Flood detected

Flood detected via a Zone Protection profile

paloalto-*

frequency

timeframe: minutes: 15 num_events: 10 filter: - term: pan.type: THREAT - term: pan.subtype: flood

3

Paloalto - Scan detected

Scan detected via a Zone Protection profile

paloalto-*

frequency

timeframe: minutes: 15 num_events: 10 filter: - term: pan.type: THREAT - term: pan.subtype: scan

4

Paloalto - Spyware detected

Spyware detected via an Anti-Spyware profile

paloalto-*

frequency

timeframe: minutes: 15 num_events: 10 filter: - term: pan.type: THREAT - term: pan.subtype: spyware

5

Paloalto - Unauthorized configuration changed

Attepmted Unauthorized configuration changes

paloalto-*

frequency

timeframe: minutes: 15 num_events: 10 filter: - term: pan.type: CONFIG - term: result: Unathorized

6

Paloalto - Virus detected

Virus detected via an Antivirus profile.

paloalto-*

frequency

timeframe: minutes: 15 num_events: 10 filter: - term: pan.type: THREAT - terms: pan.subtype: [ “virus”, “wildfire-virus” ]

7

Paloalto - Vulnerability exploit detected

Vulnerability exploit detected via a Vulnerability Protection profile

paloalto-*

frequency

timeframe: minutes: 15 num_events: 10 filter: - term: pan.type: THREAT - term: pan.subtype: vulnerability

Microsoft Exchange SIEM rules

Table caption
Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

MS Exchange

Exchange - Increased amount of incoming emails

exchange-*

spike

metric_agg_key: “exchange.network-message-id” metric_agg_type: “cardinality” doc_type: “_doc” max_threshold: 10 buffer_time: minutes: 1 filter: - query_string: query: “exchange.sender-address:*.company.com AND exchange.event-id:SEND AND exchange.message-subject:*” query_key: [“exchange.message-subject-agg”, “exchange.sender-address”]

2

MS Exchange

Exchange - Internal sender sent email to public provider

exchange-*

whitelist

metric_agg_key: “exchange.network-message-id” metric_agg_type: “cardinality” doc_type: “_doc” max_threshold: 10 buffer_time: minutes: 1 filter: - query_string: query: “NOT exchange.sender-address:(*@company.com) AND exchange.event-id:SEND AND exchange.message-subject:* AND NOT exchange.recipient-address:public@company.com” query_key: [“exchange.message-subject-agg”, “exchange.sender-address”]

3

MS Exchange

Exchange - Internal sender sent ethe same title to many recipients

exchange-*

metric_aggregation

filter: - query_string: query: “NOT exchange.recipient-address:public@company.com AND NOT exchange.sender-address:(*@company.com) AND exchange.event-id:SEND AND exchange.data.atch:[1 TO *] AND _exists_:exchange AND exchange.message-subject:(/.*invoice.*/ OR /.*payment.*/ OR /.*faktur.*/)” query_key: [“exchange.sender-address”]

4

MS Exchange

Exchange - Received email with banned title

exchange-*

any

threshold_ref: 5 timeframe: days: 1 spike_height: 3 spike_type: “up” alert_on_new_data: false use_count_query: true doc_type: _doc query_key: [“exchange.sender-address”] filter: - query_string: query: “NOT exchange.event-id:(DEFER OR RECEIVE OR AGENTINFO) AND _exists_:exchange”

5

MS Exchange

Exchange - The same title to many recipients

exchange-*

metric_aggregation

compare_key: “exchange.sender-address” ignore_null: true filter: - query_string: query: “NOT exchange.recipient-address:(*@company.com) AND _exists_:exchange.recipient-address AND exchange.event-id:AGENTINFO AND NOT exchange.sender-address:(bok@* OR postmaster@*) AND exchange.data.atch:[1 TO *] AND exchange.recipient-count:1 AND exchange.recipient-address:(*@gmail.com OR *@wp.pl OR *@o2.pl OR *@interia.pl OR *@op.pl OR *@onet.pl OR *@vp.pl OR *@tlen.pl OR *@onet.eu OR *@poczta.fm OR *@interia.eu OR *@hotmail.com OR *@gazeta.pl OR *@yahoo.com OR *@icloud.com OR *@outlook.com OR *@autograf.pl OR *@neostrada.pl OR *@vialex.pl OR *@go2.pl OR *@buziaczek.pl OR *@yahoo.pl OR *@post.pl OR *@wp.eu OR *@me.com OR *@yahoo.co.uk OR *@onet.com.pl OR *@tt.com.pl OR *@spoko.pl OR *@amorki.pl OR *@7dots.pl OR *@googlemail.com OR *@gmx.de OR *@upcpoczta.pl OR *@live.com OR *@piatka.pl OR *@opoczta.pl OR *@web.de OR *@protonmail.com OR *@poczta.pl OR *@hot.pl OR *@mail.ru OR *@yahoo.de OR *@gmail.pl OR *@02.pl OR *@int.pl OR *@adres.pl OR *@10g.pl OR *@ymail.com OR *@data.pl OR *@aol.com OR *@gmial.com OR *@hotmail.co.uk)” whitelist: - allowed@example.com - allowed@example2.com

Juniper Devices SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Junos-IDS

Juniper - IDS attact detection

junos*

JunOS devices with IDS module

Syslog from Juniper devices

Any

filter: - query_string: query: “_exists_:attack-name” include: - attack-name

2

Junos-IDS

Junos - RT flow session deny

junos*

JunOS devices SRX, RT Fflow

Syslog from Juniper devices

Any

filter: - query_string: query: “category:RT_FLOW AND subcat:RT_FLOW_SESSION_DENY” include: - srcip - dstip

3

Junos-IDS

Junos - RT flow reassemble fail

junos*

JunOS devices SRX, RT Fflow

Syslog from Juniper devices

Any

filter: - query_string: query: “category:RT_FLOW AND subcat:FLOW_REASSEMBLE_FAIL” include: - srcip - dstip

4

Junos-IDS

Junos - RT flow mcast rpf fail

junos*

JunOS devices SRX, RT Fflow

Syslog from Juniper devices

Any

filter: - query_string: query: “category:RT_FLOW AND subcat:FLOW_MCAST_RPF_FAIL” include: - srcip - dstip

Fudo SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Fudo - General Error

fudo*

http://download.wheelsystems.com/documentation/fudo/4_0/online_help/en/reference/en/log_messages.html

Syslog FUDO

Any

filter: - query_string: query: “syslog_serverity:error” include: - fudo_message

2

Fudo - Failed to authenticate using password

fudo*

http://download.wheelsystems.com/documentation/fudo/4_0/online_help/en/reference/en/log_messages.html

Syslog FUDO

Any

filter: - query_string: query: “fudo_code:FSE0634” include: - fudo_user

3

Fudo - Unable to establish connection

fudo*

http://download.wheelsystems.com/documentation/fudo/4_0/online_help/en/reference/en/log_messages.html

Syslog FUDO

Any

filter: - query_string: query: “fudo_code:FSE0378” include: - fudo_connection - fudo_login

4

Fudo - Authentication timeout

fudo*

http://download.wheelsystems.com/documentation/fudo/4_0/online_help/en/reference/en/log_messages.html

Syslog FUDO

Any

filter: - query_string: query: “fudo_code:FUE0081”

Squid SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Squid

Squid - Configuration file changed

Modyfing squid.conf file

syslog-*

Audit module

syslog

any

filter: - query_string: query: ‘message:”File /etc/squid/squid.conf checksum changed.”’

2

Squid

Squid - Cannot open HTTP port

Cannot open HTTP Port

squid-*

squid

any

filter: - query_string: query: ‘message:”Cannot open HTTP Port”’

3

Squid

Squid - Unauthorized connection

Unauthorized connection, blocked website entry

squid-*

squid

any

filter: - query_string: query: ‘squid_request_status:”TCP_DENIED/403”’

4

Squid

Squid - Proxy server stopped

Service stopped

syslog-*

syslog

any

filter: - query_string: query: ‘message:”Stopped Squid caching proxy.”’

5

Squid

Squid - Proxy server started

Service started

syslog-*

syslog

any

filter: - query_string: query: ‘message:”Started Squid caching proxy.”’

6

Squid

Squid - Invalid request

Invalid request

squid-*

squid

any

filter: - query_string: query: ‘squid_request_status:”error:invalid-request”’

McAfee SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Squid

Squid - Configuration file changed

Modyfing squid.conf file

syslog-*

Audit module

syslog

any

filter: - query_string: query: ‘message:”File /etc/squid/squid.conf checksum changed.”’

2

Squid

Squid - Cannot open HTTP port

Cannot open HTTP Port

squid-*

squid

any

filter: - query_string: query: ‘message:”Cannot open HTTP Port”’

3

Squid

Squid - Unauthorized connection

Unauthorized connection, blocked website entry

squid-*

squid

any

filter: - query_string: query: ‘squid_request_status:”TCP_DENIED/403”’

4

Squid

Squid - Proxy server stopped

Service stopped

syslog-*

syslog

any

filter: - query_string: query: ‘message:”Stopped Squid caching proxy.”’

5

Squid

Squid - Proxy server started

Service started

syslog-*

syslog

any

filter: - query_string: query: ‘message:”Started Squid caching proxy.”’

6

Squid

Squid - Invalid request

Invalid request

squid-*

squid

any

filter: - query_string: query: ‘squid_request_status:”error:invalid-request”’

Microsoft DNS Server SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1.

WINDOWS DNS

WIN DNS - Format Error

Format error; DNS server did not understand the update request

prod-win-dns-*

any

timeframe: minutes: 15 filter: - term: dns.result: SERVFAIL

2.

WINDOWS DNS

WIN DNS - DNS server internal error

DNS server encountered an internal error, such as a forwarding timeout

prod-win-dns-*

any

timeframe: - minutes: 15 filter: - term: dns.result: FORMERR

3.

WINDOWS DNS

WIN DNS - DNS refuses to perform the update

DNS server refuses to perform the update

prod-win-dns-*

any

“timeframe: - minutes: 15 filter: - term: dns.result: REFUSED

4.

WINDOWS DNS

WIN DNS - DNS Zone Deleted

DNS Zone delete

prod-win-dns-*

any

timeframe: minutes: 15 filter: - term: event.id: 513

5.

WINDOWS DNS

WIN DNS - DNS Record Deleted

DNS Record Delete

prod-win-dns-*

any

timeframe: minutes: 15 filter: - term: event.id: 516

6.

WINDOWS DNS

WIN DNS - DNS Node Deleted

DNS Node Delete

prod-win-dns-*

any

timeframe: minutes: 15 filter: - term: event.id: 518

7.

WINDOWS DNS

WIN DNS - DNS Remove Trust Point

DNS Remove trust point

prod-win-dns-*

any

timeframe: minutes: 15 filter: - term: event.id: 546

8.

WINDOWS DNS

WIN DNS - DNS Restart Server

Restart Server

prod-win-dns-*

any

timeframe: minutes: 15 filter: - term: event.id: 548

9.

WINDOWS DNS

WIN DNS - DNS Response failure

Response Failure

prod-win-dns-*

frequency

timeframe: minutes: 5 num_events: 20 filter: - term: event.id: 258

10.

WINDOWS DNS

WIN DNS - DNS Ignored Query

Ignored Query

prod-win-dns-*

frequency

timeframe: minutes: 5 num_events: 20 filter: - term: event.id: 259

11.

WINDOWS DNS

WIN DNS - DNS Recursive query timeout

Recursive query timeout

prod-win-dns-*

frequency

timeframe: minutes: 5 num_events: 20 filter: - term: event.id: 262

Microsoft DHCP SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Windows DHCP

MS DHCP low disk space

The log was temporarily paused due to low disk space.

prod-win-dhcp-*

any

timeframe: minutes: 15 filter: - term: dhcp.event.id: 02

2

Windows DHCP

MS DHCP lease denied

A lease was denied

prod-win-dhcp-*

frequency

timeframe: minutes: 15 num_events: 10 filter: - terms: dhcp.event.id: [ “15”, “16” ] include: - dhcp.event.id - src.ip - src.mac - dhcp.event.descr summary_table_field: - src.ip - src.mac - dhcp.event.descr

3

Windows DHCP

MS DHCP update denied

DNS update failed

prod-win-dhcp-*

frequency

timeframe: minutes: 15 num_events: 50 filter: - term: dhcp.event.id: 31

4

Windows DHCP

MS DHCP Data Corruption

Detecting DHCP Jet Data Corruption

prod-win-dhcp-*

any

timeframe: minutes: 15 filter: - term: dhcp.event.id: 1014

5

Windows DHCP

MS DHCP service shutting down

The DHCP service is shutting down due to the following error

prod-win-dhcp-*

any

timeframe: minutes: 15 filter: - term: dhcp.event.id: 1008

6

Windows DHCP

MS DHCP Service Failed to restore database

The DHCP service failed to restore the database

prod-win-dhcp-*

any

timeframe: minutes: 15 filter: - term: dhcp.event.id: 1018

7

Windows DHCP

MS DHCP Service Failed to restore registry

The DHCP service failed to restore the DHCP registry configuration

prod-win-dhcp-*

any

timeframe: minutes: 15 filter: - term: dhcp.event.id: 1019

8

Windows DHCP

MS DHCP Can not find domain

The DHCP/BINL service on the local machine encountered an error while trying to find the domain of the local machine

prod-win-dhcp-*

frequency

timeframe: minutes: 15 filter: - term: dhcp.event.id: 1049

9

Windows DHCP

MS DHCP Network Failure

The DHCP/BINL service on the local machine encountered a network error

prod-win-dhcp-*

frequency

timeframe: minutes: 15 filter: - term: dhcp.event.id: 1050

10

Windows DHCP

MS DHCP - There are no IP addresses available for lease

There are no IP addresses available for lease in the scope or superscope

prod-win-dhcp-*

any

timeframe: minutes: 15 filter: - term: dhcp.event.id: 1063

Linux DHCP Server SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

DHCP Linux

DHCP Linux - Too many requests

Too many DHCP requests

syslog-*

Linux DHCP Server / Syslog

frequency

query_key: “src_mac” num_events: 30 timeframe: minutes: 1 filter: - query_string: query: “DHCPREQUEST” use_count_query: true doc_type: doc

2

DHCP Linux

DHCP Linux - IP already assigned

IP is already assigned to another client

syslog-*

Linux DHCP Server / Syslog

any

filter: - query_string: query: “DHCPNAK”

3

DHCP Linux

DHCP Linux - Discover flood

DHCP Discover flood

syslog-*

Linux DHCP Server / Syslog

frequency

query_key: “src_mac” num_events: 30 timeframe: minutes: 1 filter: - query_string: query: “DHCPDISCOVER” use_count_query: true doc_type: doc

Cisco VPN devices SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Cisco IOS - Cisco VPN Concentrator

CiscoVPN - VPN authentication failed

Jan 8 09:10:37 vpn.example.com 11504 01/08/2007 09:10:37.780 SEV=3 AUTH/5 RPT=124 192.168.0.1 Authentication rejected: Reason = Unspecified handle = 805, server = auth.example.com, user = testuser, domain = <not specified>

cisco*

any

filter: - query_string: query: “cisco.id:("AUTH\/5" OR "AUTH\/9" OR "IKE\/167" OR "PPP\/9" OR "SSH\/33" OR "PSH\/23")”

2

Cisco IOS - Cisco VPN Concentrator

CiscoVPN - VPN authentication successful

jw.

cisco*

any

filter: - query_string: query: “cisco.id:("IKE\/52")”

3

Cisco IOS - Cisco VPN Concentrator

CiscoVPN - VPN Admin authentication successful

jw.

cisco*

any

filter: - query_string: query: “cisco.id:("HTTP\/47" OR "SSH\/16")”

4

Cisco IOS - Cisco VPN Concentrator

CiscoVPN - Multiple VPN authentication failures

jw.

cisco*

frequency

query_key: “src.ip” num_events: 10 timeframe: minutes: 240 filter: - query_string: query: “cisco.id:("AUTH\/5" OR "AUTH\/9" OR "IKE\/167" OR "PPP\/9" OR "SSH\/33" OR "PSH\/23")”

5

Cisco IOS - Cisco ASA

Cisco ASA - VPN authentication failed

jw.

cisco*

any

filter: - query_string: query: “cisco.id:"\%ASA-6-113005"”

6

Cisco IOS - Cisco ASA

Cisco ASA - VPN authentication successful

jw.

cisco*

any

filter: - query_string: query: “cisco.id:"\%ASA-6-113004"”

7

Cisco IOS - Cisco ASA

Cisco ASA - VPN user locked out

jw.

cisco*

any

filter: - query_string: query: “cisco.id:"\%ASA-6-113006"”

8

Cisco IOS - Cisco ASA

Cisco ASA - Multiple VPN authentication failed

jw.

cisco*

frequency

query_key: “src.ip” num_events: 10 timeframe: minutes: 240 filter: - query_string: query: “cisco.id:"\%ASA-6-113005"”

Netflow SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Netflow - DNS traffic abnormal

stream-*

spike

threshold_ref: 1000 spike_height: 4 spike_type: up timeframe: hours: 2 filter: - query: query_string: query: “netflow.dst.port:53” query_key: [netflow.src.ip] use_count_query: true doc_type: “doc”

2

Netflow - ICMP larger than 64b

stream-*

any

filter: - query: query_string: query: “netflow.protocol: 1 AND netflow.packet_bytes:>64” query_key: “netflow.dst_addr” use_count_query: true doc_type: “doc”

3

Netflow - Port scan

stream-*

cardinality

timeframe: minutes: 5 max_cardinality: 100 query_key: [netflow.src.ip, netflow.dst.ip] cardinality_field: “netflow.dst.port” filter: - query: query_string: query: “_exists_:(netflow.dst.ip AND netflow.src.ip) NOT netflow.dst.port: (443 OR 80)” aggregation: minutes: 5 aggregation_key: netflow.src.ip

4

Netflow - SMB traffic

stream-*

any

filter: - query: query_string: query: “netflow.dst.port:(137 OR 138 OR 445 OR 139)” query_key: “netflow.src.ip” use_count_query: true doc_type: “doc”

5

Netflow - Too many req to port 161

stream-*

frequency

num_events: 60 timeframe: minutes: 1 filter: - query: query_string: query: “netflow.dst.port:161” query_key: “netflow.src.ip” use_count_query: true doc_type: “doc”

6

Netflow - Too many req to port 25

stream-*

frequency

num_events: 60 timeframe: minutes: 1 filter: - query: query_string: query: “netflow.dst.port:25” query_key: “netflow.src.ip” use_count_query: true doc_type: “doc”

7

Netflow - Too many req to port 53

stream-*

frequency

num_events: 120 timeframe: minutes: 1 filter: - query: query_string: query: “netflow.dst.port:53” query_key: “netflow.src.ip” use_count_query: true doc_type: “doc”

8

Netflow – Multiple connections from source badip

stream-*

frequency

num_events: 10 timeframe: minutes: 5 filter: - query: query_string: query: “netflow.src.badip:true” query_key: “netflow.src.ip” use_count_query: true doc_type: “doc”

9

Netflow – Multiple connections to destination badip

stream-*

frequency

num_events: 10 timeframe: minutes: 5 filter: - query: query_string: query: “netflow.dst.badip:true” query_key: “netflow.dst.ip” use_count_query: true doc_type: “doc”

MikroTik devices SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

All system errors

any

alert_text_type: alert_text_only alert_text: “System error\n\n When: {}\n Device IP: {}\n From: {}\n\n{}\n” alert_text_args: - timestamp_timezone - host - login.ip - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “topic2:error and topic3:critical”

2

All errors connected with logins to the administrative interface of the device eg wrong password or wrong login name

any

alert_text_type: alert_text_only alert_text: “Login error\n\n When: {}\n Device IP: {}\n From: {}\n by: {}\n to account: {}\n\n{}\n” alert_text_args: - timestamp_timezone - host - login.ip - login.method - user - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “topic2:error and topic3:critical and login.status:login failure”

3

All errors connected with wireless eg device is banned on access list, or device had poor signal on AP and was disconected

any

alert_text_type: alert_text_only alert_text: “Wifi auth issue\n\n When: {}\n Device IP: {}\n Interface: {}\n MAC: {}\n ACL info: {}\n\n{}\n” alert_text_args: - timestamp_timezone - host - interface - wlan.mac - wlan.ACL - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “wlan.status:reject or wlan.action:banned”

4

Dhcp offering fail

any

alert_text_type: alert_text_only alert_text: “Dhcp offering fail\n\n When: {}\n Client lease: {}\n for MAC: {}\n to MAC: {}\n\n{}\n” alert_text_args: - timestamp_timezone - dhcp.ip - dhcp.mac - dhcp.mac2 - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “dhcp.status:without success”

Microsoft SQL Server SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

Logon errors, alert any

Rule definition alert_text_type: alert_text_only alert_text: “Logon error\n\n When: {}\n Error code: {}\n Severity: {}\n\n{}\n” alert_text_args: - timestamp_timezone - mssql.error.code - mssql.error.severity - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “mssql.error.code:* and mssql.error.severity:*”

2

Login failed for users, alert any

alert_text_type: alert_text_only alert_text: “Login failed\n\n When: {}\n User login: {}\n Reason: {}\n Client: {}\n\n{}\n” alert_text_args: - timestamp_timezone - mssql.login.user - mssql.error.reason - mssql.error.client - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “mssql.login.status:failed and mssql.login.user:*”

3

server is going down, alert any

alert_text_type: alert_text_only alert_text: “Server is going down\n\n When: {}\n\n{}\n” alert_text_args: - timestamp_timezone - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “mssql.server.status:shutdown”

4

NET stopped, alert any

alert_text_type: alert_text_only alert_text: “NET Framework runtime has been stopped.\n\n When: {}\n\n{}\n” alert_text_args: - timestamp_timezone - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “mssql.net.status:stopped”

5

Database Mirroring stopped, alert any

alert_text_type: alert_text_only alert_text: “Database Mirroring endpoint is in stopped state.\n\n When: {}\n\n{}\n” alert_text_args: - timestamp_timezone - kibana_link use_kibana4_dashboard: “link do saved search” kibana4_start_timedelta: minutes: 5 kibana4_end_timedelta: minutes: 0 filter: - query_string: query: “mssql.db.status:stopped”

Postgress SQL SIEM Rules

Nr.

Architecture/Application

Rule Name

Description

Index name

Requirements

Source

Rule type

Rule definition

1

PostgreSQL

PostgresSQL - New user created

postgres-*

Filebeat, Logstash, PostgreSQL

pg_log

any

filter: - query_string: query: ‘message:”LOG: CREATE USER”’

2

PostgreSQL

PostgresSQL - User selected database

postgres-*

Filebeat, Logstash, PostgreSQL

pg_log

any

filter: - query_string: query: ‘message:”LOG: SELECT d.datname FROM pg_catalog.pg_database”’

3

PostgreSQL

PostgresSQL - User password changed

postgres-*

Filebeat, Logstash, PostgreSQL

pg_log

any

filter: - query_string: query: ‘message:”ALTER USER WITH PASSWORD”’

4

PostgreSQL

PostgreSQL - Multiple authentication failures

postgres-*

Filebeat, Logstash, PostgreSQL

pg_log

frequency

query_key: “src_ip” num_events: 5 timeframe: seconds: 25 filter: - query_string: query: ‘message:”FATAL: password authentication failed for user”’ use_count_query: true doc_type: doc

5

PostgreSQL

PostgreSQL - Granted all privileges to user

postgres-*

Filebeat, Logstash, PostgreSQL

pg_log

any

filter: - query_string: query: ‘message:”LOG: GRANT ALL PRIVILEGES ON”’

6

PostgreSQL

PostgresSQL - User displayed users table

User displayed users table

postgres-*

Filebeat, Logstash, PostgreSQL

pg_log

any

filter: - query_string: query: ‘message:”LOG: SELECT r.rolname FROM pg_catalog.pg_roles”’

7

PostgreSQL

PostgresSQL - New database created

postgres-*

Filebeat, Logstash, PostgreSQL

pg_log

any

filter: - query_string: query: ‘message:”LOG: CREATE DATABASE”’

8

PostgreSQL

PostgresSQL - Database shutdown

postgres-*

Filebeat, Logstash, PostgreSQL

pg_log

any

filter: - query_string: query: ‘message:”LOG: database system was shut down at”’

9

PostgreSQL

PostgresSQL - New role created

postgres-*

Filebeat, Logstash, PostgreSQL

pg_log

any

filter: - query_string: query: ‘message:”LOG: CREATE ROLE”’

10

PostgreSQL

PostgresSQL - User deleted

postgres-*

Filebeat, Logstash, PostgreSQL

pg_log

any

filter: - query_string: query: ‘message:”LOG: DROP USER”’

MySQL SIEM Rules

Nr. Architecture/Application Rule Name Description Index name Requirements Source Rule type Rule definition

1

MySQL

MySQL - User created

mysql-*

Filebeat, Logstash, MySQL

mysql-general.log

any

filter: - query_string: query: ‘message:”CREATE USER”’

2

MySQL

MySQL - User selected database

mysql-*

Filebeat, Logstash, MySQL

mysql-general.log

any

filter: - query_string: query: ‘message:”Query show databases”’

3

MySQL

MySQL - Table dropped

mysql-*

Filebeat, Logstash, MySQL

mysql-general.log

any

filter: - query_string: query: ‘message:”Query drop table”’

4

MySQL

MySQL - User password changed

mysql-*

Filebeat, Logstash, MySQL

mysql-general.log

any

filter: - query_string: query: ‘message:”UPDATE mysql.user SET Password=PASSWORD” OR message:”SET PASSWORD FOR” OR message:”ALTER USER”’

5

MySQL

MySQL - Multiple authentication failures

mysql-*

Filebeat, Logstash, MySQL

mysql-general.log

frequency

query_key: “src_ip” num_events: 5 timeframe: seconds: 25 filter: - query_string: query: ‘message:”Access denied for user”’ use_count_query: true doc_type: doc

6

MySQL

MySQL - All priviliges to user granted

mysql-*

Filebeat, Logstash, MySQL

mysql-general.log

any

filter: - query_string: query: ‘message:”GRANT ALL PRIVILEGES ON”’

7

MySQL

MySQL - User displayed users table

User displayed users table

mysql-*

Filebeat, Logstash, MySQL

mysql-general.log

any

filter: - query_string: query: ‘message:”Query select * from user”’

8

MySQL

MySQL - New database created

mysql-*

Filebeat, Logstash, MySQL

mysql-general.log

any

filter: - query_string: query: ‘message:”Query create database”’

9

MySQL

MySQL - New table created

mysql-*

Filebeat, Logstash, MySQL

mysql-general.log

any

filter: - query_string: query: ‘message:”Query create table”’

# Alert Module #

Energy Logserver allows you to create alerts, i.e. monitoring queries. These are constant queries that run in the background and when the conditions specified in the alert are met, the specify action is taken.

../_images/image91.PNG

For example, if you want to know when more than 20 „status:500” response code from on our homepage appear within an one hour, then we create an alert that check the number of occurrences of the „status:500” query for a specific index every 5 minutes. If the condition we are interested in is met, we send an action in the form of sending a message to our e-mail address. In the action, you can also set the launch of any script.

Wazuh

Energy Logserver, through its built-in vulnerability detection module called Wazuh and the use of best practices defined in the CIS, allows to audit monitored environment for security vulnerabilities, misconfigurations, or outdated software versions. File Integrity Monitoring functionality allows for detailed monitoring and alerting of unauthorized access attempts to most sensitive data.

SIEM Plan is a solution that provides a ready-made set of tools for compliance regulations such as CIS, PCI DSS, GDPR, NIST 800-53, ISO 27001.The system enables mapping of detected threats to Mitre ATT&CK tactics. By integrating with the MISP Energy Logserver, allows to get real-time information about new threats on the network by downloading the latest IoC lists.

To configure the Wazuh agents see the Configuration section.

Tenable and Qualisis Integration

Qualys Guard and Tenable.sc is vulnerability management tools, which make a scan systems and environments to find vulnerabilities. The Logstash collector can connect to Qualys Guard API or Tenable.sc API to get results of the vulnerability scan and send it to the Elasticsarch index. Reporting and analysis of the collected data is carried out using a prepared dashboard [Vulnerability] Overview Tenable and [Vulnerability] Overview Tenable

../_images/image166.png

../_images/image166.png

To configure Qulays or Tenable.sc see the Configuration section.