Security Operations

Vulnerability Disclosure

REF: VDP-2025SAFE HARBOR: ACTIVEREWARD: HALL OF FAME
Section 01

Program Directive

Blankline Security invites researchers to identify vulnerabilities in our infrastructure. We operate a "Safe Harbor" program: researchers acting in good faith and adhering to this policy are authorized to test our systems and will not face legal action.

Safe Harbor Status: Authorization is granted to access data only for the purpose of demonstrating a vulnerability. Do not exfiltrate data.

Section 02

Target Scope

The following assets are explicitly in-scope for this program. Any asset not listed here is out of scope.

Asset Identifier
Asset Type
Priority
*.blankline.org
Wildcard Domain
High
api.blankline.org
Production API
Critical
console.blankline.org
User Dashboard
High
Blankline Desktop
Electron Client
Medium
Section 03

Recognition Protocol

As a research institute, we currently prioritize infrastructure integrity over monetary compensation. However, we believe in honoring those who help secure the frontier. Successful submissions are rewarded with public attribution and reputation verification.

Critical SeverityP1
Hall of Fame + Commendation

Examples: RCE, SQLi, Authentication Bypass, Model Weight Exfiltration.

  • ✓ Permanent listing on Security Hall of Fame
  • ✓ Physical "Founding Security Partner" Challenge Coin
  • ✓ Letter of Attestation from the Founder
High SeverityP2
Hall of Fame Induction

Examples: IDOR, Stored XSS, Privilege Escalation.

  • ✓ Listing on 2025 Security Researchers List
  • ✓ Exclusive Blankline Research T-Shirt
  • ✓ LinkedIn Recommendation
Section 04

Rules of Engagement

01

Do not destroy data. If you encounter PII, stop immediately and report the finding. Do not dump the database.

02

No Social Engineering. Attacks targeting Blankline employees (phishing, vishing) are strictly out of scope.

03

Automated Scans. High-volume automated scanning is prohibited on production endpoints. Use the staging environment.

Section 05

Cryptographic Identity

For critical vulnerabilities, encrypt your report using our PGP key. Reports containing PII must be encrypted.

public_key.asc
RSA 4096
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v2.0.22 (GNU/Linux) mQINBGVxxxxExampleKeyDataxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxEA xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxCGA xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxAQH /xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxAAD ... [TRUNCATED] ... =xxxx -----END PGP PUBLIC KEY BLOCK-----
FINGERPRINT: A1B2 C3D4 E5F6...ID: 0x9A2B3C4D