Originally published at https://github.com/akaunting
This package intends to protect your Laravel app from different type of attacks such as XSS, SQLi, RFI, LFI, User Agent, and a lot more. It will also block repeated attacks and send notification via email and/or slack when attack is detected. Furthermore, it will log failed logins and block the IP after a number of attempts.
Note: Some middleware classes (i.e. Xss) are empty as the Base
class that they extend does all of the job, dynamically. In short, they all works ;)
Run the following command:
composer require akaunting/firewall
Register the service provider in config/app.php
Akaunting\Firewall\Provider::class,
Publish configuration, language, and migrations
php artisan vendor:publish --tag=firewall
Create db tables
php artisan migrate
You can change the firewall settings of your app from config/firewall.php
file
Middlewares are already defined so should just add them to routes. The firewall.all
middleware applies all the middlewares available in the all_middleware
array of config file.
Route::group(['middleware' => 'firewall.all'], function () { Route::get('/', 'HomeController@index'); });
You can apply each middleware per route. For example, you can allow only whitelisted IPs to access admin:
Route::group(['middleware' => 'firewall.whitelist'], function () { Route::get('/admin', 'AdminController@index'); });
Or you can get notified when anyone NOT in whitelist
access admin, by adding it to the inspections
config:
Route::group(['middleware' => 'firewall.url'], function () { Route::get('/admin', 'AdminController@index'); });
Available middlewares applicable to routes:
firewall.allfirewall.agent
firewall.geo
firewall.ip
firewall.lfi
firewall.php
firewall.referrer
firewall.rfi
firewall.session
firewall.sqli
firewall.swear
firewall.url
firewall.whitelist
firewall.xss
You may also define routes
for each middleware in config/firewall.php
and apply that middleware or firewall.all
at the top of all routes.
Firewall will send a notification as soon as an attack has been detected. Emails entered in notifications.email.to
config must be valid Laravel users in order to send notifications. Check out the Notifications documentation of Laravel for further information.
Thanks for reading ❤
If you liked this post, share it with all of your programming buddies!
Follow me on Facebook | Twitter
☞ PHP with Laravel for beginners - Become a Master in Laravel
☞ Projects in Laravel: Learn Laravel Building 10 Projects
☞ Laravel for RESTful: Build Your RESTful API with Laravel
☞ Fullstack Web Development With Laravel and Vue.js
☞ Laravel 5.8 Ajax CRUD tutorial using Datatable JS
☞ Laravel 5.8 Tutorial from Scratch for Beginners
☞ Build RESTful API In Laravel 5.8 Example
☞ Login with Google in Laravel 5.8 App using Socialite Package
☞ Laravel PHP Framework Tutorial - Full Course for Beginners (2019)
#laravel #web-development #security