Incident Response
Public summary of security incident detection, containment, and communication practices.
Response Lifecycle
- Detection: identify suspicious activity through monitoring, alerts, or reports.
- Containment: isolate affected systems or credentials to limit impact.
- Investigation: analyze scope, root cause, and affected data classes.
- Remediation: deploy corrective changes and verify recovery.
- Review: capture lessons learned and update controls and runbooks.
<section>
<h2>Communication Approach</h2>
<ul>
<li>Customer communication is prioritized when an incident materially affects customer data or availability.</li>
<li>Notifications include known impact scope, containment status, and next updates when available.</li>
<li>Follow-up communication includes remediation summary and control improvements.</li>
</ul>
</section>
<section>
<h2>Operational Readiness</h2>
<ul>
<li>Incident handling is supported by documented runbooks and operational troubleshooting guides.</li>
<li>Backup and recovery procedures are documented for critical data paths.</li>
<li>Security and platform maintenance workflows include post-incident corrective actions.</li>
</ul>
</section>
<section>
<h2>Security Reporting Contact</h2>
<p>
To report a potential security issue, contact
<a href="mailto:privacy@vostego.com">privacy@vostego.com</a> and include reproducible details.
</p>
</section>