Pages

Showing posts with label Logs. Show all posts
Showing posts with label Logs. Show all posts

DoS command on kali linux

1. Hping3

hping3 should be used to…

- Traceroute/ping/probe hosts behind a firewall that blocks attempts using the standard utilities.
-  Perform the idle scan (now implemented in nmap with an easy user interface).
- Test firewalling rules.
- Test IDSes.
- Exploit known vulnerabilties of TCP/IP stacks.
- Networking research.
- Learn TCP/IP (hping was used in networking courses AFAIK).
- Write real applications related to TCP/IP testing and security.
- Automated firewalling tests.
- Proof of concept exploits.
- Networking and security research when there is the need to emulate complex TCP/IP behaviour.
- Prototype IDS systems.
- Simple to use networking utilities with Tk interface.

DoS using hping3 with random source IP


Let me explain the syntax’s used in this command:
  1. hping3 = Name of the application binary.
  2. -c 100000 = Number of packets to send.
  3. -d 120 = Size of each packet that was sent to target machine.
  4. -S = I am sending SYN packets only.
  5. -w 64 = TCP window size.
  6. -p 21 = Destination port (21 being FTP port). You can use any port here.
  7. --flood = Sending packets as fast as possible, without taking care to show incoming replies. Flood mode.
  8. --rand-source = Using Random Source IP Addresses. You can also use -a or –spoof to hide hostnames. See MAN page below.
  9. www.hping3testsite.com = Destination IP address or target machines IP address. You can also use a website name here. In my case resolves to 127.0.0.1 (as entered in /etc/hosts file)
===> Logs on Graylog server : 
Another command:
-Simple SYN flood - DoS 
#hping3 -S --flood -V domain/IP
- Simple SYN flood with spoofed IP - DoS
#hping3 -S -P -U --flood -V --rand-source domain/ip

2. nping
Command: #nping -help
#nping --tcp-connect -rate=90000 -c 900000 -q domain/ip
tham khảo: www.blackmoreops.com

Configure Screen and sending traffic logs from SRX to Remote Syslog Server


1. Configure Screen.
root@iLab.SRX# show security screen 
ids-option Test-01 {
    icmp {
        ip-sweep;
        fragment;
        large;
        flood;
        ping-death;
    }
    ip {
        bad-option;
        record-route-option;
        timestamp-option;
        security-option;
        stream-option;
        spoofing;
        source-route-option;
        loose-source-route-option;
        strict-source-route-option;
        unknown-protocol;
        block-frag;
        tear-drop;
    }
    tcp {
        syn-fin;
        fin-no-ack;
        tcp-no-flag;
        syn-frag;
        port-scan;
        syn-ack-ack-proxy;
        syn-flood; 
        land;
        winnuke;
        tcp-sweep;
    }
    udp {
        flood;
        udp-sweep;
        port-scan;
    }
}
- Add Screen to Zones
root@iLab.SRX# set security zones security-zone Internet screen Test-01 

 2. Configure sending security logs to remote syslog server
root@iLab.SRX# show security log                          
mode stream;
format sd-syslog;
source-address 192.168.221.11;
stream ilab-logs {
    format sd-syslog;
    category all;
    host {
        192.168.221.135;
        port 5014;
    }
}


3. Test  by using Kali to attack to capture logs

Reference: 
1. How to forward traffic logs from an SRX device to STRM (https://kb.juniper.net)
- Set the security log mode:
root@iLab.SRX# set security log mode stream

 -Set the security log format to sd-sylog, which is for structured syslog format:

root@iLab.SRX# set security log format sd-syslog

- Set the security log source-address, which is the SRX IP address expected by the STRM device. Here we are using the IP address of an egress interface ge-0/0/0 on the SRX:
root@iLab.SRX#set security log source-address 192.168.221.11

-Give the security log stream a name and category. In this case, the name is 'securitylog', and the 'all' category is specified.
root@iLab.SRX#set security log stream securitylog category all

-Set the host IP address of the STRM or Syslog server device that will receive the traffic logs. 
root@iLab.SRX#set security log stream securitylog host 192.168.221.135

-Also, set the host port of the STRM device that will collect the traffic logs.  This is the port the STRM device is configured to listen on.  The default syslog port is 5014.
root@iLab.SRX# set security log stream securitylog host port 5014

2. Understanding Screens options on SRX Series devices (https://www.juniper.net)
https://www.juniper.net/documentation/en_US/junos/topics/concept/understanding-screen-options-srx-series.html

Cấu hình syslog trên SRX đẩy về Remote logs server


Chú ý: khi đẩy log về thì trước tiên phải đồng bộ time
Configure sending to a Remote Syslog Server
root@iLab.SRX# show system syslog
user * {
    any emergency;
}
host 192.168.221.135 {
    any any;
    authorization any;
    port 5014;
    source-address 192.168.221.11;
    structured-data;
}
file messages {
    any any;
    authorization info;
}
file interactive-commands {
    interactive-commands any;
}

Configure push logs from linux to graylog-server



Step1: Configure input on Graylog-web
Step 2: Configure on centos: /etc/rsyslog.conf
$template GRAYLOGRFC5424,"<%PRI%>%PROTOCOL-VERSION% %TIMESTAMP:::date-rfc3339% %HOSTNAME% %APP-NAME% %PROCID% %MSGID% %STRUCTURED-DATA% %msg%\n"
*.*     @192.168.221.135:5014

How to install and configure Graylog on centos 6

Các bước thực hiện cài đặt:

********************Install java*****************************
yum install java-1.8.0-openjdk-headless.x86_64

*******************Install mongodb****************************
path: /etc/yum.repos.d/mongodb-org-3.2.repo

 [mongodb-org-3.2]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/3.2/x86_64/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-3.2.asc

 yum install mongodb-org

 chkconfig mongod on
service mongod start
*********************Install Elasticsearch*******************
rpm --import https://packages.elastic.co/GPG-KEY-elasticsearch
path: /etc/yum.repos.d/elasticsearch.repo

 [elasticsearch-2.x]
name=Elasticsearch repository for 2.x packages
baseurl=https://packages.elastic.co/elasticsearch/2.x/centos
gpgcheck=1
gpgkey=https://packages.elastic.co/GPG-KEY-elasticsearch
enabled=1

 yum install elasticsearch

 file configure: /etc/elasticsearch/elasticsearch.yml

 chkconfig elasticsearch on
service elasticsearch start

 ***************************Install Graylog*********************
rpm -Uvh https://packages.graylog2.org/repo/packages/graylog-2.2-repository_latest.rpm
yum install graylog-server
file configure: /etc/graylog/server/server.conf

 add password_secret and root_password_sha2

 You need to use the following command to create your root_password_sha2
echo -n yourpassword | sha256sum
ac66277d61c0d9bed3146c80adcc05e10f10ef0f7c3ee125d809909c59ad4460

 password_secret: 
yum install epel-release
yum install pwgen
pwgen -N 1 -s 96
TPPQY0MsX15DkeHHepmVP7ZPkvEaWRw3180qFDP7uzL7sAJysU3arFEPu6aZI3OgMmaQ25rVsX3Ach8y7xesJO0nwI1W9S52

*******************CONFIGURE *****************
=======ELASTICSEARCH=============
cluster.name: graylog2
bootstrap.mlockall: true
network.host: 192.168.221.134
discovery.zen.ping.timeout: 30
discovery.zen.ping.unicast.hosts: ["192.168.221.134:9300"]

 =======GRAYLOG=====

 is_master = true
node_id_file = /etc/graylog/server/node-id
root_timezone = Asia/Ho_Chi_Minh
elasticsearch_cluster_name = graylog2
elasticsearch_node_name = services.ilab

 elasticsearch_discovery_zen_ping_multicast_enabled = false
elasticsearch_discovery_zen_ping_unicast_hosts = 192.168.221.134:9300

  #web_listen_uri = http://10.0.1.2:9000/
web_listen_uri = http://0.0.0.0:9000/   ==>for all interface listen
and
rest_listen_uri = http://0.0.0.0:12900/

 mongodb_useauth = false
#mongodb_host = graylog.example.com
mongodb_database = graylog2
mongodb_port = 27017
mongodb_uri = mongodb://192.168.221.134:27017/graylog2

 ======MONGODB===========
mongodb
net:
  port: 27017
  bindIp: 222.255.100.26  # Listen to local interface only, comment to listen on all interfaces.

 *****************************Test********
Elasticsearch
curl -X GET 'http://192.168.221.134:9200/'
curl -X GET 'http://192.168.221.134:9200/_cluster/health?pretty=true'
=====================================================================

Referenced : graylog.org

Hiểu rõ hơn vui lòng xem tại Graylog.com  


Trouble shoot:
lỗi
[root@lab ~]# service graylog-server start
OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N

 Giải quyêt:

 Cung cấp cho VM thêm CPU để xử lý.



Phần tham khảo thêm: 
This guide describes the fastest way to install Graylog on CentOS 6. All links and packages are present at the time of writing but might need to be updated later on.
Warning
This setup should not be done on publicly exposed servers. This guide does not cover security settings!

Prerequisites

Taking a minimal server setup as base will need this additional packages:
$ sudo yum install java-1.8.0-openjdk-headless.x86_64
If you want to use pwgen later on you need to Setup EPEL on your system with sudo yum install epel-release and install the package with sudo yum install pwgen.

MongoDB

Installing MongoDB on CentOS should follow the tutorial for RHEL and CentOS from the MongoDB documentation. First add the repository file /etc/yum.repos.d/mongodb-org-3.2.repo with the following contents:
[mongodb-org-3.2]
name=MongoDB Repository
baseurl=https://repo.mongodb.org/yum/redhat/$releasever/mongodb-org/3.2/x86_64/
gpgcheck=1
enabled=1
gpgkey=https://www.mongodb.org/static/pgp/server-3.2.asc
After that, install the latest release of MongoDB with sudo yum install mongodb-org.
Additionally, run these last steps to start MongoDB during the operating system’s boot and start it right away:
$ sudo chkconfig mongod on
$ sudo service mongod start

Elasticsearch

Graylog 2.0.0 and higher requires Elasticsearch 2.x, so we took the installation instructions from the Elasticsearch installation guide.
First install the Elastic GPG key with rpm --import https://packages.elastic.co/GPG-KEY-elasticsearchthen add the repository file /etc/yum.repos.d/elasticsearch.repo with the following contents:
[elasticsearch-2.x]
name=Elasticsearch repository for 2.x packages
baseurl=https://packages.elastic.co/elasticsearch/2.x/centos
gpgcheck=1
gpgkey=https://packages.elastic.co/GPG-KEY-elasticsearch
enabled=1
followed by the installation of the latest release with sudo yum install elasticsearch.
Make sure to modify the Elasticsearch configuration file (/etc/elasticsearch/elasticsearch.yml) and set the cluster name to graylog additionally you need to uncomment (remove the # as first character) the line:
cluster.name: graylog
After you have modified the configuration, you can start Elasticsearch:
$ sudo chkconfig elasticsearch on
$ sudo service elasticsearch start

Graylog

Now install the Graylog repository configuration and Graylog itself with the following commands:
$ sudo rpm -Uvh https://packages.graylog2.org/repo/packages/graylog-2.2-repository_latest.rpm
$ sudo yum install graylog-server
Follow the instructions in your /etc/graylog/server/server.conf and add password_secret and root_password_sha2. These settings are mandatory and without them, Graylog will not start!
You need to use the following command to create your root_password_sha2:
echo -n yourpassword | sha256sum
To be able to connect to Graylog you should set rest_listen_uri and web_listen_uri to the public host name or a public IP address of the machine you can connect to. More information about these settings can be found in Configuring the web interface.
Note
If you’re operating a single-node setup and would like to use HTTPS for the Graylog web interface and the Graylog REST API, it’s possible to use NGINX or Apache as a reverse proxy.
The last step is to enable Graylog during the operating system’s startup:
$ sudo chkconfig graylog-server on
$ sudo service graylog-server start
The next step is to ingest messages into your Graylog and extract the messages with extractors or use the Pipelines to work with the messages.

SELinux information

Hint
We assume that you have -pythonpolicycoreutils installed to manage SELinux.
If you’re using SELinux on your system, you need to take care of the following settings:
  • Allow the web server to access the network: sudo setsebool -P httpd_can_network_connect 1
  • If the policy above does not comply with your security policy, you can also allow access to each port individually:
    • Graylog REST API and web interface: sudo semanage port -a -t http_port_t -p tcp 9000
    • Elasticsearch (only if the HTTP API is being used): sudo semanage port -a -t http_port_t -p tcp 9200
  • Allow using MongoDB’s default port (27017/tcp): sudo semanage port -a -t mongod_port_t -p tcp 27017
If you run a single server environment with NGINX or Apache proxy, enabling the Graylog REST API is enough. All other rules are only required in a multi-node setup.
Hint
Depending on your actual setup and configuration, you might need to add more SELinux rules to get to a running setup.

How to install Splunk on centos ( Hướng dẫn cài đặt splunk trên centos)

- cài trên logs.thudv.com - ip: 192.168.22.2
                - login vào splunk = web: admin/chip@102
                - Để download splunk bản mới nhất cần đăng ký account tại trang splunk.com
-Các cách cài đặt:
Cách 1: đơn giản nhất. Tất cả cài đặt Splunk Agent và cấu hình forwarding về Splunk Server làm NSM. Search, Report trên Splunk Server. Các thiết bị không thể cài đặt Splunk thì hoặc cấu hình gửi log trực tiếp về Splunk; hoặc cấu hình chuyển log về Syslog-NG server, sau đó Syslog-NG tiếp tục cấu hình gửi log về Splunk. 

Cách thứ 2: không cài đặt, ko sử dụng Splunk làm Agent. Sử dụng Syslogd hoặc Rsyslog; cài Syslog Agent trên các server Windows. Tất cả được cấu hình tập trung log về Syslog-NG server. Từ Syslog-ng server, tiếp tục cấu hình gửi log về Splunk. Do đó chỉ cần cài Splunk trên NSM Server là đủ.

Cách thứ 3 đó là sử dụng bộ 3 phần mềm ElasticSearch, LogStash và Kibana (http://www.elasticsearch.org/overview/). Tất cả đều là phần mềm nguồn mở nên bạn ko phải lo lắng về chi phí. Tuy nhiên cách này tôi chưa thử bao giờ nên ko thể so sánh ưu khuyết với 2 cách kia.
- Bản cài hiện tại là splunk-6.3.2-aaff59bb082c-Linux-x86_64.tgz
# tar xvzf splunk-6.3.2-aaff59bb082c-Linux-x86_64.tgz
- Start splunk                                            
#cd /splunk/bin
# ./splunk start  (or stop; restart)
hoặc
#/tmp/splunk/bin/splunk stop (start,restart)
- Để clean eventdata
#/tmp/splunk/bin/splunk  clean eventdata  (có thể thêm từng data: /tmp/splunk/bin/splunk  clean eventdata  -index myindex -f) 
- license: chọn y
- Cài đặt thành  công
- trên client có thể truy cập http://hostname:8000 (hoặc ip) để sử dụng splunk
-Cấu hình trên client đẩy log về logs server
#vi /etc/rsyslog.conf
==>cấu hình ip của splunk và port listen
- Restart rsyslog.
 #service rsyslog restart
- Cấu hình trên server splunk để lấy logs
-Mở iptables trên splunk server
                -A INPUT -m state --state NEW -m tcp -p tcp --dport 8000 -j ACCEPT   (cho phép client login vào web splunk)
                -A INPUT -m state --state NEW -m tcp -p tcp --dport 8089 -j ACCEPT  
                -A INPUT -m state --state NEW -m tcp -p tcp --dport 514 -j ACCEPT    (lắng nghe rsyslog client đẩy về)

 Trên menu click vào setting chọn Data input.
Trong Local inputs: chọn TCP
Chọn New
tiếp tục Next: chọn syslog trong source type và ip trong Host
Tiếp tục chọn Next
 Kết thúc submit
- Tiếp tục chọn start Searching
-Lúc này sẽ thấy mấy agent Centos

*** cài trên Windows agent:  splunkforwarder-6.3.2-aaff59bb082c-x64-release.msi

(chú ý khi cài đặt chỉ cần điền ip receive: chỗ port 9997)
Subscribe to: Posts (Atom)

Adsense

Translate

Copyright © THU DINH. Created By