Common Security Design Pitfalls in System Architecture
The article outlines six major security design mistakes—compatibility, cost‑cutting, mixing data and code, closed designs, blacklist defenses, and neglecting security as a design goal—illustrating each with real‑world examples and offering practical recommendations to build more robust software and hardware architectures.
Just as organisms with inherent flaws are more vulnerable to pathogens, computer systems with architectural security flaws are easier to compromise; this article examines six common security design pitfalls across hardware, software, and infrastructure to help developers create safer, more resilient architectures.
Pitfall One – Compatibility Design: Over‑compatible interfaces, such as Apple’s USB‑C, can allow malicious devices to masquerade as keyboards, enabling attacks that cannot be patched without redesigning the interface. Designers should separate device classes and enforce authentication to prevent such privilege‑escalation vulnerabilities.
Pitfall Two – Cost‑Reduction Design: Over‑loading servers to save costs raises the risk of CC (Challenge Collapsar) DDoS attacks; insufficient redundancy can cause service collapse. Maintaining spare capacity and leveraging cloud elasticity mitigates this risk while still controlling expenses.
Pitfall Three – Data‑Code Co‑Location: Storing uploaded files on the same server that executes code creates a classic upload‑to‑WebShell vulnerability. Isolating storage on a separate, non‑executable file server or database eliminates the attack path.
Pitfall Four – Closed Design: Relying on proprietary encryption algorithms gives a false sense of security; they can be reverse‑engineered or leaked. Public, well‑vetted algorithms (e.g., RSA) combined with secret keys provide stronger protection.
y = F(x) // F is the encryption function, y ciphertext, x plaintext
x = [0 0.9375 1.8750 2.8125 3.7500 4.6875 5.6250 6.5625 7.5000 8.4375 9.3750 10.3125 11.2500 12.1875 13.1250 14.0625 15.0000];
y = [0.000000E+000 8.789063E-003 3.515625E-002 7.910156E-002 1.406250E-001 2.197266E-001 3.164063E-001 4.306641E-001 5.625000E-001 7.119141E-001 8.789063E-001 1.063477E+000 1.265625E+000 1.485352E+000 1.722656E+000 1.977539E+000 2.250000E+000];Pitfall Five – Blacklist Defense: Simple filtering for SQL injection and XSS is easily bypassed; instead, use parameterized queries and proper output encoding, reserving blacklist filters only as supplemental measures.
Pitfall Six – Ignoring Security as a Design Goal: Many architects underestimate attackers and treat security as optional, leading to accumulated hidden risks that can cause catastrophic breaches. Early incorporation of security objectives and consultation with security experts are essential.
Source: CSDN, author Fu Shanyang.
Qunar Tech Salon
Qunar Tech Salon is a learning and exchange platform for Qunar engineers and industry peers. We share cutting-edge technology trends and topics, providing a free platform for mid-to-senior technical professionals to exchange and learn.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
