AEON Security Profiles v1
Status
Draft profile guidance
1. Purpose
Security conventions define structure.
Security profiles define approved algorithm sets and usage rules for those conventions.
Profiles help independently built systems exchange secured AEON documents without each system choosing incompatible algorithms or policy assumptions.
2. Profile Layering
Profiles sit above the security conventions:
Profiles act as policy declarations, not structural rules.
3. Profile Declaration
Profiles should be declared in the document metadata.
Single profile:
Multiple profiles:
4. aeon.secure-basic.v1
Purpose
Provides a minimal, widely implementable security baseline.
Designed for:
- simple document signing
- lightweight interchange
- developer tooling
- configuration files
- small services
Required conventions
Allowed algorithms
Hash:
Signature:
Not included
- encryption
- timestamp authorities
- Merkle proofs
- audit logs
Example
5. aeon.secure-standard.v1
Purpose
Provides a general-purpose secure document profile.
Designed for:
- enterprise document exchange
- APIs
- signed records
- authenticated messages
Required conventions
Allowed algorithms
Hash:
Signature:
Encryption:
Optional features
- multiple signatures
- encryption and signature combination
- signing metadata (
time,issuer)
Example
6. aeon.secure-advanced.v1
Status
Reserved for later specification.
Purpose
Represents a future high-assurance profile for large-scale verifiable systems.
Candidate use cases include:
- regulatory logs
- supply chain records
- AI traceability
- long-term archives
- distributed verification
Candidate features include:
- Merkle subtree verification
- cryptographically chained audit logs
- multiple signing authorities
- timestamp proofs
- partial document verification
7. Why Profiles Matter
Profiles provide:
Interoperability
Systems can exchange AEON documents knowing which algorithms are expected.
Security baseline
Profiles prevent weak or incompatible algorithms.
Implementation simplicity
Developers can implement a profile rather than the entire security ecosystem.
8. Initial Profile Set
The initial AEON security profile set is:
aeon.secure-advanced.v1 is reserved for later specification.