Home → Sample Report
Public sample

Risk Intelligence Report.
Illustrative example.

Synthetic example showing the structure, transparency and decision output a buyer should expect. No customer information is used.

Illustrative regulated financial entity

Executive exposure summary

Assessment basis: questionnaire + public evidence + sample cryptographic inventory.

42Readiness / 100
Modelled exposure range₹38–51 CrConfidence: Medium
Highest driverCrypto concentrationLegacy public-key dependencies
Priority horizon0–90 daysInventory + governance first
Top findings

What leadership sees first.

01
Cryptographic inventory is incomplete

Public TLS findings exist, but internal authentication, API signing, application libraries and vendor cryptography are not yet evidenced. A verified CBOM requires authorised enterprise discovery.

High
02
Long-life sensitive data lacks a PQC transition owner

Retention horizon and current public-key dependencies create potential harvest-now-decrypt-later exposure. Establish governance and prioritise high-lifetime systems.

High
03
Regulatory evidence is fragmented

Controls exist, but evidence is distributed across teams. Map SEBI/RBI/DPDP/CERT-In obligations to owners, artefacts and review dates.

Medium
Financial model

Why the estimate is a range.

ComponentModelled rangeConfidence
Regulatory / compliance exposure₹6–9 CrMedium
Incident & response exposure₹18–24 CrMedium
Cryptographic concentration₹8–11 CrMedium-low
Long-life-data / quantum exposure₹6–7 CrLow-medium

Illustrative synthetic output. Actual reports identify evidence sources, assumptions, methodology version and limitations. Modelled exposure is not a guaranteed penalty or loss forecast.

90-day action plan

Prioritise evidence before expensive migration.

0–30 days · Establish ownershipCrypto governance owner, evidence register, regulator applicability map, data-retention map.
30–60 days · Verify cryptographic inventoryApproved discovery across critical systems and key vendors; document algorithms, keys, certificates, libraries and purpose.
60–90 days · Build migration roadmapPrioritise long-life and high-criticality systems, define crypto-agility requirements and establish vendor upgrade commitments.
Discuss an assessment →FRQE methodology →