Walter.Web.FireWall 2024.11.15.421

How to get started

This package allows you to protect your firewall using annotations and pre-specified rules. A full getting started document is available at www.asp-waf.com in form of a PDF, compiled help

Unsupported You can't deploy the firewall as an embedded dll in a single file deployment as the firewall will validate the code signing certificate of the assembly. Make sure that you exclude Walter.Web.Firewall.dll from your deploy, for help see the documentation

Get started

The below sample shows how you integrate and enable the firewall in your project.

services.AddFireWall(options =>
    {
        //generate access specify to generate a .connect file that can be used with the remote desktop management software (open source)
        options.Administration.GenerateConnectFile = true;
        options.Administration.DisplayName = "My HomePage";

        //white list IP addresses,and block all other or leave blank to allow all IP will accept single IP, IP with CIDR, or IP with subnet mask 
        //options.Administration.WhiteList("84.195.151.208", "81.206.151.236", "10.0.0.1-255.255.255.0");

        options.Administration.Users.Seed(userName: "admin", password: "pa$$word1234", access: AdminAccess.Full, GeoLocation.EUROPE);
        options.Administration.Users.GuestAccess(GeoLocation.ALL);


        
        options.FireWallMode = Walter.Web.FireWall.FireWallProtectionModes.WebSiteWithApi;

        options.ProtectedEndPointTypes.Add(typeof(BaseController));
        options.TrackUsers = true;


        options.Cashing.GeoLocation.SlidingExpiration = TimeSpan.FromMinutes(20);

        options.ContactDetails.Address = "Your address";
        options.ContactDetails.EMail = "support@myDomain.com";
        options.ContactDetails.Name = "Support";
        options.ContactDetails.Phone = "+352 1111 2222 3333";
        options.ContactDetails.Country = GeoLocation.Luxembourg;

        options.Rules.AllowNonAspNetRequests = 1;
        options.Rules.AllowNonAspNetRequestsIn = TimeSpan.FromMinutes(20);
        options.Rules.RedirectNonAspNetRequestsTo = new Uri("/Home/Blocked", UriKind.Relative);
        options.Rules.RedirectUrlPhishingTo = new Uri("/Home/404", UriKind.Relative);
        options.Rules.AllowWhiteListing = false;
        options.Rules.PhysicalFileWallExcludeReasons = Walter.BOM.FirewallBlockReasons.ALL & ~Walter.BOM.FirewallBlockReasons.NoAccessFromRegion;
        options.Rules.BlockRequest.BlockDuration.SlideExpiration = true;
        options.Rules.BlockRequest.BlockDuration.Expires = TimeSpan.FromSeconds(10);
        options.Rules.AllowWhiteListing = false;
        options.Rules.Headers.AddDefaultSecurePolicy()
                                .AddStrictTransportSecurityNoCache()
                                .AddXssProtectionBlockAndReport()  
                                .AddFrameOptionsDeny()                                
                                .AddContentSecurityPolicyButTrust(trustingSites: Walter.Web.FireWall.TrustingSites.Self | Walter.Web.FireWall.TrustingSites.SubDomains | Walter.Web.FireWall.TrustingSites.GenerateNonce, allowInline:false)
                                ;

    })
    .UseDatabase(DatabaseConnections.FireWallState, "dbo", TimeSpan.FromDays(365))



public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
    app.UseFireWall(enablePortScannerListners: false)//set to true if you use honey-pot configuration nuget package walter.net.honeypot
                .UseSecurityHeadersMiddleware();
}

The firewall is fully configurable and has quite a few options that allow you to protect against fishing, scrubbing, cross-site attach and much more.

There are a ton of configuration options available using the many annotations

   namespace MyProject.Controllers
   {
       using Walter.Web.FireWall;
       using Walter.Web.FireWall.Annotations;
       using Walter.BOM.Geo;

       [Geo(blockLocation: GeoLocation.AFRICA | GeoLocation.LATIN_AMERICA | GeoLocation.Netherlands)]
       [Users(users: UserTypes.IsHuman | UserTypes.IsSearchEngine)]
       [BlockDuration(duration: 60, sliding: true, doubleDurationPerIncedent: true)]
       public sealed class MembersController : Controller
       {
           private readonly ILogger<MembersController> _logger;
            private readonly IPageRequest _page;
           public HomeController(ILogger<MembersController> logger,IPageRequest page)
           {
               _logger = logger;
               _page=page;
           }

           public IActionResult Index()
           {
               return View();
           }


           [Ignore]
           [ResponseCache(Duration = 0, Location = ResponseCacheLocation.None, NoStore = true)]
           public IActionResult Error()
           {
               //the page field will contain all the errors the user ran into
               return View(new ErrorViewModel { RequestId = Activity.Current?.Id ?? HttpContext.TraceIdentifier });
           }
       }
   }

in your razor pages you can use the firewall tag helpers after importing the tag helpers by adding the following to _ViewImports.cshtml

@using Walter.Web.FireWall

@addTagHelper *, Microsoft.AspNetCore.Mvc.TagHelpers
@addTagHelper *, Walter.Web.FireWall

You can use the tag helper in your razor pages like this

<head>
  ...
  
  @section CSS
  {
    <style firewall-style-nonce>

        h1{
        background-color:azure;
        }
    </style>
  }
<head/>

<body>
    ...
    
    <script firewall-detect></script>    

    
    <script firewall-script-nonce>
        console.warn("nonce works :-)");
    </script>
<body/>

This is just a small set of options of what's possible and additional functionality can be injected using the plugin system by using any of the NuGet packages starting with the name walter.web.firewall.