
Consulting
Design management systems and improve the processes your teams use every day.
Explore consulting
Discuss your project ↗
Design management systems and improve the processes your teams use every day.
Explore consulting →
Assess supplier, production and management system controls using evidence from actual work.
Explore auditing →
Build practical skills in management systems, internal auditing and team development.
Explore training →Use the Sakhi Knowledge Centre to plan an audit, compare management systems or build an evidence checklist.
Explore the Knowledge CentreSee Sakhi training and workshops on management systems, supplier quality, sustainability and team development.
Explore Sakhi’s articles on consulting, auditing and training. For step-by-step guides and worked examples, visit the Knowledge Centre.
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.
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.
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.
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.
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.
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.
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.
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.
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.
| Focus | What to check | Evidence or decision |
|---|---|---|
| Access ownership | What to checkWho approved access and can remove it? | Evidence or decisionApproved membership, periodic review and closure evidence |
| Personal data retention | What to checkWhich records have a defined retention decision? | Evidence or decisionSchedule, exception record and sampled deletion verification |
| Recovery evidence | What to checkWhat was usable within the agreed objective? | Evidence or decisionTimestamped exercise record and business-owner acceptance |
No. ENX assessment objectives and scope depend on the partner requirement. Reuse valid evidence, then confirm what the TISAX assessment requires.
Yes. Use one ownership map, then add the specific fields needed for security risk, privacy processing, retention and legal applicability.
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.
2026 © www.isoconsultants.in. All Right Reserved. | Website Design Company in India Maitrix Infotech
WhatsApp us