APPNEURAL · Trust Center
Incident response
Agree the incident contacts, ownership, reporting, severity, containment, communication, and recovery process before work begins.
Review area 01
Preparation and ownership
Name the service owner, incident decision-maker, customer contact, escalation path, system dependencies, and evidence preservation responsibilities. Coverage and response times must match actual staffing and the agreement.
Review area 02
Response lifecycle
A useful process distinguishes report, triage, investigation, containment, recovery, notification, and post-incident actions. Severity should reflect impact and urgency; levels do not imply a 24/7 response team.
Review area 03
Customer communications
Define what constitutes a customer-impacting incident, who communicates, the approved channel, update cadence, required content, and applicable legal/contractual deadlines. No universal notification SLA is published.
Review area 04
Report a vulnerability
Use the potential security issue enquiry form for initial contact. This is not a dedicated, monitored security mailbox or guaranteed acknowledgement channel. Do not submit credentials, exploit payloads, personal data, or sensitive production material through a general form.
Evidence and scope
Distinguish guidance from evidence.
This public summary is not an audit, certification, contract, or proof that a control is deployed. APPNEURAL has not published supporting operational evidence here. For a real engagement, confirm the system, data, owner, control implementation, test evidence, and contractual scope before relying on a statement.
Contact
Start an enterprise trust review.
Use the general enquiry form to describe your request. It is not a dedicated security incident channel, and no response-time commitment is stated here. Do not include passwords, credentials, customer records, or sensitive security evidence.
Contact APPNEURAL