Katalog CWE

CWE-1059 · Słabość

Insufficient Technical Documentation

Abstrakcja
Klasa
Status
Niekompletny
Dodano
2 lipca 2018
Ostatnia zmiana
9 września 2025

Podatności CVE z tą słabościąPełny wpis na cwe.mitre.org ↗

Opis

The product does not contain sufficient technical or engineering documentation (whether on paper or in electronic form) that contains descriptions of all the relevant software/hardware elements of the product, such as its usage, structure, architectural components, interfaces, design, implementation, configuration, operation, etc.

When technical documentation is limited or lacking, products are more difficult to maintain. This indirectly affects security by making it more difficult or time-consuming to find and/or fix vulnerabilities.

When using time-limited or labor-limited third-party/in-house security consulting services (such as threat modeling, vulnerability discovery, or pentesting), insufficient documentation can force those consultants to invest unnecessary time in learning how the product is organized, instead of focusing their expertise on finding the flaws or suggesting effective mitigations.

With respect to hardware design, the lack of a formal, final manufacturer reference can make it difficult or impossible to evaluate the final product, including post-manufacture verification. One cannot ensure that design functionality or operation is within acceptable tolerances, conforms to specifications, and is free from unexpected behavior. Hardware-related documentation may include engineering artifacts such as hardware description language (HDLs), netlists, Gerber files, Bills of Materials, EDA (Electronic Design Automation) tool files, etc.

Skutki

  • Other

    Varies by Context; Hide Activities; Reduce Reliability; Quality Degradation; Reduce Maintainability

    Without a method of verification, one cannot be sure that everything only functions as expected.

Zapobieganie

  • Documentation, Architecture and Design

    Ensure that design documentation is detailed enough to allow for post-manufacturing verification.

Przykłady podatności

Słabość nadrzędna

Słabości podrzędne

Kiedy powstaje

Dotyczy

Not Language-Specific, Not OS-Specific, Not Architecture-Specific, Not Technology-Specific, ICS/OT

Źródła

  1. Categories of Security Vulnerabilities in ICS — Securing Energy Infrastructure Executive Task Force (SEI ETF), Poorly Documented or Undocumented Features, 2022
  2. Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions Draft Guidance for Industry and Food and Drug Administration Staff (DRAFT GUIDANCE) — FDA, 2022

Wpis z katalogu CWE 4.20.