A.8.30 Technological
Outsourced development
Structured attributes from ISO/IEC 27002:2022 — control type · CIA properties · cybersecurity concept · operational capability · security domain. What do these mean?
Mapped NIST 800-53 r5 controls (17)
Our reading (mostly llm_verified) of how this ISO control and each NIST 800-53 control relate. Not an ISO or NIST product.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- SA-4explicit mandateimplements — A.8.30 directly requires security measures in outsourced development; SA-4 operationalizes this by mandating that those exact security, assurance, and control requirements be explicitly included in the acquisition contract for the outsourced system/service.
- SA-9domain mandateimplements — Both controls require the organization to impose security and privacy requirements on external development providers and to verify that those requirements are met through ongoing oversight and evidence.
Aligned NIST CSF 2.0 outcomes (20)
NIST CSF 2.0 outcomes this ISO control aligns with — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- GV.SC-05domain mandateimplements — The ISO control’s contractual clauses for secure design, coding, testing, and audit rights directly implement the CSF requirement to embed cybersecurity requirements into supplier contracts.
- PR.PS-06domain mandateimplements — A.8.30 directly operationalizes secure outsourced development practices (a core slice of PR.PS-06's integrated-and-monitored SDLC practices) within the CSF outcome's domain
Related OWASP ASVS 5.0 requirements (10)
Application-security verification requirements (OWASP ASVS 5.0) this ISO control aligns with; links open the ASVS chapter. Our analysis (mostly llm_verified) — many ISO controls have no ASVS counterpart.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Related weaknesses / CWE (3235)
Weakness classes this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- CWE-1004partialprevents — A.8.30 carries its effect through the secure-coding practices (8.28) its contract requires of the supplier, which include proper cookie attribute handling; this reduces instances of the HttpOnly omission in delivered code the way secure coding does, but the practice is fallible and the clause sits at its declared ceiling of `partial`.
- CWE-1007partialprevents — A.8.30 carries its preventive effect through the contractual requirements it places on the supplier for secure design, coding and testing practices (8.25–8.29), so a faithfully implemented clause reduces instances of this regular software/UI weakness in delivered code the way those practices do — but the effect depends on the supplier implementing those practices correctly and the contract may not specifically address homoglyph handling, leaving a nameable remainder.
- CWE-1021partialprevents — A.8.30 carries secure coding (8.28) and security testing (8.29) into the supplier contract, so clickjacking protections (X-Frame-Options, CSP frame-ancestors) are required of outsourced web development the same way those practices are; the effect is partial because it depends on supplier implementation rigour and the clause's ceiling on software weaknesses is partial.
- CWE-1022partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-1022 is a regular web-application design/coding defect (missing rel="noopener noreferrer") that secure-coding guidance reaches, but the clause mandates a practice rather than a mechanism, so what is covered is a slice the implementer chose rather than the bulk, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-1022partialfinds — A.8.30's programme reaches CWE-1022 only through the testing its contract requires of the supplier (acceptance testing per 8.29, evidence of testing for malicious content and known vulnerabilities); the clause is a contractual wrapper, not a direct testing mechanism, so the share found depends on whether the supplier's testing programme includes web-application SAST/DAST that detects missing rel='noopener noreferrer' — a minority of instances in a representative outsourced engagement.
- CWE-1024partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a faithful implementation reduces ordinary software weaknesses like type-comparison defects in delivered code the way those practices do, at `partial`; the clause's declared ceiling on this verb is `partial`.
- CWE-1025partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-1025 is a regular code-level comparison defect that secure coding practice would catch, but the clause's effect is mediated by fallible human practice and depends on other controls, capping it at the clause's declared ceiling of `partial`.
- CWE-104partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software CWEs in delivered code the way those practices do; CWE-104 is a regular Java/Struts implementation defect reachable by secure coding guidance, but the clause's effect is mediated by the supplier's practice and is bounded at `partial`.
- CWE-1043partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, and code review under those practices can flag excessively complex data structures as a code-quality issue; however, CWE-1043 is a performance/quality concern rather than a security one, so security-focused review catches only a minority of instances.
- CWE-1045partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25–8.29) in outsourced work, and those practices catch some instances of this C++ destructor-hierarchy defect during code review and testing, but the weakness is subtle and language-specific, so most instances slip through.
- CWE-1046partialprevents — A.8.30 carries secure coding practices (8.25-8.29) into outsourced development via contractual requirements, and secure coding guidance addresses code-quality issues like string concatenation in loops, so some instances are kept out of delivered code; the clause's ceiling on this verb is `partial` and the mechanism is fallible human practice, with performance issues often deprioritized relative to security concerns.
- CWE-1047partialprevents — Following the A.8.30 -> CWE-134 anchor: the clause carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reaches regular software CWEs at partial. CWE-1047 is a code-structure/maintainability weakness introduced in implementation and design, and good secure design and coding practices can discourage circular module dependencies, but the practice is fallible and the weakness is not the primary target of those practices.
- CWE-1048partialprevents — A.8.30 carries its preventive effect through the secure design and coding practices (8.25-8.29) it contracts from the supplier, which can reduce code-quality weaknesses like excessive Fan-Out in delivered code, but the clause depends on those downstream controls being implemented and Fan-Out is a structural metric that survives ordinary secure-coding practice.
- CWE-105partialprevents — A.8.30 carries secure coding and testing requirements (8.25–8.29) into the supplier contract, which reduces ordinary software implementation defects like missing Struts validators, but the effect is indirect and depends on the supplier's practice, matching the owner's `partial` grade on A.8.30 vs CWE-134 for the same reason.
- CWE-1051partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-1051 is a regular software CWE introduced at implementation, and the same `partial` ceiling that applies to A.8.30 -> CWE-134 applies here.
- CWE-1052partialprevents — A.8.30 contracts secure coding practices (8.25-8.29) into outsourced development, and coding standards that govern literal usage in initialization would reduce instances of CWE-1052 in delivered code, but the clause's effect is mediated through supplier practice and reaches only a minority of cases.
- CWE-1054partialprevents — A.8.30 carries its effect through the secure design and coding practices its contract requires of the supplier (8.25–8.29), which touch architectural layering decisions during implementation, but CWE-1054 is a subtle maintainability concern that secure coding practice does not directly target, so only a minority of instances are kept from arising.
- CWE-1056partialprevents — A.8.30 contracts secure coding practice (8.25–8.29) into outsourced development, which reaches a software-implementation weakness like variadic parameter signatures the same way it reaches CWE-134, but only through fallible supplier practice at the partial ceiling established for this clause.
- CWE-1057partialprevents — A.8.30 carries its preventive effect through the secure design and coding practices (8.25-8.29) it contracts from the supplier, which reach ordinary software implementation weaknesses including architectural-pattern violations like bypassing the central data manager, but only at the partial rung the owner set for this clause on software CWEs.
- CWE-1058partialprevents — A.8.30 carries its preventive effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, and CWE-1058 is an ordinary implementation-phase coding defect that those practices reach; the clause's ceiling on this verb is `partial` because the supplier's practices are fallible.
- CWE-106partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25–8.29) its contract requires of the supplier, so an outsourced Struts application developed under those requirements is more likely to use the Validator framework, but the practice is fallible and the clause depends on other controls being implemented, leaving a nameable remainder.
- CWE-1060partialprevents — A.8.30 contracts secure design and coding practices (8.25–8.29) into outsourced development, which addresses inefficient data-access patterns in delivered code the way those practices do; the effect is partial because the clause depends on the supplier implementing those practices faithfully and human practice is fallible, matching the ceiling established for A.8.30 on CWE-134.
- CWE-1062partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reaches ordinary software CWEs at the clause's ceiling of `partial`; CWE-1062 is a code-structure weakness in object-oriented design that secure coding guidance can reduce but not eliminate.
- CWE-1063partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary code-level weaknesses in delivered code the way those practices do; CWE-1063 is an implementation-phase code pattern that secure coding guidance and code review would catch in a minority of instances, with the remainder bounded by the fallibility of the contracted practices and the supplier's implementation rigour.
- CWE-1064partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software CWEs in delivered code the way those practices do; CWE-1064 is an implementation-phase code-quality issue that secure coding standards may address via parameter-count limits, but the clause's reach is indirect and bounded by what the contracted practices actually cover.
- CWE-1065partialprevents — A.8.30 carries secure coding and testing practices (8.25–8.29) into outsourced development via contractual requirements, which can reduce implementation-phase weaknesses like bypassing the application server's resource management API, but the clause's effect depends on the supplier's actual practice and the ceiling for A.8.30 on regular software CWEs is `partial`.
- CWE-1066partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like a missing serialization method at `partial`; the clause's ceiling on this verb is `partial` because it depends on those other controls being implemented.
- CWE-1067partialprevents — A.8.30 carries its effect through the secure design and coding practices its contract requires of the supplier (8.25–8.29), which can include proper database indexing in outsourced code; the effect is real but limited because CWE-1067 is primarily a performance concern rather than a security one, and the clause's reach depends on the supplier's implementation of those practices.
- CWE-1068partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software quality weaknesses in delivered code the way those practices do; acceptance testing (8.29) can catch some implementation-vs-design inconsistencies, but the clause does not specifically mandate design-to-implementation traceability, leaving a nameable remainder.
- CWE-107partialprevents — A.8.30 carries its effect through the secure-coding (8.28) and security-testing (8.29) practices its contract requires of the supplier, which reach ordinary code defects in delivered Java/Struts code the way those clauses do; CWE-107 is a specific maintenance-hygiene defect (forgetting to remove unused validation forms on refactor) that those practices only partially catch.
- CWE-1074partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-1074 is an implementation-phase code-quality defect that secure coding standards reach, but the supplier's practices are fallible and the clause's ceiling on this verb is `partial`.
- CWE-1075partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25-8.29) in outsourced development, so it carries its effect through those practices the way the CWE-134 anchor established; secure coding standards that prohibit unconditional control flow transfers outside switch blocks would prevent this weakness in delivered code, but the effect depends on the rigour of the contracted practices and is bounded by the same fallibility that caps A.8.28 itself.
- CWE-1077partialprevents — A.8.30 carries its effect through the secure-coding and secure-testing practices its contract requires of the supplier (8.25–8.29), so a faithfully implemented clause reduces ordinary implementation-phase code defects like CWE-1077 at the same `partial` rung those practices reach on their own — fallible human practice catches a minority of instances.
- CWE-1079partialprevents — A.8.30 carries its effect through contractual requirements for secure coding practices (8.25-8.29) imposed on the supplier, so a well-implemented clause reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-1079 is a regular OO coding defect reachable by secure-coding standards, but the clause's ceiling on `prevents` is `partial` because the effect depends on the supplier's actual practice and is bounded by what the contract reaches.
- CWE-108partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a Struts validation-form defect — an ordinary software implementation weakness — is reduced the way those practices reduce it, at `partial`; the clause sits at its declared ceiling on this verb.
- CWE-1082partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-1082 is a regular code-level defect that secure coding and testing practices reach, but only partially because the effect depends on the supplier's faithful implementation of those contracted practices.
- CWE-1083partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts into outsourced development, and CWE-1083 is an implementation-phase architectural-discipline weakness that those practices would catch in delivered code; the grade sits at the clause's `partial` ceiling because the effect is indirect and depends on the rigour of the contracted practices.
- CWE-1084partialprevents — A.8.30 carries secure coding and testing practices (8.25–8.29) into outsourced development via contractual requirements, which reduces code-level quality weaknesses like excessive data-access operations in delivered code, but the effect is mediated through the supplier's implementation of those practices and the clause has no direct mechanism against this specific maintainability defect.
- CWE-1086partialprevents — A.8.30 carries its preventive effect through the secure-development practices (8.25-8.29) it contracts from the supplier, and code review/testing during development can catch some instances of excessive child classes, but this is a maintainability/structure metric that secure coding practices do not directly target, leaving a nameable remainder.
- CWE-1087partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25-8.29) in outsourced development, so a supplier implementing those practices faithfully will produce fewer C++ virtual-destructor defects, but the effect is indirect and the practices are fallible, matching the same `partial` ceiling the owner set for A.8.30 -> CWE-134.
- CWE-1088partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a faithful implementation reduces instances of this code-level defect the way those practices do — but the clause depends on those other controls and the practice is fallible, leaving a nameable remainder.
- CWE-109partialprevents — A.8.30 carries its effect through the secure-coding and testing practices its contract requires of the supplier (8.25–8.29), so an outsourced Struts implementation under a faithful A.8.30 contract is less likely to ship with validate="false"; the ceiling is `partial` because the clause depends on the supplier's implementation of those practices and on the acceptance testing catching what slips through.
- CWE-1090partialprevents — A.8.30 carries its effect through the secure-coding practices its contract requires of the supplier (8.25–8.29), which can reduce encapsulation violations in delivered code the way those practices do, but the effect is indirect and depends on the rigour of the supplier's implementation, leaving most instances untouched.
- CWE-1092partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces architectural design weaknesses in delivered code the way those practices do; CWE-1092 is a design-phase reuse choice that secure design guidance can influence but not eliminate, leaving a nameable remainder.
- CWE-1094partialprevents — A.8.30's contractual requirements for secure coding/testing (8.25-8.29) and acceptance testing for quality and accuracy reach this implementation-phase performance defect only as a side effect of general code review and quality testing; the clause's mechanism is security-focused, so most instances of an excessive index range scan are not caught before delivery.
- CWE-1097partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-1097 is an ordinary implementation defect (missing comparison methods on a storable data element) that secure coding and testing would catch in a minority of instances, matching the A.8.30 -> CWE-134 anchor at the clause's declared ceiling.
- CWE-1098partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), reducing ordinary software implementation weaknesses in delivered code the way those practices do; CWE-1098 is a pointer-handling defect introduced at implementation, which those practices reach at the same `partial` rung as CWE-134, with the clause's declared ceiling of `partial` on this verb.
- CWE-1099partialprevents — A.8.30 carries its preventive effect through the contractual requirement for secure coding practices (8.25–8.29), and coding standards required of the supplier may include naming conventions; the effect is real but a minority one, since naming consistency is a code-style/maintainability concern peripheral to the security focus of those practices and depends on what the contract specifies.
- CWE-11partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-11 is a build/configuration defect that secure coding guidance and acceptance testing reach, but the clause's ceiling on this verb is `partial`.
- CWE-110partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, and a well-implemented supplier programme of secure coding plus security testing would catch most Struts validator/form-field drift before delivery; the clause has a declared ceiling of `partial` on this verb, and the remainder is the fallibility of contracted practice plus the cases where the supplier's implementation of 8.25–8.29 is weak.
- CWE-1100partialprevents — A.8.30 carries its effect through the contractual requirement for secure design, coding and testing practices (8.25-8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-1100 is a software architecture/design weakness that secure design guidance would address, but only partially because the clause depends on the supplier actually implementing those practices and CWE-1100 is more a maintainability/architecture concern than a direct security defect.
- CWE-1104partialprevents — A.8.30's contractual requirements for secure design, coding and testing practices (items b, g) can require the outsourced supplier to use maintained third-party components and provide evidence of testing for known vulnerabilities, carrying the same indirect effect the owner graded for A.8.30 -> CWE-134; the remainder is the clause's reliance on supplier compliance and its scope limited to outsourced development work, not the organization's own component choices.
- CWE-1105partialprevents — A.8.30 carries secure design, coding and testing practices (8.25–8.29) into outsourced development via contract, so it reduces ordinary software implementation weaknesses like insufficient encapsulation of machine-dependent functionality the way those practices do, but only at the clause's declared ceiling of partial because the effect depends on supplier implementation.
- CWE-1107partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) it contracts from the supplier, and secure coding standards can include guidance on code organization including constant placement; CWE-1107 is primarily a maintainability concern that indirectly affects security, so the clause reaches only a minority of instances at its declared ceiling.
- CWE-1108partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software CWEs in delivered code the way those practices do; excessive reliance on global variables is a coding-style weakness that secure coding guidance (8.28) reaches only partially, and the clause sits at its declared ceiling of `partial` on this verb.
- CWE-1109partialprevents — A.8.30 contracts for secure coding practices (8.25-8.29) from the supplier, which through code review and coding standards would catch some instances of variable reuse, but the effect is mediated by a fallible supplier implementation and the clause carries a declared ceiling of `partial` on this verb.
- CWE-111partialfinds — A.8.30's programme contracts for the supplier's secure development and testing practices (8.25–8.29), requires acceptance testing (d), and grants audit rights (i), so a faithful implementation surfaces some CWE-111 instances through the supplier's source-reading tests and the organization's acceptance/audit activities; however, the clause does not itself perform testing, acceptance testing is framed for quality and accuracy rather than security specifically, and the finding share depends on how the requirements are specified and audited, leaving a nameable remainder.
- CWE-1113partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), and secure coding standards typically include comment-style conventions, so a faithfully implemented clause reduces instances of this weakness in delivered code; the effect is indirect (CWE-1113 is a maintainability issue that only indirectly affects security) and depends on the supplier's actual coding standards, leaving a nameable remainder.
- CWE-1114partialprevents — A.8.30 contracts for secure coding practices (8.25–8.29), and coding standards typically cover whitespace style, so a supplier under the clause will produce more consistent whitespace than one without it; the effect is mediated through 8.28 and is fallible, leaving a nameable remainder of inconsistent style that survives review, matching the A.8.30 -> CWE-134 anchor's reasoning for ordinary software CWEs.
- CWE-1119partialprevents — A.8.30 contracts for secure coding practices (8.25–8.29) in outsourced development, which would include coding-style guidance discouraging excessive unconditional branching, so it carries some preventive effect into delivered code the way those practices do — but the effect is a minority one because it depends on the supplier actually implementing the contracted practices, and the clause's mechanism is contractual rather than direct.
- CWE-112partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation weaknesses like missing XML validation the way those practices do, at `partial`; the clause also carries a declared ceiling of `partial` on this verb.
- CWE-1121partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), and a coding-standards requirement that limits cyclomatic complexity would prevent some instances of CWE-1121 from arising in delivered code; the ceiling is `partial` because the clause depends on the supplier actually implementing such a standard and on the organization enforcing it through acceptance testing, leaving a nameable remainder.
- CWE-1123partialprevents — A.8.30 carries secure coding practices (8.28) into outsourced development via contractual requirements, and self-modifying code is the kind of construct secure coding guidelines can discourage because it impedes analysis; the effect is partial because the clause depends on the supplier's implementation of those practices and self-modifying code is primarily a maintainability concern rather than a direct security defect, leaving a nameable remainder.
- CWE-1124partialprevents — A.8.30 carries its preventive effect through the contractual requirement for secure coding practices (8.25–8.29) the supplier must follow, which can include coding standards limiting nesting depth; this is the same mechanism that graded A.8.30 -> CWE-134 at `partial`, and CWE-1124 is an analogous implementation-phase code-quality weakness the clause reaches only through those dependent practices.
- CWE-1125partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices its contract requires of the supplier (8.25-8.29), so an outsourced build under a faithful contract is less likely to ship with an unnecessarily large attack surface; the ceiling is `partial` because the clause depends on the supplier implementing those practices and on attack-surface decisions that are often driven by functional requirements the contract does not override.
- CWE-1126partialprevents — A.8.30 carries secure coding practices (8.25-8.29) into outsourced development contracts, which would reduce instances of unnecessarily wide variable scoping as part of general coding hygiene, but the effect is a minority one because the clause depends on supplier implementation and CWE-1126 is a maintainability/quality concern rather than a primary security defect.
- CWE-1127partialprevents — A.8.30's contractual requirements for secure coding practices (referencing 8.25-8.29) reach build/compilation configuration only insofar as the supplier's secure coding practice includes enabling compiler warnings; the clause does not itself mandate warning levels, and the effect depends on the supplier's implementation of the referenced practices, leaving a nameable remainder.
- CWE-113partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software CWEs in delivered code the way those practices do; CWE-113 is an implementation-phase input-handling defect of the same kind, and the clause reaches it at the same `partial` rung the owner set for A.8.30 -> CWE-134, which is also the clause's declared ceiling on this verb.
- CWE-113partialfinds — A.8.30's contractual framework requires acceptance testing (d), audit rights (i), and evidence of security testing (f, g), which provide some discovery mechanism for HTTP response splitting in delivered code, but the actual security testing capability (SAST/DAST/pen testing) belongs to A.8.29 which A.8.30 references but does not directly implement; the effect is derivative of 8.25-8.29, consistent with the `partial` ceiling on this clause.
- CWE-115partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary input-handling weaknesses in delivered code the way those practices do, at the clause's declared ceiling of `partial`.
- CWE-117partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation weaknesses like log output neutralization the way those practices do, at `partial` — the clause depends on the supplier actually implementing secure coding and on fallible human practice, and A.8.30 carries a declared ceiling of `partial` on this verb.
- CWE-1173partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-1173 is an ordinary software design/implementation weakness that secure coding guidance reaches, but the clause's ceiling on this verb is `partial`.
- CWE-1174partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), which reduces ordinary software weaknesses in delivered ASP.NET code the way those practices do; the owner has set A.8.30's ceiling at `partial` for regular software CWEs, and model-validation misconfiguration is a specific framework-usage defect that general secure-coding guidance reaches only partially.
- CWE-1188partialprevents — A.8.30 carries its effect through contractual requirements for secure design, coding and testing practices (8.25–8.29), which reach the implementation-phase introduction of CWE-1188 in delivered code the way those practices do, but the clause depends on the supplier faithfully implementing them and does not directly address the system-configuration phase of introduction, so a minority of instances are prevented.
- CWE-12partialprevents — A.8.30's contractual requirements for secure design, coding and testing practices (8.25-8.29) and acceptance testing would, when specified in the contract and verified, prevent many instances of this ASP.NET misconfiguration from being delivered; however, the clause depends on those referenced controls being properly implemented, configuration can drift after delivery, and not every contract will enumerate this specific setting, leaving a nameable remainder.
- CWE-1204partialprevents — A.8.30 contracts secure development practice (8.25-8.29) into outsourced delivery, which carries secure coding and cryptography-use requirements that reduce weak-IV generation in delivered code the way those clauses do, but the effect is bounded by supplier compliance and the fallibility of the practices the contract mandates.
- CWE-122partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices its contract requires of the supplier (8.25-8.29), so a faithfully implemented clause reduces ordinary implementation-phase software weaknesses like heap-based buffer overflows in delivered code, but the effect is mediated by supplier practice and is bounded by the ceiling the owner has set on this clause for this verb.
- CWE-123partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-123 is a regular software CWE arising from buffer overflows and integer overflows at implementation, and the clause reaches it at the same `partial` rung as CWE-134, with a declared ceiling of `partial` on this verb.
- CWE-1230partialprevents — A.8.30 carries its effect through the secure-design and threat-modelling practices its contract requires of the supplier (8.25, item c), so a faithful implementation reduces metadata-exposure design flaws the way those practices do; the owner has graded A.8.30 -> CWE-134 at `partial` for the same reason, and CWE-1230 is a regular software CWE introduced at architecture/design that those practices reach only partially.
- CWE-1235partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-1235 is a regular implementation-choice CWE that secure coding guidance can reach, but the practice is fallible and performance-critical autoboxing is not the primary focus of secure coding, leaving a nameable remainder.
- CWE-1236partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like CSV formula injection the way those practices do, at `partial` -- the practice is fallible and a different clause carries the stronger effect.
- CWE-124partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary implementation-phase memory-safety defects like buffer underwrite the way those practices do; the owner has ruled this clause's ceiling on `prevents` at `partial` for regular software CWEs, and CWE-124 is one.
- CWE-1241partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so a supplier bound by those requirements is less likely to choose a predictable PRNG where a CSPRNG is needed; the weakness can still slip in during implementation when a design calling for a CSPRNG is replaced under constraint, and acceptance testing does not always catch the substitution, leaving a nameable remainder.
- CWE-1250partialprevents — A.8.30's contractual requirements for secure design (8.25), threat modelling (item c), and acceptance testing (8.29) can reach distributed-state-consistency defects when the supplier's design review and threat model explicitly address shared-state replication, but this is a specialised architectural concern that standard secure-development practices do not routinely cover, so only a minority of instances are prevented.
- CWE-1265partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-1265 is an implementation-phase code defect that secure coding/testing practice can reduce, but the practice is fallible and the clause's ceiling on this verb is `partial`.
- CWE-127partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary software implementation weaknesses like buffer under-reads in delivered code, but the effect is bounded by the fallibility of those practices and the clause's ceiling on this verb.
- CWE-1275partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; SameSite attribute handling is a coding practice secure-coding guidance would cover, but the effect depends on the supplier's implementation and is not direct.
- CWE-1285partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so an outsourced implementation that omits index/offset validation is reduced the same way those practices reduce ordinary software CWEs — a minority effect, with the same fallibility and dependency on the referenced controls that the owner cited for A.8.30 vs CWE-134.
- CWE-1287partialprevents — A.8.30 carries secure design, coding and testing practice (8.25–8.29) into outsourced development, which reduces ordinary implementation-phase input-validation weaknesses like CWE-1287 in delivered code, but its effect depends on those other controls and is bounded by supplier practice, matching the clause's declared ceiling.
- CWE-1289partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software input-validation defects the way those practices do; CWE-1289 is a regular implementation-level CWE that benefits from that mechanism, but the effect is mediated through fallible supplier practice and the clause carries a declared ceiling of `partial` on this verb.
- CWE-129partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary implementation-phase software weaknesses like CWE-129 in delivered code the way those practices do, at the clause's declared ceiling of `partial`.
- CWE-1293partialprevents — A.8.30's contractual requirements for secure design (8.25) and threat modeling (c) can mandate multi-source correlation as an architectural pattern in outsourced development, but the clause's effect is mediated through whatever secure-design practices the contract specifies, and generic secure-design requirements do not necessarily reach this specific architectural choice.
- CWE-1295partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; debug-message hygiene is a coding/testing concern those practices reach, but the clause depends on the supplier implementing them and human practice is fallible, leaving a nameable remainder.
- CWE-13partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a well-implemented clause reduces instances of this credential-handling misconfiguration in delivered code the way A.8.28 does, but the practice is fallible and the clause depends on those sub-controls being properly applied.
- CWE-130partialprevents — A.8.30 contractually requires secure design, coding and testing practices (8.25–8.29), threat modelling, acceptance testing and evidence of vulnerability testing in outsourced delivery, which can prevent some length-parameter handling defects at the supplier; but the clause is an oversight/governance layer whose effect depends on supplier implementation rigour and the organisation's monitoring, so it catches a minority of instances rather than the bulk.
- CWE-131partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation defects in delivered code the way those practices do; CWE-131 is a regular software weakness introduced at implementation, the same class as CWE-134 which the owner graded `partial` for the same reason.
- CWE-1321partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; prototype pollution is such a weakness, but the clause's ceiling on `prevents` is `partial` because the effect depends on the supplier's implementation of secure coding and testing.
- CWE-1322partialprevents — A.8.30 carries its preventive effect through the secure-coding practices its contract requires of the supplier (8.25–8.29), so a supplier bound by those requirements is less likely to introduce blocking calls into a single-threaded event-loop architecture; the owner has ruled this ceiling at `partial` for regular software CWEs because the clause depends on the supplier's actual implementation of those practices.
- CWE-1325partialprevents — A.8.30 contracts secure design, coding and testing practices (8.25–8.29) from the supplier, so it carries the same partial effect against ordinary implementation-phase memory-management weaknesses as those practices do — a minority of instances are caught by the contracted secure-coding and testing regime, with the remainder being the fallible human-practice slice, and the clause's declared ceiling on this verb is `partial`.
- CWE-1327partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) it contractually requires of the supplier, which can catch a 0.0.0.0 bind during code review, threat modelling or acceptance testing, but the clause does not itself inspect code and the practice is fallible, so a minority of instances are prevented.
- CWE-1333partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25-8.29) its contract requires of the supplier, so a well-implemented clause reduces ReDoS instances the way those practices do; the clause's declared ceiling on this verb is `partial`, and the effect depends on supplier implementation of the mandated practices.
- CWE-1335partialprevents — A.8.30 contracts secure coding (8.28) and security testing (8.29) into outsourced development, which reduces ordinary implementation-phase software defects like incorrect bitwise shifts, but the effect is carried by the referenced controls and is fallible, matching the owner-graded A.8.30 -> CWE-134 anchor at `partial`.
- CWE-1336partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), so a faithfully implemented clause reduces template-injection defects in delivered code the way those practices do; the practice is fallible and the clause depends on the referenced controls being in place, so a minority of instances are prevented.
- CWE-1339partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary implementation-level code weaknesses in delivered code the way those practices do; CWE-1339 is an implementation choice (real-number representation) that secure coding guidance can reach, but the clause's mechanism is contractual and fallible, and the ceiling on this verb for A.8.30 is `partial`.
- CWE-134partialprevents — A.8.30's contractual requirement for secure design, coding and testing practices (item b, referencing 8.25–8.29) reaches the implementation defect that introduces CWE-134, but the mechanism is requiring a practice through contract — fallible, like A.8.28's grade of `partial` on CWE-502 and CWE-79 — so it moves a minority of instances rather than the bulk.
- CWE-135partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary software implementation defects like CWE-135 the way those practices do, but only at the ceiling the clause reaches on this verb.
- CWE-1357partialblocks — Outsourced-development controls address third-party code/components that may be insufficiently trusted.
- CWE-1386partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25-8.29) in outsourced development, which would reduce instances of this Windows filesystem implementation weakness the same way those practices do; the effect is real but bounded by the supplier's actual implementation, matching the owner-graded A.8.30 -> CWE-134 anchor at `partial`.
- CWE-1389partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) it contracts from the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-1389 is an ordinary parsing defect in code, and the clause reaches it at the same `partial` rung the owner set for A.8.30 -> CWE-134.
- CWE-1392partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, which would include not shipping default credentials; the effect is real but depends on the supplier implementing those practices, and the clause does not directly mandate credential handling, so a minority of instances are prevented.
- CWE-1393partialprevents — A.8.30 carries its effect through contractual requirements for secure design, coding and testing practices (8.25-8.29), which can require suppliers to avoid default passwords or force change-on-first-use, but the clause is a process/contractual mechanism whose effect depends on supplier implementation, matching the owner's `partial` grade for A.8.30 vs CWE-134 on the same mechanism.
- CWE-1394partialprevents — A.8.30 carries its effect through contractual requirements for secure design, coding and testing practices (8.25-8.29), which can require the supplier to avoid default cryptographic keys or generate unique keys per deployment, but the clause's reach depends on what the contract specifies and whether the supplier follows it; suppliers commonly ship default keys for ease of deployment, and the clause does not directly prevent the design choice, so it reduces but does not eliminate instances of this weakness.
- CWE-140partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary input-neutralization weaknesses in delivered code the way those practices do; the clause's ceiling on this verb is `partial` and the remainder is the fallibility of the mandated practice.
- CWE-142partialprevents — A.8.30 carries its preventive effect through the secure-coding and testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary input-handling flaws like CWE-142 in delivered code the way those practices do, but the supplier's implementation is fallible and a nameable remainder of instances slips through.
- CWE-1426partialprevents — A.8.30 can require outsourced developers to validate generative AI outputs through contractual requirements for secure design/coding/testing (item b), acceptance testing (item d), and evidence of security capabilities (item e), but the clause's mechanism is contractual and process-based rather than technical, its effectiveness depends on the organization specifying appropriate AI-output-validation requirements and the outsourced developer implementing them, and CWE-1426 is a research-gap weakness in an emerging area not addressed by the secure-development clauses (8.25–8.29) that A.8.30 references.
- CWE-1427partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), and prompt injection is fundamentally an input-neutralization defect introduced at architecture/design and implementation — the same surface those practices reach. The owner graded A.8.30 vs CWE-134 (format string) at `partial` for the same reason: the clause reduces regular software CWEs but depends on other controls and on the supplier actually implementing the practices, and LLM-specific prompt-construction guidance is not named in 8.25–8.29, leaving a nameable remainder.
- CWE-1428partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25 to 8.29), so it reduces instances of HTTP-instead-of-HTTPS being chosen in outsourced code the way those practices do, but the effect is indirect and depends on supplier implementation, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-143partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, and CWE-143 is an ordinary input-handling implementation weakness those practices address; the clause reaches it the way it reaches CWE-134, at the ceiling the owner set for this verb.
- CWE-1434partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so an outsourced ML model developed under those practices would see some reduction in inference-parameter misconfiguration via acceptance testing and secure-coding guidance; the effect is partial because ML inference-parameter tuning is a specialised area not directly named in standard secure-coding practice, and the clause's reach depends on the supplier implementing the practices faithfully.
- CWE-144partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary input-neutralization weaknesses in delivered code the way those practices do; the clause's declared ceiling on this verb is `partial`, matching the CWE-134 anchor.
- CWE-145partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary input-neutralization weaknesses in delivered code the way those practices do; CWE-145 is a regular implementation-phase CWE that secure coding and testing reach, but the clause's effect is mediated through a fallible supplier practice, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-147partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software input-handling weaknesses in delivered code the way those practices do; CWE-147 is a regular implementation-phase input-neutralization defect, and the clause's ceiling on this verb is `partial`.
- CWE-148partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software input-handling weaknesses in delivered code the way those practices do, at `partial` -- the same reasoning the owner gave for A.8.30 vs CWE-134.
- CWE-149partialprevents — A.8.30 contracts secure design, coding and testing practices (8.25–8.29) from the supplier, so a faithful implementation reduces ordinary software injection flaws like CWE-149 in delivered code the way those practices do, but the effect is bounded by the fallibility of the contracted practices and the clause's own ceiling on this verb.
- CWE-15partialprevents — A.8.30 contracts secure design, coding and testing practices (8.25–8.29) into outsourced work, so it reduces ordinary software implementation weaknesses like CWE-15 in delivered code the way those practices do, but only at partial because the effect depends on the supplier actually implementing those practices and human practice is fallible.
- CWE-150partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software injection weaknesses in delivered code the way those practices do; CWE-150 is an implementation-level neutralization defect of the same family as CWE-134, which the same clause was graded `partial` against, and the clause's declared ceiling on this verb is `partial`.
- CWE-151partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software input-neutralization flaws in delivered code the way those practices do, at the clause's declared ceiling of `partial`.
- CWE-152partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software input-neutralization weaknesses in delivered code the way those practices do, at `partial` -- the same reading the owner applied to A.8.30 -> CWE-134, and CWE-152 is the same kind of implementation-phase input-neutralization defect.
- CWE-153partialprevents — A.8.30 carries its preventive effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary input/output neutralization weaknesses in delivered code the way those practices do, but as a fallible human-practice effect it moves only a minority of instances, and the clause's ceiling on this verb is `partial`.
- CWE-154partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses like CWE-154 the way those practices do; the clause has a declared ceiling of `partial` on this verb, matching the CWE-134 anchor.
- CWE-156partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary input-neutralization weaknesses in delivered code the way those practices do, at `partial` -- the same reading the owner applied to A.8.30 vs CWE-134, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-158partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like null-byte neutralization defects in delivered code the way those practices do, at `partial` -- the clause's mechanism is contractual and depends on the supplier actually implementing the referenced controls.
- CWE-161partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), reducing ordinary input-neutralization defects in delivered code the way those practices do, but only partially because the clause depends on those other controls and human practice is fallible.
- CWE-162partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary input-neutralization flaws in delivered code the way those practices do; CWE-162 is an implementation-phase trailing-element neutralization defect of the same kind, and the clause's ceiling on `prevents` is `partial`.
- CWE-163partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a faithful implementation reduces ordinary implementation-phase input-handling weaknesses like CWE-163 in delivered code, but the mechanism is fallible human practice and depends on those other controls being in place — the same reading the owner applied to A.8.30 vs CWE-134, and the clause's declared ceiling on this verb.
- CWE-164partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation-phase weaknesses like CWE-164 in delivered code the way those practices do, at the clause's declared ceiling of `partial`.
- CWE-166partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so an outsourced implementation that mishandles a missing special element is reduced the same way those practices reduce ordinary software weaknesses; the ceiling is `partial` because the clause's effect is indirect and the underlying practice is fallible.
- CWE-167partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary input-handling implementation weaknesses in delivered code the way those practices do; CWE-167 is a regular software CWE introduced at implementation, and the clause's ceiling on this verb is `partial`.
- CWE-168partialprevents — A.8.30 carries its effect through contractual requirements for secure design, coding and testing practices (item b, referencing 8.25–8.29), so it reduces ordinary implementation-level input-handling defects in delivered code the way those practices do, at the clause's declared ceiling of `partial`.
- CWE-168partialfinds — A.8.30 requires the supplier to perform security testing (items d, f, g, referencing 8.29) and to follow secure coding practices (8.28), so the testing the contract mandates will surface some instances of CWE-168 in delivered code; the effect is mediated through the testing the contract requires rather than performed by A.8.30 itself, leaving a remainder where the supplier's testing is shallow or where the defect is not exercised by the acceptance tests.
- CWE-170partialprevents — A.8.30 carries its effect through the secure-development practices (8.25 to 8.29) it contracts from the supplier, so a faithful implementation reduces ordinary software implementation defects like CWE-170 in delivered code, at the same `partial` rung the owner set for CWE-134 on this clause.
- CWE-173partialprevents — A.8.30 carries its preventive effect through contractual requirements for secure design, coding and testing practices (point b, referencing 8.25-8.29), which would include proper handling of alternate encodings in delivered code; the effect is partial because it depends on the supplier actually implementing those practices and on acceptance testing/audit rights to verify, and the clause carries a declared ceiling of partial on this verb.
- CWE-174partialfinds — A.8.30's contractual requirements for secure design, coding and testing practices (referencing 8.25–8.29) carry some finding effect for code-level defects like CWE-174 through the supplier's testing programme, but the clause is a contractual wrapper that requires the programme to exist rather than directly performing testing itself, so the effect is mediated and reaches a minority of latent instances.
- CWE-175partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a well-implemented clause reduces ordinary implementation weaknesses like mixed-encoding handling in delivered code the way those practices do; the ceiling is `partial` because the mechanism is fallible human practice, not a direct guard.
- CWE-176partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-176 is such an ordinary implementation defect, but the clause's reach is bounded by supplier compliance and human practice, leaving a nameable remainder.
- CWE-177partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like CWE-177 in delivered code the way those practices do, at `partial`; the clause sits at its declared ceiling on this verb.
- CWE-179partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary implementation defects like early-validation ordering the way those practices do — a minority of instances, with the remainder bounded by the fallibility of the practice and the dependence on the underlying controls being configured to act.
- CWE-181partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-181 is a regular code-ordering defect that secure coding guidance addresses but does not eliminate, matching the owner's established `partial` ceiling for A.8.30 against software CWEs.
- CWE-183partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-183 is a regular software CWE (an allowlist that is too permissive), and the clause reaches it at the same `partial` rung the owner set for A.8.30 vs CWE-134, which is also the clause's declared ceiling on this verb.
- CWE-186partialfinds — A.8.30's programme requires the supplier to perform security testing per 8.29 (static analysis, code review) and mandates acceptance testing of the deliverable, which would surface some overly restrictive regexes; however, the clause is a contractual wrapper whose actual discovery is mediated by 8.29-type activities, and regex defects whose intent is not externally observable or whose test cases do not exercise the missed values are not caught, leaving a nameable remainder.
- CWE-188partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25–8.29), which carry some preventive effect against low-level implementation defects like memory-layout assumptions, but the weakness is subtle and most instances still arise under ordinary outsourced development.
- CWE-191partialprevents — A.8.30’s contractual secure-design, coding, and testing requirements reduce the introduction of integer-underflow defects in outsourced software, but fallible implementation practice leaves a substantial remainder.
- CWE-192partialprevents — A.8.30 carries secure-development practices (8.25-8.29) into outsourced work via contract, so it reduces ordinary software implementation flaws like integer coercion errors in delivered code the way those practices do; the clause's declared ceiling on this verb is `partial`, matching the CWE-134 anchor.
- CWE-193partialprevents — A.8.30 carries secure design, coding and testing practices (8.25-8.29) into outsourced development via contractual requirements, so an off-by-one error in delivered code is reduced the way those practices reduce it; the owner graded the analogous CWE-134 pair at `partial` and declared `partial` as the ceiling for this clause on this verb.
- CWE-194partialprevents — A.8.30 carries its effect through the secure-coding and secure-development practices (8.25-8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary implementation-phase numeric defects like sign-extension errors in delivered code, but the effect is mediated through fallible supplier practice and depends on those other controls being in force.
- CWE-195partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts the supplier to apply, so an organization implementing it faithfully sees a reduction in ordinary implementation-phase software weaknesses like signed-to-unsigned conversion errors, but the effect is mediated and fallible, matching the A.8.30 -> CWE-134 anchor at the clause's `partial` ceiling.
- CWE-196partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so an unsigned-to-signed conversion error introduced in outsourced implementation code is reduced the same way as other ordinary software CWEs, at the clause's declared ceiling of `partial`.
- CWE-197partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-197 is such a code-level defect, but the clause's ceiling on this verb is `partial` because the contracted practices are fallible.
- CWE-198partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; byte ordering is a subtle implementation detail that secure coding guidance can address but not fully cover, and the clause sits at its declared ceiling of `partial` for software CWEs.
- CWE-202partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts from the supplier, and CWE-202 is an architecture/design and implementation weakness that those practices partially reach; the remainder is the specific statistical-disclosure design considerations (query limits, differential privacy, aggregation thresholds) that standard secure-development practices do not mandate.
- CWE-203partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) its contract requires of the supplier, so observable discrepancies in delivered code are reduced the way those practices reduce them — but the clause mandates a practice, not a mechanism, and what it catches depends on the rigour of the supplier's implementation, leaving a fallible remainder.
- CWE-204partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software CWEs in delivered code the way those practices do; CWE-204 is a regular code-level weakness (different responses revealing internal state) that secure coding and testing practices partially prevent, and A.8.30 sits at its declared ceiling of `partial` on this verb.
- CWE-205partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) it contracts from the supplier, which can reduce observable behavioral discrepancies (consistent error responses, timing, fingerprinting) but cannot fully prevent them since such discrepancies are often emergent properties of implementation rather than deliberate choices secure coding flags.
- CWE-208partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces timing side-channel weaknesses in outsourced code the way those practices do; the ceiling is `partial` because timing discrepancies are subtle, require specialized constant-time knowledge, and depend on the supplier's implementation rigour.
- CWE-209partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-209 is a regular software CWE that secure coding addresses, but the clause's reach depends on supplier implementation and error-message hygiene is one slice of what secure coding covers, with externally-generated error messages outside the developer's direct control.
- CWE-210partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) it contractually requires of the supplier, which would reduce instances of self-generated error messages containing sensitive information in delivered code, but only partially because the clause depends on those other controls being properly implemented and the supplier following them.
- CWE-211partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25-8.29), so it reduces ordinary software weaknesses like CWE-211 at the same rung the owner set for A.8.30 vs CWE-134: a faithful implementation reduces externally-generated error message leakage through secure coding and testing requirements, but the effect is bounded by the fallibility of the practices the contract mandates.
- CWE-212partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so a faithfully implemented clause reduces regular software CWEs like CWE-212 (a code-level failure to scrub sensitive data before sharing) the way those practices do, but the mechanism is human practice and is fallible, capping the effect at the clause's declared ceiling of `partial`.
- CWE-213partialprevents — A.8.30's contractual requirements for secure design (b), threat model provision (c), acceptance testing (d), and evidence of security and privacy capabilities (e) can prevent some instances of CWE-213 by requiring the outsourced developer to account for all stakeholders' sensitivity views, but the prevention is indirect and depends entirely on the rigour of the contract terms and the developer's implementation, leaving a nameable remainder where stakeholder policy mismatches are not specifically addressed in the requirements or caught in acceptance testing.
- CWE-214partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-214 is a regular software CWE that secure coding and testing would catch, but the clause's reach is contractual and fallible, sitting at the clause's declared ceiling of `partial`.
- CWE-215partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-215 is an implementation-phase defect (sensitive data in debug code) that secure coding guidance and acceptance testing reach, but the clause's mechanism is contractual and human-practice-dependent, leaving a nameable remainder.
- CWE-219partialprevents — A.8.30 contracts secure design and coding practices (8.25–8.29) into outsourced development, which reduces ordinary software weaknesses like placing sensitive files under the web root, but the access-control half of CWE-219 is a deployment/configuration concern the clause does not reach, leaving a nameable remainder.
- CWE-224partialprevents — Following the A.8.30 -> CWE-134 anchor: A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code at `partial`. CWE-224 is a regular software CWE (canonicalization in logging), reachable by those practices, but the clause's effect is bounded by the rigour of the supplier's implementation and the clause's own ceiling on this verb.
- CWE-226partialprevents — A.8.30 carries its effect through the secure-coding and testing practices its contract requires of the supplier (8.25–8.29), so it reduces instances of CWE-226 in outsourced software code the way those practices do; the hardware manifestations (e.g., SoC register scrubbing, state-transition cleanup) are outside the clause's software-development reach, and even in software the practice is fallible, leaving a nameable remainder.
- CWE-229partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like CWE-229 the way those practices do, at the clause's declared ceiling of `partial`.
- CWE-23partialprevents — A.8.30 carries secure design, coding and testing practices (8.25–8.29) into outsourced development contracts, which reduces path-traversal defects in delivered code the way those practices do; the clause has a declared ceiling of `partial` on this verb and the mechanism is fallible human practice, so a minority of instances are prevented.
- CWE-230partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary implementation defects like missing-value handling the way those practices do, but only at the clause's declared ceiling of `partial`.
- CWE-231partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses like CWE-231 in delivered code the way those practices do, at `partial` -- the clause's declared ceiling on this verb.
- CWE-233partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-233 is a regular parameter-handling implementation defect that benefits from this, but the clause sits at its declared ceiling of `partial` because the effect depends on the supplier's actual practice.
- CWE-234partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation defects in delivered code the way those practices do; CWE-234 is a regular code-level implementation weakness, and the clause reaches it at the same `partial` rung the owner set for A.8.30 -> CWE-134, which sits at the clause's declared ceiling.
- CWE-237partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses like improper handling of structural elements the way those practices do, at `partial` — the same reading the owner applied to A.8.30 -> CWE-134.
- CWE-238partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), reducing ordinary software implementation weaknesses in delivered code the way those practices do; CWE-238 is an implementation-phase defect that secure coding standards and review partially address, with a nameable remainder of incomplete-structural-element handling that escapes the contracted practices.
- CWE-239partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) it contracts the supplier to follow, so a faithfully implemented clause reduces ordinary software implementation defects like CWE-239, but the clause itself does not write or review the code and depends on those other controls to act.
- CWE-241partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-241 is an ordinary code-level type-handling defect that secure coding and testing reach but do not eliminate, and the clause sits at its declared ceiling of `partial`.
- CWE-242partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts the supplier to apply, which reduce the use of inherently dangerous functions like gets() in delivered code the way those practices do; the same reasoning the owner applied to A.8.30 vs CWE-134, and the clause's ceiling on this verb is `partial`.
- CWE-243partialprevents — A.8.30 contracts for secure coding practices (8.25-8.29) in outsourced development, which reaches ordinary software implementation defects like improper chroot() usage the same way those practices do; the ceiling is `partial` because the clause's effect runs through fallible human practice in the supplier's development team, consistent with the A.8.30 -> CWE-134 anchor.
- CWE-244partialprevents — A.8.30 carries its effect through contractual requirements for secure coding practices (item b, referencing 8.25–8.29), so outsourced code is less likely to contain this memory-clearing defect the way secure coding practice reduces ordinary software CWEs; the owner has ruled A.8.30's ceiling on `prevents` for regular software weaknesses at `partial`.
- CWE-246partialprevents — A.8.30 carries its effect through contractual requirements for secure coding practices (8.25-8.29) imposed on the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-246 is a J2EE coding-practice defect the supplier's secure coding guidance would reach, but the clause's ceiling on this verb is `partial` because the practice is fallible and depends on supplier implementation.
- CWE-248partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) its contract requires of the supplier, so an outsourced implementation that omits exception handling is reduced the way those practices reduce it; the owner graded the same clause against CWE-134 at `partial` on this verb, and CWE-248 is the same kind of regular implementation-phase software weakness, with the same fallible-supplier-practice remainder.
- CWE-25partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; path traversal is a regular implementation CWE and the clause reaches it at the same `partial` rung as CWE-134, which is also the clause's declared ceiling on this verb.
- CWE-250partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices its contract requires of the supplier (8.25–8.29), which reach privilege-level decisions in outsourced software at the same level as other ordinary software CWEs — a reduction but not elimination, because privilege choices are made at architecture and installation phases the contract influences but does not fully control.
- CWE-252partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; unchecked return values are a regular implementation defect that secure coding and security testing would catch, but the clause's mechanism is contractual and the practices are fallible, matching the owner-graded `partial` on A.8.30 vs CWE-134.
- CWE-256partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-256 is a regular software weakness that secure coding practice (8.28) addresses, but the clause's mechanism is contractual and human-practice-dependent, capping the effect at the clause's declared ceiling of partial.
- CWE-257partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces recoverable password storage in delivered code the way those practices do, at `partial` — the clause's ceiling on this verb, with the same fallibility and dependency on supplier implementation that graded A.8.30 -> CWE-134 `partial`.
- CWE-258partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so an empty-password-in-config-file defect in outsourced code is reduced the way those practices reduce ordinary software weaknesses — a minority of instances, with the same `partial` ceiling the owner set for A.8.30 on this verb.
- CWE-259partialfinds — A.8.30's programme includes acceptance testing (item d) and contractual audit rights (item i), which can surface hard-coded passwords in delivered code, but these are a minority of instances — most are caught by the supplier's own development-time testing (A.8.29), which A.8.30 only requires contractually rather than performs itself.
- CWE-259partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; hard-coded passwords are an implementation-phase defect that secure coding guidance addresses, but the effect depends on supplier implementation and is fallible, leaving a nameable remainder.
- CWE-26partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software implementation defects like path traversal in delivered code the way those practices do, at the same `partial` rung the owner set for A.8.30 -> CWE-134.
- CWE-260partialprevents — A.8.30 contracts secure design, coding and testing practice (8.25–8.29) into outsourced work, so a supplier implementing those practices faithfully will not store cleartext passwords in configuration files in delivered code; the effect is real but a minority one because it depends on the supplier's implementation of the referenced practices, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-261partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25-8.29) in outsourced development, so a well-implemented clause reduces ordinary software weaknesses like CWE-261 in delivered code the way those practices do, but only at the partial rung because the effect is mediated through fallible supplier practice and the clause carries a declared ceiling of partial on this verb.
- CWE-266partialprevents — A.8.30 contracts secure design, coding and testing practices (8.25–8.29) into outsourced development, so a faithful implementation reduces ordinary software weaknesses like incorrect privilege assignment in delivered code, but the effect is carried through fallible human practice and a different clause carries the stronger effect — same reading as A.8.30 -> CWE-134.
- CWE-268partialprevents — A.8.30 carries its effect through the secure design and coding practices (8.25-8.29) its contract requires of the outsourced supplier, which reduces instances of privilege chaining in delivered code the way those practices do; the clause has a declared ceiling of `partial` on this verb, and the remainder is the same fallibility of human practice plus the subtlety of an architectural authorization defect that standard secure-coding guidance may not catch.
- CWE-27partialprevents — A.8.30 contracts secure design, coding and testing practices (8.25–8.29) into the supplier relationship, so a faithfully implemented clause reduces ordinary implementation-phase software weaknesses like path traversal in delivered code, but the effect is mediated through fallible supplier practice and the dependent controls themselves act only partially.
- CWE-272partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-272 is a privilege-dropping defect of the same kind, and the clause reaches it at the same `partial` rung as CWE-134, which is also A.8.30's declared ceiling on this verb.
- CWE-273partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation defects in delivered code the way those practices do; CWE-273 is a regular software CWE addressed by secure coding standards, but the clause's reach is bounded by supplier compliance and human practice, leaving a nameable remainder.
- CWE-274partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like improper privilege-handling the way those practices do, at `partial` -- the clause's ceiling on this verb.
- CWE-276partialprevents — A.8.30 carries its effect through the contractual requirements for secure design, coding and testing practices (referencing 8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-276 is such an ordinary weakness, and the clause reaches it at the same `partial` rung the owner set for A.8.30 -> CWE-134, with the same ceiling and the same fallible-practice remainder.
- CWE-279partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), which address ordinary software implementation weaknesses including incorrect permission-setting; the clause reaches CWE-279 the same way it reaches CWE-134, at the clause's declared ceiling of `partial` because the contract requires practice but does not guarantee its execution.
- CWE-28partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary implementation-phase weaknesses like path traversal in delivered code the way those practices do; the ceiling is `partial` because the clause depends on the supplier's actual implementation of those practices.
- CWE-280partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses like CWE-280 in delivered code the way those practices do, at the clause's declared ceiling of `partial`.
- CWE-281partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses like CWE-281 the same way those practices do, at `partial` — the clause's declared ceiling on this verb.
- CWE-283partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary code-level ownership-verification defects in delivered software the way those practices do, at `partial` -- the same reasoning the owner applied to A.8.30 -> CWE-134.
- CWE-284partialprevents — A.8.30's contractual requirements for secure design, coding and testing practices (referencing 8.25–8.29) reach some access control defects in delivered code the way those practices do, but CWE-284 is broader than a typical implementation flaw — it spans architecture/design, implementation, and operation/configuration, and the clause's effect is mediated through fallible supplier practice, leaving a nameable remainder.
- CWE-288partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), plus threat modelling and acceptance testing, so it reduces ordinary software architectural weaknesses in delivered code the way those practices do; CWE-288 is an Architecture-and-Design defect that secure design and threat modelling can reach, but the effect is partial because it depends on the supplier's implementation of those contracted practices.
- CWE-289partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, plus threat-model provision and acceptance testing, so an outsourced authentication bypass by alternate name is reduced the way ordinary software weaknesses are — a minority of instances, with the same ceiling the clause carries on CWE-134.
- CWE-29partialprevents — Contractual secure-coding and testing requirements can prevent some path-traversal flaws in outsourced software from being introduced, but the effect depends on fallible supplier practices and leaves a substantial remainder.
- CWE-290partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so authentication-bypass-by-spoofing defects in delivered code are reduced the way those practices reduce ordinary software CWEs; the clause's declared ceiling on this verb is `partial`, and the mechanism is fallible human practice at the supplier.
- CWE-293partialprevents — A.8.30's contractual requirements for secure design (8.25) reach an architecture-level design flaw like using the Referer for authentication, but the effect is carried through the supplier's implementation of those practices, which are fallible — matching the clause's declared ceiling of `partial` on this verb.
- CWE-294partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), and CWE-294 is an ordinary software design weakness that those practices address (authentication design using nonces, timestamps, challenge-response); the clause reduces but does not eliminate the weakness, sitting at the same rung as the CWE-134 anchor.
- CWE-295partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like improper certificate validation the way those practices do, at `partial` -- the same reasoning the owner applied to A.8.30 -> CWE-134, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-297partialprevents — A.8.30 carries its effect through contractual requirements for secure design, coding and testing practices (8.25 to 8.29) applied to outsourced development, and CWE-297 is an ordinary software implementation weakness in certificate/hostname validation that those practices reach, the same way the CWE-134 anchor graded this clause at `partial`; the clause mandates a practice rather than a mechanism, so what it catches depends on the rigour of the supplier's implementation.
- CWE-298partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation defects in delivered code the way those practices do; CWE-298 is a regular software CWE that secure coding and acceptance testing would catch some of, but not all, and the clause has a declared ceiling of partial on this verb.
- CWE-299partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software implementation flaws like missing certificate revocation checks the way those practices do, but only as a fallible contractual requirement rather than a direct mechanism.
- CWE-30partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software CWEs in delivered code the way those practices do; path traversal is a regular implementation-phase software weakness those practices reach, but the clause depends on those other controls and the practice is fallible, leaving a nameable remainder.
- CWE-302partialprevents — A.8.30 carries its effect through the secure-design and secure-coding practices (8.25–8.28) its contract requires of the supplier, and CWE-302 is an ordinary software design/implementation weakness those practices reach; the clause's ceiling on this verb is `partial` because the mechanism is fallible human practice.
- CWE-303partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25–8.29) in outsourced work, which reduces ordinary implementation defects like an incorrectly implemented authentication algorithm the same way those practices do, but the effect is bounded by the fallibility of the practices and the clause's dependence on those other controls being properly implemented — the declared ceiling for A.8.30 on `prevents`.
- CWE-304partialprevents — A.8.30’s contractual secure-design, coding, testing, and acceptance-review requirements can prevent suppliers from introducing skipped authentication steps, but this fallible human practice leaves a nameable remainder of implementation defects.
- CWE-305partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary implementation defects in delivered code the way those practices do; CWE-305 is an implementation defect in authentication code (e.g., incomplete password comparison, uninitialized array), and the clause's reach is the same as for CWE-134, which the owner graded `partial` on the same verb.
- CWE-306partialprevents — A.8.30 mandates contractual security requirements (point b referencing 8.25-8.29), acceptance testing (point d), and evidence of security capabilities (point e), which can require and verify that authentication is designed into outsourced deliverables before they ship — but it is a governance/oversight mechanism whose effect depends on the rigor of contract specification, acceptance test coverage, and developer compliance, so it prevents a slice rather than the bulk of instances.
- CWE-307partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-307 is an architectural/design weakness in authentication that secure design and threat modeling would address, but the clause's mechanism is contractual and depends on the supplier's implementation, leaving a nameable remainder.
- CWE-308partialprevents — A.8.30's contractual requirements for secure design (item b, referencing 8.25-8.29) can specify multi-factor authentication when outsourced work involves authentication design, preventing the weakness in those cases; the effect is mediated through the supplier's implementation of the contract, and authentication is only one slice of outsourced development, leaving a nameable remainder.
- CWE-31partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) its contract requires of the supplier, so a faithfully implemented clause reduces path-traversal instances in outsourced code the way those practices do; the clause's declared ceiling on this verb is `partial`, matching the CWE-134 anchor.
- CWE-312partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; cleartext storage is such a weakness, and the clause's ceiling on this verb is `partial` per the CWE-134 anchor.
- CWE-313partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), so a well-implemented clause reduces cleartext-storage instances in delivered software the way those practices do, but the supplier's implementation is fallible and the clause depends on those referenced controls being properly applied.
- CWE-314partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-314 is such a weakness, but the clause's reach is bounded by what the supplier actually implements and by the clause's own ceiling of `partial` on this verb.
- CWE-316partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) it contracts into outsourced development, which reach ordinary code-level weaknesses like uncleared sensitive memory the same way they reach other software defects, but only as a fallible practice with a declared ceiling of `partial`.
- CWE-317partialprevents — A.8.30 contracts the supplier for secure design, coding and testing practices (8.25–8.29), so a faithful implementation reduces ordinary software weaknesses in delivered code the way those practices do; CWE-317 is a regular software CWE introduced at architecture/design, and the clause reaches it through that contract, at the same rung the owner set for A.8.30 vs CWE-134.
- CWE-319partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices its contract requires of the supplier (8.25–8.29), which reach the software-channel instances of CWE-319 (HTTP vs HTTPS, unencrypted protocols) the same way those practices do; the owner has graded A.8.30 against ordinary software CWEs at `partial` and declared that the clause's ceiling on this verb is `partial`, with hardware-channel instances (JTAG, internal hardware networks) outside its reach.
- CWE-32partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary implementation weaknesses like path traversal in delivered code the way those practices do, at `partial`; the clause's declared ceiling on this verb is `partial`.
- CWE-322partialprevents — A.8.30 carries its effect through the secure-design and secure-coding practices its contract requires of the supplier (8.25–8.29), so an outsourced system developed under a faithful A.8.30 contract is less likely to ship a key-exchange protocol that omits entity authentication; the effect is real but bounded by the fallibility of those practices and by the clause's dependence on them being properly implemented, matching the owner's `partial` reading for A.8.30 against ordinary software CWEs.
- CWE-323partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a well-implemented contract reduces ordinary software weaknesses in delivered code the way those practices do; nonce reuse is a code-level cryptographic defect that secure coding guidance (8.28) and security testing (8.29) reach, but the clause depends on supplier implementation and developers are fallible, leaving a nameable remainder.
- CWE-324partialprevents — A.8.30 carries its effect through contractual requirements for secure design, coding and testing practices (8.25-8.29), which can reach CWE-324 as a software implementation weakness where secure coding mandates expiration checks and security testing verifies them; however, key expiration is often an operational/lifecycle concern beyond what outsourced development contracts govern, and the clause's effect depends on the supplier implementing the required practices, leaving a nameable remainder.
- CWE-325partialprevents — A.8.30 carries its preventive effect through the contractual requirements it places on the supplier for secure design, coding and testing practices (8.25–8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do — and CWE-325, a missing cryptographic step introduced at implementation or requirements, is the kind of defect those practices catch. The owner has already ruled this same mechanism `partial` against CWE-134, and the dependence on the supplier actually implementing 8.25–8.29 caps the rung identically here.
- CWE-328partialprevents — A.8.30 carries its effect through the secure-development and cryptography practices its contract requires of the supplier (8.25–8.29, including 8.24 and 8.28), so it reduces weak-hash usage in delivered code the way those practices do, but the clause itself does not directly prevent the weakness — it depends on the supplier implementing the referenced controls, matching the owner-graded `partial` ceiling on A.8.30 for this verb.
- CWE-329partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so a faithful implementation reduces predictable-IV defects the way it reduces other regular software CWEs; the owner has already set A.8.30's ceiling at `partial` on this verb (CWE-134 anchor), and CWE-329 is the same kind of implementation flaw.
- CWE-33partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary implementation weaknesses like path-traversal '....' handling in delivered code the way those practices do, but the practices are fallible and the clause has a declared ceiling of `partial` on this verb.
- CWE-331partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do — at `partial`, the same ceiling the owner set for A.8.30 on CWE-134, because the underlying practices are fallible and a different clause carries the stronger effect.
- CWE-332partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; PRNG entropy issues are a regular implementation defect that secure coding and security testing can catch, but the clause's effect is mediated through contractual requirements and depends on the supplier's implementation, leaving a nameable remainder.
- CWE-336partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25-8.29) its contract requires of the supplier, which address PRNG seeding in delivered code the way those practices do; the clause has a declared ceiling of `partial` on this verb, and the effect is real but a minority one because it depends on supplier implementation rigour.
- CWE-337partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-337 is a code-level seeding defect that secure coding guidance would address, but the clause depends on supplier implementation and human practice is fallible, matching the owner's `partial` ceiling on A.8.30.
- CWE-337partialfinds — A.8.30's contractual requirements for secure development practices (8.25-8.29) and acceptance testing would surface CWE-337 in outsourced deliverables through code review and static analysis, but the reach is limited to outsourced code and depends on the rigor of the contracted testing programme, leaving a nameable remainder.
- CWE-338partialprevents — A.8.30 carries its effect through the contractual requirements for secure design, coding and testing practices (8.25 to 8.29) it imposes on the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-338 is a code-level choice (using rand()/Random.nextInt() instead of a CSPRNG) that secure-coding guidance addresses, but the clause's effect depends on supplier compliance and on the referenced controls being properly implemented, leaving a fallible remainder.
- CWE-339partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a faithful implementation reduces ordinary software CWEs in delivered code, including PRNG seeding defects; the owner has already graded the same clause against CWE-134 at `partial` for the same reason, and the mechanism is human practice that is fallible.
- CWE-34partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) it contracts from the supplier, so a faithfully implemented clause reduces ordinary implementation-phase software CWEs like path traversal in delivered code, but the effect is mediated by fallible supplier practice and the clause's own ceiling is `partial`.
- CWE-341partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-341 is a software implementation weakness those practices reach, but the effect is partial because it depends on the supplier faithfully implementing the contracted practices.
- CWE-342partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-342 is a regular software CWE introduced at architecture/design or implementation, and the owner has already graded A.8.30 against a comparable software CWE (CWE-134) at `partial` for the same reason.
- CWE-343partialprevents — A.8.30 carries its preventive effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-343 is a regular software CWE introduced in design/implementation, and the clause reaches it at the same `partial` rung as CWE-134, with the same ceiling on the clause.
- CWE-347partialfinds — A.8.30's contractual requirements for secure coding/testing (8.25-8.29) and acceptance testing lead to finding CWE-347 instances through the testing programme it mandates, but the clause itself is a process/contractual wrapper — the actual finding is performed by the controls it requires, not by A.8.30 directly.
- CWE-348partialprevents — A.8.30 contracts secure design and coding practices (8.25-8.29) into outsourced work, and choosing the more trusted data source is a design/coding decision those practices reach; the effect is real but mediated through the supplier's implementation, matching the clause's declared ceiling and the CWE-134 anchor.
- CWE-349partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-349 is a regular software CWE reached by secure coding and testing, but the clause's ceiling on this verb is partial.
- CWE-35partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary implementation weaknesses like path traversal in delivered code the way those practices do, at `partial` — the same reading the owner applied to A.8.30 vs CWE-134.
- CWE-350partialprevents — A.8.30 carries its preventive effect through contractual requirements for secure design, coding and testing practices (item b, referencing 8.25-8.29), which can reach a design-phase authentication flaw like CWE-350 if the contract specifies that reverse DNS must not be used for security decisions; the effect is partial because it depends on the supplier implementing those practices and on the specific design choice being named in the contract, mirroring the owner's `partial` grade on A.8.30 vs CWE-134.
- CWE-351partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; type distinction is a subtle implementation concern that secure coding practice addresses only partially, and the clause's mechanism is a contract that depends on the supplier's fallible implementation.
- CWE-352partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CSRF is such a weakness, addressed when the supplier implements CSRF tokens and other protections under contracted secure coding/testing, but the effect is fallible and depends on the supplier's implementation, matching the A.8.30 -> CWE-134 anchor at the clause's declared ceiling of `partial`.
- CWE-354partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation weaknesses like missing checksum validation the way those practices do; the owner has declared `partial` as the ceiling for this clause on `prevents`, and the remainder is the fallibility of the referenced practices.
- CWE-356partialprevents — A.8.30 carries its effect through contractual requirements for secure design, coding and testing (8.25–8.29), which reach a UI-warning weakness in outsourced software the same way they reach other ordinary software CWEs; the clause's declared ceiling on this verb is `partial`, and the remainder is the fallibility of the supplier's design practice and the slice of UI-warning decisions not covered by security-focused design guidance.
- CWE-357partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices its contract requires of the supplier (8.25-8.29), so a faithful implementation reduces ordinary software design weaknesses like insufficient UI warnings; the ceiling is `partial` because the clause depends on those other controls and on the supplier actually implementing the specified UI warning requirements.
- CWE-358partialprevents — A.8.30 carries its preventive effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier, plus threat-model provision and acceptance testing, which reduce instances of standards-implementation errors in delivered code the way those practices do; the remainder is the supplier's developers missing or mis-implementing checks the standard requires, which the contract cannot fully reach.
- CWE-359partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices its contract requires of the supplier (8.25 to 8.29), which reach privacy-related code and design choices (e.g., not logging PII, threat modelling that includes privacy), but the clause has a declared ceiling of `partial` on this verb and CWE-359 also arises from architecture omissions and operational data-handling decisions that the contracted practices do not fully cover.
- CWE-36partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so a faithful implementation reduces ordinary implementation-phase code defects like absolute path traversal in delivered code the way those practices do; the clause's ceiling on this verb is `partial`, matching the CWE-134 anchor.
- CWE-360partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), and CWE-360 is an ordinary software design/implementation weakness those practices reach, but only at the same `partial` ceiling the clause carries on this verb.
- CWE-363partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a TOCTOU/link-following defect in delivered code is reduced the way those practices reduce ordinary code defects; the clause sits at its declared ceiling of `partial` because the effect depends on the supplier's implementation of secure coding guidance.
- CWE-364partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary software CWEs like signal-handler race conditions in delivered code, but the mechanism is fallible human practice and the clause itself does not directly prevent the defect — matching the owner's `partial` ceiling for this clause on `prevents`.
- CWE-368partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) it contracts from the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; the owner has ruled this ceiling at `partial` for the clause, and CWE-368 is an architecture/implementation race condition those practices reach only partially.
- CWE-369partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary implementation bugs like divide-by-zero in delivered code the way those practices do, but only partially because the clause depends on those other controls and human practice is fallible.
- CWE-37partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary implementation CWEs like path traversal in delivered code the way those practices do, but only partially because the clause depends on the supplier actually applying them and the clause carries a declared ceiling of `partial` on this verb.
- CWE-370partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation flaws in delivered code the way those practices do; CWE-370 is a code-level TOCTOU defect in certificate validation that secure coding guidance would address, but the effect is partial because the clause depends on the supplier's actual implementation and human practice is fallible, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-372partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation defects the way those practices do; CWE-372 is a regular software CWE introduced at implementation, and the clause reaches it at the same `partial` rung as CWE-134, bounded by supplier compliance and the clause's declared ceiling.
- CWE-374partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-374 is a regular code-level defect reachable by secure coding guidance, but the clause depends on supplier implementation and the practices are fallible, capping the effect at the clause's declared ceiling of `partial`.
- CWE-375partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary implementation weaknesses in delivered code the way those practices do; CWE-375 is a code-level defect introduced at implementation that secure coding practice addresses, but the clause's mechanism is contractual and fallible, leaving a nameable remainder.
- CWE-382partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so a faithfully implemented clause reduces ordinary software CWEs in delivered code the way those practices do; CWE-382 is a regular code-level bad practice that secure coding guidance would catch, but the effect is bounded by the fallibility of the contracted practice.
- CWE-383partialfinds — A.8.30's acceptance testing (d) for quality and accuracy of deliverables, referencing 8.29, could include security testing that surfaces CWE-383 instances, but the clause is primarily a governance/contractual control; the specific evidence requirements (f, g) target malicious content and known vulnerabilities, not J2EE bad practices, and the actual code-level detection is performed by the supplier's SAST under 8.28-8.29 rather than by A.8.30 itself.
- CWE-383partialprevents — A.8.30 contracts secure design, coding and testing practices (8.25-8.29) into outsourced development, so a faithful implementation reduces ordinary software implementation-phase weaknesses like direct thread management in J2EE code the same way those practices do, at the clause's declared ceiling of partial.
- CWE-39partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses like path-traversal defects in delivered code the way those practices do, at `partial`; the clause sits at its declared ceiling on this verb.
- CWE-390partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-390 is an ordinary code-level error-handling defect that secure coding and security testing reach, but the clause's ceiling on `prevents` is `partial` because the supplier's implementation of those practices is fallible.
- CWE-391partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-391 is an ordinary code-level error-handling defect that secure coding practice addresses, but the clause's reach is bounded by the supplier's implementation of those practices, and A.8.30 carries a declared ceiling of `partial` on this verb.
- CWE-392partialprevents — A.8.30 carries its preventive effect through the contractual requirement for secure coding practices (8.25-8.29) it imposes on the supplier, which would reduce instances of missing error reporting in delivered code the same way it reduces other ordinary software CWEs, but only partially because the clause depends on the supplier's actual implementation of those practices.
- CWE-394partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces instances of unchecked return values in delivered code the way those practices do, at `partial` -- the clause's declared ceiling on this verb, because the effect depends on the supplier's fallible implementation of the contracted practices.
- CWE-395partialprevents — A.8.30 contracts secure coding practice (8.25–8.29) into outsourced development, which reduces ordinary code-level defects like catching NullPointerException as a substitute for null checks, but the effect is mediated through supplier compliance and human practice, leaving a nameable remainder.
- CWE-396partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25–8.29) its contract requires of the supplier, which reduces ordinary implementation-phase code-quality weaknesses like over-broad catch blocks, but the practice is fallible and the clause sits at its declared ceiling of `partial`.
- CWE-397partialprevents — A.8.30 contracts for secure coding practices (8.25-8.29) in outsourced development, which would catch overly broad exception declarations during code review, but the effect is partial because the practice is fallible and depends on supplier implementation, matching the owner's ceiling for this clause on regular software CWEs.
- CWE-40partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so an outsourced implementation that follows them is less likely to introduce the input-validation gap behind a UNC-share path traversal; the effect is real but a minority one because the clause depends on the supplier actually applying those practices and on the rigour of their implementation.
- CWE-401partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, and secure coding practice reduces memory leaks the way it reduces other implementation defects — a real but minority effect, capped at the clause's declared ceiling of `partial`.
- CWE-403partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, and CWE-403 is an ordinary software implementation weakness that secure coding practice would address; the clause reaches it the way those practices do, at partial because the effect depends on the supplier faithfully implementing the contracted practices and human practice is fallible.
- CWE-409partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-409 is a regular implementation weakness that secure coding and testing would address, but the clause's reach is bounded by the supplier's fallible practice, matching the owner-graded A.8.30 -> CWE-134 anchor at the clause's declared ceiling.
- CWE-41partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-41 is an ordinary implementation defect in path handling, and the same `partial` ceiling the owner set for A.8.30 -> CWE-134 applies here.
- CWE-412partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a supplier implementing those practices would design locks to resist external control; the effect is partial because it depends on the supplier actually applying those practices and the clause's reach is mediated through other controls.
- CWE-413partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-413 is a regular implementation-phase code defect that secure coding and testing practices address, and the clause sits at its declared ceiling of `partial`.
- CWE-415partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a double-free defect in delivered code is reduced the way those practices reduce it; the same reasoning the owner applied to A.8.30 -> CWE-134 (format string) at `partial` applies here, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-416partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary implementation-phase software weaknesses like use-after-free in delivered code the way those practices do, at `partial` — the same reading that graded A.8.30 -> CWE-134 `partial` and that sits at the clause's declared ceiling.
- CWE-419partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so an outsourced system developed under the clause is less likely to ship with an unprotected administrative channel; the clause's ceiling on this verb is partial, and the remainder is the fallibility of the contracted practices and any design choices the supplier makes outside the contract's reach.
- CWE-420partialprevents — A.8.30 carries secure design, threat modeling (item c), and secure development practices (8.25-8.29) into outsourced software development contracts, which reduces instances of this architectural omission in delivered software the way those practices do; however, CWE-420 also arises in hardware contexts (the demonstrative example is Verilog, and observed CVE-2020-8004 concerns flash bus access) that the clause's software-centric contractual requirements do not reach, leaving a nameable remainder.
- CWE-421partialprevents — A.8.30 carries secure design and threat-modelling requirements (items b, c) into outsourced software development, which reaches an architecture/design race-condition flaw in delivered code the way the A.8.30 -> CWE-134 anchor does; the clause's ceiling on this verb is partial because it depends on the supplier actually implementing 8.25-8.29 practices.
- CWE-422partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) it contracts from the supplier, so a Windows GUI application developed under such a contract is less likely to ship an unprotected messaging channel; the remainder is the niche, platform-specific nature of the flaw and the dependence on supplier implementation of those referenced practices, which is the same boundary that graded A.8.30 -> CWE-134 at `partial`.
- CWE-425partialprevents — A.8.30 contracts secure design, coding and testing practices (8.25-8.29) into outsourced development, which addresses authorization enforcement in web applications the same way those practices do; the effect is real but bounded by supplier compliance and the fallibility of the practices themselves, matching the A.8.30 -> CWE-134 anchor at the clause's declared ceiling.
- CWE-426partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a faithful implementation reduces ordinary implementation-level software CWEs like CWE-426 in delivered code, but the practice is fallible and the clause sits at its declared ceiling of `partial`.
- CWE-427partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, and CWE-427 is an ordinary software implementation weakness that those practices address; the clause reduces instances in delivered code the way those practices do, at `partial` because the practice is fallible and the clause has a declared ceiling of `partial` on this verb.
- CWE-431partialprevents — A.8.30 carries its preventive effect through the secure-design, coding and testing practices (8.25–8.29) it contracts from the supplier, which reduce missing-handler defects in delivered software the way those practices do; the owner has set A.8.30's ceiling at `partial` on this verb, and a missing exception handler is the kind of ordinary software implementation weakness those practices reach but do not eliminate.
- CWE-432partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), and CWE-432 is a regular software implementation defect in signal-handler code that those practices would reduce, the same way the owner graded A.8.30 -> CWE-134 at `partial`.
- CWE-433partialprevents — A.8.30 carries secure development practice into outsourced work via contractual requirements referencing 8.25-8.29, and CWE-433 is a regular software weakness (file placement and server configuration) that those practices would address in delivered code, the same way the owner graded A.8.30 -> CWE-134 at `partial`; the clause sits at its declared ceiling.
- CWE-434partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-434 is an implementation defect in upload handling that secure coding/testing practices address, but the clause's mechanism is contractual and fallible, leaving a nameable remainder.
- CWE-435partialprevents — A.8.30's contractual requirements for secure design (8.25), threat modelling, and acceptance testing can prevent some interaction errors by mandating interface specification and integration consideration, but CWE-435 is an emergent, under-studied class that often arises from subtle integration scenarios (case-sensitivity, header handling, OS differences) not fully reached by the clause's standard secure-development requirements.
- CWE-437partialprevents — A.8.30's contractual requirements for secure design (8.25-8.29) and explicit threat-model provision (item c) reach this software design/implementation weakness, reducing instances where the intermediary's endpoint model is incomplete; the remainder is bounded by the inherent challenge of fully modeling third-party endpoint behaviors, which the clause's mechanisms only partially address.
- CWE-440partialprevents — A.8.30's contractual requirements for secure design, coding and testing practices (item b, referencing 8.25-8.29) and its acceptance testing for quality and accuracy of deliverables (item d) reduce some instances of specification-mismatch defects in outsourced software, but CWE-440 is broader than ordinary software CWEs -- it includes hardware design issues (as in the Hack@DAC RISC-V demonstrative example), subtle logic errors, and specification ambiguities that contractual requirements and acceptance testing cannot reach.
- CWE-447partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) it contracts from the supplier, which reach ordinary implementation defects in delivered software at the same `partial` rung as CWE-134; CWE-447 is a UI completeness defect where the feature is missing despite UI feedback, which secure coding and acceptance testing catch only partially.
- CWE-449partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29) plus acceptance testing (8.30d), which reduces ordinary implementation defects in delivered code the way those practices do; UI action-mismatch defects with security implications (e.g., the firewall option-swap CVE) are partially caught, but most CWE-449 instances are functional/UX correctness issues outside the security-focused practices the clause mandates.
- CWE-45partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary input-validation defects in delivered code the way those practices do; CWE-45 is an implementation-level path-handling defect that secure coding practice would catch in a minority of cases, with the same fallibility that bounds the CWE-134 anchor at `partial`.
- CWE-453partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation defects in delivered code the way those practices do; CWE-453 is a regular code-level implementation weakness, and the clause's reach is bounded by the rigour of the contracted practices, matching the owner-graded A.8.30 → CWE-134 anchor.
- CWE-454partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices its contract requires of the supplier (8.25–8.29), so a faithfully implemented clause reduces ordinary software CWEs like CWE-454, but the effect is mediated by those downstream practices and is bounded by supplier compliance — consistent with the owner's `partial` ruling on A.8.30 vs CWE-134.
- CWE-456partialprevents — A.8.30 carries its preventive effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a faithful implementation reduces ordinary software CWEs like CWE-456 in delivered code, but the effect is mediated by fallible human practice and the clause carries a declared ceiling of `partial` on this verb.
- CWE-459partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like incomplete cleanup in delivered code the way those practices do, at `partial` -- the same reading that graded A.8.30 -> CWE-134 `partial` and that sits at the clause's declared ceiling.
- CWE-460partialprevents — A.8.30 contracts secure development practice (8.25–8.29) from the supplier, which carries its effect into ordinary implementation defects like improper exception cleanup, but the clause depends on those downstream practices being effective and is bounded by the ceiling the owner set on this verb.
- CWE-466partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary implementation defects like pointer-range errors in delivered code the way those practices do, but the clause's ceiling on this verb is `partial` because the effect depends on supplier practice and memory-safety defects are subtle enough to slip through.
- CWE-467partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary implementation-phase software CWEs like sizeof-on-pointer the way those practices do, but only partially because the clause depends on the supplier's actual implementation and secure coding is a fallible human practice.
- CWE-47partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like path-equivalence defects in delivered code the way those practices do, at `partial`; the clause's declared ceiling on this verb is `partial`.
- CWE-470partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, and unsafe reflection is a regular software CWE introduced at design/implementation that those practices would address; the clause has a declared ceiling of `partial` on this verb, and the effect is real but a minority one because it depends on the supplier faithfully implementing secure coding.
- CWE-471partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; MAID is an implementation-level defect (assumed-immutable form fields, cookies, mutable arrays) that secure coding guidance and security testing can catch in a minority of cases, with the clause's declared ceiling of `partial` on this verb.
- CWE-472partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a well-implemented clause reduces ordinary input-validation defects like trusting hidden form fields in delivered code the way those practices do; the owner has ruled A.8.30's ceiling on `prevents` at `partial`, and the remainder is the fallibility of the contracted practice plus code the supplier did not write.
- CWE-473partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered PHP code the way those practices do, at the same `partial` rung the owner set for A.8.30 -> CWE-134.
- CWE-474partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-474 is a first-party implementation choice (picking a function whose behavior varies across platforms) that secure coding awareness and cross-platform testing can catch, but the practice is fallible and the clause depends on the supplier actually implementing it, leaving a nameable remainder.
- CWE-475partialprevents — A.8.30 carries secure design, coding and testing practices (8.25-8.29) into outsourced development through contractual requirements, so it reduces instances of this implementation-level weakness the way those practices do; the effect is real but bounded by the fallibility of the practices and the subtlety of undefined-behavior constraints often hidden in macros.
- CWE-476partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation defects like NULL pointer dereferences in delivered code the way those practices do, at `partial` — the clause depends on the supplier actually implementing secure coding and testing, and fallible developers still introduce these defects.
- CWE-477partialfinds — A.8.30 carries its effect through the secure-development and testing practices its contract requires of the supplier (8.25–8.29), so the testing programme it mandates would find some instances of CWE-477 via SAST (which rates this weakness's automated static detection as High), but the reach is indirect — it depends on the supplier's implementation of the required practices, and not every deprecated-function call is in every ruleset, leaving a nameable remainder.
- CWE-477partialprevents — A.8.30 carries its preventive effect through the secure-coding practices (8.25–8.29) its contract requires of the supplier, so a well-implemented clause reduces ordinary software weaknesses like use of obsolete functions in delivered code, but the effect is bounded by the supplier's actual practice and the clause's own ceiling of `partial`.
- CWE-48partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like CWE-48 in delivered code the way those practices do, but only partially because the practice is fallible and the clause has a declared ceiling of `partial` on this verb.
- CWE-480partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so an outsourced implementation under the clause is reviewed, tested and statically analysed, which catches a minority of operator typos; the clause's declared ceiling on this verb is `partial`.
- CWE-481partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary implementation-phase code defects like the =/== typo the way those practices do, but the mechanism is fallible human practice and a different clause carries the stronger effect.
- CWE-482partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25–8.29) its contract requires of the supplier, so a well-implemented clause reduces ordinary implementation-typo CWEs like CWE-482 the way those practices do, but only partially because the clause depends on the supplier actually applying secure coding and code review, and typos of `==` for `=` are subtle enough to slip past.
- CWE-482partialfinds — A.8.30's contractual requirements for secure coding (8.28) and security testing (8.29), plus acceptance testing (d) and audit rights (i), lead to discovery of some CWE-482 instances through the supplier's testing programme, but the clause itself does not perform testing and the discovery is bounded by what the supplier's programme actually covers and what evidence is required.
- CWE-483partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation defects like CWE-483 the way those practices do, but only at the partial rung the owner has set as the clause's ceiling on this verb.
- CWE-483partialfinds — A.8.30's contractual requirements for secure coding and testing practices (8.25-8.29), acceptance testing, and right to audit create the conditions for CWE-483 to be found in outsourced code, but the actual discovery is performed by the supplier's testing programme (8.29), not by A.8.30 itself — consistent with the A.8.30 -> CWE-134 anchor where the clause's effect runs through the controls it mandates.
- CWE-487partialprevents — A.8.30 carries secure coding practices (8.25-8.29) into outsourced development contracts, and CWE-487 is a regular Java implementation weakness that secure coding guidance addresses; the effect is real but partial because the clause's mechanism is contractual and depends on fallible supplier practice, matching the A.8.30 -> CWE-134 anchor.
- CWE-489partialfinds — A.8.30's programme requires the supplier to implement secure development and testing practices (8.25–8.29), acceptance testing, and evidence of testing for malicious content and known vulnerabilities, which would surface active debug code through SAST, code review, and acceptance testing; however, the clause is a contractual/process control whose effect is mediated through supplier compliance and evidence documentation rather than direct testing, so only a minority of instances are reliably found.
- CWE-49partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, and CWE-49 is an ordinary software implementation weakness that those practices reduce; the clause's own ceiling on this verb is `partial`, matching the CWE-134 anchor.
- CWE-491partialprevents — A.8.30 carries its preventive effect through the secure-coding practices (8.25–8.29) its contract requires of the supplier, which would reach a Java clone() implementation defect like CWE-491, but the effect is indirect and depends on the supplier actually implementing those practices — the same ceiling the owner set on A.8.30 vs CWE-134.
- CWE-492partialprevents — A.8.30 carries its effect through the contractual requirement for secure coding practices (8.25–8.29) the supplier must follow, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-492 is a Java implementation defect introduced at coding time, and the clause reaches it at the same `partial` rung as the CWE-134 anchor, with the same fallible-developer remainder.
- CWE-493partialprevents — A.8.30 carries its effect through the secure-coding and security-testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary code-level weaknesses in delivered code the way those practices do; CWE-493 is a coding-practice defect (declaring fields final) that secure coding guidance addresses, but the clause mandates a practice whose effect depends on supplier rigour, leaving a nameable remainder.
- CWE-494partialprevents — A.8.30 contracts the supplier for secure design, coding and testing practices (8.25-8.29), which carry the preventive effect on this ordinary software weakness; the clause's own mechanism is contractual, so its reach is mediated and fallible in the same way the owner graded A.8.30 -> CWE-134.
- CWE-495partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), and CWE-495 is an ordinary implementation-phase code defect that secure coding practice addresses; the clause reduces such defects in delivered code the way those practices do, at the `partial` ceiling the owner set for this clause on regular software CWEs.
- CWE-497partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contractually requires of the supplier, and those practices cover not exposing system information in error messages, debug output or exception handlers — the same mechanism that graded A.8.30 -> CWE-134 `partial` and A.8.28 -> CWE-79 `partial`; the clause reduces instances but the practices are fallible and the ceiling for A.8.30 on this verb is `partial`.
- CWE-498partialprevents — A.8.30 carries its effect through contractual requirements for secure design, coding and testing practices (8.25–8.29) imposed on the supplier, so it reduces ordinary software implementation weaknesses like CWE-498 the way those practices do, but only at the partial rung because the clause depends on the supplier faithfully implementing secure coding and the practice is fallible.
- CWE-499partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25–8.29) its contract requires of the supplier, so a faithful implementation reduces ordinary implementation-level defects like missing serialization denial in delivered code the way those practices do, but the clause depends on fallible supplier practice and A.8.30 carries a declared ceiling of `partial` on this verb.
- CWE-5partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, which reduces programmer-introduced HTTPS misconfigurations in delivered J2EE code, but the weakness also arises from user behaviour and operational deployment choices the clause does not reach, and A.8.30 carries a declared ceiling of `partial` on this verb.
- CWE-501partialprevents — A.8.30 carries its effect through the secure design and coding practices (8.25-8.29) its contract requires of the supplier, which reduce ordinary software weaknesses including trust boundary violations in delivered code; the clause has a declared ceiling of `partial` on this verb, and trust boundary violations are a design-level weakness that secure development practices address but do not eliminate.
- CWE-507partialprevents — A.8.30's contractual requirements for secure development, evidence of testing for malicious content (item f), acceptance testing (item d), and audit rights (item i) reduce but do not eliminate the introduction of a Trojan horse; a determined supplier-side attacker can hide malicious code from their own tests, and the organization's acceptance testing catches only what it is pointed at, leaving a nameable remainder.
- CWE-509partialprevents — A.8.30 directly addresses malicious content via (f) requiring evidence of testing for malicious content upon delivery and (g) for known vulnerabilities, plus (b) secure coding/testing practices and (d) acceptance testing, but the clause mandates evidence of testing rather than performing the testing itself, so prevention depends on the supplier's testing rigor and the organization's verification, which is fallible human practice — the same mechanism that caps A.8.28 vs CWE-502 at partial.
- CWE-51partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like path-normalization defects in delivered code the way those practices do, at `partial` -- the clause sits at its declared ceiling for this verb.
- CWE-510partialprevents — A.8.30's contractual requirements for secure design, coding and testing (b), its specific provision for testing against malicious content upon delivery (f), and its contractual right to audit development processes (i) create a deterrent and preventive effect against trapdoors being inserted by outsourced developers, but a determined malicious actor can still evade these measures, leaving a nameable remainder of trapdoors that come into existence despite the clause.
- CWE-511partialprevents — A.8.30's guidance item (f) directly addresses malicious content and (b) carries secure development practice into the supplier contract, so a well-implemented clause reduces the chance a logic/time bomb is delivered; but the mechanism is contractual requirements and acceptance testing, which a determined or sufficiently hidden bomb can pass, leaving a nameable remainder.
- CWE-512partialprevents — A.8.30's guidance items (b) contractual secure-coding/testing requirements, (c) threat model provision, (d) acceptance testing, and especially (f) evidence of testing against malicious content directly address spyware as a class of malicious/unauthorized functionality in outsourced deliverables, so a well-implemented clause prevents a portion of instances; but the mechanism is contractual and governance-level, dependent on supplier compliance and testing rigour, and spyware is often an intentional, subtle design choice that standard testing evidence does not guarantee catching.
- CWE-515partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reaches a software implementation weakness like CWE-515 the same way it reaches other ordinary software CWEs; covert storage channels are subtle and often look like normal program behaviour, so the contracted practices reduce but do not eliminate their introduction, and the clause's declared ceiling on this verb is `partial`.
- CWE-52partialprevents — A.8.30 carries secure design, coding and testing requirements (8.25–8.29) into the supplier contract, which reduces regular implementation-phase input-validation weaknesses like CWE-52 but does not eliminate them; the clause's own ceiling on this verb is `partial`.
- CWE-520partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25-8.29) in outsourced development, which would catch some instances of .NET impersonation misconfiguration introduced at design or implementation, but operational/deployment-time configuration choices and the fallibility of contracted practices leave a nameable remainder, matching the A.8.30 -> CWE-134 anchor's reasoning.
- CWE-523partialprevents — A.8.30 carries its effect through contractual requirements for secure design, coding and testing practices (8.25-8.29), which would include proper HTTPS/TLS use for login pages, reducing the likelihood of CWE-523 arising in outsourced code the same way it reduces other ordinary software weaknesses; the ceiling is `partial` because the clause depends on the supplier actually implementing the practices and on the referenced controls being effective.
- CWE-526partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25-8.29), so a faithful implementation reduces ordinary software weaknesses like storing sensitive data in cleartext environment variables, but the effect is mediated by fallible supplier practice and is not full.
- CWE-528partialprevents — A.8.30 contracts secure design and coding practices (8.25-8.28) into outsourced development, which can require the supplier to address where core dumps are generated, what they contain, and how they are protected during architecture and design; however, core dump handling is often an operational/configuration concern that may fall outside the explicit contractual design requirements, and the effect depends on the supplier faithfully implementing the referenced secure-development controls.
- CWE-529partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25-8.29) its contract requires of the supplier, and CWE-529 is introduced by missing a security tactic during architecture and design — squarely within what those practices address. Consistent with the owner's A.8.30 -> CWE-134 `partial` anchor: the clause reduces ordinary software weaknesses in delivered code at a minority level because it depends on the supplier actually implementing the contracted practices, and configuration-oriented weaknesses like file placement are peripheral to the clause's main focus.
- CWE-53partialprevents — A.8.30 carries its effect through the secure-coding and testing practices (8.25–8.29) its contract requires of the supplier, so a well-implemented clause reduces ordinary implementation weaknesses like path-equivalence handling in delivered code the way those practices do, but the mechanism is fallible human practice and the clause itself does not directly prevent the defect.
- CWE-531partialprevents — Contractual secure-coding and testing requirements can keep suppliers from introducing sensitive information into test code, but they do not categorically prevent this testing-phase weakness.
- CWE-532partialprevents — A.8.30 carries secure coding practices (8.28) into outsourced work via contract, and secure coding guidance typically addresses what should not be logged, so a faithful implementation reduces instances of CWE-532 in delivered code; the ceiling is `partial` because the effect depends on the rigour of the contracted practice and the clause's own ceiling on this verb is `partial` (per the CWE-134 anchor).
- CWE-536partialprevents — A.8.30 carries its preventive effect through the secure-coding and testing practices (8.25–8.29) its contract requires of the supplier, which reduces ordinary software CWEs like CWE-536 in delivered servlet code, but the clause depends on those other controls and the practice is fallible, so the effect is a minority one.
- CWE-539partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), which include secure design and coding guidance that reaches cookie handling; the clause has a declared ceiling of `partial` on this verb for software weaknesses, and CWE-539 is a design/implementation defect in first-party web code that those practices address only as a slice.
- CWE-54partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses like CWE-54 in delivered code the way those practices do, at the clause's declared ceiling of `partial`.
- CWE-54partialfinds — A.8.30 requires the supplier to implement security testing (8.29) via contract, and that testing programme reaches CWE-54 through static analysis, dynamic testing and penetration testing; but A.8.30 is one step removed -- it mandates the testing rather than performing it, so finding depends on the supplier's actual implementation of 8.25-8.29, leaving a nameable remainder of instances the supplier's programme does not catch.
- CWE-541partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25–8.29) in outsourced development, and CWE-541 is an ordinary implementation-phase coding weakness (credentials placed in an include file) that those practices would catch; the effect is partial because it depends on the supplier faithfully implementing the contracted practices, which is fallible, and A.8.30 carries a declared ceiling of `partial` on this verb.
- CWE-543partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) it contracts from the supplier, and thread-safe singleton construction is a standard secure-coding topic, so a well-implemented clause reduces ordinary implementation defects of this kind — but the mechanism is human practice, which is fallible, and the clause's declared ceiling on this verb is `partial`.
- CWE-546partialprevents — A.8.30 carries its effect through contractual requirements for secure coding practices (8.25-8.29), which can include coding standards that prohibit or limit TODO/FIXME/HACK comments in delivered code, reducing some instances; however, suspicious comments are a code-quality indicator rather than a security defect, are often added legitimately during development, and are not comprehensively addressed by typical secure-coding standards, leaving a nameable remainder.
- CWE-547partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts from the supplier, and secure coding practice reduces hard-coded security-relevant constants in delivered code the way it reduces other ordinary software weaknesses; the clause's declared ceiling on this verb is `partial`, and the remainder is the fallibility of contracted practice plus code the supplier does not write.
- CWE-548partialprevents — Outsourced-development contracts requiring secure design, coding and testing reduce the introduction of directory-listing defects, but fallible supplier practices and incomplete coverage leave a substantial remainder.
- CWE-549partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; password field masking is a standard secure coding/UI design practice that would be covered by such contractual requirements, but the effect is partial because it depends on the supplier faithfully implementing the contracted practices.
- CWE-551partialprevents — A.8.30 carries its effect through the contractual requirements it places on the supplier for secure design, coding and testing practices (8.25–8.29), which reduce ordinary software implementation defects in delivered code the same way those practices do; CWE-551 is an implementation defect in authorization-check ordering that secure coding and testing practices can catch, but the clause's reach is indirect and fallible, matching the A.8.30 -> CWE-134 anchor at `partial`.
- CWE-553partialprevents — A.8.30 mandates contractual requirements for secure coding/testing (b), acceptance testing (d), and evidence of security testing (f,g) for outsourced development, which can catch a shell file placed in an accessible directory before delivery; however, the clause governs a practice rather than a mechanism, the practice is fallible, and CWE-553 also arises from operational/deployment decisions outside the outsourced-development scope, leaving a nameable remainder.
- CWE-554partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a well-implemented clause reduces ordinary software weaknesses in delivered code the way those practices do; input validation framework usage falls under secure coding guidance, but the mechanism is human practice at the supplier and is fallible, capping the effect at the clause's declared ceiling of partial.
- CWE-555partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; a plaintext password in a configuration file is the kind of misconfiguration secure coding guidance addresses, but the clause's ceiling on this verb is `partial`.
- CWE-556partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-556 is a software configuration weakness in scope of outsourced development, but the clause's mechanism is contractual and depends on the rigour of the supplier's implementation, leaving a nameable remainder.
- CWE-563partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary implementation weaknesses like dead stores in delivered code the way those practices do, but only at the partial rung the clause reaches on software weaknesses.
- CWE-564partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts the supplier to follow, so a faithfully implemented clause reduces ordinary software CWEs like CWE-564 in delivered code the way those practices do, but the clause's own ceiling is `partial` because the contract depends on those other controls actually being applied.
- CWE-565partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-565 is an architecture/design and implementation omission in web code that secure design and coding guidance would reach, but the clause's ceiling on this verb is `partial`.
- CWE-567partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a faithful implementation reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-567 is a regular implementation-phase code defect that secure coding guidance on thread safety would address, but the clause's mechanism is human practice and falls short of full coverage, matching the owner-graded A.8.30 -> CWE-134 anchor at the same rung.
- CWE-570partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-570 is an implementation-phase logic defect that secure coding and review would catch, but the clause's reach is contractual and fallible, leaving a nameable remainder.
- CWE-574partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software coding-practice weaknesses in delivered code the way those practices do; CWE-574 is a Java/EJB coding violation that secure coding guidance reaches, but only as a fallible human practice carried through a contract, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-574partialfinds — A.8.30's contractual requirements for secure coding/testing (8.25-8.29), acceptance testing (item d), and audit rights (item i) provide mechanisms that can discover CWE-574 instances, but the clause's primary effect is pre-deployment prevention, and the actual finding is mediated through the testing activities A.8.30 requires rather than performed by A.8.30 itself.
- CWE-576partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a faithful implementation reduces ordinary software coding weaknesses like the EJB java.io misuse in delivered code, but only at the level those practices reach — a minority effect bounded by supplier compliance.
- CWE-576partialfinds — A.8.30 requires the supplier to provide evidence of security testing (items d, f, g) and grants audit rights (item i), so the receiving organization knows testing was performed and the supplier's A.8.29 programme (SAST/code review) is contractually mandated to run — CWE-576 is detectable by static analysis, so a share of instances surfaces through that channel. But A.8.30 itself does not perform testing; the finding is done by the supplier's tools under A.8.29, and acceptance testing (item d) is functional in nature and would not catch this code-level EJB violation on its own.
- CWE-577partialprevents — A.8.30 carries its effect through the secure-coding practices (8.28) its contract requires of the supplier, so an outsourced developer following those practices would not introduce the EJB socket violation; the same reasoning the owner applied to A.8.30 vs CWE-134, and the clause's declared ceiling on this verb is `partial`.
- CWE-579partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, and CWE-579 is an ordinary Java/J2EE implementation defect that those practices would reach; the owner's established reading of A.8.30 on software weaknesses (CWE-134 = partial) applies, with the same fallible-practice remainder and the same declared ceiling.
- CWE-58partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) it contracts from the supplier, the same mechanism the owner graded `partial` for CWE-134; CWE-58 is an ordinary implementation defect in first-party code that those practices would partially address, but the Windows 8.3 filename behaviour is a niche detail not reliably covered by standard secure coding guidance or testing checklists.
- CWE-580partialprevents — A.8.30 contracts for secure coding practices (8.25-8.29) from the supplier, which would catch a missing super.clone() call the way those practices do; the effect is real but a minority one because the supplier's implementation is fallible, matching the A.8.30 -> CWE-134 anchor at the same rung.
- CWE-581partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-581 is a regular Java coding defect that secure coding standards and code review would catch, but the clause's effect is mediated by supplier practice and is bounded at the ceiling the owner set for this clause.
- CWE-583partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25-8.29) its contract requires of the supplier, so a finalize() method declared public in delivered code is reduced the way those practices reduce ordinary software weaknesses, but the clause sits at its declared ceiling of `partial` because the practice is fallible and the supplier's developers are not the organization's own.
- CWE-584partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation defects in delivered code the way those practices do; CWE-584 is a code-level finally-block defect introduced at implementation, and a well-implemented outsourced-development clause catches a minority of such instances because the underlying practice is fallible.
- CWE-585partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary code-level implementation defects like empty synchronized blocks the way those practices do, at `partial`; the clause's declared ceiling on this verb is `partial`.
- CWE-586partialprevents — A.8.30 carries its effect through the secure-coding practices (A.8.25–8.29) its contract requires of the supplier, which would include avoiding explicit finalize() calls; the owner has graded A.8.30's effect on ordinary software CWEs at `partial` because the clause depends on those downstream practices and developers remain fallible, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-587partialprevents — A.8.30 carries secure coding and testing requirements (8.25-8.29) into outsourced development contracts, which addresses hardcoded pointer addresses as a C-level implementation defect the way secure coding practice does; the effect is partial because the clause depends on the supplier's implementation of those practices and developers remain fallible, matching the A.8.30 -> CWE-134 anchor.
- CWE-587partialfinds — A.8.30's contractual requirements for secure development practices (8.25-8.29) and acceptance testing reach CWE-587 through the static/dynamic analysis those practices mandate, but the clause's mechanism is primarily pre-deployment acceptance (which is `prevents`) and its reach is limited to outsourced development, leaving a nameable remainder of instances the programme does not surface.
- CWE-588partialprevents — A.8.30 contracts secure design, coding and testing practices (8.25–8.29) into the supplier relationship, so it carries the same partial preventive effect against ordinary C-language implementation defects like CWE-588 that those practices do, capped at the clause's declared ceiling of partial.
- CWE-588partialfinds — A.8.30 contracts for the supplier to perform security testing (8.29), which would find CWE-588 via SAST, but the clause itself does not run analysis; discovery depends on the supplier's implementation of the contracted testing programme, so only a minority of latent instances are surfaced through this contractual wrapper.
- CWE-589partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, and secure coding practice addresses awareness of platform API availability; the effect is real but bounded by the supplier's implementation of those referenced practices, matching the clause's declared ceiling.
- CWE-59partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-59 is an ordinary implementation defect, but the clause's reach is bounded by the supplier's fallible practice and the ceiling on this verb is `partial`.
- CWE-590partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation defects in delivered code the way those practices do; CWE-590 is such a defect, and the clause's declared ceiling on this verb is `partial`.
- CWE-591partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) it contracts from the supplier, which reduce ordinary software implementation weaknesses including improper memory locking; the same logic that graded A.8.30 vs CWE-134 partial applies here, with the remainder being fallible practice and platform-specific memory-locking subtleties the contract does not fully reach.
- CWE-594partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a well-implemented clause reduces instances of this coding defect the way those practices do, but the supplier's practices are fallible and the clause depends on those other controls being properly implemented, leaving a nameable remainder.
- CWE-595partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25–8.29) in outsourced development, so a supplier implementing those practices will catch most reference-comparison defects, but the clause's effect runs through the supplier's fallible practice rather than a direct mechanism, matching the A.8.30 -> CWE-134 anchor at the clause's declared ceiling.
- CWE-598partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), so a faithful implementation reduces instances of CWE-598 in delivered code the way those practices do — real but a minority effect, with the same `partial` ceiling the owner set on this clause for regular software CWEs.
- CWE-6partialprevents — A.8.30's contractual requirements for secure design/coding/testing (b) and acceptance testing (d) can require the outsourced developer to set session ID length to 128 bits and verify it, but the control is a governance/contractual layer whose effect depends on the developer's compliance and the rigour of the test plan — a fallible practice, similar to A.8.28's mechanism graded `partial` for analogous code-level weaknesses.
- CWE-603partialprevents — A.8.30 carries its effect through the secure-design and secure-coding practices its contract requires of the supplier (8.25–8.29), which would mandate server-side authentication and so prevent most instances of this architectural flaw from being delivered; the clause sits at its declared ceiling of `partial` because the mechanism is human practice and fallible, and a supplier can still ship client-side authentication despite the contractual requirement.
- CWE-605partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-605 is a socket-binding defect that secure coding guidance and security testing would catch in development, but the clause's mechanism is contractual and depends on those other controls, leaving a fallible remainder.
- CWE-608partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary coding defects in delivered code the way those practices do; CWE-608 is exactly such a defect, but the clause's ceiling on this verb is `partial` because the effect depends on the supplier's implementation of the contracted practices.
- CWE-609partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, and double-checked locking is an ordinary software implementation defect those practices reach; the clause has a declared ceiling of `partial` on this verb because the supplier's practice is fallible.
- CWE-611partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like XXE in delivered code the way those practices do, at `partial` -- the same reasoning the owner applied to A.8.30 vs CWE-134 (format string).
- CWE-612partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) its contract requires of the supplier, and CWE-612 is an ordinary software design/implementation weakness in how search indices handle authorization, so the clause reduces instances the way those practices do; the ceiling is `partial` because the clause depends on those other controls being implemented.
- CWE-614partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software coding defects like a missing Secure cookie flag the way those practices do, but the contracted practices are fallible and a nameable remainder of instances still arises.
- CWE-615partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-615 is an implementation-phase code-comment weakness that secure coding guidance reaches, but the clause's mechanism is human practice and fallible, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-618partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) it contracts from the supplier, which reach this ordinary software weakness in the same way they reach CWE-134, but the practices are fallible and supplier-dependent, leaving a nameable remainder.
- CWE-621partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation defects like CWE-621 the way those practices do — at `partial`, because the contracted practices are fallible and the clause sits at its declared ceiling on this verb.
- CWE-622partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation defects like improper argument validation in hooks the way those practices do; the owner has graded A.8.30 at `partial` on this verb for software CWEs generally, and CWE-622 is a regular implementation-phase defect that secure coding reaches only partially.
- CWE-623partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; an ActiveX safe-for-scripting marking is a design/coding decision a supplier's secure-coding and review practices can catch, but the clause's effect is mediated by the supplier's implementation and is not direct.
- CWE-625partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; a permissive regex is a regular implementation defect that secure coding and testing reach some of the time, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-627partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses like dynamic variable evaluation in delivered code the way those practices do, but secure coding is a fallible human practice and the clause's ceiling on this verb for software CWEs is `partial`.
- CWE-628partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-628 is a regular implementation-phase defect that secure coding and testing reach partially, with the same ceiling the owner set on this clause.
- CWE-64partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) it contracts from the supplier, and proper handling of .LNK shortcut resolution is a code-level decision those practices would reach; the effect is indirect, depends on supplier implementation, and addresses only a slice of how this weakness arises.
- CWE-640partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a well-implemented clause reduces ordinary software weaknesses in delivered code the way those practices do; CWE-640 is a regular design/implementation CWE that secure design and coding practices address, but the clause depends on those other controls being properly implemented, capping the effect at `partial`.
- CWE-641partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), which would reduce instances of CWE-641 in delivered code the way those practices do, but the clause depends on the supplier's implementation and human practice is fallible, leaving a nameable remainder.
- CWE-643partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts from the supplier, and XPath injection is an ordinary implementation-level injection flaw those practices address; the owner graded the analogous format-string pair at `partial` and declared `partial` as the clause's ceiling on this verb.
- CWE-644partialprevents — A.8.30 carries its effect through the secure-coding and testing practices (8.25–8.29) its contract requires of the supplier, which reduce ordinary implementation defects like unneutralized HTTP header content the way those practices do, but the clause's mechanism is contractual and human-practice-dependent, so it moves a minority of instances — the same reading the owner applied to A.8.30 vs CWE-134.
- CWE-645partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), so a faithful implementation reduces the introduction of design-level authentication weaknesses like an overly restrictive lockout mechanism, but the effect is indirect and depends on the supplier's practice — a minority of instances, consistent with the clause's declared ceiling of `partial` on `prevents`.
- CWE-646partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software weaknesses such as file-name/extension reliance in delivered code the way those practices do, at `partial`; the clause's declared ceiling on this verb is `partial`.
- CWE-647partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) it contracts from the supplier, so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-647 is a regular implementation defect that secure coding and security testing would catch, but the clause's effect is indirect and depends on the supplier actually following the contracted practices, matching the same `partial` ceiling the owner set for A.8.30 -> CWE-134.
- CWE-648partialfinds — A.8.30's programme — acceptance testing (d), audit rights (i), and required evidence of supplier testing (f, g) — would discover some instances of incorrect privileged-API use through code review and security testing of deliverables, but the clause does not mandate specific testing methods and its effect is mediated through the supplier's compliance with 8.25–8.29, leaving a nameable remainder where acceptance testing is shallow or the supplier's own testing misses the flaw.
- CWE-649partialprevents — A.8.30 mandates contractual secure-design requirements, threat modelling, and acceptance testing for outsourced development, which if well implemented would specify integrity checks for security-relevant inputs and catch their absence — but the control is governance-level, the prevention depends on the specificity of the contract and the rigour of testing, and it reaches only outsourced code, leaving a fallible slice rather than the bulk.
- CWE-65partialfinds — A.8.30's mechanism is contracting the supplier to apply 8.25–8.29 (including security testing) and granting audit/acceptance rights, so the supplier's SAST/DAST/penetration programme reaches this first-party implementation weakness; however, CWE-65 (Windows hard-link handling) is a niche file-system behaviour that standard test suites rarely target, so only a minority of latent instances are surfaced by one cycle of the programme.
- CWE-650partialprevents — A.8.30 carries its effect through contractual requirements for secure design, coding and testing practices (8.25-8.29), which reduce ordinary software weaknesses like CWE-650's flawed assumption that GET cannot modify state, but the mechanism is fallible human practice at the supplier, capping the effect at a minority of instances.
- CWE-651partialprevents — A.8.30 carries its effect through contractual requirements for secure design and coding practices (8.25-8.29), which would lead a supplier to consider what information is exposed in WSDL files during design; the clause has a declared ceiling of `partial` on this verb and depends on the secure-development controls it references, leaving the access-control half of the weakness (who can reach the WSDL) outside its reach.
- CWE-651partialfinds — A.8.30 mandates acceptance testing under 8.29 and contractual secure development practices (8.25-8.28), so its programme reaches CWE-651 through security review of the supplier's WSDL artifact; however, A.8.30 is a contractual/process wrapper whose effectiveness depends on supplier implementation rigour, and WSDL information exposure is not universally caught by every acceptance test, leaving a nameable remainder of instances the testing programme misses.
- CWE-654partialprevents — A.8.30's contractual requirements for secure design (referencing 8.25) reach the architecture-level decision to use multiple factors, so a supplier bound by the contract is less likely to ship single-factor authentication; the effect is partial because the contract can require secure design practice but cannot guarantee the supplier actually implements multi-factor decisions, mirroring the A.8.30 -> CWE-134 anchor.
- CWE-66partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-66 is a software implementation defect in file-name handling that secure coding and testing would address, but the clause's effect is mediated by supplier practice and is bounded at the clause's declared ceiling of `partial`.
- CWE-663partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25-8.29) it contracts the supplier to follow, which reach ordinary implementation defects like non-reentrant function calls in concurrent contexts; the practice is fallible and a minority of instances are caught, matching the clause's declared ceiling on this verb.
- CWE-664partialprevents — A.8.30 carries secure design, coding and testing practice (8.25–8.29) into outsourced software via contractual requirements, which reduces ordinary software resource-lifecycle defects the way those practices do; the effect is partial because the clause depends on those other controls being implemented and the practices are fallible, matching the owner-graded ceiling for A.8.30 on this verb.
- CWE-67partialprevents — A.8.30 carries secure design, coding and testing practice (8.25–8.29) into outsourced work via contract, so a faithful implementation reduces ordinary software implementation defects like improper handling of Windows device names; the clause's ceiling on `prevents` is `partial` because the effect depends on the supplier's actual practice.
- CWE-676partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25-8.29) its contract requires of the supplier, which reduce ordinary implementation weaknesses like use of dangerous functions, but the practice is fallible and the clause sits at its declared ceiling of `partial`.
- CWE-683partialfinds — A.8.30 contracts for secure development practices including testing (items d, f, g referencing 8.29), so the supplier's SAST/DAST programme is required and can detect some CWE-683 instances — but A.8.30 itself does not run tests, and SAST misses instances in dynamically typed code, variadic functions, and across supplier boundaries the contract does not reach.
- CWE-685partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts the supplier to apply, which reduce ordinary software implementation defects like argument-count errors but do not eliminate them, matching the owner's `partial` ceiling for this clause on regular software CWEs.
- CWE-686partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-686 is a code-level type-error defect that secure coding practice addresses, but the effect is partial because the clause depends on the supplier's implementation and developers remain fallible.
- CWE-687partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), so a faithfully implemented clause reduces ordinary implementation-phase code defects like CWE-687 in delivered code the way those practices do; the owner graded the analogous pair A.8.30 -> CWE-134 at `partial` for the same reason, and that is the clause's declared ceiling on this verb.
- CWE-688partialfinds — A.8.30's contractual requirements for secure design, coding and testing practices (8.25-8.29), acceptance testing (d), and evidence of testing (f, g) lead to some discovery of CWE-688 through the supplier's SAST/code review, but the clause itself does not perform testing -- it depends on the supplier implementing 8.29, and acceptance testing is typically functional rather than security-focused, so only a minority of latent instances are surfaced.
- CWE-689partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, which reduce ordinary software implementation weaknesses in delivered code; CWE-689 is a code-level race condition that secure coding guidance and security testing would catch in a minority of instances, and the clause sits at its declared ceiling of `partial` on this verb.
- CWE-69partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices its contract requires of the supplier (8.25–8.29), so a faithfully implemented clause reduces regular software implementation CWEs in delivered code; CWE-69 is an implementation-phase Windows-specific defect that secure coding practice would catch in a minority of instances, with the clause's declared ceiling of `partial` on this verb.
- CWE-690partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a well-implemented clause reduces regular software CWEs like CWE-690, but the effect is mediated by the supplier's practice and the clause sits at its declared ceiling of `partial`.
- CWE-691partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary code-level weaknesses in delivered code the way those practices do; CWE-691 is an implementation-phase control-flow defect that secure coding and testing practices reach, but the practice is fallible and a different clause carries the stronger effect, matching the A.8.30 -> CWE-134 anchor at the same rung.
- CWE-692partialprevents — A.8.30 carries its preventive effect through the secure-coding practices (8.25-8.29) its contract requires of the supplier, and CWE-692 is an ordinary software implementation defect in how XSS filtering is written; the owner has graded A.8.30 -> CWE-134 (format string) at `partial` for the same reason, and A.8.28 -> CWE-79 (XSS) at `partial`, both of which bound this pair at the same rung.
- CWE-693partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), so it prevents some protection-mechanism failures in outsourced code the way those practices do; CWE-693 is far broader than the format-string case (architecture, runtime, ignored-mechanism failures), so the remainder is large and not cleanly bounded.
- CWE-695partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so a faithful implementation reduces instances of this regular software CWE the way those practices do; the owner has ruled A.8.30's ceiling on this verb at `partial` because the clause depends on 8.25–8.29 and contractual requirements cannot guarantee developers never reach for prohibited low-level functionality.
- CWE-697partialprevents — A.8.30 carries secure coding practice (8.28) into the supplier relationship via contractual requirements, which reduces the incidence of implementation-phase code defects like incorrect comparisons, but the effect is mediated through a fallible human practice and the clause's own ceiling on this verb is partial.
- CWE-698partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), reducing ordinary implementation-phase software weaknesses in delivered code the way those practices do; CWE-698 is such a weakness, so the clause prevents a minority of instances, with the same ceiling the owner set for A.8.30 on CWE-134.
- CWE-707partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), reducing neutralization failures in delivered code the way those practices do; the same mechanism and ceiling that graded A.8.30 -> CWE-134 at `partial` apply to the broader CWE-707 parent class.
- CWE-708partialprevents — A.8.30 carries its effect through the secure-development practices (8.25 to 8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses like incorrect ownership assignment the way those practices do, at `partial`; the clause's declared ceiling on this verb is `partial`.
- CWE-72partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) it contracts into outsourced development, so it reduces ordinary software implementation weaknesses the way those practices do; CWE-72 is a narrow, platform-specific path-handling defect that secure coding practice would address, but the effect is partial because the clause depends on the supplier implementing the contracted practices and the weakness is too obscure to be named in most contracts.
- CWE-73partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a well-implemented clause reduces ordinary software weaknesses like CWE-73 in delivered code the way those practices do, at partial -- the same reading the owner applied to A.8.30 vs CWE-134.
- CWE-733partialprevents — A.8.30's contractual requirements for secure coding (8.28) and security testing (8.29) can include practices that resist compiler optimization of security-critical code (volatile pointers, compiler flags, secure memory functions), so a faithfully implemented clause reduces some instances; the remainder is bounded by developer awareness of this specialized build-phase issue and the variability of compiler behavior, which the clause does not directly reach.
- CWE-749partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-749 is a regular design/coding weakness those practices address, but the clause mandates a fallible practice rather than a mechanism, leaving a nameable remainder.
- CWE-756partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so a faithful implementation reduces instances of missing custom error pages in outsourced code the way those practices do; the owner has ruled A.8.30's ceiling on this verb at `partial` for regular software CWEs, and CWE-756 is one of those, with the remainder bounded by the clause's dependence on other controls and by error-page configuration that can be introduced at installation, system configuration, or operation phases outside the development contract's reach.
- CWE-757partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices its contract requires of the supplier (8.25–8.29), which would address algorithm-downgrade design choices in outsourced development the way those practices do, but the clause's mechanism is contractual and human-practice-mediated, so a minority of instances are prevented and the remainder is the fallibility of the practice.
- CWE-759partialprevents — A.8.30 carries its effect through the secure-coding and secure-development practices its contract requires of the supplier (8.25–8.29), so a faithful implementation reduces ordinary software implementation defects such as unsalted hashing in delivered code, but the clause's reach is bounded by the supplier's actual practice and by what the contract specifies, leaving a nameable remainder.
- CWE-76partialfinds — A.8.30's contractual requirements (acceptance testing per 8.29, evidence of testing against malicious content and known vulnerabilities) ensure the supplier's testing programme is in place, and that programme would discover some instances of CWE-76 through security testing, but A.8.30 is a contractual wrapper that delegates the actual testing, and CWE-76's equivalent-encoding variants require specific test-case design that a generic testing mandate does not guarantee.
- CWE-76partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25-8.29) in outsourced development, which carry the same partial effect against equivalent-special-element handling that those clauses carry against ordinary software CWEs; the effect is real but bounded by supplier implementation fidelity, matching the CWE-134 anchor on this same clause.
- CWE-760partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a faithful implementation reduces ordinary software implementation weaknesses like predictable-salt usage the way those practices do, at `partial` -- the clause depends on those other controls and human practice is fallible, matching the owner-graded A.8.30 -> CWE-134 anchor.
- CWE-765partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25–8.29) in outsourced development, so a supplier following those practices will catch some instances of CWE-765 through code review and testing, but the effect is indirect and fallible, matching the clause's declared ceiling of `partial` on this verb.
- CWE-766partialprevents — A.8.30 contracts for secure coding practices (8.25–8.29) in outsourced development, so a critical field declared public instead of private is the kind of ordinary software weakness those practices reduce, but the effect is mediated by the supplier's implementation and the clause's ceiling on `prevents` is `partial`.
- CWE-767partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like CWE-767 the way those practices do, at `partial` -- the clause depends on supplier implementation and human practice is fallible, matching the A.8.30 -> CWE-134 anchor.
- CWE-770partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-770 is such an ordinary software weakness (missing limits in resource allocation), and the clause's declared ceiling on this verb is `partial`.
- CWE-771partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) it contracts from the supplier, so it reduces ordinary implementation weaknesses like missing-reference resource leaks in delivered code the way those practices do, at the clause's `partial` ceiling.
- CWE-772partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts from the supplier, so it reduces ordinary software implementation weaknesses like CWE-772 in the same way those practices do, at the clause's declared ceiling of `partial`.
- CWE-773partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a faithfully implemented clause reduces regular software implementation defects like missing file-handle reclamation, but the effect is mediated by those other controls and the supplier's practice is fallible.
- CWE-774partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), and CWE-774 is an ordinary software implementation weakness that secure coding practice would address; the clause reaches it the way those practices do, at the clause's declared ceiling of `partial`.
- CWE-775partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a well-implemented contract reduces ordinary implementation weaknesses like missing file-descriptor release in delivered code the way those practices do, but secure coding is a fallible human practice and the clause's ceiling on this verb is `partial`.
- CWE-776partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier, which reduce ordinary software implementation weaknesses like insecure XML parsing configuration in delivered code, but the practices are fallible and the clause depends on those other controls being properly implemented, so only a minority of instances are prevented.
- CWE-777partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) it contracts from the supplier, so a faithful implementation reduces ordinary implementation-phase software CWEs like CWE-777; the ceiling is `partial` because the effect depends on the supplier's practice and the clause does not itself inspect regex anchors.
- CWE-779partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices its contract requires of the supplier (8.25–8.29), so an organization that specifies appropriate logging levels in its secure coding standards will see fewer instances of excessive logging in delivered code, but the clause's reach is indirect and depends on what the contract specifies — a minority of instances, matching the A.8.30 → CWE-134 anchor.
- CWE-78partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary software CWEs like OS command injection in delivered code the way those practices do, but the effect is mediated by the supplier's implementation and is not complete.
- CWE-78partialfinds — A.8.30's programme requires acceptance testing per 8.29 and evidence of testing for known vulnerabilities, but as a contractual wrapper it does not itself perform testing; for latent instances already in deployed code, its reach is limited to ongoing monitoring, audit rights, and disclosure-based evidence — mechanisms that surface a minority of OS command injection instances, with most custom-code injection flaws escaping because they are not published CVEs and the acceptance testing that would have caught them is development-time.
- CWE-782partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier, which reach access-control implementation in outsourced driver/OS code and reduce a minority of IOCTL access-control defects; the clause sits at its declared ceiling of `partial` because the effect depends on supplier practice and on the rigour of acceptance testing, and IOCTL access control is a low-level implementation detail that secure-coding requirements only partly govern.
- CWE-785partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25–8.29) it contracts from the supplier, so it reduces ordinary software implementation defects like CWE-785 the way those practices do, but only at the partial rung because the clause depends on the supplier's actual implementation and human practice is fallible.
- CWE-785partialfinds — A.8.30 requires the supplier to follow secure testing practices (8.25-8.29), provide evidence of testing for known vulnerabilities, submit to acceptance testing, and grant audit rights; through these the programme can discover some instances of CWE-785 in delivered code, but the clause does not mandate static analysis specifically and the finding is indirect, so a minority of instances are found.
- CWE-786partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like buffer underflow in delivered code the way those practices do, at `partial` -- the clause's effect is mediated through the supplier's fallible practices, and A.8.30 carries a declared ceiling of `partial` on this verb.
- CWE-787partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary implementation-phase memory-safety defects in delivered code the way those practices do; the clause has a declared ceiling of `partial` on this verb, and the same reasoning that graded A.8.30 -> CWE-134 `partial` applies here.
- CWE-788partialprevents — A.8.30 carries its preventive effect through the secure-development practices its contract requires of the supplier (8.25-8.29), so it reduces ordinary implementation-phase buffer overflow weaknesses in delivered code the way those practices do, at `partial`; the clause sits at its declared ceiling for this verb.
- CWE-789partialprevents — A.8.30 carries its preventive effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation defects like CWE-789 in delivered code the way those practices do, at `partial` -- the clause's ceiling on this verb.
- CWE-793partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; CWE-793 is a regular software CWE of the same kind as CWE-134, which the owner graded `partial` on this same clause and verb.
- CWE-794partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) it contracts from the supplier, and CWE-794 is a regular software implementation defect in filtering logic that those practices address; the owner has graded the analogous pair A.8.30 vs CWE-134 at `partial` for the same reason, and A.8.30 carries a declared ceiling of `partial` on this verb.
- CWE-795partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts from the supplier, so a faithful implementation reduces ordinary software implementation defects like incomplete filtering of special elements; the effect is real but bounded by the fallibility of the contracted practice, matching the owner's `partial` ceiling for this clause.
- CWE-797partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) it contracts from the supplier, so a well-implemented clause reduces ordinary software input-filtering defects like CWE-797 the way those practices do, but the effect is bounded by supplier implementation and the clause's own ceiling on this verb is `partial`.
- CWE-798partialprevents — A.8.30 carries its effect through the secure-coding practices (A.8.28) its contract requires of the supplier, which reduces hard-coded credentials in delivered code the way those practices do; the clause depends on the supplier actually implementing secure coding, and secure coding is a fallible practice, so a minority of instances are prevented.
- CWE-80partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; XSS is a regular software CWE that secure coding (8.28) and security testing (8.29) reach at `partial`, and A.8.30 inherits that ceiling.
- CWE-805partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary software implementation weaknesses like CWE-805 in delivered code the way those practices do, but the effect is partial because it depends on supplier implementation and the clause's reach is contractual rather than direct.
- CWE-806partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary implementation-phase software weaknesses like CWE-806 the way those practices do, but only at the clause's declared ceiling of `partial`.
- CWE-807partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-807 is a design/implementation weakness that secure coding/design guidance addresses, but the clause mandates a practice whose coverage depends on the supplier's rigour, leaving a nameable remainder.
- CWE-81partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary input-neutralization weaknesses in delivered code the way those practices do; the clause's ceiling on this verb is `partial` and the strongest control for CWE-81 is A.8.29 security testing.
- CWE-820partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary implementation-phase software weaknesses in delivered code the way those practices do; CWE-820 is such a weakness, but the clause's mechanism is contractual and depends on the supplier's actual implementation, leaving a nameable remainder of synchronization defects that escape the contract's reach.
- CWE-821partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; synchronization defects are subtle and the clause's effect is bounded by supplier implementation, matching the CWE-134 anchor at the same rung.
- CWE-822partialprevents — A.8.30 carries secure coding and testing practices (8.25–8.29) into outsourced development via contractual requirements, reducing implementation-phase memory-safety defects like untrusted pointer dereference, but the clause mandates a fallible practice rather than a mechanism and depends on the underlying controls to do the work, so the effect is a minority reduction.
- CWE-823partialprevents — A.8.30 carries secure design, coding and testing practices (8.25-8.29) into outsourced development contracts, which reduces ordinary implementation-phase memory-safety flaws like CWE-823 in delivered code the way those practices do, but the effect is mediated by fallible human practice and depends on the referenced clauses being implemented, capping the rung at partial.
- CWE-825partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary implementation-phase code defects like use-after-free the way those practices do; the owner has set a ceiling of `partial` on this verb for the clause, and the mechanism is fallible human practice.
- CWE-826partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a faithful implementation reduces ordinary software CWEs including resource-lifetime bugs; CWE-826 is a subtle implementation defect that secure coding practice helps with but does not reliably prevent, matching the clause's declared ceiling on this verb.
- CWE-83partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary software CWEs like CWE-83 in delivered code the way those practices do; the clause's ceiling on this verb is `partial` because the mechanism is fallible human practice.
- CWE-830partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), and CWE-830 is an ordinary software weakness in delivered code that those practices reach — threat modeling (c) and secure coding/testing guidance would catch some inclusions of untrusted web functionality — but the weakness often arises from a deliberate design choice or an unawareness of the dependency, which the clause's indirect mechanism does not fully prevent.
- CWE-831partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation defects in delivered code the way those practices do; CWE-831 is a first-party C implementation defect that secure coding guidance and security testing can catch but not eliminate, matching the A.8.30 -> CWE-134 anchor at the clause's `partial` ceiling.
- CWE-832partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so it reduces ordinary implementation-phase software weaknesses like CWE-832 the way those practices do, but only at the level the supplier actually implements them — consistent with the owner's `partial` grade for A.8.30 vs CWE-134.
- CWE-833partialprevents — A.8.30 carries its effect through the secure-design, coding and testing practices (8.25–8.29) its contract requires of the supplier; secure coding can mandate lock-ordering discipline and security testing can surface some deadlock conditions, so a minority of deadlock instances are kept out at implementation, but deadlock is a concurrency/logic defect outside the security focus of those practices, leaving most instances untouched.
- CWE-836partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) it contracts from the supplier, and a well-implemented contract reaches this architectural authentication flaw the way those practices do; the ceiling is `partial` because the clause depends on the supplier's implementation of those practices, mirroring the A.8.30 -> CWE-134 anchor.
- CWE-838partialprevents — A.8.30 carries its effect through the secure-coding practices (8.25–8.29) its contract requires of the supplier, which include proper output encoding; this reduces instances of CWE-838 in delivered code the way those practices do, but the clause depends on those other controls and its ceiling on this verb is partial.
- CWE-842partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-842 is a software-level access-control defect introduced in implementation/operation that contracted secure development reaches at the same partial level as other regular software CWEs.
- CWE-843partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; type confusion is a regular implementation defect that secure coding practice addresses, but the clause mandates a practice rather than a mechanism, leaving a nameable remainder.
- CWE-85partialprevents — A.8.30 carries its preventive effect through the secure design, coding and testing practices (8.25–8.29) it contracts into outsourced development, which is the same mechanism that reduces ordinary software CWEs like CWE-85; the owner has set a declared ceiling of `partial` for this clause on `prevents`, and CWE-85 is a regular implementation-phase XSS weakness within that reach.
- CWE-86partialfinds — A.8.30's programme requires the supplier to perform secure development and testing (8.25–8.29) and to provide evidence of testing for known vulnerabilities, plus acceptance testing — so the testing practices it contracts for would find CWE-86 instances in delivered code. But A.8.30 is a process/contractual control: it does not itself inspect code, and its effect is carried through the supplier's implementation of those practices, which is fallible and bounded by what the supplier actually does — matching the same `partial` ceiling the owner set for A.8.30 on `prevents` against CWE-134.
- CWE-86partialprevents — A.8.30 carries secure design, coding and testing practice (8.25–8.29) into the supplier relationship by contract, so a faithful implementation reduces ordinary software implementation CWEs in delivered code; CWE-86 is such a CWE, but the clause's effect depends on the supplier actually applying those referenced controls, capping it at the clause's declared ceiling of partial.
- CWE-862partialblocks — Requiring evidence of minimum security capabilities and acceptance testing ensures that missing or bypassed authorization checks are detected before the delivered software is accepted.
- CWE-87partialprevents — A.8.30 carries its effect through the secure development practices (8.25-8.29) it contracts from the supplier, which include proper input neutralization; an organization implementing it faithfully sees a reduction in regular software CWEs like CWE-87, but the clause depends on those other controls and the ceiling is `partial`.
- CWE-88partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, and argument injection is an ordinary software implementation weakness those practices address; the clause sits at its declared ceiling of `partial` because the underlying practices are fallible and the clause depends on them being implemented by the supplier.
- CWE-89partialprevents — A.8.30 contracts secure design, coding and testing practices (8.25-8.29) into outsourced development, so a faithful implementation reduces SQL injection in delivered code the way those practices do, but the effect is mediated through the supplier's compliance and the clause carries a declared ceiling of partial on this verb.
- CWE-89partialfinds — A.8.30's acceptance-testing requirement (d) and evidence-of-testing requirements (f, g) carry the finding effect through the supplier's 8.29 testing programme, which finds SQL injection comprehensively; but the clause's own reach is the contractual wrapper, dependent on the supplier actually performing the testing and on the receiving organisation's acceptance scope, so it finds a minority of latent instances rather than the bulk.
- CWE-9partialfinds — A.8.30's programme requires acceptance testing (8.29) and evidence of secure coding/testing practices, which would surface weak EJB method permissions in deployment descriptors, but the control itself is contractual — the discovery is performed by the testing it mandates of the supplier, not by A.8.30 directly, so it covers a minority of instances.
- CWE-908partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary implementation-phase software weaknesses like CWE-908 the way those practices do, but only partially because the clause depends on the supplier actually implementing secure coding and the practice is fallible; A.8.30 carries a declared ceiling of `partial` on this verb.
- CWE-91partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like XML injection the way those practices do, at `partial` -- the practice is fallible and a different clause carries the stronger effect. A.8.30 carries a declared CEILING of `partial` on this verb.
- CWE-911partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses in delivered code the way those practices do; reference-count bugs are subtle implementation defects that secure coding practice helps with but does not fully prevent, and the clause carries a declared ceiling of `partial` on this verb.
- CWE-914partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like CWE-914 in delivered code the way those practices do; the clause's declared ceiling on this verb is `partial`.
- CWE-915partialprevents — A.8.30 contracts the supplier to apply secure design, coding and testing practices (8.25–8.29), so a well-implemented clause reduces ordinary software weaknesses in delivered code the way those practices do; CWE-915 is a code-level mass-assignment defect reachable by those practices, but the effect depends on the supplier's implementation and the clause's ceiling on this verb is `partial`.
- CWE-916partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-916 is an implementation choice (weak hash, no salt, no stretching) that secure coding and design guidance would address, but the clause's effect depends on the supplier's faithful implementation and is bounded by the same fallibility that caps A.8.28 itself at `partial`.
- CWE-918partialfinds — A.8.30's contractual requirements for acceptance testing (8.29) and evidence of testing for malicious content and known vulnerabilities cause SSRF to be discovered in delivered outsourced code, but the finding is performed by the testing programme A.8.30 contracts for rather than by A.8.30 itself, and the effect is reduced because it is mediated through a supplier relationship.
- CWE-925partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses in delivered Android code the way those practices do; CWE-925 is a code-level defect in the supplier's first-party source, which secure coding reaches, but the clause's ceiling on `prevents` is `partial` because the practice is fallible and depends on the rigour of the supplier's implementation.
- CWE-925partialfinds — A.8.30 carries its finding effect indirectly through the acceptance testing and evidence-of-testing requirements it mandates (which reference 8.29's security testing programme); the clause itself does not perform testing, so the effect is bounded by the supplier's implementation and reaches only a minority of latent instances.
- CWE-926partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25-8.29), which would cover Android component export configuration as a design/coding weakness; the clause reaches this weakness the same way it reaches CWE-134, at `partial` because the effect depends on the contract actually specifying mobile security practices and the supplier implementing them.
- CWE-926partialfinds — A.8.30 carries its effect through the secure-development and testing practices its contract requires of the supplier (8.25–8.29), so the supplier's static analysis of the Android manifest and dynamic testing would surface improperly exported components in delivered code; the effect is indirect and bounded by what the supplier's testing programme actually covers, matching the same `partial` ceiling the clause carries on `prevents` for ordinary software CWEs.
- CWE-927partialprevents — A.8.30 carries its effect through the secure design, coding and testing practices (8.25–8.29) it contracts into outsourced development, so it reduces instances of an ordinary software weakness like implicit-intent misuse in delivered Android code the way those practices do — at `partial`, because the contracted practices are fallible and the clause's own ceiling on `prevents` is `partial`.
- CWE-93partialprevents — A.8.30 carries its effect through the secure-development practices (8.25-8.29) its contract requires of the supplier, so it reduces ordinary input-neutralization defects like CRLF injection the way those practices do; the clause carries a declared ceiling of `partial` on this verb, and CRLF injection is the same class of regular software CWE as the format-string anchor graded `partial`.
- CWE-939partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier; a well-implemented contract reduces this mobile-handler authorization defect the way those practices do, but the clause's reach is mediated by the supplier's implementation and is bounded by A.8.30's declared ceiling of `partial`.
- CWE-939partialfinds — A.8.30's contractual requirements for secure design, coding and testing (referencing 8.25-8.29) and its acceptance-testing mandate lead to some discovery of custom URL scheme handler authorization flaws through the supplier's testing programme, but A.8.30 is a contractual wrapper one step removed from the actual testing, and coverage of this specific mobile/inter-app communication weakness depends on what the supplier's tests reach.
- CWE-94partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses like code injection in delivered code the way those practices do, at `partial` -- the effect depends on the supplier's faithful implementation of those practices, which is fallible, and the clause sits at its declared ceiling of `partial` on this verb.
- CWE-940partialprevents — A.8.30 contracts for secure design, coding and testing practices (8.25–8.29) in outsourced work, which is the same mechanism that addresses source-verification defects in delivered software; the effect is real but bounded by the fallibility of the contracted practices and the clause's dependence on 8.25–8.29, matching the A.8.30 -> CWE-134 anchor at `partial`.
- CWE-942partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software weaknesses in delivered code the way those practices do; CWE-942 is a design/configuration weakness in cross-domain policy files that secure design guidance and threat-modelling (item c) would catch in some cases, but the clause's ceiling on this verb is `partial` and the remainder is the same fallible-practice remainder as for CWE-134.
- CWE-942partialfinds — A.8.30 carries discovery only through the supplier acceptance-testing, secure-coding, and evidence requirements it mandates, which surfaces some permissive cross-domain policies in outsourced code, but the control itself does not independently scan deployed code and depends on supplier compliance, so it finds a minority of instances.
- CWE-96partialprevents — A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like static code injection the way those practices do, at `partial`; the clause has a declared ceiling of `partial` on this verb.
- CWE-97partialprevents — A.8.30 contracts secure design, coding and testing practices (8.25–8.29) into outsourced development, which reduces ordinary software implementation weaknesses like SSI injection in delivered code, but its effect depends on the supplier actually applying those practices and the clause itself does not directly prevent the defect.
- CWE-98partialprevents — A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a faithfully implemented clause reduces ordinary software implementation defects like improper input handling in PHP include/require statements, but the effect is mediated by the supplier's practice and is bounded by the same ceiling the owner set on A.8.30 vs CWE-134.
Mitigated MITRE ATT&CK techniques (3163)
Adversary techniques (MITRE ATT&CK Enterprise) this ISO control helps mitigate; links open attack.mitre.org. Our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- T1195mostlyprevents — Contractual mandates for secure design, coding, testing, and evidence of malicious-content and vulnerability checks directly reduce the likelihood that a supplier will deliver compromised code or components.
- T1068partialprevents — A.8.30 requires secure coding practices, acceptance testing, and evidence of testing against known vulnerabilities in outsourced development, which reduces the introduction of exploitable flaws in that code; however, it covers only outsourced development (not in-house or third-party components), cannot catch zero-days, and addresses the development process rather than runtime exploitation, so it lowers the rate of exploitable vulnerabilities without preventing the technique.
- T1176.002partialprevents — A.8.30's requirements for acceptance testing, evidence of testing against malicious content (f) and known vulnerabilities (g), contractual secure-coding obligations, and audit rights constrain malicious extensions introduced through the outsourced development deliverable, but the technique also enters via extension marketplaces and side-loading by developers, which sit outside the outsourced-supply-chain scope the clause governs.
- T1190partialprevents — A.8.30 mandates secure design, coding and testing practices in outsourced development (points b, d, f, g) and acceptance testing, which reduces the prevalence of exploitable bugs in delivered software, but it is a process/governance control that sets requirements rather than implements security itself, leaves zero-day vulnerabilities and deployment misconfigurations outside its reach, and covers only the outsourced portion of the application estate.
- T1195.001partialprevents — A.8.30's acceptance testing (d) and evidence requirements for testing against malicious content (f) and known vulnerabilities (g) directly address malicious code in delivered software, and the threat model (c) and audit rights (i) constrain the outsourced development relationship; however, the clause is scoped to outsourced development work and does not cover open-source dependencies, typosquatting, CI/CD pipeline components, or IDE/agent configuration files that constitute the bulk of T1195.001's vectors.
- T1195.002partialprevents — A.8.30 requires contractual secure design, coding, testing, and acceptance testing for outsourced development, which can prevent some supply chain compromises, but the control governs the relationship and requirements rather than directly blocking the technique, and a supplier can still be compromised or malicious despite contractual obligations.
- T1195.002partialdetects — A.8.30 includes detective elements — acceptance testing (d), evidence of testing against malicious content (f) and known vulnerabilities (g), and audit rights (i) — that can surface a compromised deliverable, but these are conditional on supplier cooperation, the thoroughness of acceptance testing, and whether audits are actually exercised; the clause is primarily preventive/contractual, so detection is a framework the control sets up rather than a mechanism it performs.
- T1203partialprevents — A.8.30 requires secure design, coding and testing practices (8.25–8.29), acceptance testing, and evidence of testing against known vulnerabilities in outsourced development, which reduces the exploitable vulnerability surface in software developed under such agreements; however, the clause only governs outsourced development (not COTS client applications like browsers, Office, Adobe Reader, or Flash that are the primary T1203 targets), cannot eliminate zero-day vulnerabilities, and operates upstream of the runtime exploitation event.
- T1204.005partialprevents — A.8.30 requires acceptance testing, evidence of testing against malicious content (point f) and known vulnerabilities (point g), and contractual secure-coding requirements for outsourced deliverables, which directly addresses malicious libraries introduced through outsourced development; however, it does not cover the broader T1204.005 surface of public package managers (NPM, PyPi, GitHub) or libraries developers install themselves outside the outsourced channel.
- T1210partialprevents — A.8.30 reduces exploitable vulnerabilities in outsourced code via secure-design contracts, threat modelling, acceptance testing and vulnerability testing, but it covers only the outsourced-development slice of the attack surface — COTS software, operating systems, open-source components and in-house code that T1210 commonly targets are outside its scope, and even within outsourced work the requirements reduce rather than eliminate vulnerabilities.
- T1211partialprevents — A.8.30's contractual requirements for secure design, coding, testing, threat modeling, and evidence of vulnerability testing reduce the presence of exploitable flaws in outsourced deliverables, but only cover outsourced development (not in-house code, third-party software, or platform/cloud infrastructure where T1211 also operates), and testing reduces rather than eliminates vulnerabilities.
- T1212partialprevents — A.8.30 reduces vulnerabilities in outsourced-developed code via secure coding/testing requirements and acceptance testing, but only addresses a slice of T1212's attack surface — OS, in-house, COTS, and cloud-infrastructure vulnerabilities remain outside its scope, and even within outsourced code it reduces rather than eliminates exploitable flaws.
- T1499.004partialprevents — A.8.30's requirements for secure design, coding, testing against known vulnerabilities, threat modeling, and acceptance testing reduce the presence of exploitable vulnerabilities in outsourced deliverables, but the control only governs outsourced development (leaving in-house and third-party software uncovered), cannot eliminate zero-day vulnerabilities, and does not address runtime exploitation — so the technique still has a meaningful attack surface to run against.
- T1505.003partialprevents — A.8.30's contractual requirements for secure coding (b), acceptance testing (d), and evidence of testing against malicious content (f) and known vulnerabilities (g) reduce the development-time vectors for web shell introduction — planted backdoors in delivered code and vulnerable code that permits shell installation — but the technique primarily operates post-deployment via runtime exploitation, credential compromise, or zero-days, which the clause does not address.
- T1552partialprevents — A.8.30's requirements for secure coding practices, testing against known vulnerabilities, and security requirements for the development environment can reduce insecure credential storage in outsourced deliverables, but the control only governs outsourced development and cannot reach credentials stored insecurely in operating systems, applications, or in-house code where T1552 also operates.
- T1552.001partialprevents — A.8.30's contractual requirements for secure coding (b), acceptance testing (d), and testing for known vulnerabilities (g) can prevent credentials from being embedded in outsourced source code, configuration files, or deliverables — a real slice of T1552.001. It does not address the broader technique: user-created credential stores, cloud/container credential files, Group Policy Preferences, backups, or credentials left by internal developers, so the prevention is bounded to the outsourced-deliverable portion.
- T1554partialprevents — A.8.30's requirements for acceptance testing, evidence of testing for malicious content and known vulnerabilities, and contractual secure coding/testing practices can prevent tampered binaries from being introduced via the outsourced development path, but T1554 also occurs through post-delivery tampering, in-house development compromise, and other supply chain vectors outside A.8.30's scope.
- T1559.003partialprevents — A.8.30's contractual requirements for secure design, coding and testing (8.25-8.29), threat modeling, and acceptance testing can reduce improper XPC client validation and input sanitization in outsourced macOS development, but the control only governs outsourced relationships and sets requirements rather than directly implementing them, leaving in-house code, already-deployed third-party software, and developer-side execution gaps unaddressed.
- T1574.001partialprevents — A.8.30's contractual requirements for secure coding/testing (b), evidence of testing against malicious content (f) and known vulnerabilities (g), and security requirements for the development environment (j) can prevent DLL hijacking vectors that originate in the delivered software — insecure DLL loading patterns, vulnerable DLL resolution code, or malicious DLLs inserted during development. However, T1574.001 is fundamentally a runtime technique where the adversary plants or substitutes DLLs on the target system after delivery, which lies outside the outsourced-development control's scope.
- T1574.004partialprevents — A.8.30 can mandate secure coding practices (via 8.25–8.29), threat modeling, and testing against known vulnerabilities in outsourced development, which would reduce dylib hijacking opportunities in newly built software; however, it is a contractual/oversight control whose effect depends on developer implementation, covers only the outsourced portion of the estate, and does not address runtime search-path integrity or pre-existing applications vulnerable to weak linking.
- T1574.005partialprevents — A.8.30 mandates contractual secure-coding requirements, acceptance testing, and vulnerability testing for outsourced development, which can push suppliers to set proper file permissions on installer binaries and temp directories — addressing the root cause. But the control only applies to outsourced development (not in-house or third-party installers), and it is a process mandate that depends on the supplier implementing the requirements, so it cannot reach full prevention.
- T1574.009partialprevents — A.8.30's contractual requirements for secure design/coding/testing (b) and acceptance testing (d) can require outsourced developers to quote paths properly in services, shortcuts and registry entries, and to test for this class of weakness, but the control governs only outsourced development, addresses the issue only through process and contractual means rather than direct technical enforcement, and cannot reach unquoted paths introduced by the organization itself or by deployment-time configuration.
- T1574.010partialprevents — A.8.30 can require secure coding practices, threat modeling, and acceptance testing (b, c, d) that may catch some permission-related issues during development, but T1574.010 exploits file permissions on already-deployed Windows services — a deployment/configuration concern largely outside the outsourced-development relationship's scope.
- T1677partialprevents — A.8.30's contractual requirements for secure design/coding/testing (b), testing against malicious content (f) and known vulnerabilities (g), and security requirements for the development environment (j) can reduce the likelihood of pipeline poisoning in outsourced development, but the clause sets oversight and contractual obligations rather than mandating specific CI/CD safeguards, and T1677's vectors (direct config modification, indirect file injection, public PR execution) are not all addressed by these general outsourced-development requirements.
- T1687partialprevents — A.8.30's testing and acceptance requirements (d, f, g) can catch some vulnerabilities in outsourced code before delivery, but the clause governs the supplier relationship and pre-delivery testing — it does not address exploitation of commercial security products (AV, EDR, firewalls), zero-days, post-deployment vulnerabilities, or runtime defense impairment, which constitute the bulk of T1687.
- T1700partialprevents — A.8.30 can require contractual secure-design, threat-modeling, and acceptance-testing provisions (including for AI components) that constrain how outsourced AI agents are built and what tools they can invoke, but prompt injection exploits the runtime instruction-following behavior of LLMs in a way that development-time controls cannot fully eliminate — the technique's core mechanism survives even well-secured outsourced development.
Prevented OWASP Web Top 10 (2025) risks (11)
OWASP Web Top 10 (2025) risk categories this ISO control helps prevent or mitigate — our analysis (mostly llm_verified).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Why these map — rationale
- A06partialblocks — A.8.30 requires the organization to communicate, agree and enforce secure design requirements (including threat modeling) on outsourced developers, which directly prevents design-level weaknesses from being baked into the delivered architecture for the slice of development that is outsourced.
- A08partialblocks — A.8.30 requires contractual requirements for secure design/coding/testing (8.25-8.29), threat models, acceptance testing, evidence of vulnerability/malicious-content testing, and audit rights, which directly target the integrity failures named in A08:2025 and thereby prevent many (but not all) such defects from reaching production.
Control IDs, short titles and the structured attribute table (control type, CIA properties, cybersecurity-concept, operational capability, security domain) are facts from ISO/IEC 27001:2022 Annex A / ISO/IEC 27002:2022. The full implementation guidance prose lives in ISO/IEC 27002:2022 — not reproduced here. Cross-walks to NIST 800-53, NIST CSF 2.0, OWASP ASVS, CWE, MITRE ATT&CK and OWASP Web Top 10 are our own analysis (mostly llm_verified), not an ISO, NIST, MITRE or OWASP product — how ours compare.