Skip to content
Documentation

Continuous DAST Developer & SecOps Guide.

Everything you need to configure safe-by-default dynamic application security testing, OSINT reconnaissance, and Fix-as-Code remediation.

Product preview · some screens and examples use simulated data. Scan execution, payment processing, and compliance evidence require the documented services to be configured. See feature status and limitations.

Safe-by-Default Architecture

Traditional dynamic scanners execute indiscriminate payload fuzzing against web targets, often corrupting stateful databases, flooding payment gateways, or triggering collateral production outages. MIAN DAST enforces three mandatory cryptographic gates before any probe leaves the edge.

Gate 01Attestation Gate

Mandatory domain ownership verification via DNS TXT records (`_mian-attest.domain.com`), cloud tokens, or signed SOW before probes arm.

Gate 02Boundary Proxy Fence

Cryptographic proxy firewall dropping 100% of outbound probes targeting third-party vendor APIs (e.g. Stripe, SendGrid, Twilio, or CDN origins).

Gate 03Adaptive Latency Canary

Real-time baseline p95 telemetry probe. If production server latency spikes over 20% or returns HTTP 5xx, all probes immediately throttle and halt.

Safety design goal

Scope and non-destructive defaults are intended to reduce risk. They cannot guarantee that every target will be unaffected; validate authorization and test scans in staging before production use.