Effective Date: January 1, 2025
Last Updated: January 1, 2025

1. Introduction
1.1 Net Onboard Sdn Bhd is committed to maintaining a proactive and structured approach to detecting, managing, and mitigating security incidents.
1.2 This Incident Response Policy aligns with:
– ISO 27001 (Information Security Management System)
– NIST Incident Response Framework
– Malaysia’s Personal Data Protection Act (PDPA) 2010
– General Data Protection Regulation (GDPR) (if applicable to EU users)
1.3 This policy outlines the steps, roles, and responsibilities in responding to cybersecurity incidents, data breaches, and system disruptions.

2. Scope & Applicability
2.1 This policy applies to:
– All users, employees, vendors, and third-party service providers handling Net Onboard’s IT systems and cloud services.
– All IT infrastructure, networks, applications, and databases under Net Onboard’s control.
2.2 It covers:
– Cybersecurity threats (malware, hacking, phishing, ransomware).
– Unauthorized access (data breaches, account compromises, insider threats).
– Service disruptions (DDoS attacks, system failures, infrastructure malfunctions).

3. Incident Classification & Severity Levels
3.1 All incidents are categorized based on severity and impact:
3.1.1. Critical Severity
– Description: Data breach, ransomware attack, or full system outage
– Response Time: 30 minutes
– Resolution Target: Within 4 hours
3.1.2. High Severity
– Description: Major security threat or unauthorized access detected
– Response Time: 30 minutes
– Resolution Target: Within 8 hours
3.1.3. Medium Severity
– Description: Suspicious activity or partial service disruption
– Response Time: 1 hour
– Resolution Target: Within 24 hours
3.1.4. Low Severity
– Description: Minor security alerts, such as failed login attempts
– Response Time: 4 hours
– Resolution Target: By the next business day

4. Incident Response Lifecycle
4.1 Phase 1: Identification
– Continuous security monitoring & log analysis is performed.
– Alerts from firewalls, IDS/IPS systems, antivirus software, and AI-based anomaly detection are reviewed.
– Users must report security concerns immediately via [email protected].
4.2 Phase 2: Containment
– Affected systems will be isolated to prevent further damage.
– Immediate account lockout and network segmentation measures will be applied.
– Third-party cybersecurity teams may be engaged for emergency response.
4.3 Phase 3: Eradication
– Malicious code, unauthorized access, or compromised credentials will be removed.
– Security patches and system updates will be deployed.
– Network security policies will be reviewed to prevent recurrence.
4.4 Phase 4: Recovery
– Affected systems will be restored from secure backups (geo-redundant storage).
– Service functionality will be tested before reconnecting to production environments.
– Continuous monitoring for residual threats will continue.
4.5 Phase 5: Post-Incident Review & Reporting
– A detailed incident report will be generated, documenting findings and lessons learned.
– Root cause analysis (RCA) will be performed.
– Security policies and user awareness training will be updated accordingly.

5. Data Breach Notification & Compliance
5.1 If a data breach is confirmed:
– Affected users will be notified within 72 hours in accordance with PDPA & GDPR.
– Regulatory authorities will be informed based on legal requirements.
– Users will receive guidance on protective actions (e.g., password resets, account monitoring).

6. User Responsibilities in Security Incidents
6.1 Users must:
– Report any suspected security incidents or suspicious activity immediately to [email protected].
– Follow company security policies (e.g., using strong passwords, enabling MFA).
– Cooperate with the investigation team during security incidents.

7. Compliance & Regulatory Standards
7.1 This policy ensures compliance with:
– ISO 27001 & NIST Cybersecurity Framework
– Malaysia’s Personal Data Protection Act (PDPA) 2010
– General Data Protection Regulation (GDPR) (if applicable)

8. Governing Law & Dispute Resolution
8.1 This policy is governed by Malaysian law.
8.2 Disputes regarding security incidents will be handled through mediation before proceeding to arbitration or litigation.

9. Amendments & Updates
9.1 Net Onboard reserves the right to update this Incident Response Policy at any time.
9.2 Users will be notified of material changes via email or system notifications.
For incident reporting and security-related inquiries, contact [email protected].