Walter.Web.FireWall 2021.9.19.1015

There is a newer version of this package available.
See the version list below for details.
Install-Package Walter.Web.FireWall -Version 2021.9.19.1015
dotnet add package Walter.Web.FireWall --version 2021.9.19.1015
<PackageReference Include="Walter.Web.FireWall" Version="2021.9.19.1015" />
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add Walter.Web.FireWall --version 2021.9.19.1015
The NuGet Team does not provide support for this client. Please contact its maintainers for support.
#r "nuget: Walter.Web.FireWall, 2021.9.19.1015"
#r directive can be used in F# Interactive, C# scripting and .NET Interactive. Copy this into the interactive tool or source code of the script to reference the package.
// Install Walter.Web.FireWall as a Cake Addin
#addin nuget:?package=Walter.Web.FireWall&version=2021.9.19.1015

// Install Walter.Web.FireWall as a Cake Tool
#tool nuget:?package=Walter.Web.FireWall&version=2021.9.19.1015
The NuGet Team does not provide support for this client. Please contact its maintainers for support.

The application firewall that can be used in .NET 5.0, .Net CORE 3.1 and .NET standard 2.1 applications that
     would benefit for protection against several types of attacks and is easily activated by service integration.

     services.AddFireWall(FireWallTrial.License, FireWallTrial.DomainKey
     , domainName: new Uri("https://www.your-domain.com/", UriKind.Absolute)
     , options => {
         //your options
     });

      Have a look at the GitHub samples at https://github.com/ASP-WAF/FireWall
      and https://github.com/ASP-WAF/FireWall/wiki to see how to use the firewall in
      applications. You can view the firewall in action using https://www.asp-waf.com/Firewall      
     
     You can get started with the firewall using the samples shown in
     https://www.asp-waf.com/download/ASP-WAF-FireWall-Getting-Started.pdf
     as well as the on line documentation at https://firewallapi.asp-waf.com/

NuGet packages (11)

Showing the top 5 NuGet packages that depend on Walter.Web.FireWall:

Package Downloads
Walter.Web.FireWall.EventLog

Reporting interface for the firewall and the windows to support structured logging to the windows EventLog. The Package extends the reporting functionality to NuGet package Walter.Web.Firewall and is easily activated by dependency injection during service configuration services.AddFireWall(FireWallTrial.License, FireWallTrial.DomainKey , domainName: new Uri("https://www.your-domain.com", UriKind.Absolute) , options => { //your firewall settings }).UseEventLogLogging(options=>{ options.LogName = "FireWall"; options.SourceName = "www.your-domain.com"; }); More information on how to use this Add-On is available in this manual https://www.asp-waf.com/download/ASP-WAF-FireWall-Getting-Started.pdf

Walter.Web.FireWall.SqlLogger

Package that enable SQL Server database storage and logging to NuGet package Walter.Web.Firewall The NuGet package is easily activated by dependency injection during service configuration services.AddFireWall(FireWallTrial.License, FireWallTrial.DomainKey , domainName: new Uri("https://www.your-domain.com", UriKind.Absolute) , options => { //your firewall settings }).UseDataBase(ConfigurationManager.ConnectionStrings["FireWallState"].ConnectionString) .UseFireWallReportingDatabase(ConfigurationManager.ConnectionStrings["FireWallReporting"].ConnectionString); More information on how to use this Add-On is available in this manual https://www.asp-waf.com/download/ASP-WAF-FireWall-Getting-Started.pdf

Walter.Web.FireWall.SMTPLogger

The Package adds E-Mail based reporting functionality to NuGet package Walter.Web.Firewall and allows for the logging of incidents via E-Mail by using a E-Mail buffer and sends the emails at configured intervals. The NuGet package is easily activated by dependency injection during service configuration services.AddFireWall(FireWallTrial.License, FireWallTrial.DomainKey , domainName: new Uri("https://www.your-domain.com", UriKind.Absolute) , options => { //your firewall settings }).UseSMTPReportingDatabase(options =>{ options.Archive = TimeSpan.FromDays(180); options.Server = "mail.server.com"; options.UserName = "noreply@your-domain.com"; options.Password = "pa$$w0rd1234"; options.Port = 8889; options.From = "noreply@your-domain.com"; options.IgnoreServerCertificateErrors = true; options.DefaultEmail = "webmaster@your-domain.com"; options.Archive = TimeSpan.FromDays(60); options.MailingList.AddRange(new[] { new EMailAddress("Security Admin","security@your-domain.com") { Frequency= TimeSpan.FromHours(1), Roles= EMailRoles.FireWallAdministrationViolations | EMailRoles.UnauthorizedPhysicalFilesViolation }, new EMailAddress("WAF","info@your-domain.com"){ Frequency= TimeSpan.FromHours(1), Roles= EMailRoles.ProductUpdates | EMailRoles.OwnAccountRelatedViolations } , }); }); More information on how to use this Add-On is available in this manual https://www.asp-waf.com/download/ASP-WAF-FireWall-Getting-Started.pdf as well as on-line at https://www.asp-waf.com/NuGet

Walter.Web.FireWall.Geo.MaxMind

Use MaxMind Geo data service or API keys to make the Walter.Web.IFireWall interface geographically aware allowing you to block requests for certain countries and enables you to render a different result based on the region or country the request came from. The Package adds functionality to NuGet package Walter.Web.Firewall services.AddFireWall(FireWallTrial.License, FireWallTrial.DomainKey , domainName: new Uri("https://www.your-domain.com", UriKind.Absolute) , options => { //your firewall settings }).UseGeography(directory:new DirectoryInfo("d:\\MaxMind")); This assumes that data files are in d:\MaxMind folder leave blank if you use App_Data and in your application configuration you can set blocking scope like this app.UseFireWall() .UseGeoBlockingMiddleware(options => { options.Block(new[]{GeoLocation.China ,GeoLocation.RussianFederation}); }); More information on how to use this Add-On is available in this manual https://www.asp-waf.com/download/ASP-WAF-FireWall-Getting-Started.pdf

Walter.Web.FireWall.Geo.Native

Free FireWall native Geo-country code API with limited accuracy. The Package adds functionality to NuGet package Walter.Web.Firewall More information on how to use this Add-On is available in this manual https://www.asp-waf.com/download/ASP-WAF-FireWall-Getting-Started.pdf This free API library may not give accurate results as it uses unchecked public domain data

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
2021.10.19.1522 191 10/19/2021
2021.10.16.1325 634 10/18/2021
2021.10.6.1546 942 10/6/2021
2021.10.5.1450 972 10/5/2021
2021.10.4.1155 982 10/5/2021
2021.10.1.753 870 10/1/2021
2021.9.27.1005 757 9/28/2021
2021.9.26.1913 699 9/26/2021
2021.9.19.1015 387 9/19/2021
2021.9.17.1702 261 9/17/2021
2021.9.17.1449 549 9/17/2021
2021.9.13.1600 356 9/13/2021
2021.9.12.1100 223 9/13/2021
2021.9.11.2004 393 9/11/2021
2021.9.9.1110 438 9/9/2021
2021.9.7.1901 510 9/8/2021
2021.9.7.1121 454 9/7/2021
2021.9.6.1518 492 9/7/2021
2021.9.4.1124 561 9/4/2021
2021.9.2.708 533 9/4/2021
2021.9.0.1259 563 9/2/2021
2021.8.2200 463 8/23/2021
2021.8.2100 525 8/23/2021
2021.8.22.900 629 8/22/2021
2021.8.18.1500 644 8/18/2021
2021.8.18.930 645 8/18/2021
2021.8.14.1600 621 8/16/2021
2021.8.14.829 222 8/14/2021
2021.8.9.1105 373 8/9/2021
2021.8.8.1612 455 8/8/2021
2021.8.8.1138 386 8/8/2021
2021.8.6.1044 502 8/6/2021
2021.8.4.1355 494 8/5/2021
2021.7.30.2118 556 7/31/2021
2021.7.27.926 511 7/28/2021
2021.7.23.931 463 7/26/2021
2021.7.22.1456 590 7/23/2021
2021.7.15.1547 539 7/15/2021
2021.7.13.812 545 7/13/2021
2021.7.8.1527 564 7/10/2021
2021.7.5.1649 426 7/5/2021
2021.6.29.1453 617 6/30/2021
2021.6.26.1753 585 6/27/2021
2021.6.25.1849 548 6/25/2021
2021.6.24.1518 544 6/24/2021
2021.6.20.729 755 6/20/2021
2021.6.15.2006 703 6/15/2021
2021.6.14.2025 672 6/15/2021
2021.6.13.2035 652 6/14/2021
2021.6.12.1154 545 6/13/2021
2021.6.9.1120 599 6/9/2021
2021.6.3.1509 511 6/3/2021
2021.5.31.1533 487 5/31/2021
2021.5.31.1415 550 5/31/2021
2021.5.25.1732 486 5/25/2021
2021.5.24.1128 626 5/24/2021
2021.5.24.1019 541 5/24/2021
2021.5.12.1054 289 5/12/2021
2021.5.12.637 259 5/12/2021
2021.5.10.1442 265 5/11/2021
2021.5.8.1226 278 5/8/2021
2021.5.6.2037 275 5/6/2021
2021.5.5.1901 313 5/6/2021
2021.5.3.1621 310 5/4/2021
2021.5.1.905 375 5/1/2021
2021.4.28.1511 351 4/28/2021
2021.4.20.1520 391 4/21/2021
2021.4.16.949 82 4/21/2021
2021.4.16.738 394 4/21/2021
2021.4.14.1216 441 4/16/2021
2021.4.9.1538 465 4/13/2021
2021.4.8.947 436 4/13/2021
2021.4.6.1235 392 4/6/2021
2021.4.5.1653 413 4/5/2021
2021.4.1.913 380 4/1/2021
2021.3.31.2003 435 4/1/2021
2021.3.18.1622 399 3/18/2021
2021.3.3.1259 427 3/3/2021
2021.3.2.1415 387 3/2/2021
2021.3.1.11 427 2/28/2021
2021.3.1.1 433 2/27/2021
2021.3.1 392 2/27/2021
2021.2.23.6 368 2/23/2021
2021.2.23.4 124 2/23/2021
2021.2.21.1 392 2/21/2021
2021.2.20.1 401 2/20/2021
2021.2.19.2 467 2/19/2021
2021.2.18.6 398 2/19/2021
2021.2.17.1 425 2/17/2021
2021.2.16.1 486 2/16/2021
2021.2.15.3 447 2/15/2021
2021.2.15.1 463 2/14/2021
2021.2.14.3 471 2/14/2021
2021.2.12.6 475 2/12/2021
2021.2.12.2 468 2/12/2021
2021.2.11.1 384 2/11/2021
2021.2.10.1 405 2/10/2021
2021.2.8.1 484 2/9/2021
2021.2.7.2 468 2/7/2021
2021.2.7.1 494 2/6/2021
2020.12.27.1 497 12/27/2020
2020.12.26.5 513 12/27/2020
2020.12.26.4 139 12/27/2020
2020.12.26.3 519 12/27/2020
2020.12.19.1 609 12/19/2020
2020.12.16.1 538 12/16/2020
2020.12.15.1 513 12/15/2020
2020.12.14.5 835 12/14/2020

Major releases that add functionality other than optimization and minor bug fixing
     19 September
     - Update NuGet packages release for .Net 5.0.10
     
     11 September 2021
     - Fix bug where whois processor would write empty WHOIS json data to storage

     9 September 2021
     - Add method in AbuseBaseController to load uploaded reports retrieving AbuseReportViewModel when calling GetReports()

     7 September 2021
     - Add abstract controller to make it easier to render abuse reports in the hosting web application
     as it only needs to use AbuseBaseController and call GetReports on it.


     31 August 2021
     - Fix bug where visits are flagged as incidents where they never triggered a incident
     - Update Maintenance for WHOIS to generate less pressure on log file
     - Update KPI update for WHOIS to be non- blocking
     - Update interactivity in a more consistent way

     22 August 2021
     - Communicate additional data in abuse report firewall API for the remote management desktop
     - Change connect file format for the remote management desktop

     18 Aug 2021
     - Connect-file will be generated when Port number is known.
     - Minor bug fixes

     8 Aug 2021
     - update to .NET 6.0 SDK (v6.0.100-preview.6)
     - Add violation stack for port based attacks
     - Add Page ID to incidents allowing to identify the page more easily
     - add Running incident counter to incident


     30 June 2021
     - Add .Net 6.0 binaries to the NuGet package
     - Add additional data to Abuse report interface

     15 June 2021
     - Update Management API
     - Update to allow certificate-base request filter for API
     - Update to .Net Core 3.1.17 and .Net 5.0.8

     07 July 2021
     - Add reporting entry for last request and last incident via API
     - Save violations audit on page request
     - Save violations audit on breadcrumb for violations report

     05 July 2021
     - Fix bug in reporting data

     22 June 2021
     - Add additional counters to WHOIS object

     15 June 2021
     - Add properties to Management objects to evaluate

     11 June 2021
     - Add Payload information in firewall logging data classes if a payload was requested on an incident

     09 June 2021
     - Update to .Net SDK 5.0.301 and 3.1.410
     - Update storage data objects

     07 June 2021
     - Update NuGet Package references
     - Update Connect file include plugins data
     - Update data types
     - Add SimpleCountry meta data
     - Add Simple User meta data
     - Update firewall rules


     31 May 2021
     - Update WHOIS ISP cashing
     - Enforce firewall block recommendation rather than render a white page on phishing or penetration attempts
     configuration via default rules in the firewall configuration
     - Remove TSQL replay errors from previous session ensuring that only current content is stored in ~/App_Data/Setup/SQL
     - Detect changes in APR tables
     - Improved IFireWall WHOIS query method and include ISP counters

     28 May 2021
     - Apply .net security pack update
     - Alter storage-sub-system schema

     25 May 2021
     - Change loop frequency to reduce pooling frequency
     - Add counters to WHOIS
     - Block ISP's if Rule on rule engine or endpoint based on trust settings
     allowing general blocking for IoT devices if request are made via external data center/ provider
     - Change storage for firewall state classes
     - Add firewall management API data
     - upgrade firewall storage
     - upgrade breadcrumb data

     12 April 2021
     - Update to new code base after .net security violation fix

     10 May 2021
     - Update Database based storage

     05 May 2021
     - Integrate default endpoints so that there is no need for the default endpoints NuGet package and load the modules if the site uses management or renders pages

     04 May 2021
     - Add Key exchange for administration console on a per client basis
     - Add default endpoints for user discovery if the FireWallMode in the settings containing JavaScript clients

     29 April 2021
     - Add support for custom port with administration system
     - Add support for custom GuestUser password

     04 April 2021
     - Add ISPTrustLevelAttribute for end point protection
     - Add Minimum Credibility ISP requirement on Rule engine configuration
     - fix bug in BreadCrumb serialization

     05 April 2021
     - Add Administration configuration
     - Endpoint Annotation for 2nd level user detection
     - Update user discover script

     22 March 2021
     - Performance update

     14 March 2021
     - Update firewall and expose HoneyPot traps to firewall extension model

     05 March 2021
     - Add 2 new Rules that can be used as annotation on endpoints.
     * BrowserIntentionsAttribute - allows a way to block requests from user agents with a bad reputation
     * SiteMapAttribute - Allows a way to block users from URL's that have not been rendered to them in Razor-Pages or Views
     * Add new Tag helper for firewall-browser-intentions-
     - Add Counters for SearchEngines in User-Agents
     - Add Intent counters in User-Agents (reputation)
     - Minor bug fixes
     - Update package reference

     02 March 2021
     - Update user agents add intentions

     25  February 2021
     - Add MaliciousUserAgentsAttribute
     - Add support for MaliciousUserAgents in firewall rules

     24 February 2021
     - Update IPageRequest.BreadCrumbs class
     - Update Annotations
     - Update TagHelpers

     17 February 2021
     - Add endpoint types to protect supporting classes that are based on ControllerBase, Controller and RazorPage
     using the IFireWallConf.ProtectedEndPointTypes property

     12 February 2021
     - Framework extension changes
     - Update package references

     30 January 2021
     - Update disk change rule engine

     25 January 2021
     - Update rule engine

     02 January 2021
     - Updated terms and conditions to REL. 2021.01.02

     29 December 2020
     - Extend Storage interface and Documentation interfaces
     - Refactor DI registration

     27 December 2020
     - Fix Bug
     - Add reporting for Suspicious user agents

     26 December 2020
     - Extend IFireWall and FireWallBase class and interface add classes for reporting as well as change the constructor to allow for DI overriding state classes.
     - Extend IIncidentDatabase with IIncidentDatabase.All(bool distinct,TimeSpan limitTo)
     - Extend failed WHOIS request trying to retrieve ISP data
     - Extend reporting interface include firewall binary version and size
     - Extend Look-Who-Is-Talking (LWT) reporting capabilities

     21 December 2020
     - Integrate database maintenance when a database is used for firewall state on disposing the firewall (when the web application shuts down) as to not incur blocking
     - Update database state include who-is-talking history tracking repository...

     19 December 2020
     - Update package references
     - Integrate LookWhoisTalking repository for reporting
     see https://firewallapi.asp-waf.com/html/P-Walter.Web.FireWall.IFireWall.WhoisTalking.htm
     see https://firewallapi.asp-waf.com/html/AllMembers.T-Walter.Web.FireWall.ViewModels.Talking.htm
     - Update package references

     16 December 2020
     - Update text reporting showing days left in license and active and maximum concurrent users

     15 December 2020
     - Update text report generating local time and no longer users UTC date/time
     - Update user agent cashing

     14 December 2020
     - Update package references
     - Update WHOIS query infrastructure
     - Add publicity for concurrent user count
     - Add country field to State date when a database is used

     12 December 2020
     - Update WHOIS query engine to query IP address requester and not IP address of reverse DNS of the ISP or Data center
     - Update package references
     - Compile with Language version 9.0

     05 December 2020
     - Update default license implementation
     - Update NuGet Package references
     - Update database storage SQL script for State objects

     04 December 2020
     - Bug in SQL script for database storage migration
     - Extend health Logging interface to contain references to failed update script
     - Update package references
     - Change Json data size from a byte[] of 4000 to 8000 to facilitate bigger datasets for firewall state objects when stored to database

     03 December 2020
     - Extend IFirewall interface for reporting features
     See https://firewallapi.asp-waf.com/?topic=html/Overload-Walter.Web.FireWall.IFireWall.GetVisitStats.htm
     https://firewallapi.asp-waf.com/?topic=html/Overload-Walter.Web.FireWall.IFireWall.GetPhishyVisitStats.htm

     02 December 2020
     - Update country definition of a WHOIS entry if the country is unknown and a geography plugin is used

     01 December 2020
     - Update Connection string application name in connection from default .net message to application name when database storage is used to save state and no application name was provided.
     - Update IFireWall.Whois() method to map LAN IP addresses to the firewall contact details
     - Extend Incident classes to update for IWHOIS data for use in the management interfaces

     27 November 2020
     - Bug Fix cookie options set secure only if web application is using TLS connection

     22 November 2020
     - Update compiler hints improving .net Core 3.1 and .Net 5.0 compiled binaries
     - Fix bug in update script for incident database

     20 November 2020
     - update packages to .net core 3.1.404

     17 November 2020
     - Update documentation
     - Annotate return types IFireWall, IPageRequest, IIncidentDatabase, IUserIdentity, IFureWallUser, IFireWallConfig and more
     - Extend IIncidentDatabase management API interface
     - Change nullability of some types

     14 November 2020
     - Add support for IWhoisBackGroundProcessor for NuGet Package
     Documentation at https://firewallapi.asp-waf.com/?topic=html/T-Microsoft.Extensions.DependencyInjection.WhoisWhoisBackGroundProcessorExtensions.htm
     - Add access to the default instance for most of the propiatary storage classes for the firewall allowing direct access for advance use interface
     IResetRepository:  https://firewallapi.asp-waf.com/?topic=html/M-Walter.Web.FireWall.Infrastructure.Repositories.IResetRepository.Instance.htm
     IWhoisRepository:  https://firewallapi.asp-waf.com/html/M-Walter.Web.FireWall.Infrastructure.IWhoisRepository.Instance.htm
     IIncidentDatabase: https://firewallapi.asp-waf.com/html/M-Walter.Web.FireWall.RuleEngine.IIncidentDatabase.Instance.htm

     13 November 2020
     - Update the way that default interface object created and will capture missing interfaces when a custom FireWall instance
     used extension methods in service registration but the constructor does not capture the interface.
     - Fix Spelling and update documentation

     12 November 2020
     - Update IPageRequest allow to read block cookie reasons using ContainsBlockCookie method allowing you to log the reasons documented

     11 November 2020
     - Update packages and support .Net 5.0

     08 November 2020
     Update signatures FireWallBase for null validly testing by the compiler and IntelliSense

     01 November 2020
     - Add overload methods to override default storage location and data retention for firewall database state per data type

     30 October 2020
     - implement database state for firewall

     15 October 2020
     - Update User blocking message
     - Add FireWall exception handler event
     - Reduce firewall footprint when using CookieFactory in Firewall
     - Improve GDPR action by cashing Cookie requests between HttGet and HttpPost AJAX callbacks


     14 October 2020
     - Update to .net core 3.1.4

     12 October 2020
     1. Change Database logging interface providing access to full IPageRequest interface

     09 October 2020
     1. Fix bug in UserAgent database storage creation script
     2. Update ToDo message generated when finding security issue in application

     08 October 2020
     1 update documentation
     2 update filter improve dependency independence

     06 October 2020
     1. Update Browser data
     2. Add extension method to service configuration to better configure UserAgent storage
     3. Improved user agent cashing and device recognition
     documentation at: https://firewallapi.asp-waf.com/?topic=html/AllMembers.T-Walter.Web.FireWall.Browser.IUserAgent.htm

     05 October 2020
     1. Update NuGet Package References
     2. Update EULA
     3. Provide access to browser and browser meta data of IUserAgent in IPageRequest.User.UserAgent

     1 October 2020
     1. Add interactions to IPageRequest for on a Root page if User discovery is used
     2. Update NuGet package References
     3. Fix bug where user cookie was always a session cookie



     30 September 2020
     1. Sort result for text based reporting

     29 September 2020
     1. Integrate Lazy logging from Walter.dll
     2. Fix bug on license validator
     3. Update FireWall session storage interface
     4. Update NugetPackage references

     24 September 2020
     1. fix index error on ILogger interface in Guard Module
     2. Include Minify data to reporting interface

     23 September 2020
     1. Add Minification to the reporting data class

     22 September 2020
     1. Add User type filters that allow the firewall to reject BOT's and Malicious users
     documentation at https://firewallapi.asp-waf.com/?topic=html/T-Walter.Web.FireWall.Filters.BlockBotsFilter.htm
     documentation at https://firewallapi.asp-waf.com/?topic=html/T-Walter.Web.FireWall.Filters.BlockMaliciousUserFilter.htm

     19 September 2020
     1. Add Minify attribute
     documentation at https://firewallapi.asp-waf.com/?topic=html/T-Walter.Web.FireWall.Filters.MinifyAttribute.htm
     2. Add Firewall disk manipulation detection event
     documentation at https://firewallapi.asp-waf.com/?topic=html/E-Walter.Web.FireWall.FireWallBase.OnDiskManipulation.htm
     3. Add User GDPR cookie solution using transparent encryption and IPageRequest.User cookie capabilities
     documentation at https://firewallapi.asp-waf.com/?topic=html/Overload-Walter.Web.FireWall.IUserIdentity.WriteCookie.htm
     https://firewallapi.asp-waf.com/?topic=html/P-Walter.Web.FireWall.Configurations.CookieConfig.UseTransparentEncryption.htm

     16 September 2020
     1. Streamline the FileWall tag helpers
     2. Update Disk logging NuNet Package now in Walter.Web.FireWall.DiskLogging NuGet Package
     3. Update ILogging NuNet Package now in Walter.Web.FireWall.ILogging NuGet Package
     4. Update package references

     14 September 2020
     1. Update package references
     2. Add NoCashAttribute
     https://firewallapi.asp-waf.com/?topic=html/T-Walter.Web.FireWall.Filters.NoCacheAttribute.htm
     3. Add ModelFilter attribute
     https://firewallapi.asp-waf.com/?topic=html/T-Walter.Web.FireWall.Filters.ModelFilterAttribute.htm

     09 September 2020
     1. Add access to Rules class for advanced configuration before rule engine uses it to generated default rules
     https://firewallapi.asp-waf.com/?topic=html/Events.T-Walter.Web.FireWall.IFireWallConfig.htm

     2. Add access to RuleEngine configuration for runtime PEN scripts detection by making RulesConfig.BlockedPatterns Property public
     https://firewallapi.asp-waf.com/?topic=html/P-Walter.Web.FireWall.Configurations.RulesConfig.BlockedPatterns.htm

     3. Update documentation and sample documentation in on-line help and manual
     https://www.asp-waf.com/download/ASP-WAF-FireWall-Getting-Started.pdf

     4. Fix issue where sometimes a user gets rejected for being in the wrong group without having a filter defined.
     https://firewallapi.asp-waf.com/?topic=html/P-Walter.Web.FireWall.Configurations.RulesConfig.RejectUsersByDefault.htm


     08 September 2020
     1. Add OnRootPageRequestDisposed and OnResourceSend event to FireWallBase class as well as IFireWall interface
     Methods allow for post processing in proprietary projects
     https://firewallapi.asp-waf.com/?topic=html/Events.T-Walter.Web.FireWall.FireWallBase.htm
     2. Provide access to default rules for UrlValidationPatterns
     https://firewallapi.asp-waf.com/?topic=html/P-Walter.Web.FireWall.Configurations.RulesConfig.BlockedPatterns.htm

     2. Fix bug where sometimes users would be blocked as no user rule was defined

     06 September 2020
     1. update documentation
     2. Update terms
     3. Update NuGet package references

     04 September 2020
     1. update documentation
     2. Add manual blocking on event

     03 September 2020
     1. Add events for firewall management
     https://firewallapi.asp-waf.com/?topic=html/Events.T-Walter.Web.FireWall.IFireWall.htm
     2. Add method for using custom IFireWall implementation using base class
     https://firewallapi.asp-waf.com/?topic=html/M-Walter.Web.FireWall.FireWallBase.-ctor.htm

     27 August 2020
     1. Update License test for machine name in URL allowing it as a valid local licensed domain as LocalHost
     2. Update documentation
     3. Save incidents to disk in clear json format making it easier to validate blocking incidents
     4. Show RuleId and ViolationId in Page if triggered and enabled

     26 August 2020
     1. Export FireWall base to the framework for custom implementation of IFireWall

     22 August 2020
     1. Alter default cookie names
     2. Set CRF token settings based on firewall settings
     3. update text report to associate fictitious user nr to incident details