Incident Response Policy
Last Updated: June 2026
> Legal notice: Published policy for CheckDeskPro, operated by JMP Mukhi LLC. Reviewed by counsel for commercial operation. Not legal advice for your specific situation.
JMP Mukhi LLC · 2872 Mattox St, Suite B, Tupelo, MS 38801, USA · support@checkdeskpro.com · Governing law: State of Mississippi, USA
1. Purpose
This Incident Response Policy describes how CheckDeskPro responds to security incidents, service disruptions, system failures, and other operational events that may affect customers or the availability of the Service.
The goal of this policy is to promote timely investigation, containment, remediation, and communication regarding significant incidents.
2. Scope
This policy applies to:
- Security incidents
- Unauthorized access attempts
- Data exposure events
- Service outages
- Infrastructure failures
- Software defects affecting operations
- Third-party service disruptions
- Disaster recovery events
3. Incident Response Objectives
CheckDeskPro seeks to:
- Protect customer information
- Minimize service disruption
- Restore normal operations
- Investigate root causes
- Reduce future risk
- Communicate appropriately with affected customers
4. Incident Categories
Security Incidents
Examples include:
- Unauthorized account access
- Credential compromise
- Malware activity
- Suspicious network activity
- Data exposure events
Availability Incidents
Examples include:
- Website outages
- Service interruptions
- Infrastructure failures
- Authentication failures
Operational Incidents
Examples include:
- Software defects
- Data processing failures
- Deployment issues
- Configuration errors
5. Incident Detection
Incidents may be identified through:
- System monitoring
- Security monitoring
- Error reporting
- Customer reports
- Third-party notifications
- Internal reviews
6. Initial Assessment
Upon becoming aware of an incident, CheckDeskPro may:
- Review available information
- Assess potential impact
- Determine severity level
- Identify affected systems
- Initiate response procedures
7. Containment
Reasonable efforts may be made to:
- Isolate affected systems
- Limit further impact
- Prevent unauthorized access
- Preserve evidence
- Maintain service continuity when possible
Containment actions may vary depending on the nature of the incident.
8. Investigation
CheckDeskPro may investigate:
- Root causes
- Affected systems
- Scope of impact
- Duration of exposure
- Customer impact
- Corrective actions
Investigation timelines may vary depending on incident complexity.
9. Recovery
Recovery efforts may include:
- Restoring systems
- Deploying fixes
- Recovering data where possible
- Verifying system integrity
- Monitoring for recurring issues
Recovery procedures may be adjusted based on operational needs.
10. Customer Notification
When appropriate, CheckDeskPro may notify affected customers regarding:
- Significant security incidents
- Material service disruptions
- Data exposure events
- Extended outages
Notification timing may depend on:
- Available facts
- Investigation status
- Legal obligations
- Security considerations
11. Third-Party Incidents
Certain services used by CheckDeskPro may be provided by third-party vendors.
Incidents affecting those providers may impact CheckDeskPro services.
CheckDeskPro may coordinate with vendors when investigating and responding to such incidents.
12. Disaster Recovery
CheckDeskPro maintains operational practices intended to support recovery from:
- Infrastructure failures
- Hosting disruptions
- Hardware failures
- Software failures
- Certain disaster scenarios
Recovery capabilities may vary depending on the circumstances involved.
13. Post-Incident Review
Following significant incidents, CheckDeskPro may:
- Review response effectiveness
- Identify lessons learned
- Implement corrective actions
- Improve monitoring
- Improve operational procedures
The objective is continuous improvement of service reliability and security.
14. Customer Responsibilities
Customers remain responsible for:
- Protecting credentials
- Maintaining device security
- Managing user permissions
- Reviewing account activity
- Reporting suspected incidents promptly
Customer security practices play an important role in overall protection.
15. No Guarantee
While CheckDeskPro seeks to maintain secure and reliable operations, no system can guarantee prevention of all incidents.
This policy describes response objectives and practices and does not create a guarantee of specific outcomes.
16. Policy Updates
This Incident Response Policy may be updated periodically.
Material changes may be communicated through the Service or by other reasonable means.
Continued use of CheckDeskPro constitutes acceptance of revised versions of this policy.
17. Contact Information
JMP Mukhi LLC 2872 Mattox St, Suite B Tupelo, Mississippi 38801 United States
- Security: security@checkdeskpro.com
- Support: support@checkdeskpro.com
- Privacy: privacy@checkdeskpro.com
- Legal Notices: legal@checkdeskpro.com
- Website: checkdeskpro.com