CWE-655 Insufficient Psychological Acceptability
A security control people find too hard to use gets turned off or worked around. Usability is part of whether a protection actually protects.
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.
A security control people find too hard to use gets turned off or worked around. Usability is part of whether a protection actually protects.
If one stolen or spoofed factor unlocks everything, the whole control fails with it. Layer independent checks at more than one choke point.
When privilege levels share one boundary, a bug in the low-privilege part becomes a bug in the high-privilege part. Split modules and guard the seams.
Building XQuery strings from user input lets attackers change the query itself. Bind variables and validate input to keep data separate from logic.
A publicly reachable WSDL can reveal private methods and deprecated services. Limit who can fetch it and keep internal names out of it.
Assuming GET never changes state lets attackers modify or delete data through endpoints that only block POST, PUT and DELETE.
A program that opens files by name can be tricked into using a hard link to a sensitive target. CWE-65 is the Windows version of that mistake.
Encrypting or scrambling a client-side token does not stop tampering. Without an integrity check, attackers just search for a value that works in their favor.
Calling a privileged function with bad arguments, from a bad state, or without shedding privileges afterward hands attackers an escalation path.
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.