Methodology
Version 2027.1 (previous: 2026.1). Any change to sources, categories, weights, half-lives or the formula creates a new version, and every snapshot records the version used.
What the index measures
CybRes CCC summarises how often, how seriously and how recently observable public events involving a company appear in three linked risk areas: cyber, credit stress and business continuity. Each sub-index runs from 0 (no adverse signal) to 100.
It is not a security rating, an audit, a credit rating, a default probability, an opinion on creditworthiness or investment advice. Credit ratings in India come only from agencies registered under the SEBI (Credit Rating Agencies) Regulations, 1999, and CybRes is not one. A well-run company that discloses openly can show more signals than a less transparent one.
Three sub-indices, never blended
The three are published side by side. They are never added into one number, because a combined score would hide which risk is moving and invite reading it as a rating.
Cyber Event Signal · half-life 90 days
| Category | Definition | Primary public source | Weight |
|---|---|---|---|
| Data breach | Confirmed or credibly reported unauthorised access to customer, employee or business data. | News, exchange filings, BRSR P9 | 1.0 |
| Ransomware | Ransomware or extortion attack affecting the company or its operations. | News, exchange filings | 1.0 |
| Cyber attack | Intrusion, hacking, DDoS, malware or account takeover targeting the company. | News, exchange filings | 0.9 |
| Data exposure | Data found exposed publicly (misconfigured storage, leak on forums) without confirmed attack. | News, researcher disclosures | 0.8 |
| Cyber regulatory action | Penalty or direction by RBI, SEBI, IRDAI, CERT-In, the Data Protection Board or courts linked to IT, cyber or data protection. | RBI, SEBI, IRDAI, CERT-In, DPB orders | 0.8 |
| Third-party cyber incident | Cyber incident at a vendor or partner that affected the company or its customers. | News, vendor disclosures | 0.6 |
| Digital fraud | Phishing, impersonation or online fraud exploiting the company's brand, platform or customers. | News, regulator notices | 0.5 |
| Vulnerability | Publicly disclosed security flaw in the company's product, app or system. | Advisories, researcher disclosures | 0.4 |
| Security governance (context) | Security investment, certification or governance news. Shown for context; not scored. | Annual report, BRSR, news | 0 (context) |
Credit-Stress Signal · half-life 180 days · analyst-verified before publication
| Category | Definition | Primary public source | Weight |
|---|---|---|---|
| Default or delay on loans or debt securities | Company discloses, or a debenture trustee notifies, a default or delay in paying interest or principal. | Exchange disclosures, debenture trustee notices | 1.0 |
| Insolvency petition admitted | NCLT admits an insolvency petition against the company or a material subsidiary. Filed-but-not-admitted petitions are not scored. | NCLT orders, IBBI announcements | 1.0 |
| CRA downgrade to below BBB- | A SEBI-registered credit rating agency publishes a downgrade that moves an instrument below BBB-. CybRes reports the CRA's action; it does not rate. | SEBI-registered CRA press releases | 0.9 |
| Going-concern doubt or qualified audit opinion | Statutory auditor reports material uncertainty about going concern, or issues a qualified, adverse or disclaimer opinion. | Annual report, results filing | 0.8 |
| Statutory auditor resignation mid-term | Statutory auditor resigns before completing its term, as disclosed to the exchange. | Exchange disclosure | 0.7 |
| CRA marks issuer not cooperating | A CRA publishes that the issuer is not cooperating (INC). | CRA press release | 0.7 |
| CRA downgrade within BBB- or above | A CRA downgrade that leaves the instrument at BBB- or above. | CRA press release | 0.6 |
| Promoter pledge invocation or sharp rise | Lenders invoke pledged promoter shares, or promoter pledging rises sharply, as disclosed. | SAST pledge disclosures | 0.6 |
| CRA negative outlook or watch | A CRA revises the outlook to negative or places an instrument on watch with negative implications. | CRA press release | 0.5 |
| Financial-regulator penalty (non-cyber) | Monetary penalty or order by a financial regulator for a matter not related to cyber or IT. | RBI, SEBI, IRDAI orders | 0.4 |
Continuity Signal · half-life 120 days · analyst-verified before publication
| Category | Definition | Primary public source | Weight |
|---|---|---|---|
| Regulator restriction on business | Regulator restricts business, for example a bar on onboarding new digital customers after outages. | RBI, SEBI or IRDAI orders; exchange disclosure | 1.0 |
| Disruption of a plant, unit or division | Operations of a plant, unit or division disrupted by calamity, fire, flood, force majeure or similar. | Reg 30 disclosure, news | 0.9 |
| Extended digital or platform outage (4h+) | Customer-facing digital service unavailable for more than 4 hours (apps, payments, online banking, core systems). | News, exchange or regulator notices, status pages | 0.8 |
| Market-infrastructure or trading-platform outage | Outage at an exchange, depository, clearing corporation or broker trading platform. | Exchange and MII notices | 0.8 |
| Critical supplier or third-party disruption | A critical supplier, outsourcer or third party fails and disrupts the company's operations. | Reg 30 disclosure, news | 0.6 |
| Strike or lockout | Strike or lockout disclosed by the company. | Reg 30 disclosure | 0.5 |
| Short digital outage (under 4h) | Customer-facing digital service unavailable for under 4 hours. | News, status pages | 0.3 |
| DR test or BCP disclosure (context) | Successful DR test or business-continuity disclosure. Shown for context; not scored. | Annual report, BRSR | 0 (context) |
Sources
- News: public headlines and snippets retrieved through a commercial search API (SerpApi or Serper.dev), searching India-edition news for the company name with cyber, credit-event and disruption terms over the last 12 months.
- Exchange and regulator filings: Reg 30 disclosures (including disruption of operations), default and auditor-resignation disclosures, BRSR Principle 9 figures, annual reports; RBI, SEBI, IRDAI, CERT-In and Data Protection Board orders; NCLT orders and IBBI announcements.
- Credit rating agency press releases: reported as the agency's own published action. CybRes does not rate.
- Advisories: CERT-In advisories and vulnerability notes, mapped to sectors. Context only; never scored against a company.
- Passive hygiene checks: what any browser or mail server sees on a company's primary public domain. Shown separately; not part of any sub-index.
CybRes does not scan ports, probe applications, attempt logins, buy breached data or use any non-public source.
Classification and review
Each news item is classified by an AI model (OpenAI) instructed to judge only from the headline and snippet, to mark items unrelated unless the event involves the named company, to report credit events as facts without any view on creditworthiness, and to prefer lower severity when unsure. If the model is unavailable, a transparent keyword classifier assigns low severity.
- Cyber: automated items count immediately and are labelled "Automated, unreviewed" until an analyst confirms, edits or rejects them.
- Credit-stress and continuity: nothing is published or counted until an analyst verifies the item against the primary document (exchange filing, CRA release, NCLT order or regulator order) and records the link.
- Every item is mapped to the company by ISIN, never by name alone. Analysts who work on a company's private engagements never review its public signals; assignments are logged.
Severity
- 1 — Minor: limited, quickly resolved, little customer or financial impact
- 2 — Low: some disruption, small data set or small amount; contained
- 3 — Moderate: notable customer impact, a material amount, or regulatory interest
- 4 — High: large data set, extended outage, admitted insolvency, regulatory action
- 5 — Severe: systemic impact, very large breach, payment default, or business restriction
Formula
For each counted signal:
points = weight × (severity ÷ 5) × relevance × decay
decay = 0.5 (age in days ÷ half-life)
For each sub-index, S is the sum of points of its counted signals, and
sub-index = 100 × (1 − e −S ÷ 1.5)
Half-lives: Cyber 90 days, Credit-Stress 180 days, Continuity 120 days. A signal loses half its weight every half-life.
Verified filings reporting data breaches (BRSR Principle 9) add 0.5 × min(breaches, 3) ÷ 3 to the Cyber sub-index, decayed from the fiscal year end (31 March) with the cyber half-life.
A signal counts only if its relevance is at least 0.5, its category carries weight, it has not been rejected, it was published in the last 365 days and, for credit and continuity, an analyst has confirmed it. Near-identical syndicated headlines are merged.
Bands: 0 none · under 30 low · 30–59 elevated · 60+ high. Bands describe the volume of public signal, not the probability of an incident or a default.
Transmission flags
A flag appears on a company page when two sub-indices show linked signals close together. It is a prompt for scrutiny, not a verdict, and it lists the linked source items.
| Flag | Rule |
|---|---|
| Cyber → Continuity | Cyber signal of severity 4+ and a continuity signal within 30 days |
| Continuity → Credit | Continuity signal of severity 4+ and a credit-stress signal within 180 days |
| Cyber → Credit | Cyber signal of severity 4+ and a credit-stress signal within 180 days |
| CCC triple | Signals in all three sub-indices within 180 days |
Passive hygiene checks
TLS certificate and protocol, certificate expiry headroom, HTTPS redirect, HSTS, Content-Security-Policy, clickjacking protection, nosniff, Referrer-Policy, SPF, DMARC, DKIM on common selectors, DNSSEC, MTA-STS and CAA. security.txt and public status-page reachability are shown but not scored. Status pages are checked hourly when a company publishes one.
Universe
Coverage is the NIFTY 200, refreshed weekly and on each rebalance date from the official NSE Indices constituent file, keyed on ISIN. Companies that leave the index become inactive; their signals are kept so history stays attributable.
| Sync | Active | Added | Removed |
|---|---|---|---|
| 18 Nov 2026 | 200 | APARINDS, MAHABANK, HINDCOPPER, LICI, MEESHO, NLCINDIA, VAML | ALKEM, COROMANDEL, HUDCO, KPITTECH, SHREECEM, TATAELXSI, TATAINVEST |
Changes in v2027.1 (from v2026.1)
| Area | v2026.1 | v2027.1 |
|---|---|---|
| Structure | One cyber and digital risk index | Three sub-indices: Cyber, Credit-Stress, Continuity, never blended |
| Digital outage | Inside the cyber index (weight 0.6) | Moved to Continuity: extended outage 4h+ (0.8), short outage (0.3), market-infrastructure outage (0.8) |
| Cyber categories | Weights as published | Unchanged; "regulatory action" narrowed to cyber, IT and data protection (non-cyber financial penalties move to Credit-Stress) |
| New categories | — | 10 credit-stress and 8 continuity categories with primary sources (tables above) |
| Decay | 90-day half-life | Cyber 90, Credit-Stress 180, Continuity 120 days; formula written out in full |
| Review | Automated until reviewed | Credit and continuity count only after analyst verification against the primary document |
| Entity mapping | By company name | By ISIN; universe synced automatically |
| Flags | — | Four transmission flags with linked evidence |
| Hygiene | TLS, redirect, headers, SPF, DMARC | Adds certificate expiry, DNSSEC, MTA-STS, CAA and status-page reachability |
| Certificates | — | Independent certificate status shown as a separate badge; never changes any score |
Snapshots computed before this change keep their v2026.1 label. Cyber values can move at the switch because outages left the cyber index.
Known limitations
- Press coverage varies by company size and sector; compare a company with its sector peers.
- Headlines can be inaccurate or later corrected; we link every source so readers can judge.
- Search APIs do not return every article. Absence of signal is not evidence of good security, sound finances or resilient operations.
- Credit-stress signals report events that have already happened; they do not predict anything.
Corrections and right of reply
Anyone, including the company concerned, can request a correction. Requests and outcomes are logged publicly with dates; we aim to answer within 5 working days. See also our independence policy.