ASVS 5.0 V6.1.2: Document Context Specific Password Words
Keep a documented list of words tied to your organization that users may not put in passwords. Level 2 guide with examples and a way to check it.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Keep a documented list of words tied to your organization that users may not put in passwords. Level 2 guide with examples and a way to check it.
Write down how rate limits, anti automation and adaptive responses stop credential stuffing without letting attackers lock out real users. Level 1 requirement.
Files from untrusted sources need an antivirus scan before you serve them to anyone else. Here is a quarantine pattern with ClamAV and how to test it. Level 2.
Filenames in headers and email attachments must be encoded under RFC 6266 so quotes, newlines and non ASCII characters cannot break structure. Level 2 guide.
Never let a user submitted filename reach your response unchecked. Validate or ignore it, and always set Content-Disposition yourself. Level 2 requirement with code and tests.
Server side extraction must ignore path information supplied by the archive entries. Resolve every target, verify containment, and refuse anything that escapes.
Never use a user supplied filename to build a path. Generate names yourself, or validate and canonicalize hard to stop path traversal, file inclusion and SSRF.
Files from users that land in a public folder must not run as scripts when requested. Store them outside the web root and serve them as inert data.
A tiny PNG can declare a billion pixels. Check image dimensions from the header and refuse anything over your limit before decoding.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.