Community

Blog Events Webinars Tutorials Forum
  1. Blog
  2. Events
  3. Webinars
  4. Tutorials
  5. Forum
Create Account
×
Community Blog The Computing Conference 2018 Workshop: Log Based Security Analysis

The Computing Conference 2018 Workshop: Log Based Security Analysis

We will show you how to use Alibaba Cloud Log Service to collect logs from the ground up for identifying and analyzing suspicious operations in real time.

Today, more and more enterprises are focusing on establishing log-based security analysis and protection systems. We will show you how to use the Log Service to collect massive logs from the ground up, and how to filter and identify suspicious operations and analyze them in real time to further enable security dashboard and visualization. The practices cover several typical security analysis scenarios.

1

By following this article, you should be able to understand how to use the Log Service for threat identification and analysis in typical security scenarios, including:

  1. Host brute-force attack and abnormal logon identification
  2. Database SQL attack and export identification
  3. Web service CC attack behavior analysis

We will then briefly talk about how you can build a security dashboard to help you visualize the threat analysis.

Log Service Initial Preparation

You will need to have a valid Alibaba Cloud account.

Head to the Log Service Console, and create a project. For our example, we have created a project called "yq201809". You should be able to visit your project directly using the URL https://sls.console.aliyun.com/#/project/yq201809/categoryList

You will need to create a Logstore for Log Service to work. We have called this "yq-demo". To query the page of the prepared logstore yq-demo, click "Search":

2

Scenario 1: Host Brute-Force Attack and Abnormal Logon Identification

View logon logs

Enter the following command on the query page to see the host logon logs:

__topic__ : winlogin

The log structure is as follows:

__topic__:  winlogin         // log topic: the logon log is winlogin
client_ip:  197.210.226.56   // the IP address of the logon client
result:  success             // logon result: success/fail
target:  host4.test.com      // the host being logged on to
target_type:  server         // machine type: server/normal
type:  ssh                   // logon method:ssh/rdp
user:  admin                 // logon account

Brute-force attack identification

Task: Identify brute-force attacks through SQL correlation analysis

Logic: There is a successful logon to a specific server after consecutive failed logon attempts

Key steps:

Enter the following query analysis statement:

__topic__: winlogin and target_type: server  | select date_format(max_by(__time__, __time__), '%m-%d %H:%i:%s') as "×î½üʱ¼ä",  target as "·þÎñÆ÷", 4 as "Æƽâ´ÎÊý", count(1) as "ʼþ´ÎÊý" FROM  (select __time__, target, result, lag(result, 1, 'δ֪') over ( PARTITION  by target order by __time__) as pre1, lag(result, 2, 'δ֪') over ( PARTITION  by target order by __time__) as pre2 , lag(result, 3, 'δ֪') over ( PARTITION  by target order by __time__) as pre3 , lag(result, 4, 'δ֪') over ( PARTITION  by target order by __time__) as pre4 from log) where result='success' and pre1='fail' and pre1='fail' and pre2='fail' and pre3='fail' and pre4='fail' group by target

This statement is roughly divided into three parts:

Filter: select logon logs where the target type is server:

__topic__: winlogin and target_type: server

Add context to each log via the window function lag: whether previous logon attempts succeeded:

__topic__: winlogin and target_type: server  | select __time__, target, result, lag(result, 1, 'δ֪') over ( PARTITION  by target order by __time__) as pre1, lag(result, 2, 'δ֪') over ( PARTITION  by target order by __time__) as pre2 , lag(result, 3, 'δ֪') over ( PARTITION  by target order by __time__) as pre3 , lag(result, 4, 'δ֪') over ( PARTITION  by target order by __time__) as pre4 from log

Through subqueries and grouping, find all logon logs where current logon attempt succeeded after previous attempts failed, and use the window functions max_by, etc., to record the most and the least recent times:

__topic__: winlogin and target_type: server  | select date_format(max_by(__time__, __time__), '%m-%d %H:%i:%s') as "×î½üʱ¼ä",  target as "·þÎñÆ÷", 4 as "Æƽâ´ÎÊý", count(1) as "ʼþ´ÎÊý" FROM  (select __time__, target, result, lag(result, 1, 'δ֪') over ( PARTITION  by target order by __time__) as pre1, lag(result, 2, 'δ֪') over ( PARTITION  by target order by __time__) as pre2 , lag(result, 3, 'δ֪') over ( PARTITION  by target order by __time__) as pre3 , lag(result, 4, 'δ֪') over ( PARTITION  by target order by __time__) as pre4 from log) where result='success' and pre1='fail' and pre1='fail' and pre2='fail' and pre3='fail' and pre4='fail' group by target

Select "1 hour" for the "Time" to see a list of brute-force attack events:

3

Select the form and click "Add to Dashboard": select the existing dashboard My security dashboard and name it "Brute-force attack events".

Reference: See the pre-configured "quick query": brute-force attacks.

4

Identify abnormal logons and configure IP drill down

Task: Analyze the logon addresses through the SQL geographic functions and the security functions to identify abnormal logons. In addition, configure the drill down to further view the logon IP addresses.

Logic: In general, the server has been logged into from China or the United States (through VPN). There are some logons with IP addresses from other countries, and the IP addresses are infected.

Key steps:

Enter the following query analysis statement:

__topic__: winlogin and result: success and target_type: server | select date_format(min_by(__time__, __time__), '%m-%d %H:%i:%s') as "×îÔçʱ¼ä", date_format(max_by(__time__, __time__), '%m-%d %H:%i:%s') as "×î½üʱ¼ä", target as "·þÎñÆ÷", count(1) as "µÇ¼´ÎÊý", arbitrary(client_ip) as "¿ÉÒÉ¿Í»§¶Ë£¨ÑùÀý£©" , '²é¿´IPÐÅÏ¢' as "²Ù×÷" where ip_to_country(client_ip) <> 'Öйú' and security_check_ip(client_ip) = 1 group by target order by "µÇ¼´ÎÊý" DESC

Select "1 hour" for the "Time" to see a list of abnormal logon events:

Configure drill down: Click "+" next to the "Operation" list, open "Drill Down", select "Custom HTTP Link", and configure as www.ip138.com/ips138.asp?ip=${suspicious client (example)}&action=2, as follows:

5

Select the form and click "Add to Dashboard": select the existing dashboard My security dashboard and name it "Abnormal logon events".

Reference: See the pre-configured "quick query": abnormal logons.

6

Refine logon security dashboard

Task: Build a logon dashboard with a map chart, add potential risks to the dashboard, and refine the layout.

Key steps:

Enter the following query analysis statement (double click to select all and copy):

__topic__: winlogin and result: success | select ip_to_country(client_ip) as country, count(1) as "³É¹¦µÇ¼´ÎÊý" group by  country

Select "1 hour" for the "Time" to see the distribution of logon events based on the source country, and select "World Map" under "Map" in "Chart Type":

7

Select the form and click "Add to Dashboard": select the existing dashboard My security dashboard and name it "Logon event distribution".

Go to "My Security Dashboard" in the "View" and click the "Edit" to adjust the layout:

8

Reference: See the pre-configured "Dashboard": Scenario 1:...

9

Scenario 2: Database SQL Attack and Export Identification

View logon logs

Enter the following command on the query page to see the SQL execution logs in MySQL:

__topic__ : mysql

The log structure is as follows:

__topic__:  mysql      // log topic: the SQL execution log is for MySQL
sql:  SELECT * FROM accounts WHERE id >= 20000 
         and id < 30000 limit 10000   // executed SQL statement
target:  db1.abc.com   // database server
db_name:  crm_system   // database
table_name:  accounts  // table
sql_type:  select      // SQL statement type: select, update, delete, etc.
user:  op_user1        // SQL statement executor
client_ip:  1.2.3.4    // IP address of the client for the execution
affected_rows:  10000  // affected function, for example, the returned rows
response_time:  1210   // response time of the execution (ms)

Identify SQL attacks

Task: Identify SQL attacks through SQL parsing

Logic: A hacker executes a series of SQL statements through an acquired database account (or through SQL injection) to drop a virus to the server disk. (for example, dumpfile into)

Key steps:

Enter the following query analysis statement (double click to select all and copy):

__topic__: mysql | select date_format(__time__, '%m-%d %H:%i:%s') as "ʱ¼ä", 'ÎļþдÈë' as "¹¥»÷ÀàÐÍ", client_ip as "¿Í»§¶Ë", concat(db_name, table_name) as "Êý¾Ý¿â", target as "·þÎñÆ÷", sql as "¹¥»÷SQL"  where regexp_like(sql, '(?i).+into\s+dumpfile\b.+')

Select "1 hour" for the "Time" to see a list of SQL attack events:

10

Select the form and click "Add to Dashboard": select the existing dashboard My security dashboard and name it "SQL attack events".

Reference: See the pre-configured "quick query": SQL attacks.

Identify database export

Task: Identify database export through SQL statistics

Logic: A hacker retrieves important tables (such as account and order information) by acquiring a database account and executing a series of SELECT statements.

Key steps:

Enter the following query analysis statement (double click to select all and copy):

__topic__: mysql and sql_type: select | SELECT date_format(min_by(__time__, __time__), '%m-%d %H:%i:%s') as "ÍϿ⿪ʼʱ¼ä", max_by(__time__, __time__)-min_by(__time__, __time__) as "ÍÏ¿âºÄʱ(Ãë)", db_name as "Êý¾Ý¿â", table_name as "±í¸ñ",  sum(affected_rows) as "ÍÏ¿âÐÐÊý", arbitrary(sql) as "ÍÏ¿âSQL(ÑùÀý)",  arbitrary(client_ip) as "¿Í»§¶Ë(ÑùÀý)" group by db_name, table_name HAVING  "ÍÏ¿âÐÐÊý" > 200

Select "1 hour" for the "Time" to see a list of database export events:

11

Select the form and click "Add to Dashboard": select the existing dashboard My security dashboard and name it "Database export events".

Reference: See the pre-configured "quick query": Database export.

Build database security dashboard

Task: Adjust the layout of [My Security Dashboard] in combination with the previous rules

Reference: See the pre-configured dashboard: Scenario 2:...

Scenario 3: Web Service CC Attack Behavior Analysis

View logon logs

Enter the following command on the query page to see the Anti-DDoS Pro access and attack logs:

__topic__ : ddos_access_log

See Anti-DDoS Pro Log format.

Identify CC attack rules

Task: View CC attack target sites and features

Logic: CC attack logs can be obtained through cc_blocks > 0

Reference: You can refer to the prepared Scenario 3:... DDoS operation center and Access center dashboard.

View DDoS security dashboard

View the existing dashboard, modify and adjust the DDoS security dashboard:

12

Preview:

13

14

DDoS Security Log Service Anti-DDoS Cybersecurity Computing Conference
0 2 1
Share on

Read next post:

Integrating Alibaba Cloud Log Service with Splunk

wjo1212

2 posts | 0 followers

You may also like

Comments

wjo1212

2 posts | 0 followers

Related Products

More Posts by wjo1212

See All