Skip to content

fix(opsec): add early-stage standards section with CCSS, remove unlinkable cross-chain placeholder #480

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mattaereal merged 1 commit into from
May 5, 2026
Merged

fix(opsec): add early-stage standards section with CCSS, remove unlinkable cross-chain placeholder #480

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions docs/pages/opsec/integration/overview.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
title: "OpSec Integration | Security Alliance"
description: "Integrate OpSec with DevSecOps, privacy frameworks, and governance. Map controls to ISO 27001, NIST, CIS Controls, OWASP, SOC 2, MITRE AADAPT, OWASP SCWE, EEA EthTrust, and OWASP Smart Contract Top 10 standards for unified Web3 security approach."
description: "Integrate OpSec with DevSecOps, privacy frameworks, and governance. Map controls to ISO 27001, NIST, CIS Controls, OWASP, SOC 2, MITRE AADAPT, OWASP SCWE, EEA EthTrust, OWASP Smart Contract Top 10, and CCSS standards for unified Web3 security approach."
tags:
- Security Specialist
- Operations & Strategy
Expand Down Expand Up @@ -151,7 +151,11 @@ Aligning operational security practices with established security standards and

4. **EEA EthTrust Security Levels v3** — [EthTrust SL v3](https://entethalliance.org/specs/ethtrust-sl/). Defines certification requirements and three assurance levels (S, M, Q) for audited smart contracts. Level S requires formal verification and comprehensive testing; Level M requires thorough manual review; Level Q covers quick-scan assessments. Map OpSec audit procedures to the appropriate EthTrust level to communicate assurance rigor to stakeholders and regulators.

5. **Cross-Chain Security Standards**: Emerging standards for cross-chain bridge and messaging protocol security, where bridge exploits remain a dominant attack vector.
### Early-Stage & Emerging Standards

The following standards are actively maintained but have narrower adoption or are still evolving. They are worth tracking if you operate in their scope.

1. **Cryptocurrency Security Standard (CCSS)** — [CCSS v3.2](https://cryptoconsortium.org/ccss/). A maturity standard for crypto-infrastructure security covering key management, wallet operations, and key-person controls. CCSS defines three assurance levels: Level 1 covers self-assessment; Level 2 adds third-party audit; Level 3 requires penetration testing and full documentation review. Use CCSS when designing or evaluating the security posture of custodial wallets, exchanges, or treasury operations that handle private keys at scale.

## Creating a Unified Security Approach

Expand Down
1 change: 1 addition & 0 deletions wordlist.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ BYOK
CAIP
CCIP
CCPA
CCSS
Certora
CIS
CISA
Expand Down
Loading