Framework overlap

Does OWASP ASVS cover Annex 11 to EU GMP?

You hold OWASP ASVS and have been told to do Annex 11 to EU GMP. Here is how much overlaps, control by control.

71% of Annex 11 to EU GMP you already have

OWASP ASVS already covers about 71% of Annex 11 to EU GMP, leaving 5 of 17 controls as genuinely new work.

Already covered 0 Likely covered 12 New work 5

No control in OWASP ASVS maps directly to one in Annex 11 to EU GMP. Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

Nothing in OWASP ASVS reaches these. This is the list to scope.

Clause 11
Periodic evaluation
Clause 14
Electronic signatures
Clause 4
Validation
Clause 5
Data
Clause 8
Printouts
Show the 12 you already have
Clause 1
Risk management
Clause 10
Change and configuration management
Clause 12
Security
Clause 13
Incident management
Clause 15
Batch release
Clause 16
Business continuity
Clause 17
Archiving
Clause 2
Personnel
Clause 3
Suppliers and service providers
Clause 6
Accuracy checks
Clause 7
Data storage
Clause 9
Audit trails

How this is calculated

Already covered means a mapping runs from a control in OWASP ASVS to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair ยท Today's edition