OWASP SAMMvsPTES
See exactly how OWASP SAMM controls map to PTES. Pre-computed mappings, identified gaps, and coverage analysis.
According to the TheArtOfService Compliance Knowledge Graph:
OWASP SAMM maps to PTES with 31% coverage across 16 directly mapped controls. Analysis of 51 OWASP SAMM controls identifies 35 compliance gaps — primarily concentrated in Governance.
Source: TheArtOfService Knowledge Graph | 51 controls analysed | 722 frameworks | 438K+ cross-framework mappings
Control Mappings
Showing 20 of 37 mapped controls across 6 domains. Sign up to explore all 438K+ mappings across 722 frameworks.
OWASP SAMM: Information Security Policies(1 mappings)
OWASP SAMM: Asset Management(9 mappings)
OWASP SAMM: Access Control(10 mappings)
+17 more mappings
Plus AI-powered gap analysis, compliance advisory, PDF exports, and cross-mapping for all 722 frameworks.
Create Free Account →Free forever — no credit card required
Related Comparisons
Other OWASP SAMM comparisons
Stop Paying Consultants to Read Spreadsheets
AI-powered compliance intelligence across 722 frameworks — at a fraction of consulting costs.
Free
- ✓ 722 framework browser
- ✓ Cross-framework mappings (438K+)
- ✓ 824 compliance assessments
- ✓ 3 AI queries & searches per day
Professional
- ✓ Unlimited AI Compliance Advisory
- ✓ Unlimited full-text search
- ✓ Framework self-assessment
- ✓ PDF, Excel & CSV exports
What are the key differences between OWASP SAMM and PTES?
OWASP SAMM has 51 controls across its framework, while PTES covers 53 controls. Direct mapping analysis identifies 16 overlapping controls (31% coverage). The frameworks diverge most significantly in Governance, where 5 OWASP SAMM controls have no direct PTES equivalent.
How many controls map between OWASP SAMM and PTES?
Of 51 total OWASP SAMM controls, 16 map directly to PTES controls — representing 31% coverage. The remaining 35 controls represent compliance gaps requiring additional documentation or compensating controls to satisfy both frameworks simultaneously.
What are the compliance gaps when mapping OWASP SAMM to PTES?
35 OWASP SAMM controls have no direct equivalent in PTES. The highest concentration of gaps is in Governance with 5 unmapped controls. These gaps represent areas where additional controls, policies, or documentation must be created to achieve compliance with both frameworks.
Which control domains have the most gaps between OWASP SAMM and PTES?
The domain with the highest gap count is Governance (5 gaps). Export the full domain-by-domain gap breakdown via the Professional tier to generate a prioritised remediation roadmap.
Related Resources
This platform provides educational compliance tools, not legal, regulatory, or professional compliance advice. Cross-framework mappings are AI-assisted interpretations and do not reproduce or replace official standards. Framework names and trademarks belong to their respective owners. Consult qualified professionals for your specific compliance requirements. See our Terms of Service.