forms-shield/1.0.0 · updated Jul 9, 2026

Form protection

How to stop abuse, spam, and automated submissions without disrupting legitimate use.

Forms Shield observes interactions with critical forms and helps graduate verification, rate limiting, and blocking.

The key is to protect the surface without turning every form into an obstacle. ADDA therefore combines pace, user-agent, reputation, and recent-event signals with an explainable outcome.

When the same pressure appears on several routes or in coordinated variations, move from forms-shield to WAF, an incident, or intelligence.

Checklist

• Identify critical forms and submission routes.
• Review recent events before increasing friction.
• Escalate to WAF or an incident if the pattern becomes repeatable.

Quickstart

1. Identify which forms concentrate abuse or sensitive volume.
2. Review recent events and adjust friction by priority, not intuition.
3. Escalate evidence if protection affects operations or relevant users.

Operational flow

Observe

Read shield events and patterns of capture or bulk submission.

Distinguish noise from sustained pressure.

Graduate friction

Apply verification or limiting before blocking while trust remains partial.

Preserve the legitimate experience.

Escalate

If abuse persists, connect WAF, tasks, or an incident to coordinate the response.

Do not leave the defense confined to the same surface.

flowchart LR
  S1["Observe"]
  S2["Graduate friction"]
  S3["Escalate"]
  S1 --> S2
  S2 --> S3

Validators and checks

They run a contextual reading for this surface and return suggested steps with an operational focus.

Validate form coverage

Reads recent events and recommends the shield's next steps.

Examples

Payload for an abuse manual candidate

{
  "title": "Refuerzo forms shield",
  "sourceType": "forms_shield_event",
  "sourceRef": "/contacto",
  "summary": "El formulario de contacto recibe envíos automatizados repetidos desde varias IP."
}

Links and references

APIs

/api/adda/v1/shields/events
/api/adda/v1/brand-shield/check
/api/adda/v1/tasks

Docs and supporting routes

docs/ADDA_WAF.md
docs/ADDA_API.md

Common issues

• Adding captchas or friction without reviewing the false-positive rate worsens the experience.
• Failing to cross-check forms-shield with mail and WAF leaves multichannel campaigns unexplained.

Suggested actions

• Sample events before changing policies.
• Connect the finding to an incident or manual candidate if a procedural gap appears.

Useful reason codes

Score dictionary

wafRiskScore

Risk detected on the observed route or form.

decision

Decided action: allow, verify, limit, or block.

matchedRules

Rules that explain why protection was activated.

Protocol notes

• Good form defense reduces abuse without making legitimate users invisible.

Article history

Jul 9, 2026

Added an article for the forms-shield surface with a quickstart, validation, and escalation guidance.