Insecure design meaning, in plain words

Insecure design means protection was never built into the design before coding started. How it differs from coding bugs and how to reduce it, per OWASP, MITRE.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Insecure design is a problem where protection is missing at the design stage, before the building starts. It is not a coding slip. The difference is that the needed protection was never part of the design.

How does insecure design work?

Picture finishing a house without ever deciding where the front-door lock goes. However carefully the carpenter works, the result is an entrance without a lock.

OWASP Top 10:2021 explains that it added this category in 2021. It looks at flaws in design and structure rather than in code, and it urges wider use of threat identification, secure design patterns, and reference architectures. Implementation bugs can occur even under a secure design, and their causes and fixes differ, so they are handled separately.

One example is a member identity check that passes for anyone who knows the email address. However carefully inputs are validated, the hole stays unless the flow itself changes. Familiar examples are explained under business logic flaws.

Why does insecure design matter?

Adding parts or settings later does not easily fill a design hole. The later it is found after completion, the larger the work and cost to fix it. Nothing may look wrong in appearance or operation, so operation can continue without anyone noticing.

The measures OWASP lists center on what you do before and during building. For high-risk parts such as authentication, access control, and business flows, you identify weak points from an attacker's viewpoint (threat modeling). You write security conditions at the requirements stage and add tests that assume misuse.

Limiting how much each user or function may use is also part of design measures, and rate limiting is one example. When development is outsourced, tell the contractor which flows must be protected at the time of ordering.

If you are not sure which flows on your site need that review, contact us.

Related terms

  • Vulnerability: a weakness in a program or design that can become an entry for attack.
  • Rate limiting: narrowing how many requests are accepted when many arrive in a short time.
  • Business logic flaws: flaws where the design of a flow such as buying or registering has a loophole.
  • Broken authentication: a login mechanism that is weak enough to be broken through.

Next step

Specific examples of design holes are on the business logic flaws page. The free URL check shows only what is visible from outside. For reviewing the flows of purchase or member registration, contact us.

Frequently asked questions

Can an assessment tool find insecure design?

It is hard for tools alone. A hole such as being able to skip steps in a purchase flow is noticed only by a person who knows the specification and reads the flow. An assessment combines tool scans with checks by a person.

Can design flaws in a finished site be fixed?

Sometimes yes, and sometimes the cost comes close to rebuilding. First sort out the functions that must be protected and the places that are not. Then choose between reviewing the flow within a narrow range and rebuilding.

Frequently asked questions

Can an assessment tool find insecure design?

It is hard for tools alone. A hole such as being able to skip steps in a purchase flow is noticed only by a person who knows the specification and reads the flow. An assessment combines tool scans with checks by a person.

Can design flaws in a finished site be fixed?

Sometimes yes, and sometimes the cost comes close to rebuilding. First sort out the functions that must be protected and the places that are not. Then choose between reviewing the flow within a narrow range and rebuilding.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.