ProtectHQ — DPDP, ISO/IEC 42001 and software asset management

India's data protection obligations now carry fixed dates.

ProtectHQ scopes, audits, remediates and then operates compliance programmes across several regulated disciplines. Engagements are taken one standard at a time, or combined, as the obligation requires.

Statutory clock
—days left
13 November 2026

Consent Manager registration under Rule 4 and the First Schedule, and the Data Protection Board's powers.

—days left
13 May 2027

Notice, consent, security safeguards, breach reporting, retention, children's data, cross-border transfers and Significant Data Fiduciary duties.

DPDP Rules, 2025 notified 14 November 2025.

Our practices

Different regulators, different evidence, one recurring failure: a gap report nobody can act on. We stay through remediation and the first year of operation. Each practice is engaged on its own or alongside the others.

Digital Personal Data Protection Act, 2023

DPDP compliance

Applicability and Significant Data Fiduciary testing, data discovery and records of processing, consent and notice re-architecture, retention schedules, breach response, data principal rights operations.

DPDP services
AI governance · ISO/IEC 42001:2023

AI governance

AI inventory and use-case triage, Annex A control design, AI impact assessments, risk treatment, internal audit and certification readiness through Stage 1 and Stage 2.

AI governance services
ISO/IEC 19770 aligned

Software asset management

Entitlement baselining, effective licence position, publisher audit defence, remediation and true-up negotiation support, then a run-state that keeps the position current.

SAM services

Where the practices overlap

Commissioned separately, the same evidence is gathered more than once by more than one team. Commissioned together, a single inventory and control set answers every auditor. This is an argument for combining them, not a condition of engaging us.

DPDP AI governance Software assets Training data and model inputs Discovery and inventory AI tooling and licences Evidence base
  • DPDP and AI governance. Personal data used to train, fine-tune or prompt a model is both a lawful-basis question and an AI lifecycle control.
  • AI governance and software assets. AI arrives as licensed tooling and API consumption, so the AI inventory and the licence estate are the same list seen twice.
  • DPDP and software assets. You cannot map data flows without knowing what software is deployed, by whom and under what contract.
  • The centre. One inventory, one owner map, one set of contracts and one control register, mapped three ways.

Scope, audit, remediate, operate

Four phases, applied identically whichever standard is in scope. Each concludes with a deliverable you can put in front of a regulator, a board or a publisher's auditor.

Phase 1

Scoping

What is in, what is out, and on what evidence. Systems, entities, data flows, contracts, licence estate. Written down and signed off before anyone starts testing.

Phase 2

Audit

Control-by-control testing against the statute or the standard, with sampling, interviews and artefacts. Findings rated by exposure, not by how awkward they are to raise.

Phase 3

Remediation

We draft the notices, build the registers, rewrite the clauses, configure the workflow and sit with your engineers. Owners and dates against every finding.

Phase 4

Continuous compliance

Rights requests, breach drills, licence reconciliation, control monitoring, management review packs. Either we run it for a term or we train the team that will.

Read the method in detail

Standards and frameworks we work in

Three practices carry their own method pages. Others we deliver on request, or map alongside an engagement already under way. The register below is maintained as the practice grows.

Standard or frameworkHow we take itWhat an engagement covers
Core practice Full four-phase engagement, with its own page On request Delivered as a standalone engagement Mapped alongside Controls cross-referenced inside another engagement

Engage one standard, or several

Nothing here is sold as a bundle. A single-standard engagement is complete in itself, and most clients begin with one. Combining them changes what you pay for evidence, not whether we will take the work.

Start with a scoping call

Forty-five minutes, no deck. Tell us what you process, where it sits and what you have already committed to. You will leave with a view of what is genuinely in scope and what it takes to close it.

Book a scoping call

Digital Personal Data Protection Act, 2023 and DPDP Rules, 2025

DPDP compliance, from applicability to operations

The Rules turned principles into dated obligations. Most organisations do not yet know which of them apply, to which systems, or who owns the answer.

This practice is engaged on its own. Clients who also carry ISO/IEC 42001 or software licensing obligations can combine them, but nothing here requires it.

Book a scoping call

What changed

The DPDP Act, 2023 set the principles. The DPDP Rules, 2025, notified on 14 November 2025, supplied the mechanics and the calendar. Consent Manager registration and the Board's powers commence a year after notification; the operational obligations — notice, security safeguards, breach reporting, retention, children's data, cross-border transfers and Significant Data Fiduciary duties — commence eighteen months after, on 13 May 2027.

Why it is harder than it reads

Consent has to be free, specific, informed and as easy to withdraw as it was to give — which is an architecture problem, not a banner problem. Retention needs schedules with deletion that actually fires. Breach reporting needs a clock that starts before anyone has decided whether it is a breach. And every obligation has to survive an auditor asking for the evidence.

What we do, by phase

Scoping

Every system that touches personal data, found and written down — including the ones that never reached the architecture diagram. Scope is signed off before anyone starts testing.

Audit

Clause by clause against the Act and the Rules, evidenced from live systems rather than from policy documents. Findings rated by regulatory exposure, with the penalty basis stated.

Remediation

Consent, notices, retention and breach response rebuilt until they work in production. Every finding closed against evidence, never against an assurance that it has been handled.

Continuous compliance

Rights requests answered inside statutory timelines, drift caught as systems change, and a board pack that states your position honestly enough to rely on.

The statutory clock

The Rules were notified in November 2025 with commencement staged across eighteen months. Two dates matter.

14 Nov 2025 notified
13 Nov 2026
13 May 2027
Today

Notified

The Rules are made. Nothing commences yet, but the obligations are now fully specified and can be designed against.

Twelve months

Consent Manager registration under Rule 4 and the First Schedule, and the Data Protection Board's powers.

Eighteen months

Notice, security safeguards, breach reporting, retention, children's data, cross-border transfers and Significant Data Fiduciary duties.

Commencement dates as set out in the DPDP Rules, 2025. The marker moves with today's date.

What each phase hands you

Every phase ends with something you can put in front of a regulator, a board or an auditor.

PhasePrincipal deliverableWho it is for
ScopingScope statement, data inventory, processing record, flow mapsYour programme owner
AuditGap register against the Act and Rules, with evidence and exposure ratingRisk committee and counsel
RemediationWorking controls, documents, contracts and runbooks — not recommendationsEngineering and operations
RunOperating rights desk, drills, re-audit and management reportingThe board, and the Board

Scope, sequence and fees are agreed in writing before the audit begins.

The lifecycle you must be able to evidence

Each stage carries its own obligation, and two things cut across all of them: a rights request can arrive at any point, and a breach does not wait for you to be ready.

Collect Process Store Retain Delete Notice in plain language,free and specific consent Purpose limitation —only what you asked for Reasonable securitysafeguards, and logs A schedule, not ahabit of keeping things Deletion that fires,and proves it fired Data principal rights Access, correction, erasure, nomination and grievance — answerable at any stage, inside the statutory window Breach detected Board notified Principals informed the clock starts here without undue delay in terms they understand Most breaches surface in storage and retention
The obligations are not a checklist bolted to the side of this diagram — each one lives at a stage, and the evidence an auditor asks for is the record that the stage behaved.

Commencement is staged, and uneven

Of the twenty-three rules, most of the operational weight falls in the final tranche — which is also the one organisations tend to treat as distant.

23 rules in all 7 on publication Board, appeals, procedure 1 at twelve months Consent Managers 15 at eighteen months Everything operational

Procedural rules took effect on publication and the Consent Manager framework follows at twelve months, but notice, consent, security, breach reporting, retention, children's data, transfers and Significant Data Fiduciary duties all commence together at eighteen months. That final tranche is where the engineering sits, which is why a programme begun when the deadline feels close has already lost the time it needed.

Questions we get asked

We are a processor, not a fiduciary. Does this apply to us?

Your obligations are narrower but not absent, and they arrive through your contracts as much as through the statute. Fiduciaries are pushing security, breach-notification and deletion commitments down to processors now. We scope processor engagements against both the Rules and the contracts you are being asked to sign.

May 2027 is a long way off. Why start now?

Because consent re-architecture and retention with real deletion are engineering programmes with release cycles attached, not documents. The organisations that will be comfortable in May 2027 began in 2026. The November 2026 Consent Manager commencement also needs the same underlying artefacts: purpose taxonomy, consent records, withdrawal propagation.

Can you work with our existing privacy tool?

Yes. We are tool-agnostic and sell no licences. If you already run a consent or privacy platform we configure against it and tell you honestly which obligations it does not cover.

Do you give legal opinions?

No. We give assessments, controls and evidence. Where a position needs a legal opinion we frame the question and work with your counsel on the answer.

Find out what is actually in scope

Most DPDP programmes stall because scope was assumed rather than tested. Start where it matters.

Book a scoping call

AI governance · ISO/IEC 42001:2023

AI governance that withstands a Stage 2 audit

ISO/IEC 42001 is the first certifiable management system standard for artificial intelligence. It asks what you use AI for, who is accountable for it, and what happens when a system behaves outside its intended purpose.

This practice is engaged on its own. Where DPDP or licensing work is already under way, the control sets are mapped across rather than rebuilt.

Book a scoping call

What the standard expects

The familiar management-system shape — context, leadership, planning, support, operation, performance evaluation, improvement — wrapped around AI-specific obligations. Annex A sets out control objectives covering AI policy, internal organisation, resources, impact assessment, lifecycle, data, information for interested parties, use of AI systems and third-party relationships.

Certification follows an independent two-stage audit: a review of the documented system, then an audit of that system operating. Our role is to make both uneventful.

Where it meets your other obligations

An AIMS does not stand alone. Training data pulls in DPDP. Model hosting pulls in your cloud and security controls. Vendor models pull in third-party risk. If you already run ISO/IEC 27001, most of the governance machinery exists and should be extended rather than duplicated.

We build one control set with multiple mappings, so the same evidence answers the privacy auditor and the AIMS auditor.

What we do, by phase

Scoping

Every AI system located, including the ones procurement never saw, and your role for each — developer, provider or deployer — since the obligations differ. A certificate scope you can defend.

Audit

Assessed against every clause and every Annex A control objective, with a statement of applicability justified line by line and mapped to the ISO 27001 controls you already run.

Remediation

Policy, impact assessments, lifecycle gates and human oversight built so a Stage 1 reviewer can follow them without a guide — and so a model can actually be switched off.

Continuous compliance

Internal audit and management review on the standard's cadence, new use cases assessed inside your release process, and surveillance audits that hold no surprises.

Roadmap to certification

The constraint is rarely effort. It is elapsed time: a certification body needs to see the system operating, not just documented.

Month 024 689+ Scope and gap Build the system Operate it — evidence period Stage 1 Stage 2 Internal audit and management review happen here Skip this and Stage 2 finds an empty system
Indicative for a contained scope with an existing ISO/IEC 27001 management system. Starting without one, add three to six months.

The scope statement determines the cost

A certificate names a boundary. Drawn tightly, the audit stays finite; drawn around the phrase "all AI", it commits you to inventorying every spreadsheet someone calls a model.

The organisation Certificate scope named entities, sites and use cases Customer-facing decisioning Document and claims triage The models behind both you build it, you are the provider bought in, you are the deployer training data, drift, retirement Internal productivity tools A pilot with no live users Vendor features you cannot see governed, not certified bring it in when it ships handled through supplier terms Outside the boundary, and on the record

Every exclusion needs a stated reason, because a weak one widens the scope mid-audit. Governing a system and certifying it are different commitments: plenty of AI belongs in your inventory without belonging inside the certificate.

Questions we get asked

We only use third-party AI. Do we need 42001?

You may. Deployers carry obligations around intended use, oversight, monitoring and supplier management. Whether you certify is a commercial decision, usually driven by customers asking. Whether you govern it is not optional once the system touches customers or employment decisions.

How long to certification?

For an organisation with an existing ISO/IEC 27001 system and a contained scope, six to nine months is realistic. Starting from no management system, nine to fifteen. The constraint is almost always evidence of the system operating, which takes elapsed time rather than effort.

Can you certify us?

Preparation and certification are deliberately separate, and should stay that way. We prepare the management system, run the internal audit and support you through both audit stages; the certificate itself follows an independent audit.

Scope the AIMS before you commit to a certificate

The scope statement decides the cost of everything after it. We will help you set one you can actually defend.

Book a scoping call

Software asset management — ISO/IEC 19770 aligned

Your effective licence position, established before it is demanded

Most organisations first establish their licence position inside the response window of a publisher's audit letter. That is the most expensive moment at which to begin.

This practice is engaged on its own, and frequently is — a licence position needs no privacy or AI programme alongside it.

Book a scoping call

Where exposure comes from

Rarely from deliberate under-licensing. It comes from virtualisation and clustering rules, indirect and digital access, processor-based metrics on hardware nobody re-counted after a refresh, editions upgraded by a feature toggle, contractors left in a directory group, and perpetual estates drifting into subscription terms at renewal.

What a run-state looks like

An entitlement baseline that is maintained rather than rebuilt, discovery that reconciles against it on a schedule, a request-to-deploy path that cannot be bypassed, and a licence position you can produce in a week because it is never more than a month old.

What we do, by phase

Scoping

Publishers ranked by spend and by audit likelihood, entitlement sources gathered from contracts rather than portals, and an honest account of what your discovery tooling cannot see.

Audit

An effective licence position per publisher with every metric rule and assumption written out, including the virtualisation, indirect access and sub-capacity analysis that creates most exposure.

Remediation

Reclaim, re-edition and re-host first, then re-run the position — so you negotiate against the corrected number rather than the frightening one in the first draft.

Continuous compliance

A licence position never more than a month old, deployment controls that cannot be bypassed, and a renewal calendar you arrive at already prepared.

How a licence position moves

The first number is almost never the final number. Technical remediation comes before any conversation with the publisher.

Entitlements Deployments Raw gap After remediation After negotiation what you bought what is installed the audit letter number reclaim, re-edition, re-host what you actually pay Illustrative shape of an engagement — not a projection of your estate
Most of the reduction between the third and fourth columns is technical, not commercial. It is also the part publishers do not do for you.

If a letter has already arrived, the order of work changes

The expensive mistakes are made in the first fortnight, usually by being helpful too quickly.

Letter arrives Control the scope Your own position Remediate Respond acknowledge, nothingmore than that entities, period, products,data formats, deadline entitlements rebuiltfrom the contracts reclaim, re-edition,re-host, then recount against the correctednumber Nothing goes to the publisher before this line Data handed over early becomes the baseline you negotiate against Every step above is reversible except one: what you send. Scope, period and format are negotiable at the start and almost never afterwards.
Call before you reply. The acknowledgement is routine; the first substantive response sets the shape of everything that follows.

Questions we get asked

We have received an audit letter. Is it too late?

No, but the order of work changes. Scope control and data handling come first, the internal position second, and nothing goes to the publisher until you know what it says. Call before you respond.

Do we need a SAM tool?

Eventually, for scale. Not to get a first position. Tools report what they are fed; the entitlement baseline and the metric interpretation are the hard parts, and both are human work. We will tell you when a tool is worth buying and we take nothing from the vendor if you do.

Can you handle cloud and SaaS as well as on-premises?

Yes. SaaS waste and licence tier mismatch is usually the quickest money back, and bring-your-own-licence into cloud is where the most unpleasant surprises live.

Get a defensible licence position

Start with one publisher. If the number comes back clean, you have lost very little.

Book a scoping call

How engagements run

Scope, audit, remediate, operate

Advisory work commonly concludes at the findings report, which is where the work properly begins. These four phases are structured so each is incomplete without the next — and so you may conclude the engagement after any one of them.

Phase 1 — Scoping

Everything expensive downstream is decided here: what is in, what is out, and on what grounds.

You leave with a signed-off scope, an inventory with owners, and a fixed price for the audit — a proposal you are free to take to someone else.

Phase 2 — Audit

Control by control against the statute or the standard, evidenced from live systems — including an honest note on what we could not test.

You leave with a findings register rated by exposure, root causes rather than symptoms, and a remediation plan sequenced by dependency.

Phase 3 — Remediation

We do the work beside your team rather than supervising it, and close each finding against evidence rather than against an assurance.

You leave with working controls, the artefacts that prove they work, and a closure report mapping every original finding to what changed.

Phase 4 — Continuous compliance

Compliance decays: systems change, people leave, a new product ships with a new data flow. This phase keeps the position current enough for your board to state it honestly.

You leave with an operating calendar, monthly reporting, drills on schedule, and a handover pack written from day one so you can take the work in-house whenever you want to.

How the phases overlap

They are not four separate projects with four kick-offs. Each one starts before the last has finished, because the handover is where programmes usually lose a month.

Scoping Audit Remediation Continuous compliance Scope signed off Findings register Closure report continues Engagement starts Steady state
Each bar begins while the one above it is still running: findings are raised as they are found, and remediation starts on the first of them rather than waiting for all of them. Relative sequence only — the elapsed time of each phase depends on the estate and is agreed in writing at scoping.

Why the engagement does not end at remediation

A clean audit describes one day. What happens to that position over the following year is the part nobody budgets for.

Control position Held, with re-tests and drills Left alone after remediation Remediation closes A year later Each dot is a re-test, a drill or a reconciliation

Nothing deliberate causes the decline. A system is replaced, an integration is added, someone leaves and takes the only knowledge of a manual step with them, a product ships with a data flow that was never mapped.

The run phase is not monitoring for its own sake. It is the difference between a board that can state its position and a board that is repeating what a consultant told it a year ago.

Illustrative shape, not measured data. The pattern is consistent across engagements; the slope is not something anyone can honestly put a number on.

How we work with your team

A single named lead in the working sessions, a one-page written status each week, and findings raised the week they are found rather than held for the report. Where your policy requires it, we work inside your systems and your evidence never leaves them.

What we need from you

A sponsor who can settle a scope question in a day, access to the people who operate the systems rather than only those who own them, and whatever contracts and records exist — however messy, since reconstructing them is part of the job. Above all, permission to write down what we find.

A gap report that nobody can act on is an expensive way to document a problem you already suspected.

Book a scoping call

About

An independent governance and assurance practice

ProtectHQ delivers data protection, AI management system and software asset assurance work for organisations operating in India. It is the professional services practice of KIPIT Consulting Services (OPC) Private Limited.

Why these practicesOne discipline, several statutes

DPDP, ISO/IEC 42001 and software asset management appear unrelated until you deliver them. Each turns on establishing what you actually hold, evidencing it, closing the distance between the documented state and the real one, and keeping it closed as the organisation changes underneath you. The statute differs; the discipline does not.

It is also why the practice extends to adjacent standards without changing method. The frameworks we currently work in are listed on the home page.

How the practice is staffedSenior practitioners only

Senior practitioners on the work, and engagements sized so the lead is present throughout. We decline work rather than staff it with people learning the standard on a client programme.

Operating principlesFour positions
  • A finding without an owner and a date is an observation, not a finding.
  • Scope decided at the end of an engagement is scope decided by whoever is loudest.
  • Evidence beats assertion, including when the evidence is inconvenient for us.
  • Every engagement should make us less necessary. The handover pack is written from day one.
The teamWho you deal with

There is no junior bench and no account manager between you and the practitioner testing your controls.

Meet the team

Tell us what you are facing

A deadline, an audit letter, a customer questionnaire you cannot answer. Any of those is a fine place to start.

Book a scoping call

Contact

Book a scoping call

Forty-five minutes with the practitioner who would run the engagement.

This opens your email client with the details filled in. Nothing is sent from this page and nothing is stored here.

Direct

contact@protecthq.in

Registered office

KIPIT Consulting Services (OPC) Private Limited
F. No. GAL-122, New Town Heights
Sector 86, Narsinghpur
Gurgaon, Haryana 122004, India
CIN U62090HR2024OPC122269

The practitioners

The practitioners who deliver the work

Senior practitioners deliver every engagement, and the person who scopes it is the person who tests your controls.

Backgrounds and qualifications

Buyers of assurance services assess the people before the firm. This page is therefore specific about experience held and the qualifications supporting it.

Sonal Virdi

Technical Advisor and Auditor, Data Protection · Co-founder

Works across DPDP compliance and AI governance — applicability and scope at one end, and at the other the control evidence an auditor will actually ask to see. Twenty years in banking and fintech security, so controls are designed for organisations already carrying regulatory scrutiny rather than retrofitted to them afterwards. Also builds the assessment frameworks and audit toolkits the practice runs its engagements from.

  • ISO/IEC 42001 Lead Auditor and Lead Implementer
  • Accredited Independent Data Auditor (AIDAI)
  • PCIP Certified Professional
  • 20+ years in banking and fintech information security
  • Specialist in data governance and compliance audit toolkits

Jaideep Singh Kochar

Technical Advisor and Auditor, Data Protection · Co-founder

Works on the parts of an engagement where something has already gone wrong, or is about to: breach detection and response, security safeguards testing, and the reply when a regulator or a software publisher writes. Twenty years inside global technology companies, which is where the licensing and audit-defence knowledge behind the software asset work comes from. An investigator's eye on assurance — what someone would go looking for, not only what a checklist asks.

  • Certified Fraud Examiner (CFE) and expert witness
  • Certified Ethical Hacker (CEH)
  • EC-Council Certified Incident Handler (ECIH)
  • 20+ years working with global technology companies
  • Extensive experience liaising with national and international law enforcement agencies

Both are reachable at contact@protecthq.in.

What a specialist practice gives you

  • The engagement lead is in the working sessions, not only in the steering committee.
  • Findings reach you the week they are found rather than being held for the report.
  • Senior attention throughout, with no handover to a successor partway through.
  • We decline work rather than staff it with people learning the standard on your programme.

Where it constrains you

A specialist practice is not a volume one. Very large parallel estates take longer with us than with a global bench, certification and legal opinions sit with the bodies and counsel properly responsible for them, and our calendar is a real constraint on start dates.

Stated here rather than discovered at kick-off.

Speak to the practitioner who would run it

Describe what you are facing and the engagement lead for that practice takes the call. There is no qualification layer to clear first.

Book a scoping call

Privacy and data handling

How we handle data — yours and your clients'

We ask organisations to be precise about personal data. The same standard applies to us.

Terms of service

Terms of service

These terms cover the use of this website and the general basis on which we provide professional services.