EDITION 2.0 · UPDATED 01 MAY 2026 · INTERNAL · LEADERSHIP · ENG · GTM

The product suite, end‑to‑end.

One portal that explains what we are building, why we are building it, and in what order — across the Cybersec91 and Infosec91 umbrellas. Written so a new joiner gets the picture in an afternoon and an architect can drop into specifics by lunch.

Umbrellas
2
Cybersec91 · Infosec91
Products mapped
14
Across 6 domains
Horizon
0 · 3 · 5 yr
Threat & capability
Volumes
8 live
120+ chapters
§00 In one paragraph

We are building India's sovereign security stack in two halves. Infosec91 is the assurance half — Identity, Data, Privacy, Governance: who has access to what, and is it allowed. Cybersec91 is the defense half — Threat, AppSec, Cloud, AI security: what is happening right now, and how do we stop it. Both share one foundation: a post-quantum-ready cryptographic core, a tamper-proof audit fabric, and the option to deploy anywhere — from public cloud to a fully air-gapped defence installation. MFA was the first product. The next 36 months turn it into a suite that covers every layer attackers care about, including the new ones that arrive with AI agents and Mythos-class workloads.

§01 The umbrella
Infosec91 · Assurance

Who has access to what, and is it allowed.

Identity, data, privacy, and governance. The slow, careful half — built for auditors, regulators, and the CISO's evidence binder.

Multi-Factor Authentication (MFA)● LIVE
Single Sign-On (SSO)● BUILDING
Privileged Access (PAM)○ Y2
Identity Governance (IGA)○ Y2
Data Security & DLP○ Y2
Privacy & Consent (DPDP)○ Y2
Compliance Automation◇ Y3
Cybersec91 · Defense

What is happening right now, and how do we stop it.

Threat, application, cloud, and AI security. The fast half — built for SOC analysts, IR teams, and the 3 AM page.

Zero Trust Access (ZTNA)○ Y2
SIEM & Detection○ Y2
SOAR & Response◇ Y3
Application & API Security◇ Y3
Cloud Security (CSPM/CWPP)◇ Y3
Endpoint & Device Trust◇ Y3
Mythos AI Security Layer◇ Y3–5

Working assumption. If your view of the Cybersec91/Infosec91 split is different, this is where to push back — every other page in the portal builds on it. Mythos is treated as the AI/agent product line that lives in the Cybersec91 half; flag if it should be modeled differently.

§02 Four architectural commitments
01

Sovereign by default

Every byte of customer data stays in India. DPDP, RBI, SEBI, IRDAI, CERT-In, NCIIPC mappings ship with the product.

02

Deployable anywhere

Cloud, on-prem, or fully air-gapped. Same code, same operating model. Defence and SaaS on one platform.

03

Plug in, don't replace

IdP-agnostic. SCIM, SAML, OIDC, RADIUS, LDAP. Weeks-not-quarters integration with what you already run.

04

Post-quantum ready

Pluggable crypto. ML-KEM / ML-DSA / SLH-DSA aligned. When the mandate lands, it's a config flag, not a migration.

§03 The library
VOL 04 · NEW Suite map

The full product suite, end-to-end

Every product in Cybersec91 + Infosec91, the gaps each one closes, and how they share infrastructure.

  • · Umbrella split
  • · 14 products
  • · 6 domains
  • · Shared core
  • · Buyer map
Open suite map
VOL 05 · NEW Feature matrix

Every product, every capability

A capability-by-product grid with build status, owner team, and target quarter. The single source of truth for scope.

  • · 200+ capabilities
  • · Status
  • · Owner team
  • · Target qtr
  • · Filterable
Open matrix
VOL 06 · NEW Threat horizon

Threats & response, 0–3–5 years

What attackers will do over the next five years — incl. AI agents and Mythos-era threats — mapped to the products that defend against each.

  • · Now (0)
  • · Mid (3)
  • · Far (5)
  • · Threat → product
Open horizon
VOL 07 · NEW Build sequence

What we build, in what order, and why

Engineering dependency graph. Which platform components unlock which products. The reuse argument made visible.

  • · Platform layers
  • · Dependencies
  • · Sequencing
  • · Owner teams
Open sequence
VOL 00 Primer

Identity Security, explained

Plain-English, visual primer. Start here if you are new to the category. 10 chapters, 9 diagrams.

  • · What is identity
  • · The 6-layer stack
  • · Acronym jungle
  • · Where we fit
Open primer
VOL 01 Strategy

Building the Identity Security Platform

How MFA becomes the foundation for an entire identity and access suite. Strategic brief, 11 sections.

  • · Platform reuse
  • · 8 token types
  • · PQ crypto
  • · Tier 1/2/3
Open strategy
VOL 02 Playbook

The MFA Positioning Playbook

Complete GTM reference — positioning, personas, pricing, sales process. 17 sections.

  • · Positioning
  • · Personas
  • · Objections
  • · Pricing
Open playbook
VOL 03 Compliance

Compliance Mapping Library

8 frameworks, 60+ controls mapped to capabilities. Auditor-ready evidence + sales lead magnet.

  • · DPDP
  • · RBI · SEBI · IRDAI
  • · CERT-In · NCIIPC
  • · NIST · ISO
Open library
§04 Reading paths
Novice → fluent

The new joiner

~ 90 minutes · one sitting
  1. Read Identity Security, explained end-to-end. The mental model.
  2. Skim Suite map §01–§02 to see where MFA fits in the bigger picture.
  3. Skim Threat horizon §00 (Now). What we are defending against today.
  4. Bookmark Strategy + Playbook for week two.
Engineering / Product

The builder

~ 2 hours · plus deep dives
  1. Read Suite map §03 — the shared platform core.
  2. Open Build sequence — what unlocks what, in what order.
  3. Cross-reference Feature matrix for your product line and quarter.
  4. Use Threat horizon §02 (Far) as input for architecture choices.
Leadership / GTM

The seller

~ 60 minutes
  1. Read Suite map for the umbrella story.
  2. Read Threat horizon — every objection prevention starts here.
  3. Use Playbook §02 (positioning) for the sentence to memorize.
  4. Pull from Compliance library for buyer-specific evidence.
§05 Full index