You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Opsec Framework: add Web3-specific standards like MITRE AADAPT, OWASP SCS, EEA EthTrust in the Integration subcategory #176
Adding Web3-Specific Standards in a new section in integrations page that introduces and maps new smart contract security standards including MITRE AADAPT™, OWASP SCWE, EEA EthTrust SL(v3) and the OWASP Smart Contract Top 10:2025.
Why do you think it is important?
These standards represent the most up-to-date and structured approaches to Web3 vulnerability taxonomy, adversarial tactics, techniques, and procedures (TTPs). Including them supports a Shift-Left approach in smart contract development; helping developers, auditors, and researchers to understand attacker behavior easily (AADAPT), identify common weaknesses (SCWE) and refer them during their works as traditional security has well established CVE/CWEs, whereas EthTrust provides an additional layer by defining certification requirements and assurance levels, and also prioritize critical risks (Top 10) which is updated/ranked yearly.
Can you cite resources where to base the content from?
MITRE AADAPT: A framework of adversary tactics and techniques for digital asset systems, modeled after MITRE ATT&CK®.
OWASP SCWE: A smart contract-specific weakness enumeration inspired by CWE. This also covers all 36 SWC from the now-outdated https://swcregistry.io/ and more.
OWASP Smart Contract Top 10: An awareness standard highlighting the top 10 vulnerabilities in smart contracts. This comes under OWASP Top 10 initiative.
changed the title [-]Content(add): Web3-specific standards like MITRE AADAPT, OWASP SCS, EEA EthTrust[/-][+]Opsec Framework: add Web3-specific standards like MITRE AADAPT, OWASP SCS, EEA EthTrust in the Integration subcategory[/+]on Oct 13, 2025
Working on this. PR #475 opened targeting develop.
Added MITRE AADAPT, OWASP SCWE, OWASP Smart Contract Top 10, and EEA EthTrust SL v3 to the Web3-Specific Standards subsection in the Integration overview page, replacing the previous generic placeholders.
Thanks @mattaereal — yes, the active discussion is on PR #475. @WarlordSam07, feel free to chime in there, especially on whether you'd like the deleted placeholder entries kept as an "emerging standards" subsection or omitted entirely.
Activity
[-]Consider adding Web3-specific standards like MITRE AADAPT, OWASP SCS, EEA EthTrust[/-][+]Content(add): Web3-specific standards like MITRE AADAPT, OWASP SCS, EEA EthTrust[/+][-]Content(add): Web3-specific standards like MITRE AADAPT, OWASP SCS, EEA EthTrust[/-][+]Opsec Framework: add Web3-specific standards like MITRE AADAPT, OWASP SCS, EEA EthTrust in the Integration subcategory[/+]frameworks-volunteer commentedon May 4, 2026
Model:
z-ai/glm-5.1Reasoning:highProvider:openrouterWorking on this. PR #475 opened targeting develop.
Added MITRE AADAPT, OWASP SCWE, OWASP Smart Contract Top 10, and EEA EthTrust SL v3 to the Web3-Specific Standards subsection in the Integration overview page, replacing the previous generic placeholders.
mattaereal commentedon May 5, 2026
@WarlordSam07 you can take a look at the current conversation on the PR #475 if you want to follow the conversation
frameworks-volunteer commentedon May 5, 2026
Model:
z-ai/glm-5.1Reasoning:highProvider:openrouterThanks @mattaereal — yes, the active discussion is on PR #475. @WarlordSam07, feel free to chime in there, especially on whether you'd like the deleted placeholder entries kept as an "emerging standards" subsection or omitted entirely.
fix: add Web3-specific standards (AADAPT, SCWE, EthTrust, SC Top 10) …
Monthly Main branch update (#486)
Chore: monthly .org update (#552)
Chore: monthly .org update (#617)
Fix: make developer-targeted-intrusion section visible on .org (#628)
Remove dev:true from "Policy as Code" (#630)
Chore: monthly .org update (#660)