CERT-In log retention: 180 days in-country without unaffordable storage
The requirement is not the expensive part — the architecture is. A three-tier design that meets 180 days in Indian jurisdiction at roughly a fifth of the licensing-led cost.
Enterprise security questionnaires are largely the same questions in different orders. Organisations answer them from scratch each time, consuming days of senior engineering attention and producing inconsistent answers across deals.
This library provides pre-drafted responses to the 240 questions that recur across CAIQ, SIG Lite, VSA and bespoke enterprise formats, each written to be truthful, specific and evidence-backed rather than defensively vague.
Every answer carries a pointer to the evidence artefact that substantiates it, and a maturity variant — so a company without a formal programme has an honest answer that does not read as a failure.
Why it is structured the way it is, and the failure patterns it was designed around.
The requirement is not the expensive part — the architecture is. A three-tier design that meets 180 days in Indian jurisdiction at roughly a fifth of the licensing-led cost.
A working risk register with a pre-populated scenario library, quantified exposure model and treatment tracking — not an empty template.
Most organisations discover their first real gap during an audit or an incident. The assessment surfaces it in fifteen minutes instead — scored, benchmarked and prioritised, with nothing to buy.
Built for
Kept current
Version 2.2, revised 27 May 2026. We update when a framework changes, when new rules are notified, or when an engagement teaches us something that improves it.
XLSX + DOCX · 62 pages
What this will not do
A template cannot know your systems, test your controls or make the judgement calls that determine whether a programme holds up in an audit. Use it to move faster, not to skip the thinking — and treat any resource claiming to make you compliant on its own as a warning about its author.
The failure is never detection. It is authorisation — nobody knows who can file, and the person who does is asleep. Here is how to build a reporting capability that survives a Saturday.
Tiering model plus four proportionate question sets, so a low-risk vendor answers eight questions and a critical one gets genuine scrutiny.
A DPDPA-conformant notice set — customer, employee, vendor and website — with itemised processing tables and multilingual structure built in.
Your position across privacy, security, governance, risk and AI accountability, scored against sector benchmarks rather than a generic scale.
The specific gaps that matter most for your sector and size, ordered by risk reduction rather than by framework clause number.
Where you stand against DPDPA, ISO 27001, ISO 42001 and SOC 2 — and which of them your buyers are most likely to ask for next.
No sales call required to see your results. Take it, read the output, and decide independently whether you want to talk to anyone.