Security & Data Breach Policy
his policy describes the security principles and incident response process applicable to personal data and business information handled through the Company’s Website and related systems. It is a governance policy; actual controls must be implemented and evidenced by the Company’s IT and service-provider teams.
1 Security principles
- Use the Website for lawful business information, legitimate enquiries, authorized pharmaceutical distribution relationships and other purposes consistent with its published functions.
- Restrict access by role and business need; promptly remove access when personnel or vendors no longer require it.
- Use secure hosting, HTTPS, supported software versions, strong authentication and timely security updates.
- Protect backups and business records; periodically test restoration and continuity arrangements.
- Use appropriate malware protection, logging, monitoring and vulnerability management.
- Require confidentiality and security obligations from employees and service providers.
- Securely delete or anonymize information when retention is no longer necessary, subject to legal holds and statutory retention duties.
2. Data classification
The Company should classify data as public, internal, confidential or restricted. Restricted data may include drug license documents, account credentials, personal identity documents, payment-related records, sensitive commercial terms and any health-related information. Restricted data must be shared only through approved secure channels.
3. Incident definition
A security incident includes suspected or confirmed unauthorized access, disclosure, alteration, loss, destruction, ransomware, account compromise, malware infection, misdirected email, lost device, compromised vendor, Website defacement or other event affecting confidentiality, integrity or availability of personal data or critical business information.
4. Response steps
- Identify and report: personnel and vendors must immediately report suspected incidents to the designated Company contact / IT administrator.
- Contain: isolate affected systems or accounts, revoke compromised credentials, block malicious access and preserve logs.
- Assess: determine the data and systems affected, categories and approximate number of individuals, likely consequences, time period, root cause and vendor involvement.
- Notify: make notifications to affected individuals, regulators, the Data Protection Board or other authorities within the time and manner required by applicable law and sectoral rules. Do not wait for a complete forensic report where an immediate statutory notification is required.
- Remediate: remove the threat, patch vulnerabilities, restore clean backups, reset credentials and implement corrective controls.
- Document: preserve incident timeline, decisions, evidence, communications, impact assessment, notifications and lessons learned.
- Review: conduct a post-incident review and update training, contracts, systems and this policy.
5. Statutory breach notifications
Where the DPDP Act and Rules require notification of a personal data breach, the Company will follow the applicable prescribed format, recipients and timelines, including any initial intimation and subsequent detailed report requirements then in force. Other laws, contractual terms and sector-specific requirements may impose additional or earlier reporting duties. The Company must verify the current requirements at the time of an incident.
6. Third-party incidents
Where a processor or vendor handles data for the Company, the contract must require prompt incident notification, cooperation, evidence preservation, containment, remediation and support for legally required notices. The Company should maintain current emergency contacts for critical vendors.
7. Contact
Report suspected incidents immediately to info@sklifetime.com and by telephone at 8555020162. The Company should internally designate a primary and backup incident lead and maintain an out-of-band emergency contact method.