PingPup Security & Compliance

Last Updated: October 21, 2026

At PingPup, the security, integrity, and confidentiality of customer data and observability telemetry are foundational to our platform. We implement defense-in-depth security controls, rigorous cryptographic isolation, and enterprise-grade access governance across all infrastructure tiers.

1. Global Monitoring Infrastructure Security

PingPup operates a high-availability, globally distributed probing network designed for secure, non-invasive health checks:

• Automated Verification: To eliminate transient false positives, our edge infrastructure employs automated multi-region consensus checks before escalating downtime incidents.
• Non-Invasive Diagnostics: Health probes perform non-intrusive network handshakes and TLS certificate inspections. Probes never execute untrusted scripts or parse user-generated application data on customer target systems.
• DDoS & Traffic Safeguards: Probe dispatchers maintain strict rate limits, staggered polling intervals, and automated backoff to ensure monitoring traffic never impacts target infrastructure availability.

2. Multi-Tenant Data Isolation & Storage Security

All customer telemetry, endpoint definitions, and incident histories are protected by strict segregation controls:

• Logical Data Segregation: Multi-tenant data segregation is enforced at the database kernel level through cryptographically validated Row-Level Security (RLS) policies. Every query is bound strictly to the authenticated tenant context, preventing cross-tenant data access.
• Encryption at Rest: All persistent storage volumes, telemetry repositories, and database backups are encrypted at rest using industry-standard AES-256 encryption.
• Secrets & Credential Protection: API keys, webhook signing secrets, and third-party delivery credentials are encrypted using secure envelope encryption with restricted key rotation. Plaintext credentials are never returned to client interfaces after initial creation.

3. Network & Transport Layer Security

• Encryption in Transit: All ingress and egress traffic across PingPup APIs, dashboards, and edge nodes is strictly enforced over TLS 1.3 with Perfect Forward Secrecy (PFS) and HTTP Strict Transport Security (HSTS).
• Cryptographic Webhook Signatures: Outgoing incident webhooks include cryptographic HMAC-SHA256 signatures with timestamp anti-replay verification, allowing customer endpoints to cryptographically verify origin authenticity.
• Network Perimeter Defense: Edge ingress is guarded against malicious traffic, automated scrapers, and volumetric attacks via distributed web application firewalls (WAF) and intelligent rate limiters.

4. Access Governance & Privileged Access Management (PAM)

• Principle of Least Privilege: Internal access to infrastructure and production systems is governed by strict Role-Based Access Control (RBAC) and the principle of least privilege.
• Multi-Factor Authentication (MFA): Hardware-backed multi-factor authentication is mandatory for all personnel accessing administrative environments.
• Immutable Audit Logging: Administrative access and security-sensitive operations are captured in tamper-evident audit logs with centralized security alerting.
• Proof-of-Delivery Verification: PingPup maintains an immutable delivery ledger documenting outbound incident dispatches, verified transport status codes, and latency telemetry for operational SLA auditability.

5. Payment Security & PCI-DSS Compliance

PingPup does not collect, process, or store raw credit card numbers, CVVs, or sensitive payment instrumentation on our servers:

• All payment processing, invoicing, and tax calculations are handled by certified PCI-DSS Level 1 Merchant of Record partners.
• Payment interactions take place within hosted, tokenized environments adhering to global banking security standards.

6. Vulnerability Management & Responsible Disclosure

We welcome reports from independent security researchers and developers to help keep PingPup secure:

• Reporting Channel: If you believe you have identified a potential security issue, please contact us immediately at [email protected].
• Coordinated Disclosure: We ask that researchers provide a detailed technical description with reproducible steps and allow a reasonable window for remediation prior to public disclosure.
• Safe Harbor: PingPup commits to not taking legal action against researchers who discover and report vulnerabilities in good faith in accordance with standard coordinated vulnerability disclosure principles.