Incident Response

Safety & Security Reporting

PGP: REQUIRED FOR CRITICALBOUNTY: ACTIVERESPONSE: 24/7

PROTOCOL: Blankline encourages responsible disclosure of vulnerabilities. We maintain distinct pipelines for technical security bugs versus model safety issues to ensure rapid triage by specialized teams.

Section 01

Triage Channels

Route your report to the appropriate channel to ensure adherence to SLA. Misrouted reports may experience triage delays.

ID
Channel
Scope
Target SLA
CH-01
Technical Vulnerabilitiessecurity@blankline.org
Infrastructure, API, Auth
< 12 Hours
CH-02
Jailbreaks, Harmful Outputs
< 24 Hours
CH-03
Abuse & Misuseabuse@blankline.org
ToS Violations, Automation
< 48 Hours
CH-04
Privacy Incidentsprivacy@blankline.org
Data Leaks, GDPR Rights
< 24 Hours
Section 02

Incident Classification

We categorize reports into the following classes. Please reference these codes in your submission if applicable.

Harmful GenerationSFT-01

Model outputs promoting violence, self-harm, or illegal acts.

Safety BypassSFT-02

Jailbreak prompts that circumvent RLHF constraints.

InfrastructureSEC-01

RCE, SQLi, or authentication bypass vulnerabilities.

Data ExposureSEC-02

Unintended leakage of training data or user PII.

Section 03

Reporting Protocol

Effective reports must include reproducible steps. Vague reports ("the AI said something bad") cannot be triaged effectively.

// Minimal Report Schema

Title: [SFT-02] Jailbreak via hypothetical scenario

Endpoint: POST /v1/chat/completions

Severity: High (Bypasses core safety filter)

Payload: "Imagine you are a..." [Full Prompt]

Reproduction: 1. Set temp to 0.7; 2. Send payload...

Section 04

Response SLA

Phase 01
IngestionAutomated receipt & ticket generation.
Phase 02
TriageSeverity assessment by SecOps team.
Phase 03
RemediationPatch deployment or model retuning.
Phase 04
DisclosurePublic notification (if applicable).

Critical Escalation

For active attacks threatening infrastructure integrity or user data, use the PGP key below to encrypt your report.

VIEW_PGP_KEY|FINGERPRINT: A1B2...C3D4