While it took days for 42% of respondents to contain a web incident, you can take the following steps to prevent these incidents:
To learn more, download the full report http://www.verizonenterprise.com/DBIR/2014/?utm_source=earlyaccess&utm_medium=redirect&utm_campaign=DBIR
]]>This post gave a formula to do it:
=INT(MID(A1,1,3)) & “.” &
INT(MID(A1,5,3)) & “.” &
INT(MID(A1,9,3)) & “.” &
INT(MID(A1,13,3))
Source: http://superuser.com/questions/931682/excel-remove-leading-0s-from-ip-address
]]>All i had to do was to remove the entries there then go to the splunk server and enter:
./splunk clean eventdata
(Warning all data in the indexes will be lost)
]]>I have a simple solution to share with you.
Since this website uses BNShosting web mirror service, i thought of using the squid service to block the tons of WordPress attacks using XMLRPC from ever getting to the origin server.
On your squid proxy configuration (squid.conf) add the following entries:
# for Identifying WordPress xmlrpc attacks in URL
acl wordpressAttackers url_regex xmlrpc
acl wordpressAttackers1 url_regex wp-includes/template-loader.php
# Block WordPress Xmlrpc Attackers
http_access deny wordpressAttackers
http_access deny wordpressAttackers1
Save the file, then restart the squid service.
The next time a hacker attempts to brute force your password or insert malware via the xmlrpc or /template-loader.php, the squid service will deny the attempt and filter these attacks before it even gets to the source server.
So i opened a command prompt and entered:
findstr “string-to-be-search” filename.ext > result.txt
This gave me a smaller file that i could work with. Other ideas to try is to find the UNIX date string and use it to filter the log file into the date range you want to work with.
Hope this helps others.
]]>