Prevent regular-expression denial of service

Prevent regular-expression denial of service is easiest to get right when the boundary is named before the implementation begins. Decide which system owns the decision, which inputs are trusted, what the caller can observe, and what must remain private. That framing prevents a local optimization from quietly becoming an undocumented protocol.

Regular expressions are compact programs. Some patterns take exponential time when a carefully chosen input forces the engine to explore many overlapping paths. A public regex tester, search filter, validation endpoint, or log parser can therefore become a denial-of-service surface even when the pattern itself looks ordinary.

Decide whether users may supply patterns, input strings, or both. Prefer a linear-time engine for untrusted patterns, and enforce a maximum pattern length, input length, execution time, and concurrency. Keep regex work off the request thread when a timeout cannot interrupt the engine safely. Do not let a pattern control filesystem, database, or authorization logic.

Write the model down as a small state diagram or table before selecting a library. Identify the durable state, the derived state, and the transitions that may be retried. This makes it easier to compare a managed service with an in-process implementation and to explain why a particular trade-off is acceptable for this workload.

Nested quantifiers, overlapping alternations, ambiguous groups, and backreferences are common warning signs, but visual inspection is unreliable. A pattern can be safe for typical input and pathological for a crafted suffix. Unicode modes and large input can change performance. A timeout that merely stops waiting may leave the engine consuming CPU in another thread.

A resilient design assumes that inputs are incomplete, dependencies are slow, operators make mistakes, and requirements will change. Put limits at the boundary, return errors that a caller can act on, and preserve enough context to distinguish a bad request from an unavailable dependency. Avoid broad fallbacks that make an unsafe state look successful.

Compile patterns in a bounded worker or use a safe engine with an explicit feature subset. Reject unsupported constructs with a clear message and measure the match budget. Cache only validated compiled patterns and include the tenant or user in the quota decision. Return a timeout result that is distinct from no match, and never retry a timed-out match automatically.

Keep the first implementation narrow enough to review line by line. Make inputs, outputs, authorization context, and failure behavior explicit instead of hiding them behind a convenience helper. The example should be safe to run with synthetic data, emit a correlation identifier, and leave a durable artifact that another engineer can inspect after the request has finished.

Use a corpus of known pathological patterns and generate adversarial input around repeated prefixes and suffixes. Measure CPU, wall time, memory, and worker occupancy under concurrency. Test invalid syntax, Unicode, empty input, maximum lengths, and cancellation. Confirm a rejected or timed-out pattern cannot delay unrelated requests.

Use a small test matrix that covers the ordinary path, an empty or missing input, a duplicate request, a timeout, a permission failure, and a version mismatch. Assert both the response and the side effects. When a test fails, compare the observed transition with the model rather than adding a retry or widening a timeout without evidence.

Monitor match duration percentiles, timeouts, worker saturation, rejected pattern counts, and per-identity usage. Keep a kill switch for user-supplied patterns and a safe fallback for essential validation. Review regex dependencies and engine versions. A public tester should advertise its limits so users do not assume it can evaluate arbitrary production patterns safely.

Give the operator a bounded recovery action: replay a safe event, rebuild a derived view, rotate a credential, drain a queue, or roll back a compatible revision. Record the owner, retention period, alert threshold, and rollback condition next to the implementation. A runbook is useful only when it can be followed without reconstructing the design from production logs.

For a small service, prefer the design with the fewest hidden states that still meets the application security requirement. Add a managed dependency when it removes a failure mode you can measure, not simply because it is popular. Keep the interface replaceable by isolating provider-specific code behind a narrow adapter and by testing the behavior your users depend on.

Revisit the decision when traffic shape, data sensitivity, team ownership, or recovery objectives change. A design that is excellent for a single tenant or a low-volume internal tool can be the wrong design for a public multi-tenant path. Record the assumptions so the next change starts with evidence rather than folklore.

Before publishing a change related to prevent regular-expression denial of service, write down the input contract, authorization context, state transitions, limits, and user-visible errors. Identify the smallest synthetic dataset that demonstrates the normal path and the smallest dataset that demonstrates the dangerous path. Add a correlation ID to the example, make retries deliberate, and decide which artifacts can be retained for support without copying secrets or unnecessary personal data. This checklist is deliberately boring: repeatable release evidence is more valuable than a clever demo.

Use a disposable environment to exercise the implementation with realistic concurrency and a dependency failure. Compare the observed result with the contract, then record the measured latency, resource use, and recovery action. If a managed service or library is involved, pin its version and capture the relevant configuration. Ship behind a reversible change when the behavior is new, and schedule a follow-up review after real traffic reveals assumptions that a test fixture could not.

Use the OWASP Regular Expression Denial of Service guidance, the safe-regex research and tooling for your language, and the selected engine's feature and timeout documentation. Prefer a linear-time engine when the input is attacker-controlled.

Prefer primary protocol specifications, vendor security documentation, and measured behavior from a disposable environment. Read the failure and deprecation sections, not only the happy-path quick start. A short reference list attached to the code gives future maintainers a way to distinguish an intentional constraint from an accidental implementation detail.