Cadenza

Cadenza provides provable data integrity for critical energy infrastructure. It uses Ed25519 signatures, Merkle tree chaining, and RFC 3161 timestamping to ensure operational data is authentic and unchanged — even against the operator, and without a blockchain. The architecture implements security controls aligned with eight CISSP domains.

Cadenza US — Design for FERC Order 2222 →

CISSP Domain Mapping

Cadenza implements security controls aligned with eight CISSP domains:

1. Security and Compliance

• Tamper-evident audit trail for all operational readings
• RFC 3161 timestamping by independent authority ensures non-repudiation
• Supports evidence and incident duties under NIS2/BSIG requirements

2. Access Control

• Ed25519 private keys never leave the edge device — cryptographic proof at the source
• Verify-only core: Spring Boot verifies signatures but never mints source signatures
• Append-only storage prevents unauthorized modification of verified records

3. Security Architecture

• Defense-in-depth: edge signing → Merkle chaining → external timestamping
• Merkle tree structure: altering any single record changes the root fingerprint
• No blockchain, token, or extra chain process required

4. Identity and Authentication

• Ed25519 elliptic-curve cryptography for device identity and data signing
• Each attestation tagged with Cadenza-Attestation-v1 for protocol clarity
• Private keys stored securely at the edge, never transmitted

5. Cryptography

• Ed25519: post-quantum-resistant elliptic-curve digital signature algorithm
• Merkle tree: collision-resistant hash function binds all records cryptographically

6. Data Security

• Data integrity verified at every layer: edge, transport, and storage
• Tamper demo proves that changing an EMS copy does not affect the signed leaf
• cadenzaPage.cissp6c

7. Software Security

• Go agent handles edge signing with minimal attack surface
• Spring Boot core enforces verify-only policy — no source signature minting

8. Security Operations

• Quellenkarte (source map) with GRUEN/GELB/ROT status for operational awareness
• Three-party room: Anlage, Vermarkter, VNB share verified Istwerte; ISB reads only
• cadenzaPage.cissp8c

What we do not claim

• Not NIS2-certified and not a KRITIS fulfilment statement
• Not a blockchain, token, or extra chain process

What we may say

• Supports evidence and incident duties under the new BSIG (NIS2)
• On-prem; no third-country model API is required
• Provable data origin and integrity for audit and regulatory compliance