Sirraya Crypto · Sirraya Sign · Applied Cryptography
Cryptographic infrastructure built for the transition ahead.
From classical algorithms to post-quantum and stateful hash-based signatures—designed around one principle: your trust infrastructure should not become obsolete every time cryptography changes.
FIPS 186-5
Classical
FIPS 204
ML-DSA
FIPS 205
SLH-DSA
RFC 8554
LMS/HSS
RFC 8391
XMSS
RFC 6979
ECDSA

Sirraya Crypto Discovery

You can't migrate cryptography
you can't see.

Sirraya Crypto Discovery turns cryptographic evidence across your software supply chain into an explainable post-quantum migration path — and helps ensure the same migration debt does not return.

01 / DISCOVER

Discover cryptography.

Identify cryptographic assets across the software supply chain using multiple independent evidence sources.

Source code scanning
Certificate analysis
TLS inspection
Compiled binary scanning

From exposure to action

CRYPTOGRAPHIC EXPOSURE

Evidence collected across the environment

RSA-2048Classical
Certificate public key
ECDSA P-256Classical
TLS certificate
X25519Classical
TLS key exchange
Confidence: MULTI-SOURCE EVIDENCE

POST-QUANTUM MIGRATION

Prioritized and ready for engineering action

01 / X25519HIGH PRIORITY

Harvest exposure detected

→ Hybrid / ML-KEM migration path
02 / ECDSA P-256FORGERY EXPOSURE

ML-DSA hybrid transition recommended

CI GATE ACTIVENo new classical migration debt

Built for migration, not just inventory

From visibility to permanent enforcement.

01

Multi-source evidence

Source, certificates, TLS and binaries provide independent evidence instead of relying on a single detection method.

02

Quantum-aware risk

Harvest-now-decrypt-later exposure and signature forgery exposure are treated as different threat models.

03

Migration into code

Recommendations can produce migration scaffolds and markers instead of stopping at a report.

04

Permanent enforcement

A CBOM-aware gate helps prevent new classical cryptographic migration debt from being introduced.

THE PRINCIPLE

Find what exists. Understand the risk. Build a path forward. Then make sure you do not recreate the problem you are trying to solve.

DISCOVER → ENFORCE

Supported Cryptography

One signing layer. Multiple generations.

FIPS 186-5
RSA

Mature public-key cryptosystem for digital signatures.

FIPS 186-5
ECDSA

Elliptic curve signatures with broad ecosystem support.

RFC 8032
Ed25519

High-speed Edwards-curve signatures with compact keys.

Crypto-Agility
Hybrid Signing
Policy Enforcement
Hardware Ready
Known-Answer Tests
Rust Implementation
View full documentation
Cryptographic Continuity

The cryptographic stack
for long-lived systems.

Not a library. Not a service. A complete infrastructure layer for organizations that cannot afford to rebuild trust every time cryptography evolves.

Algorithmic Diversity
Different mathematical foundations prevent single-point failure
Explicit State Management
Stateful signatures expose mutation through type system
Policy Enforcement
Cryptographic requirements expressed as code, not documentation
Continuous Validation
Known-answer tests and interop checks in CI pipeline

Three families. One interface.

Select a family to explore its properties

CLASSICAL
Today's Foundation
keySize2048-3072 bit
sigSize64-512 bytes
speedFast
FIPS 186-5
RSA

Mature public-key cryptosystem with universal deployment.

FIPS 186-5
ECDSA P-256 / P-384

Elliptic curve signatures optimized for constrained devices.

RFC 8032
Ed25519

High-performance Edwards-curve signatures with compact keys.

The signature state dilemma

Most cryptographic APIs hide state management. We made it a first-class citizen.

STATELESS API
let signature = sign(&key, message);

// Key unchanged
// No hidden state
// Signature deterministic
Simple, predictable, safe
STATEFUL API
let signature = sign(&mut key, message);

// Key state advances
// Signing count tracked
// Type system enforces safety
Explicit, traceable, secure

Policy as executable code.

A signing policy isn't documentation. It's a machine-checkable expression of exactly which cryptographic properties an artifact must satisfy before it's trusted.

Multi-algorithm requirements (ALL vs ANY)
Hybrid signatures with classical + PQC
Automatic policy evolution during migration
Real-time verification against policy
POLICY EXPRESSION
policy Require {
    algorithms: [Ed25519, ML-DSA-87],
    mode: ALL,
    verify: true
}

policy Optional {
    algorithms: [SLH-DSA],
    mode: ANY,
    verify: false
}
VERIFICATION FLOW
Ed25519VALID
ML-DSA-87VALID
SLH-DSAOPTIONAL

Validated against reality.

Every algorithm passes through specification compliance, known-answer tests, and independent interoperability checks.

108
Tests passing
RFC 8554
LMS Known-Answer
RFC 6979
ECDSA Known-Answer
3+
Interop targets
Engineering milestones. Not certification claims.

Change the cryptography.
Keep the trust infrastructure.

Sirraya Crypto provides the foundation. Sirraya Sign builds the system. Together, they enable cryptographic continuity for organizations that think in decades.

Sirraya Crypto Discovery

Regulatory Mapping

Map discovered cryptographic assets to post-quantum transition frameworks, understand applicability, and identify where migration action may be required.

CBOM policy analysis complete
Mapped Assets
4
Cryptographic findings evaluated
Migration Required
2
Prioritized transition candidates
Attention Required
1
Assets requiring review
Compliant
1
Aligned findings

Cryptographic Findings

Policy interpretation is based on discovered algorithm, primitive, usage, and framework context.

Regulatory Assessment

RSA

2048 / PKCS#1 v1.5

Migration Required
FrameworkCNSA 2.0
ApplicabilityPotentially Applies
Cryptographic StatusClassical
Transition Target2027
Why this matters

RSA provides no resistance against cryptographically relevant quantum computers. Framework applicability depends on the system and organizational scope.

Recommended Action

Plan migration to an approved post-quantum or hybrid signing architecture.

Policy SourceCNSA 2.0
Policy Interpretation

Regulatory mapping identifies the relationship between discovered cryptographic assets and selected policy frameworks. Framework applicability depends on organizational scope, jurisdiction, system classification, and deployment context. Results should support compliance assessment rather than replace legal or regulatory review.

Sirraya Crypto · Sirraya Sign

Cryptographic infrastructure
built for the transition ahead.

Six cryptographic families. One signing layer. Multiple generations of algorithms designed for real-world deployment—from classical to post-quantum to stateful hash-based signatures.

EstablishedClassical
Today's Foundation

Classical Cryptography

Established algorithms that form the backbone of modern security infrastructure. Mature, widely deployed, and battle-tested across billions of devices and systems worldwide.

FIPS 186-5
Standards compliance

Algorithms & Components

RSA
ECDSA P-256 / P-384
Ed25519

Operational Characteristics

Battle-tested
latency
Global scale
throughput
Industry standard
security
Explore Sirraya Crypto

FIPS 186-5 · FIPS 204 · FIPS 205 · RFC 6979 · RFC 8554 · RFC 8391

Crypto-agility · Cryptographic continuity · Firmware signing · Software supply-chain security · Stateful signatures · Known-answer tests · Interoperability · Policy enforcement

Deployed Across Critical Industries

Where cryptographic continuity matters most.

From firmware that lives for decades to financial systems processing millions of transactions, Sirraya Crypto is designed for environments where failure is not an option.

8+
Industries served
25+ years
Deployment lifetime
1-5
Security levels
15+
Standards aligned

Firmware & Embedded Systems

Secure boot chains, OTA updates, and long-lived device authentication where firmware must remain trustworthy for decades.

IoT devicesAutomotive ECUsIndustrial controllers
Ed25519ML-DSA-44LMS/HSS
Deployment lifetime10+ years
Signature size64 bytes - 2.5 KB
Update frequencyContinuous
Standards
FIPS 204RFC 8554IETF SUIT

Cryptographic Continuity

Build for the
cryptographic future.

From post-quantum migration to policy-driven signing infrastructure. We partner with organizations building systems that must remain trustworthy for decades.

Enterprise Engagements

Structured partnerships for organizations requiring cryptographic excellence.

Built on Open Standards

FIPS 186-5
Classical signatures
FIPS 204
ML-DSA
FIPS 205
SLH-DSA
RFC 8554
LMS/HSS
RFC 8391
XMSS
RFC 6979
ECDSA KAT

Cryptographic decisions compound.

The systems you build today will operate in a post-quantum world. Start the conversation now to ensure your cryptographic foundation evolves with the threat landscape.

NIST PQC Standardization · Post-Quantum Readiness · Cryptographic Agility · Supply Chain Security