Yirla Incident Response Policy
Incident Response Policy
Purpose
This policy outlines how Yirla responds to security and availability incidents that may impact customers or their data.
What We Consider an Incident
An incident includes events such as:
Unauthorized access to systems or data
Service outages or severe degradation
Data integrity or availability issues
Suspected compromise of credentials or infrastructure
Detection & Assessment
Yirla uses monitoring, logging, and alerts to identify potential incidents. When an issue is detected, the team evaluates:
Scope and severity
Systems and customers affected
Required containment actions
Response & Containment
Once confirmed, Yirla will:
Take steps to contain the issue
Mitigate impact to customers
Preserve relevant logs and evidence
Restore normal service as quickly and safely as possible
Customer Communication
For incidents with customer impact:
Affected customers will be notified within a reasonable timeframe
Communications will include known impact, mitigation steps, and next actions
Updates will be provided as material information becomes available
Post-Incident Review
After resolution, Yirla conducts an internal review to:
Identify root cause
Implement corrective actions
Improve controls and monitoring
Post-incident summaries may be shared with customers upon request for significant incidents.
Contact
Security incidents or concerns can be reported to: