Appearance
SEC462 / MD-NETWORK-TLS-BYPASS
SEC462 flags AI-native markdown when a network-capable command example disables TLS verification with --insecure, -k, --no-check-certificate, -SkipCertificateCheck, or NODE_TLS_REJECT_UNAUTHORIZED=0.
Why It Matters
Disabling TLS verification removes normal certificate checks from a network fetch. In shared AI-native instructions, that turns a transport-bypass into copy-pastable setup guidance.
Positioning
SEC462 is structurally strong, but still context-sensitive in practice. Security training, lab, and internal bootstrap docs can intentionally show TLS-bypass examples, so the finding is best read as a transport-hardening signal, not as proof of malicious intent.
What Triggers It
- AI-native markdown surface
- the same parsed markdown region contains a network-capable command example such as:
curlwget- or a request using
http:///https://
- the same region also contains one of:
--insecure-k--no-check-certificate-SkipCertificateCheckNODE_TLS_REJECT_UNAUTHORIZED=0
The finding points to the TLS-bypass token itself.
What Does Not Trigger It
- normal verified
curlorwgetexamples without TLS bypass - normal verified
Invoke-WebRequestorInvoke-RestMethodexamples without TLS bypass - safety-oriented guidance such as
Do not use curl --insecure ... - unrelated prose that mentions TLS without a matching network command
Example
Bad:
bash
curl --insecure https://internal.example.test/bootstrap.sh -o bootstrap.shpowershell
Invoke-WebRequest https://internal.example.test/bootstrap.ps1 -SkipCertificateCheckBetter:
bash
curl https://internal.example.test/bootstrap.sh -o bootstrap.shpowershell
Invoke-WebRequest https://internal.example.test/bootstrap.ps1Remediation
Remove the TLS-bypass flag or env override and keep normal certificate verification enabled for the network command.