Security and compliance at Linq
Independently audited, continuously monitored
Linq holds SOC 2 Type I and SOC 2 Type II certification. SOC 2 reports are published for 2022, 2024, 2025, and 2026, along with a March 2026 bridge letter covering the period between audits. SOC 2 Type II is the standard procurement and security teams check first, because it proves controls operate effectively over time rather than existing on paper.
Beyond the audits, 70 controls are tested on an ongoing basis and their live pass status is published on our Trust Center, which is also where audit reports are requested. Every one of those controls is listed below.
All 70 controls we monitor
Grouped into the same five categories as our Trust Center. Some controls appear under more than one category, exactly as they do there.
Infrastructure security
33 controls- Unique production database authentication enforced
- The company requires authentication to production datastores to use authorized secure authentication mechanisms, such as unique SSH key.
- Encryption key access restricted
- The company restricts privileged access to encryption keys to authorized users with a business need.
- Unique account authentication enforced
- The company requires authentication to systems and applications to use unique username and password or authorized Secure Socket Shell (SSH) keys.
- Production application access restricted
- System access restricted to authorized access only
- Access control procedures established
- The company's access control policy documents the requirements for the following access control functions: adding new users; modifying users; and/or removing an existing user's access.
- Production database access restricted
- The company restricts privileged access to databases to authorized users with a business need.
- Firewall access restricted
- The company restricts privileged access to the firewall to authorized users with a business need.
- Production OS access restricted
- The company restricts privileged access to the operating system to authorized users with a business need.
- Production network access restricted
- The company restricts privileged access to the production network to authorized users with a business need.
- Access revoked upon termination
- The company completes termination checklists to ensure that access is revoked for terminated employees within SLAs.
- Unique network system authentication enforced
- The company requires authentication to the "production network" to use unique usernames and passwords or authorized Secure Socket Shell (SSH) keys.
- Remote access MFA enforced
- The company's production systems can only be remotely accessed by authorized employees possessing a valid multi-factor authentication (MFA) method.
- Remote access encrypted enforced
- The company's production systems can only be remotely accessed by authorized employees via an approved encrypted connection.
- Infrastructure performance monitored
- An infrastructure monitoring tool is utilized to monitor systems, infrastructure, and performance and generates alerts when specific predefined thresholds are met.
- Network segmentation implemented
- The company's network is segmented to prevent unauthorized access to customer data.
- Network firewalls reviewed
- The company reviews its firewall rulesets at least annually. Required changes are tracked to completion.
- Risk management program established
- The company has a documented risk management program in place that includes guidance on the identification of potential threats, rating the significance of the risks associated with the identified threats, and mitigation strategies for those risks.
- MDM system utilized
- The company has a mobile device management (MDM) system in place to centrally manage mobile devices supporting the service.
- Incident response plan tested
- The company tests their incident response plan at least annually.
- Penetration testing performed
- The company's penetration testing is performed at least annually. A remediation plan is developed and changes are implemented to remediate vulnerabilities in accordance with SLAs.
- Password policy enforced
- The company requires passwords for in-scope system components to be configured according to the company's policy.
- Confidentiality Agreement acknowledged by employees
- The company requires employees to sign a confidentiality agreement during onboarding.
- Confidentiality Agreement acknowledged by contractors
- The company requires contractors to sign a confidentiality agreement at the time of engagement.
- Employee background checks performed
- The company performs background checks on new employees.
- Backup processes established
- The company's data backup policy documents requirements for backup and recovery of customer data.
- Production data segmented
- The company prohibits confidential or sensitive customer data, by policy, from being used or stored in non-production systems/environments.
- Data encryption utilized
- The company's datastores housing sensitive customer data are encrypted at rest.
- Portable media encrypted
- The company encrypts portable and removable media devices when used.
- Development lifecycle established
- The company has a formal systems development life cycle (SDLC) methodology in place that governs the development, acquisition, implementation, changes (including emergency changes), and maintenance of information systems and related technology requirements.
- Production data backups conducted
- The company performs periodic backups for production data. Data is backed up to a different location than the production system.
- Cybersecurity insurance maintained
- The company maintains cybersecurity insurance to mitigate the financial impact of business disruptions.
- Continuity and Disaster Recovery plans tested
- The company has a documented Business Continuity/Disaster Recovery (BC/DR) plan and tests it at least annually.
- Continuity and Disaster Recovery plans established
- The company has Business Continuity and Disaster Recovery Plans in place that outline communication plans in order to maintain information security continuity in the event of the unavailability of key personnel.
Product security
4 controls- Data encryption utilized
- The company's datastores housing sensitive customer data are encrypted at rest.
- Control self-assessments conducted
- The company performs control self-assessments at least annually to gain assurance that controls are in place and operating effectively. Corrective actions are taken based on relevant findings. If the company has committed to an SLA for a finding, the corrective action is completed within that SLA.
- Penetration testing performed
- The company's penetration testing is performed at least annually. A remediation plan is developed and changes are implemented to remediate vulnerabilities in accordance with SLAs.
- Vulnerability and system monitoring procedures established
- The company's formal policies outline the requirements for the following functions related to IT / Engineering: vulnerability management; system monitoring.
Organizational security
13 controls- Asset disposal procedures utilized
- The company has electronic media containing confidential information purged or destroyed in accordance with best practices, and certificates of destruction are issued for each device destroyed.
- Portable media encrypted
- The company encrypts portable and removable media devices when used.
- Anti-malware technology utilized
- The company deploys anti-malware technology to environments commonly susceptible to malicious attacks and configures this to be updated routinely, logged, and installed on all relevant systems.
- Employee background checks performed
- The company performs background checks on new employees.
- Code of Conduct acknowledged by contractors
- The company requires contractor agreements to include a code of conduct or reference to the company code of conduct.
- Code of Conduct acknowledged by employees and enforced
- The company requires employees to acknowledge a code of conduct at the time of hire. Employees who violate the code of conduct are subject to disciplinary actions in accordance with a disciplinary policy.
- Confidentiality Agreement acknowledged by contractors
- The company requires contractors to sign a confidentiality agreement at the time of engagement.
- Confidentiality Agreement acknowledged by employees
- The company requires employees to sign a confidentiality agreement during onboarding.
- Performance evaluations conducted
- The company managers are required to complete performance evaluations for direct reports at least annually.
- Password policy enforced
- The company requires passwords for in-scope system components to be configured according to the company's policy.
- MDM system utilized
- The company has a mobile device management (MDM) system in place to centrally manage mobile devices supporting the service.
- Visitor procedures enforced
- The company requires visitors to sign-in, wear a visitor badge, and be escorted by an authorized employee when accessing the data center or secure areas.
- Security awareness training implemented
- The company requires employees to complete security awareness training within thirty days of hire and at least annually thereafter.
Internal security procedures
32 controls- Continuity and Disaster Recovery plans established
- The company has Business Continuity and Disaster Recovery Plans in place that outline communication plans in order to maintain information security continuity in the event of the unavailability of key personnel.
- Continuity and Disaster Recovery plans tested
- The company has a documented Business Continuity/Disaster Recovery (BC/DR) plan and tests it at least annually.
- Cybersecurity insurance maintained
- The company maintains cybersecurity insurance to mitigate the financial impact of business disruptions.
- Configuration management system established
- The company has a configuration management procedure in place to ensure that system configurations are deployed consistently throughout the environment.
- Development lifecycle established
- The company has a formal systems development life cycle (SDLC) methodology in place that governs the development, acquisition, implementation, changes (including emergency changes), and maintenance of information systems and related technology requirements.
- Whistleblower policy established
- The company has established a formalized whistleblower policy, and an anonymous communication channel is in place for users to report potential issues or fraud concerns.
- Board oversight briefings conducted
- The company's board of directors or a relevant subcommittee is briefed by senior management at least annually on the state of the company's cybersecurity and privacy risk. The board provides feedback and direction to management as needed.
- Board charter documented
- The company's board of directors has a documented charter that outlines its oversight responsibilities for internal control.
- Board expertise developed
- The company's board members have sufficient expertise to oversee management's ability to design, implement and operate information security controls. The board engages third-party information security experts and consultants as needed.
- Board meetings conducted
- The company's board of directors meets at least annually and maintains formal meeting minutes. The board includes directors that are independent of the company.
- Backup processes established
- The company's data backup policy documents requirements for backup and recovery of customer data.
- System changes externally communicated
- The company notifies customers of critical system changes that may affect their processing.
- Management roles and responsibilities defined
- The company management has established defined roles and responsibilities to oversee the design and implementation of information security controls.
- Organization structure documented
- The company maintains an organizational chart that describes the organizational structure and reporting lines.
- Roles and responsibilities specified
- Roles and responsibilities for the design, development, implementation, operation, maintenance, and monitoring of information security controls are formally assigned in job descriptions and/or the Roles and Responsibilities policy.
- Security policies established and reviewed
- The company's information security policies and procedures are documented and reviewed at least annually.
- Support system available
- The company has an external-facing support system in place that allows users to report system information on failures, incidents, concerns, and other complaints to appropriate personnel.
- System changes communicated
- The company communicates system changes to authorized internal users.
- Access reviews conducted
- The company conducts access reviews at least quarterly for the in-scope system components to help ensure that access is restricted appropriately. Required changes are tracked to completion.
- Access requests required
- The company ensures that user access to in-scope system components is based on job role and function or requires a documented access request form and manager approval prior to access being provisioned.
- Incident response plan tested
- The company tests their incident response plan at least annually.
- Incident response policies established
- The company has security and privacy incident response policies and procedures that are documented and communicated to authorized users.
- Incident management procedures followed
- The company's security and privacy incidents are logged, tracked, resolved, and communicated to affected or relevant parties by management according to the company's security incident response policy and procedures.
- Physical access processes established
- The company has processes in place for granting, changing, and terminating physical access to company data centers based on an authorization from control owners.
- Data center access reviewed
- The company reviews access to the data centers at least annually.
- Company commitments externally communicated
- The company's security commitments are communicated to customers in Master Service Agreements (MSA) or Terms of Service (TOS).
- External support resources available
- The company provides guidelines and technical support resources relating to system operations to customers.
- Service description communicated
- The company provides a description of its products and services to internal and external users.
- Risk assessment objectives specified
- The company specifies its objectives to enable the identification and assessment of risk related to the objectives.
- Risks assessments performed
- The company's risk assessments are performed at least annually. As part of this process, threats and changes (environmental, regulatory, and technological) to service commitments are identified and the risks are formally assessed. The risk assessment includes a consideration of the potential for fraud and how fraud may impact the achievement of objectives.
- Risk management program established
- The company has a documented risk management program in place that includes guidance on the identification of potential threats, rating the significance of the risks associated with the identified threats, and mitigation strategies for those risks.
- Third-party agreements established
- The company has written agreements in place with vendors and related third-parties. These agreements include confidentiality and privacy commitments applicable to that entity.
Data and privacy
3 controls- Data retention procedures established
- The company has formal retention and disposal procedures in place to guide the secure retention and disposal of company and customer data.
- Customer data deleted upon leaving
- The company purges or removes customer data containing confidential information from the application environment, in accordance with best practices, when customers leave the service.
- Data classification policy established
- The company has a data classification policy in place to help ensure that confidential data is properly secured and restricted to authorized personnel.
Audit and penetration test reports
Reports are released through a self-serve access request under a standard NDA — no sales call required. The bridge letter and vulnerability disclosure policy open without a request.
- 2026 SOC 2 Type II ReportRequest access
- 2026 Penetration Test ReportRequest access
- March 2026 SOC 2 Bridge LetterOpen access
- 2025 SOC 2 Type II ReportRequest access
- 2024 SOC 2 Type II ReportRequest access
- SOC 2 Type II Compliance Report 2022Request access
- SOC 2 Type I Compliance Report 2022Request access
- Vulnerability DisclosureOutlines our vulnerability disclosure processOpen access
Every subprocessor we use
The complete list, maintained on our Trust Center. It pairs with our Data Processing Addendum.
- AWSCloud infrastructure, compute, database hosting, object storage, and encryption key management
- CloudflareContent delivery network, web application firewall, DDoS protection, and TLS termination for all public-facing traffic
- Grafana LabsInfrastructure and application log aggregation, monitoring dashboards, and alerting
- SentryCloud application error tracking and performance monitoring
- HexData visualization and analytics
Read the Data Processing Addendum.
Security & compliance FAQ
Is Linq SOC 2 compliant?
Yes. Linq holds both SOC 2 Type I and SOC 2 Type II certifications. SOC 2 reports are published for 2022, 2024, 2025, and 2026, along with a March 2026 bridge letter covering the period between audits. All of them are available through the Linq Trust Center at security-report.linqapp.com.
How do I get a copy of Linq's SOC 2 report?
Request it through the Linq Trust Center at security-report.linqapp.com. The 2026 SOC 2 Type II report, the 2026 penetration test report, and the 2025, 2024, and 2022 reports are released through a self-serve access request under NDA. The March 2026 SOC 2 bridge letter and the vulnerability disclosure policy open without a request.
How does Linq encrypt customer data?
Datastores housing sensitive customer data are encrypted at rest, and privileged access to encryption keys is restricted to authorized users with a business need. Portable and removable media are encrypted, and production systems can only be accessed remotely over an approved encrypted connection with multi-factor authentication. All four are monitored controls published on the Linq Trust Center. AWS provides the underlying encryption key management.
What security controls does Linq monitor?
Linq continuously monitors 70 distinct security controls, grouped on its Trust Center into five categories: infrastructure security, internal security procedures, organizational security, product security, and data and privacy. Every control and its live pass status is published at security-report.linqapp.com and refreshed continuously. All of them are listed on this page.
Does Linq perform penetration testing?
Yes. Penetration testing is performed at least annually, with a remediation plan developed and changes implemented in accordance with defined SLAs. The 2026 penetration test report is available through the Trust Center, and Linq publishes a vulnerability disclosure policy outlining how to report an issue. Linq also conducts control self-assessments at least annually and tests its incident response plan at least annually.
Who are Linq’s subprocessors?
Linq discloses five subprocessors: AWS for cloud infrastructure, compute, database hosting, object storage, and encryption key management; Cloudflare for CDN, web application firewall, DDoS protection, and TLS termination; Grafana Labs for log aggregation, monitoring, and alerting; Sentry for application error tracking and performance monitoring; and Hex for data visualization and analytics. The current list is maintained on the Trust Center and pairs with the Linq Data Processing Addendum.
What happens to customer data when a customer leaves?
Linq purges or removes customer data containing confidential information from the application environment when customers leave the service, in accordance with best practices. This sits alongside formal retention and disposal procedures and a data classification policy — all three are monitored controls published on the Trust Center.
Does Linq have a disaster recovery plan?
Yes. Linq has documented Business Continuity and Disaster Recovery plans that outline communication procedures for maintaining information security continuity, and it tests them at least annually. Linq also maintains cybersecurity insurance and performs periodic production data backups to a location separate from the production system.
How do I reach the Linq security team?
Email [email protected]. You can also ask a question directly through the Linq Trust Center at security-report.linqapp.com.
Questions from your security team?
Reach our security team directly, or ask a question through the Trust Center.
