# Surge Security Overview

Surge publishes a public search API over its indexed pages; the guide is at https://surge.app/agents/agent-access.

Source: https://surge.app/security/
Source observed: 2026-11-05T16:19:49.705Z
Last checked: 2026-11-12T19:32:26.688+00:00
Indexed: 2026-11-05T16:21:21.608+00:00

---

# Surge Security Overview

**Last updated:** April 17, 2025

This Security Overview forms part of the agreement between Surge and each customer governing use of Surge services. We use **Customer Data** to mean data supplied by a customer or its users to Surge in connection with the services, including data supplied through the customer's products and services, or data created for the customer's use as part of the services. **Services** means services or APIs branded under the name Surge.

The overview describes our security certifications, self-attestations, and technical, organizational, administrative, and physical measures for protecting Customer Data and the Services. We may update it as threats and practices evolve, but changes will not significantly diminish the overall protections described here. The latest version is available by emailing [security@surge.app](mailto:security@surge.app). This overview does not apply to alpha, beta, not generally available, limited-release, developer-preview, or similar services, or to services provided by telecommunications providers.

## Security organization and program

We operate a risk-based security program designed to protect the security, confidentiality, integrity, and availability of the Services and Customer Data. Our Chief Information Security Officer regularly consults executive management, and executive management reviews and approves our information-security policies and standards at least annually.

## People security and onboarding

Our employee security controls include:

- Background checks for new employees before hiring, administered by a reputable third-party provider in accordance with applicable local law. Checks may verify education, employment, references, and, where legally permitted and relevant to the role, criminal, credit, and right-to-work information.
- Confidentiality agreements.
- Mandatory annual security and privacy training, with extensions for employees on leave.
- An anonymously reportable employee inbox where anonymous reporting is legally allowed.
- Security-threat awareness activities, including simulated phishing campaigns.
- Customer Data access limited to authorized employees under our access-control procedures.

## Physical security

Our offices follow a regularly reviewed physical-security policy covering office access, IT-equipment protection, and after-hours monitoring. We require infrastructure providers to maintain physical-security standards meeting or exceeding SOC 2 standards.

## Third-party vendor management

We may use third-party vendors to deliver the Services. Our vendor-management program applies technical and organizational controls proportionate to the vendor's service and associated risks. We vet prospective vendors against our confidentiality, security, and privacy standards. Vendors handling Customer Data receive additional contractual controls and are regularly audited. We also review vendors against our security and business-continuity standards, their access to Customer Data and protective measures, and evolving legal or regulatory requirements.

## Security certifications and attestations

We possess the following security-related certification and attestation:

- **SOC 2 Type 1**

For certification, attestation, or related security documentation, email [security@surge.app](mailto:security@surge.app).

## Hosting architecture and data segregation

### Infrastructure providers

All services are hosted by Amazon Web Services (AWS). AWS security information is available at:

- [AWS Security](https://aws.amazon.com/security/)
- [AWS Shared Responsibility Model](https://aws.amazon.com/compliance/shared-responsibility-model/)

### Production environment and Customer Data access

Our production environment is logically isolated in a Virtual Private Cloud (VPC), and Customer Data is encrypted at all times. The infrastructure providers are located in the United States and do not have access to unencrypted Customer Data. Network access between production hosts is restricted using access controls and least privilege. Access-control lists segregate security zones in our production and corporate environments and are reviewed regularly.

We segregate Customer Data with logical identifiers and a unique customer identifier. Our APIs permit authorized access only to data tagged with the relevant customer-specific identifier, preventing access by other customers.

## Security by design

We apply security-by-design principles throughout our Software Development Lifecycle, from requirements and product design through deployment. Activities include internal security reviews before releasing new services or code, independent third-party penetration tests for new services, and threat modeling to identify threats and vulnerabilities.

## Access controls

### Provisioning access

We use team-based access controls and least privilege. Surge employees receive Customer Data access only after approval and only when their roles require it. We review non-time-based production permissions at least quarterly and promptly revoke Customer Data access when an employee or contractor leaves.

Production access requires an individually assigned username, password, and multi-factor authentication. Management approval and internal training are required before access is granted. We log high-risk production actions and changes. Automated controls detect deviations from technical standards and can trigger alerts within minutes of configuration changes.

### Password controls

Our employee password policy follows NIST 800-63B guidance, including longer passwords and multi-factor authentication. For customer logins, we hash credentials before storing them and check passwords against security-breach databases. Customers can enable or require two-factor authentication (2FA) for their users.

## Change management

We use a formal change-management process for production changes to software, applications, and systems. Each change is reviewed and tested in a test environment before production deployment, and the process is documented in an auditable record system. High-risk changes receive a security-impact assessment and stakeholder approval. Rollback plans and procedures are maintained when needed to preserve service security.

## Encryption

### Encryption in transit

We encrypt Customer Data between a customer's software application and the Services using **TLS v1.2**.

### Encryption at rest

We encrypt Customer Data at rest in AWS using the **Advanced Encryption Standard**.

## Vulnerability management

We use policies and controls intended to address vulnerabilities within timeframes that balance risk with business and operational needs. Third-party tools perform regular scans of our hosting environment and corporate systems. We assess, test, and apply critical patches proactively. Operating-system patches are deployed by regenerating a base virtual-machine image and rolling it out to all nodes in the Surge cluster on a predefined schedule; high-risk patches may be deployed directly to existing nodes.

To report a suspected vulnerability, review our [Vulnerability Disclosure Policy](https://surge.app/vulnerability-disclosure/).

## Penetration testing

We conduct penetration testing and work with independent third parties on detailed application-level penetration tests. We prioritize, assess, and address identified threats and vulnerabilities for prompt remediation.

## Security incident management

### Prevention measures

Our incident-management policies and procedures align with **NIST SP 800-61**. Our security team evaluates relevant threats and vulnerabilities and selects remediation and mitigation strategies. We retain security logs for **180 days**, with access restricted to the security team. We use third-party tools to detect, mitigate, and prevent Distributed Denial of Service (DDoS) attacks.

### Incident response

When we discover a Security Incident as defined in the Agreement, we promptly investigate. Subject to applicable law and regulation, we notify the customer under the Agreement by email to the address specified in the customer's account. Our response may include customer notification where required, coordination with law enforcement, and reports to privacy or regulatory authorities as necessary.

## Resilience and service continuity

### Resilience

We use multiple independent availability zones within our infrastructure providers so a single data-center failure does not affect service availability. We can identify and bypass problems affecting individual hosts or entire data centers in real time, and our orchestration tools can regenerate hosts from the most recent backups.

### Service continuity

Hosting-infrastructure tools monitor server performance, data, and traffic capacity in each availability zone. When they detect degraded performance or capacity overload, they automatically increase capacity or redirect traffic, and we receive immediate notifications.

## Customer Data backups

We routinely back up Customer Data hosted on AWS data-center infrastructure. Backups are stored redundantly across multiple availability zones and encrypted both in transit and at rest using modern encryption standards appropriate to the type of Customer Data.

## Security questions

For security documentation, our SOC 2 report, or answers to a security questionnaire, email [security@surge.app](mailto:security@surge.app).

---

[Read this page’s summary](https://surge.app/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fsurge.app%2Fsecurity%2F&trace=t_96494d7d69f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Surge’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://surge.app/agents/agent/faq?q={question}&trace=t_96494d7d69f3`

[Tool guide and examples](https://surge.app/agents/agent-access) · [OpenAPI](https://surge.app/agents/api/public/v1/openapi.json) · [Page TLDR form](https://surge.app/agents/agent-tools/page-tldr?url=https%3A%2F%2Fsurge.app%2Fsecurity%2F). Opening a form does not execute a tool.