ProficientNowTechRFCs

6. WAF Architecture

RFC-TENANT-SECURITY-0001                                         Section 6
Category: Standards Track                                  WAF Architecture

6. WAF Architecture

← Ingress Security | Index | Next: Network Policies →


6.1 WAF Overview

6.1.1 Purpose

The Web Application Firewall provides protection against common web attacks by inspecting HTTP traffic and blocking malicious requests before they reach applications.

6.1.2 Protection Scope

Attack CategoryProtection MethodOWASP Reference
SQL InjectionSignature detectionA03:2021
Cross-Site ScriptingInput validationA03:2021
Command InjectionPattern matchingA03:2021
Path TraversalPath normalizationA01:2021
Protocol ViolationsRequest validationA05:2021
Scanner DetectionBehavioral analysis
Bot TrafficChallenge verification

6.2 Rule Architecture

6.2.1 Rule Hierarchy

6.2.2 Rule Categories

CategorySourceAuthorityOverride Permitted
OWASP CRSOWASP ProjectSecurity TeamNo
Custom GlobalSecurity TeamSecurity TeamNo
Application ExceptionsTenant + SecuritySecurity Team ApprovalWith approval
Application RulesTenantSecurity Team ApprovalWith approval

6.2.3 OWASP CRS Coverage

The OWASP Core Rule Set provides protection against:

Rule GroupProtection
900Initialization and configuration
910Method enforcement
911HTTP protocol validation
913Scanner detection
920Protocol enforcement
921Protocol attack
930Local file inclusion
931Remote file inclusion
932Remote code execution
933PHP injection
934Node.js injection
941Cross-site scripting
942SQL injection
943Session fixation
944Java injection

6.3 Operating Modes

6.3.1 Mode Definitions

ModeBehaviorUse Case
DetectionLog threats, allow trafficNew rule testing, baseline
PreventionBlock threats, log eventsProduction protection
DisabledNo processingEmergency bypass only

6.3.2 Mode Transitions

Per INV-4, rule changes MUST follow this transition path:

6.3.3 Mode Authority

TransitionAuthorityApproval Required
Detection → PreventionSecurity TeamYes
Prevention → DetectionSecurity TeamNo (safety valve)
Any → DisabledPlatform TeamEmergency only
Disabled → DetectionSecurity TeamYes

6.4 Exception Management

6.4.1 Exception Types

TypeScopeUse Case
Rule DisableSpecific rule IDKnown false positive
Path ExclusionURL path patternAPI endpoints with unusual payloads
IP WhitelistSource IPTrusted internal systems
Parameter ExclusionSpecific parameterField contains code/scripts

6.4.2 Exception Lifecycle

6.4.3 Exception Requirements

RequirementDescription
JustificationDocument why exception is needed
Scope LimitationNarrowest possible scope
Time LimitExceptions SHOULD have expiry dates
Audit TrailAll exceptions version controlled (INV-13)
Periodic ReviewExceptions reviewed quarterly

6.5 Bot Mitigation

6.5.1 Bot Detection Signals

SignalDetection Method
Request RateAbnormal request frequency
User AgentKnown bot signatures
BehaviorNon-human interaction patterns
IP ReputationKnown malicious sources
TLS FingerprintAutomated client signatures

6.5.2 Challenge Types

ChallengeMechanismUser Impact
CookieSet and verify cookieTransparent
JavaScriptExecute JS verificationTransparent
CAPTCHAImage/text challengeUser interaction
hCaptchaPrivacy-focused challengeUser interaction
reCAPTCHAGoogle challengeUser interaction
TurnstileCloudflare challengeMinimal interaction

6.5.3 Challenge Flow


6.6 IP Reputation

6.6.1 Reputation Sources

SourceTypeUpdate Frequency
DNSBLDNS-based blocklistReal-time
External BlacklistsIP listsPeriodic
Internal BlacklistManual entriesOn-demand
BehavioralAuto-ban from behaviorReal-time

6.6.2 Reputation Actions

ReputationAction
BlacklistedBlock immediately
SuspiciousIssue challenge
UnknownNormal processing
WhitelistedBypass bot checks

6.7 Logging and Alerting

6.7.1 Log Events

Event TypeContentDestination
Blocked RequestFull request, rule matched, source IPSIEM
Detected ThreatRequest details, rule, detection modeSIEM
Challenge IssuedSource IP, challenge typeLogs
Challenge FailedSource IP, failure reasonSIEM
IP BannedSource IP, ban reason, durationSIEM

6.7.2 Alert Conditions

ConditionSeverityResponse
High block rateWarningInvestigate traffic
New attack patternWarningReview rules
WAF bypass attemptCriticalImmediate review
Mass bot trafficWarningReview rate limits

6.7.3 Compliance Logging

Per INV-9, blocked request logs MUST include:

FieldPurpose
TimestampEvent timing
Source IPAttack origin
Target URLAttack target
Rule IDWhat triggered block
Request excerptEvidence (sanitized)
Action takenBlock, log, challenge

6.8 OWASP Coverage Matrix

6.8.1 OWASP Top 10 2021

RiskWAF CoverageApplication Coverage
A01: Broken Access ControlPath-based rulesAuthorization logic
A02: Cryptographic FailuresTLS enforcementKey management
A03: InjectionFull CRS coverageParameterized queries
A04: Insecure DesignLimitedApplication architecture
A05: Security MisconfigurationProtocol rulesConfiguration management
A06: Vulnerable ComponentsLimitedDependency scanning
A07: Auth FailuresRate limitingAuthentication logic
A08: Software IntegrityLimitedSupply chain security
A09: Logging FailuresWAF loggingApplication logging
A10: SSRFEgress rulesInput validation

6.8.2 OWASP API Top 10 2023

RiskWAF CoverageNotes
API1: Broken Object Level AuthorizationLimitedApplication responsibility
API2: Broken AuthenticationRate limitingApplication responsibility
API3: Broken Object Property Level AuthorizationNoneApplication responsibility
API4: Unrestricted Resource ConsumptionRate limitingFull coverage
API5: Broken Function Level AuthorizationNoneApplication responsibility
API6: Unrestricted Access to Sensitive Business FlowsRate limitingPartial coverage
API7: Server Side Request ForgeryEgress policiesNetwork policy support
API8: Security MisconfigurationProtocol rulesConfiguration management
API9: Improper Inventory ManagementNoneAPI management tooling
API10: Unsafe Consumption of APIsEgress policiesApplication responsibility

Document Navigation


End of Section 6