Sakhi Management ConsultingDiscuss your project
MenuClose
ISO/IEC 27001, TISAX, India DPDP and ISO 22301

Cybersecurity, Privacy & Business Continuity

Start with one important customer service. Map the information it handles, where it is processed, who has access and which systems keep it running. That map gives teams a common basis for ISO/IEC 27001, TISAX scope, India DPDP readiness and business continuity planning.

  1. Follow the informationPersonal and customer data, systems, owners and external processors
  2. Match the obligationsContract, applicable DPDP requirements, security risk and recovery needs
  3. Prove the controlsAccess review, scoped evidence and observed recovery exercises

Implementation guidance

How do ISO/IEC 27001, TISAX and ISO 22301 differ?

ISO/IEC 27001 defines requirements for an information security management system, including risk treatment and selected controls. TISAX is an automotive information security assessment and exchange mechanism. Confirm the customer’s requested assessment objectives, sites and handling activities before choosing the scope. ISO 22301 focuses on managing disruptions and maintaining critical activities. A shared inventory can support all three, while scope, evidence and assessment decisions remain specific to each.

How should an Indian organisation prepare for DPDP?

Map the personal data processed for each service, the purpose, the responsible business owner, processor relationships, sharing and retention rules. Validate the applicable processing grounds and notices with your privacy or legal owner. Design a way to receive and route rights requests and information about personal data breaches. India’s Digital Personal Data Protection Rules, 2025 provide phased commencement. Use the current notifications and applicability for the organisation rather than copying another company’s deadline. Keep documented evidence that retention and access changes actually took effect.

What makes a continuity exercise useful?

Use a business impact analysis to set the maximum tolerable disruption, recovery objectives, priority activities and dependencies. Establish a recovery time objective (RTO) and recovery point objective (RPO) where applicable. In a controlled test, record when the disruption began, when the team recovered the service, where data was restored from, what was missing and whether business users could complete the critical workflow. A restored login alone tells you little about whether orders, approvals or customer communications recovered.

Worked example

A supplier portal that fails during a shift change

A component supplier’s shared portal handles drawings and dispatch notices. It gives the customer and plant users access to different records. The team maps access owners and external providers, tests an authorised backup restore in a safe environment, and validates an alternative dispatch process. It records which transaction can still be completed and reconciles any entries made during the exercise before putting the service back into normal use.

Run a tabletop exercise for an unavailable order system

Use a fictional outage to test the recovery decisions behind ISO 22301 continuity planning. Give participants the expected recovery time, tolerable data loss and business priority. Record when the team can resume the service and reconcile transactions.

  1. Pick the business service

    Use order dispatch as the exercise scope. Have operations identify dependencies such as warehouse access, carrier contacts, order data and customer communications, with an alternate contact for each owner.

  2. Test the decisions

    At minute 15, tell participants a critical approval contact is unavailable. Ask who can authorise the fallback and how the dispatch lead would log orders while the application is down.

  3. Prove business recovery

    Ask the team to demonstrate on mock data how it would reconcile a manually released order after recovery. Log elapsed time, missing records and unresolved decisions as follow-up evidence.

Evidence checklist

FocusWhat to checkEvidence or decision
Access ownershipWho approved access and can remove it?Approved membership, periodic review and closure evidence
Personal data retentionWhich records have a defined retention decision?Schedule, exception record and sampled deletion verification
Recovery evidenceWhat was usable within the agreed objective?Timestamped exercise record and business-owner acceptance

Common questions

Does ISO/IEC 27001 certification automatically satisfy TISAX?

No. ENX assessment objectives and scope depend on the partner requirement. Reuse valid evidence, then confirm what the TISAX assessment requires.

Can the same inventory support security and DPDP work?

Yes. Use one ownership map, then add the specific fields needed for security risk, privacy processing, retention and legal applicability.

When does a continuity recovery clock stop?

Define the finish in business terms before the exercise. For dispatch, a possible finish is a verified order released and its inventory and shipping records reconciled. Set a separate target for data loss.

Our Inspiration

Mata Ji
Quote Icon Guru Maa Ji Quote Icon

Information

Enquiry Now

    2026 © www.isoconsultants.in. All Right Reserved. | Website Design Company in India Maitrix Infotech

    × How can I help you?