Patterns used for discovering when some one or something thinks he knows a url used to process payments
During development you are able to test if you URL's to see if they are getting blocked and adjust the lists accordingly.
The following code sample show how such detection could be structured using the IFireWall or FireWallBase.OnIncident event
private void FireWall_OnIncident(object sender, FireWallIncidentEventArgs e)
{
switch (e.StackEntry.Reason)
{
case Walter.BOM.FirewallBlockReasons.PenetrationAttempt:
if (Enum.TryParse<Walter.Web.FireWall.RuleEngine.UrlValidatedResult>(e.Data[IncidentAssertType.RuleNr], out var list))
{
_logger?.Lazy().LogCritical("Url triggered {pattern} in {location} in Configuration.Rules.blockedPatterns.{list}"
, e.Data[IncidentAssertType.Pattern]
, e.Data[IncidentAssertType.Location]
, list);
LogTodo<ConfigurationTasks>(ConfigurationTasks.UrlNotValid, $"Update Configuration.Rules.blockedPatterns.{list} on {e.Data[IncidentAssertType.Pattern]} at the {e.Data[IncidentAssertType.Location]} in URL{e.Page.OriginalUrl}",false);
}
break;
// your other specialized tests
default:
base.LogTodo<ConfigurationTasks>(ConfigurationTasks.Setup, message: $"Test Rule \"{e.StackEntry.Rule}\" on {e.Page.OriginalUrl}", optional: true);
break;
}
}
Target Platforms: Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2